Jump to content

macOS Sonoma Wireless Issues Discussion.


SavageAUS
807 posts in this topic

Recommended Posts

Good morning. I have noticed that, if I change the SMBIOS model when I have OCLP root patch applied (and Sonoma wifi working), I lose wifi, as if root patch was not applied.

I have to revert root patch, reboot, apply root patch with the SMBIOS in use and, after reboot, wifi works again.
I don't know if it is the expected behavior since OCLP, when applying root patch, in one of the first lines of information it says "Applying root patch for <SMBIOS model>".
Has anyone else observed this behavior?

  • Like 2
Link to comment
Share on other sites

30 minutes ago, miliuco said:

Good morning. I have noticed that, if I change the SMBIOS model when I have OCLP root patch applied (and Sonoma wifi working), I lose wifi, as if root patch was not applied.

I have to revert root patch, reboot, apply root patch with the SMBIOS in use and, after reboot, wifi works again.
I don't know if it is the expected behavior since OCLP, when applying root patch, in one of the first lines of information it says "Applying root patch for <SMBIOS model>".
Has anyone else observed this behavior?

 

This is normal behaviour. The root patch is linked to the Model. Similarly, after a macOS update, I was obliged to apply the root patch again.

  • Like 4
Link to comment
Share on other sites

1 hour ago, Matgen84 said:

 

This is normal behaviour. The root patch is linked to the Model. Similarly, after a macOS update, I was obliged to apply the root patch again.

 

Thanks!!! I assumed that it was indeed so.

 

Edited by miliuco
  • Like 2
Link to comment
Share on other sites

On 8/10/2023 at 2:01 PM, mnfesq said:

 

Thanks for the clarification.  This all started because I have apps that require SIP to be disabled.  Most of those apps will work with FF0F0000 but one app in particular requires SIP to be completely disabled, which is 6F020000.  This latter csr-active-config will not work with OCLP wireless patches, either to apply them or even post install.  However, FF0F0000 will work post install.  That means that I have to change my csr-active-config to 03080000 before applying the OCLP wireless patches after any update. Then I can revert to FF0F0000 to make my apps, such as XtraFinder, work.

 

@deeveedee Good job, my friend.  This seems to be working just fine.  I will report back after the update to beta 6 to confirm that OCLP will detect my wifi device for reapplication of the OCLP wireless patches.

 

@deeveedee I'm back to report that beta 6 installed perfectly and that OCLP detected my wireless device and its need to be repatched.  What surprised me is that I did not need to change my csr-active-config from FF0F0000 for this to happen or to run OCLP.   I couldn't be more pleased.  One small issue remains, however.  I cannot use the most current version of BlueToolFixup.kext.  In Ventura, it will not detect any bluetooth devices.  In Sonoma it does so this issue will likely be resolved by my eventual migration of my main partition from Ventura to Sonoma.  In Ventura, I am still using the version that was created as a fork from the main branch.  Those changes were supposedly incorporated into version 2.6.8 but that version never worked for me either.  Only the forked kext worked.  Thanks again for your help.

  • Like 1
Link to comment
Share on other sites

On 8/23/2023 at 6:46 PM, mnfesq said:

 

@deeveedee "What surprised me is that I did not need to change my csr-active-config from FF0F0000 for this to happen or to run OCLP."

 

Well that's because you fully disabled SIP and enabled features usually only required by developers for debugging. You really shouldn't use this value because it's a securty risk. 03080000 is enough to apply root patches.

  • Like 1
Link to comment
Share on other sites

On 8/23/2023 at 11:20 AM, miliuco said:

Good morning. I have noticed that, if I change the SMBIOS model when I have OCLP root patch applied (and Sonoma wifi working), I lose wifi, as if root patch was not applied.

I have to revert root patch, reboot, apply root patch with the SMBIOS in use and, after reboot, wifi works again.
I don't know if it is the expected behavior since OCLP, when applying root patch, in one of the first lines of information it says "Applying root patch for <SMBIOS model>".
Has anyone else observed this behavior?

 

1. Which SMBIOS are you using to in your config?

2. Which Mac Model are you using in OCLP for applying root patches?

