Jump to content

Atheros Wifi Big Sur 11.2.3 Need Help


8 posts in this topic

Recommended Posts

Greetings.

 

I've tried all the ways to enable Atheros wifi kext on Big Sur. the kexts and even installing to /L/E.

No wifi.

mount -uw but doesn't work on the last step to create a snap shot.

 

I found a video tutorial that listed the steps to mount -uw / yet doesn't work using Clover 5133 with Big Sur 11.2.3

 

Anybody have a fix a for sure one that works?

 

Thanks

 

 

 

Enabling Write Access.txt

Edited by makk
SOLVED
Posted (edited)

For those needing in Clover to have wifi here's your fix.

Just install two > Kexts> Other two kexts only. No need to do fancy foot work and break the seal.

 

Just replace bootx64.efi and cloverx64.efi for Clover to work >see attached photos

 

Using Clover 5127 from PG7 Thanks Man! Great find!


Doesn't work with 5133 Clover borked.

 

Wifi now a go with Big Surgeon. lol

Screen Shot 2021-04-27 at 5.14.57 AM.png

Screen Shot 2021-04-27 at 5.08.03 AM.png

Screen Shot 2021-04-27 at 5.18.45 AM.png

Screen Shot 2021-04-27 at 5.06.20 AM.png

r5127 BOOT + Drivers + Kext Ateros ar9285 BigSur.zip

Edited by makk

UPDATE

 

Was able to load Atheros with Clover 5133 

Must have been NVRAM issue.

 

What I did:

 

Replaced BootX86.efi from 5133 to 5127

Replaced CloverX86.efi from 5133 to 5127

 

Then after successful boots and having Wifi Atheros again,

 

Replaced back with 5133 for both of the above

 

working now in Clover 5133 Atheros wifi

 

Using two kexts in EFI>kexts>Other 

 

Two kexts only no need to mess with System.

 

Kext set to "Inject" and not 'Detect'

 

Works great! Thank you guys! It is good to know you all!

 

 

17 hours ago, makk said:

Greetings.

 

I've tried all the ways to enable Atheros wifi kext on Big Sur. the kexts and even installing to /L/E.

No wifi.

mount -uw but doesn't work on the last step to create a snap shot.

 

I found a video tutorial that listed the steps to mount -uw / yet doesn't work using Clover 5133 with Big Sur 11.2.3

 

Anybody have a fix a for sure one that works?

 

Thanks

 

 

 

Enabling Write Access.txt 1.01 kB · 0 downloads

I don't think this is a good idea since it breaks the seal and you get no updates.

 

Refer to "Injecting" kexts in config.plist

 

SIP Disabled

 

 

  • 3 weeks later...
On 4/27/2021 at 7:38 PM, makk said:

UPDATE

 

Was able to load Atheros with Clover 5133 

Must have been NVRAM issue.

 

What I did:

 

Replaced BootX86.efi from 5133 to 5127

Replaced CloverX86.efi from 5133 to 5127

 

Then after successful boots and having Wifi Atheros again,

 

Replaced back with 5133 for both of the above

 

working now in Clover 5133 Atheros wifi

 

Using two kexts in EFI>kexts>Other 

 

Two kexts only no need to mess with System.

 

Kext set to "Inject" and not 'Detect'

 

Works great! Thank you guys! It is good to know you all!

 

 

I don't think this is a good idea since it breaks the seal and you get no updates.

 

Refer to "Injecting" kexts in config.plist

 

SIP Disabled

 

 

You can re-enable the install/upgrade snapshot as booting snapshot before updating.

On 5/18/2021 at 3:14 PM, HenryV said:

You can re-enable the install/upgrade snapshot as booting snapshot before updating.

How's that done?

 

Thank you

15 hours ago, makk said:

How's that done?

 

Thank you

Create a new APFS snapshot:

/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -s "you_pick_name" -v /Volumes/your_Big_Sur_volume_name

 

Second, make it bootable:

/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -r "you_pick_name" -v /Volumes/your_Big_Sur_volume_name

 

With these commands I was able to boot into recovery terminal and create a new snapshot and make it bootable.  In order to verify that Big Sur was booting from the new snapshot, the system files were altered by changing the login graphic.  Big Sur booted with the new login graphic confirming the new snapshot was bootable .  Once booted I checked with terminal from the desktop to verify that there was a new snapshot with the name I had selected when it was created.  I did not, however, take the time to reboot into recovery console and delete the new shapshot and undo the system file changes, make a new bootable snapshot, and then boot Big Sur to see if the original state was preserved.

On 5/21/2021 at 3:23 PM, HenryV said:

Create a new APFS snapshot:

/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -s "you_pick_name" -v /Volumes/your_Big_Sur_volume_name

 

Second, make it bootable:

/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -r "you_pick_name" -v /Volumes/your_Big_Sur_volume_name

 

With these commands I was able to boot into recovery terminal and create a new snapshot and make it bootable.  In order to verify that Big Sur was booting from the new snapshot, the system files were altered by changing the login graphic.  Big Sur booted with the new login graphic confirming the new snapshot was bootable .  Once booted I checked with terminal from the desktop to verify that there was a new snapshot with the name I had selected when it was created.  I did not, however, take the time to reboot into recovery console and delete the new shapshot and undo the system file changes, make a new bootable snapshot, and then boot Big Sur to see if the original state was preserved.

Thank you Henry

 

I'll see if it works on my end.

 

I use Clover now.  Was getting CMOS resets with OC.

×
×
  • Create New...