makk Posted April 27, 2021 Share Posted April 27, 2021 (edited) 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 April 28, 2021 by makk SOLVED Link to comment Share on other sites More sharing options...
makk Posted April 27, 2021 Author Share Posted April 27, 2021 (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 r5127 BOOT + Drivers + Kext Ateros ar9285 BigSur.zip Edited April 27, 2021 by makk Link to comment Share on other sites More sharing options...
makk Posted April 27, 2021 Author Share Posted April 27, 2021 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 Link to comment Share on other sites More sharing options...
PPCnostalgic Posted May 16, 2021 Share Posted May 16, 2021 I did it too on my old X79 + Xeon E5, now my Atheros PCIe WiFi card works with Big Sur 11.3.1 Thank you very much for sharing! Link to comment Share on other sites More sharing options...
HenryV Posted May 18, 2021 Share Posted May 18, 2021 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. Link to comment Share on other sites More sharing options...
makk Posted May 21, 2021 Author Share Posted May 21, 2021 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 Link to comment Share on other sites More sharing options...
HenryV Posted May 21, 2021 Share Posted May 21, 2021 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. Link to comment Share on other sites More sharing options...
makk Posted May 24, 2021 Author Share Posted May 24, 2021 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. Link to comment Share on other sites More sharing options...
Recommended Posts