3. Have you added the Booter and Kernel Patches from OCLPs config or RestrictEvents.kext with boot-arg sbvmm so that you can boot your system with the native SMBIOS for your CPU family?

Edited by cankiulascmnfye
Link to comment
Share on other sites

8 hours ago, cankiulascmnfye said:

 

Well that's because you fully disabled SIP and enabled features usually only required by developers for debugging. You really shouldn't use this value because it's a securty risk. 03080000 is enough to apply root patches.

 

My csr-active-config is set at FF0F0000 in order for me to run an app called Xtrafinder.  It has nothing to do with OCLP.  I have another app that requires SIP to be fully disabled, which is 6F020000, but with that config, OCLP does not work at all - either for patching or to run post-patch.  

Link to comment
Share on other sites

17 hours ago, cankiulascmnfye said:

 

1. Which SMBIOS are you using to in your config?

2. Which Mac Model are you using in OCLP for applying root patches?

3. Have you added the Booter and Kernel Patches from OCLPs config or RestrictEvents.kext with boot-arg sbvmm so that you can boot your system with the native SMBIOS for your CPU family?

Good night. 

I think @Matgen84 answer "This is normal behaviour. The root patch is linked to the Model" solved my question.
We can see that OCLP links to the SMBIOS model by root patching the hackintosh without using any other OCLP feature nor building the EFI nor adding patches to config.plist, just the Post-Install Root Patch button, since one of the log's first lines is "Applying root patch for <SMBIOS model>". <SMBIOS model> does match the current model of SMBIOS that macOS boots with. I don't change this or anything else when running OCLP.
What I had seen is this: I have iMacPro1,1 SMBIOS with root patch applied well and Fenvi wifi works, I change SMBIOS to iMac19,1 in config.plist and when I reboot, root patch seems to be not applied and Fenvi wifi doesn't work . And vice versa, applying root patch with iMac19,1 and changing to iMacPro1,1.

So it seems normal to lose root patch when changing SMBIOS with root patch applied to different SMBIOS.

 

 

17 hours ago, ameenjuz said:

is there BCM94360NG wifi card working  Nss2 5G speed 867 using OCLP Patch on MacOS Sonoma?

I don't know but it's very easy to check it by yourself, apply OLCP root patch and, if it doesn't work, revert it to the previous situation, I don't think it will do any harm to macOS.

 

Edited by miliuco
  • Like 2
Link to comment
Share on other sites

Today I tried to patch the BCM94360NG in my EliteDesk. Unfortunately without success. It did something as the exclamation mark is not present anymore but still no option to turn the Wi-Fi on/off and no available networks. Also disabling the SecureBootModel, SIP and AMFI made Sonoma boot very slow, more than 50 sec. On the other hand I've never used Apple services as I am an Android user and might be a good idea to switch to Intel since it works great in my Desktop and Laptop.

  • Like 2
Link to comment
Share on other sites

4 hours ago, CloverLeaf said:

Today I tried to patch the BCM94360NG in my EliteDesk. Unfortunately without success. It did something as the exclamation mark is not present anymore but still no option to turn the Wi-Fi on/off and no available networks. Also disabling the SecureBootModel, SIP and AMFI made Sonoma boot very slow, more than 50 sec. On the other hand I've never used Apple services as I am an Android user and might be a good idea to switch to Intel since it works great in my Desktop and Laptop.

I think that you missed configuration I have BCM94360NG wifi card working fine after all required kexts and patch on macOS Sonoma 14 beta 7

everything is working fine with continuity feature

follow the Guide 

https://github.com/5T33Z0/OC-Little-Translated/blob/main/14_OCLP_Wintel/WIiFi_Sonoma.md#2-config-and-efi-adjustments

 

  • Like 2
  • Thanks 2
Link to comment
Share on other sites

Gigabyte Z77X-d3h i5 2310 Sandy Brigue kepler GT640 TP-LINK WDN-4800

 

Tests carried out without success, the active wifi icon appears but the kext loaded does not appear in both cases using the kext AMFIPass.kext or the boot amfi=0x80

 

"Legacy" cards

Atheros: AR93xx

Wifi AR93xx TP-LINK WDN-4800

PCI168c,30

AirPortAtheros40 IDs

0x0030, #AR93xx

 

IO80211ElCap.kext and its plugin AirPortAtheros40.kext (enabled for Atheros cards)

Adjust MinKernel settings as below: 16.0.0 16.0.0 18.0.0

 

Change SecureBootModel Disabled to rule out early kernel panics caused by security conflicts.

 

Change csr-active-config 03080000

Optional: Add amfi=0x80 if boot-args cannot root patch both AMFIPass.kext methods

Optional: Add -brcmfxbeta if boot-args cannot connect to Wi-Fi after applying root patches.

Optional: Add -amfipassbeta to boot-args (if AMFIPass.kext is not loaded in the latest Sonoma beta).

 

Enter (kextstat | grep -v com.apple) into the Terminal to check if all the required kexts you added are loaded. If not, add -amfipassbeta (if AMFIPass.kext is not present) and -brcmfxbeta (if wireless works but cannot connect to accesspotsints)

 

Tests carried out with the same result MacPro7.1 and Imac12.2 it does not work KEPLER YES 

2023-09-02 17.50.59.jpg

Edited by kaoskinkae
  • Like 1
Link to comment
Share on other sites

On 8/26/2023 at 7:07 PM, mnfesq said:

 

My csr-active-config is set at FF0F0000 in order for me to run an app called Xtrafinder.  It has nothing to do with OCLP.  I have another app that requires SIP to be fully disabled, which is 6F020000, but with that config, OCLP does not work at all - either for patching or to run post-patch.  

Yes, you missed bit 12. Adding it we will have

6F0A0000

but your FF0F0000 is wrong because of bit 4. Unset it and you will have

EF0F0000

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

On 8/26/2023 at 6:07 PM, mnfesq said:

 

My csr-active-config is set at FF0F0000 in order for me to run an app called Xtrafinder.  It has nothing to do with OCLP.  I have another app that requires SIP to be fully disabled, which is 6F020000, but with that config, OCLP does not work at all - either for patching or to run post-patch.  

 

Xtrafinder is a relict of times when Finder didn't support Tabs. It was buggy back then and I think it still is. Only difference is: in the beginning it was freeware :D

 

And why are you hijacking this thread for your app issue which is unreleated to fixing Wifi in Sonoma???

Edited by cankiulascmnfye
Link to comment
Share on other sites

On 7/25/2023 at 5:45 AM, Aguys said:

Join the party, DW1820A...
 

Screenshot 2023-07-24 at 21.33.39.png

Does your Bluetooth detected as apple one? not THIRD_PARTY_DONGLE, if so how do you fix that? Because I've used BlueTool kext, BrcmPatchRam3 and the FirmwareData but system information still show it as THIRD_PARTY_DONGLE, kindly waiting for your help, thanks

Link to comment
Share on other sites

Hello everyone, hope you all doing well. Wanna ask about bluetooth related things. How do I change it to be detected as Apple device, it's DW1820A - BCM4350 ? Because of this airdrop wont work, has anyone solve this issue? Thanks beforeimage.thumb.png.a66d43b273f4f3cd9465d81a6ac845b1.png 

Edited by vanmoo
Link to comment
Share on other sites

23 hours ago, cankiulascmnfye said:

 

Xtrafinder is a relict of times when Finder didn't support Tabs. It was buggy back then and I think it still is. Only difference is: in the beginning it was freeware :D

 

And why are you hijacking this thread for your app issue which is unreleated to fixing Wifi in Sonoma???

 

You are free to have your own opinion about XtraFinder.  I still like the up arrow and use it all the time.  But the real point of my posts are to address the issue of whether it is necessary to have the csr-active-config 03080000 in order for OCLP to patch wifi in Sonoma and to pop-up after updates are installed to begin the re-patching process.  Is that hijacking?  I'm sure I'm not the only person on this forum that would like more options for their csr-active-config.

  • Like 3
Link to comment
Share on other sites

4 hours ago, ham4ever said:

does BCM94331 even work on Sonoma, tried many combination of kexts and OCLP, but cant get it to work...

 

This chipset is included in the OCLP Sonoma beta branch, I think it must work applying the patch in the right way.

I recommend to read carefully khronokernel's post following instructions to the letter.

https://github.com/dortania/OpenCore-Legacy-Patcher/pull/1077#issuecomment-1646934494

  • Like 3
Link to comment
Share on other sites

3 hours ago, miliuco said:

 

This chipset is included in the OCLP Sonoma beta branch, I think it must work applying the patch in the right way.

I recommend to read carefully khronokernel's post following instructions to the letter.

https://github.com/dortania/OpenCore-Legacy-Patcher/pull/1077#issuecomment-1646934494

 

Thanks, i followed the guide and the wifi is working and is it connected, but no bluetooth. 

Link to comment
Share on other sites

33 minutes ago, ham4ever said:

Thanks, i followed the guide and the wifi is working and is it connected, but no bluetooth. 

Did you have any Bluetooth related kext before now?

(Stupid question) Do you have the USB cable from the card plugged into a USB port in the mobo?

Edited by miliuco
  • Like 1
Link to comment
Share on other sites

On 7/24/2023 at 5:39 AM, miliuco said:

Good morning.

I know that it is not the ideal situation that many of us want to have the system as vanilla as possible, but what the OCLP team has achieved is amazing.

My wifi is Fenvi T919.


I have followed TO THE LETTER the instructions that have been published here (Hackintosh notes):
https://github.com/dortania/OpenCore-Legacy-Patcher/pull/1077#issuecomment-1646934494
And it has worked well. I have wifi and Airdrop back in Sonoma.
Note that khronokernel's instructions must be followed exactly.


Don't forget to enable (Enabled=True) 3 extensions to be added and the extension to be blocked, they are disabled by default.
If I don't block com.apple.iokit.IOSkywalkFamily the system won't boot with KP.


I'm attaching my config.plist in case it helps anyone having trouble, check out these specific details:

  • csr-active-config | data | 03080000
  • boot-args | string | amphi=0x80
  • com.apple.iokit.IOSkywalkFamily blocked
  • IOSkywalk.kext, IO80211FamilyLegacy.kext and AirPortBrcmNIC.kext added in this order (Kexts folder and config.plist).

For the future I hope the integration of the amfi-disabled branch with the sonoma-development branch to be able to work without the need to disable AMFI. I guess incremental updates are lost with this setup. But the OCLP approach works, at least for me.

 

Note: as it's a preliminary fix, maybe it doesn't work on some systems.

 

  Reveal hidden contents

wifi-hackintool.thumb.png.281ea5aca6499b46188a79cfebb17efe.png

 

wifi-profiler1.thumb.png.582332fd243e3567b13d98db42dfb419.png

 

wifi-profiler2.thumb.png.bb17d6b94038fbb8b8f5081d5b20485c.png

 

wifi-settings1.thumb.png.3af39f3ae75406ee884db14d41bd9f6b.png

 

wifi-settings2.thumb.png.fa23ed71c174c8d551b6053287821e57.png

 

wifi-menubar.thumb.png.f985139469af7f472543fa7acf61bc33.png

 

Important: com.apple.iokit.IOSkywalkFamily blocking must have Enabled=True and Strategy=Exclude. Otherwise you get kernel panic at boot.

 

  Reveal hidden contents

com.apple.iokit.IOSkywalkFamily.thumb.png.796405e8abe0f85de75e5ab011d0287c.png

 

Thank you, OCLP team!!!

 

config.plist 27.63 kB · 69 downloads

Thanks to everyone who posted on this thread.  I followed this method exactly and have complete Sonoma functionality on a Gigabyte ga-z170x-ud5-th with a Broadcom 4360WiFi / Bluetooth adapter.

  • Like 1
Link to comment
Share on other sites

19 hours ago, miliuco said:

Did you have any Bluetooth related kext before now?

(Stupid question) Do you have the USB cable from the card plugged into a USB port in the mobo?

 

i used to have BlueToolFixup.kext, BrcmFirmwareData.kext en BrcmPatchRAM3.kext . i used them now also but still no bluetooth.

 

yes there is some cable from the card to the mobo. 

 

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...