macOS Sonoma Wireless Issues Discussion.

[Max.1974]

Are you run OCLP and click on Starting Root  after adjust your config.plist? 

 

Post-Install Root Patch and click blue Botton 

 

 

[Max.1974]

 

Im used this configs for Sonoma only, Ventura is another EFI. 

 

 

 

 

[Aguys]

1 hour ago, SavageAUS said:

I am still unable to apply the root patches.

I'm afraid OCLP only detect BCM94350 not BCM94352, that's why no wireless patch available? Since BCM94352 not natively supported by IO80211FamilyLegacy.kext, yes? I hope I'm wrong.

 

Maybe you can test to spoof your card as BCM94350, and let's see if wireless patch become available.

Edited July 25, 2023 by Aguys

[Max.1974]

config.plist.zip

 

Generic SMBIOS  iMacPro 1,1

 

 

Kexts.zip

[SavageAUS]

I'm afraid OCLP only detect BCM94350 not BCM94352, that's why no wireless patch available? Since BCM94352 not natively supported by IO80211FamilyLegacy.kext, yes? I hope I'm wrong.
 
Maybe you can test to spoof your card as BCM94350, and let's see if wireless patch become available.

I can give it a go for the sake of others. I have ordered the same card that’s in my desktop and other laptop (Metabox in signature) it’s just this dell with a different chip giving me grief for now but when the new chip arrives I’m sure it will work as the other 2 did.
Perhaps the OCLP devs will add this card into the patch. I’m even happy to send them mine if they need it once I get my new one
This is the one I bought.


Sent from my iPhone using Tapatalk

[SavageAUS]

I just tested Ventura on my Metabox laptop and it kernel panics. Do we need to add min kernel to OCLP Kexts so they are not injected into Ventura?

I just YOLO’d it and set min kernel to 23.0.0 and Ventura is working fine again as is SoHaveWiFi.


Sent from my iPhone using Tapatalk

[deeveedee]

39 minutes ago, Max.1974 said:

 

Im used this configs for Sonoma only, Ventura is another EFI. 

 

 

 

 

You have revpatch=sbvmm as a boot-arg.  Does it work that way?

 

I've only specified revpatch this way

 

[cankiulascmnfye]

@Aguys Country Code is set via DeviceProperties in my case. It's only relevant for the used frequency bands, I think. I've used XX and DE before and they all worked with Ventura. Maybe I'll give it another shot on the weekend.

Just now, deeveedee said:

 

You have revpatch=sbvmm as a boot-arg.  Does it work that way?

 

I've only specified revpatch this way

 

 

Both methods are supported.

[cankiulascmnfye]

13 minutes ago, SavageAUS said:

I just tested Ventura on my Metabox laptop and it kernel panics. Do we need to add min kernel to OCLP Kexts so they are not injected into Ventura?

I just YOLO’d it and set min kernel to 23.0.0 and Ventura is working fine again as is SoHaveWiFi.


Sent from my iPhone using Tapatalk

 

Of course. MinKernel 23.0.0

For kext that should not be injected into Sonoma, set MaxKernel to 22.9.9 or if you want to be pedantic: 22.99.99

28 minutes ago, SavageAUS said:

I can give it a go for the sake of others. I have ordered the same card that’s in my desktop and other laptop (Metabox in signature) it’s just this dell with a different chip giving me grief for now but when the new chip arrives I’m sure it will work as the other 2 did.
Perhaps the OCLP devs will add this card into the patch. I’m even happy to send them mine if they need it once I get my new one
This is the one I bought.


Sent from my iPhone using Tapatalk

 

I hope these are not actual sizes (for both)

[mboy]

My bootloader freezes which I believe is due to com.apple.iokit.IOSkywalkFamily blocking

 

The end of the verbose boot log

 

06:684 00:015 AAPL: #[EB.LD.LF|IN] 0 1 <"<null string>"> <"1">
06:715 00:030 AAPL: #[EB.B.SBS|SZ] 723512
06:738 00:023 AAPL: #[EB|B:SHA] <e10c0de554e93abf44f4fc138dd5e12fb30863c8>
06:756 00:018 AAPL: #[EB.WL.PWLFNV|!] Err(0xE) <- RT.GV wake-failure 7C436110-AB2A-4BBB-A880-FE41995C9F82
06:771 00:015 AAPL: #[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFNV
06:786 00:014 AAPL: #[EB.WL.PWLFRTC|NONE]
06:801 00:015 AAPL: #[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFRTC
06:820 00:018 AAPL: #[EB.LD.LKC|D] <"boot\System\Library\KernelCollections\BootKernelExtensions.kc.development">
06:842 00:021 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"boot\\System\\Library\\KernelCollections\\BootKernelExtensions.kc.development">
06:860 00:018 AAPL: #[EB.LD.LKC|R.2] <"boot\System\Library\KernelCollections\BootKernelExtensions.kc">

 

Here are my config.plist settings:

[Max.1974]

1 hour ago, deeveedee said:

 

You have revpatch=sbvmm as a boot-arg.  Does it work that way?

 

I've only specified revpatch this way

 

 

Sorry late @deeveedee , yeap, works like that, but your way looks better !!! 

 

Thanks ALL!!! 

 

1 hour ago, cankiulascmnfye said:

@Aguys Country Code is set via DeviceProperties in my case. It's only relevant for the used frequency bands, I think. I've used XX and DE before and they all worked with Ventura. Maybe I'll give it another shot on the weekend.

 

Both methods are supported.

 

 

14 minutes ago, mboy said:

My bootloader freezes which I believe is due to com.apple.iokit.IOSkywalkFamily blocking

 

The end of the verbose boot log

 

06:684 00:015 AAPL: #[EB.LD.LF|IN] 0 1 <"<null string>"> <"1">
06:715 00:030 AAPL: #[EB.B.SBS|SZ] 723512
06:738 00:023 AAPL: #[EB|B:SHA] <e10c0de554e93abf44f4fc138dd5e12fb30863c8>
06:756 00:018 AAPL: #[EB.WL.PWLFNV|!] Err(0xE) <- RT.GV wake-failure 7C436110-AB2A-4BBB-A880-FE41995C9F82
06:771 00:015 AAPL: #[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFNV
06:786 00:014 AAPL: #[EB.WL.PWLFRTC|NONE]
06:801 00:015 AAPL: #[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFRTC
06:820 00:018 AAPL: #[EB.LD.LKC|D] <"boot\System\Library\KernelCollections\BootKernelExtensions.kc.development">
06:842 00:021 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"boot\\System\\Library\\KernelCollections\\BootKernelExtensions.kc.development">
06:860 00:018 AAPL: #[EB.LD.LKC|R.2] <"boot\System\Library\KernelCollections\BootKernelExtensions.kc">

 

Here are my config.plist settings:

 

My works fine, but crashes others apps, im get back intel and LocalSend Drop, and use Ventura for while. Sonoma hav to much issues. 

[miliuco]

@mboy

Enabled=True

 

 

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

@Cyberdevs You were right, this is causing quite a few errors.

 

Edited July 25, 2023 by miliuco

[miliuco]

@BALDY_MAN

Can you upload your Sonoma EFI (only config.plist file) if you can't get wifi networks yet?

 

 

@Max.1974

You have SecureBootModel=x86legacy, try Disabled.

 

Edited July 25, 2023 by miliuco

[deeveedee]

I was inspecting the OCLP Wi-Fi patching and see what appears to be a dependency on SMBIOS Model.

 

OCLP is designed for Real Macs, so OCLP patching adheres to the configs of real SMBIOS MacModels.  Could some of the Wi-Fi issues being reported here be because some hacks are using Wi-Fi chipsets that are not the same as their real Mac counterparts?

 

For those who want to review this, here is the commit.

Edited July 25, 2023 by deeveedee

[Cyberdevs]

@deeveedee

I think that's a possibility, as you stated OCLP was initially designed for real Macs not hackintoshes, it being working on hacks is a bonus but I think the devs took some of the variations (if not all) about the WiFi cards used in hack as well.

I'm installing Sonoma on my 2013 MacBookPro to see if the AirportBrcmFixup.kext is really necessary or not but the EFI folder generated by OCLP adds it automatically so there must be a reason for that.

[Max.1974]

1 hour ago, miliuco said:

@Max.1974

Você tem SecureBootModel=x86legacy, tente Disabled.

 

 

Hello mi Hermano, thanks in advance, I try it, but not boot, without line boot, stuck on Apple logo. Im uninstall Sonoma patched with OCLP, because have been too much crashes, and im prefer use dual boot with my good Ventura for my work, and enjoy Sonoma without Airdrop, but better stability for now. Thanks!!! 

 

Notes: this name x86legacy was renamed automatic by OCLP 

 

     

Edited July 25, 2023 by Max.1974

[mboy]

1 hour ago, miliuco said:

@mboy

Enabled=True

 

 

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

@Cyberdevs You were right, this is causing quite a few errors.

 

Sorry; bootloader freezes with Enabled=YES.  I get a kernel panic with Enabled=NO

[mnfesq]

I have an app that I use daily that require SIP to be fully disabled.  Can someone who has wifi working please test this csr-active-config to see if it works with the OLCP patch?

 

csr-active-config=6F020000

 

Thanks.

[Cyberdevs]

For those who have issues with fenvi T919 BT/Wireless I attached the kexts required and the order they need to be in the config.plist

The AirPortBrcmNIC.kext is inside the IO80211FamilyLegacy.kext and it also needs to be injected.

 

Blocking com.apple.iokit.IOSkywalkFamily is a MUST and make sure it is set to Exclude:

 

<key>Block</key>
        <array>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>Comment</key>
                <string>Allow IOSkywalk Downgrade</string>
                <key>Enabled</key>
                <true/>
                <key>Identifier</key>
                <string>com.apple.iokit.IOSkywalkFamily</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>23.0.0</string>
                <key>Strategy</key>
                <string>Exclude</string>
            </dict>
        </array>

 

You don't need any other kexts for the fenvi T919 so remove them to avoid any issues.

 

Kext order

Spoiler

 

Hackintool screenshot

Spoiler

 

Blocking the com.apple.iokit.IOSkywalkFamily

Spoiler

 

 

Another addition:

If you use the nightly GUI app it might not work because it's few commits behind so I suggest to build from the last commit. The GUI didn't apply Haswell Graphics patches to my 2013 MacBook Pro but the manual build did.

 

1783627072_WirelessKextsforSonoma.zip

[deeveedee]

22 minutes ago, Cyberdevs said:

For those who have issues with fenvi T919 BT/Wireless I attached the kexts required and the order they need to be in the config.plist

The AirPortBrcmNIC.kext is inside the IO80211FamilyLegacy.kext and it also needs to be injected.

 

Blocking com.apple.iokit.IOSkywalkFamily is a MUST and make sure it is set to Exclude:

 

<key>Block</key>
        <array>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>Comment</key>
                <string>Allow IOSkywalk Downgrade</string>
                <key>Enabled</key>
                <false/>
                <key>Identifier</key>
                <string>com.apple.iokit.IOSkywalkFamily</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>23.0.0</string>
                <key>Strategy</key>
                <string>Exclude</string>
            </dict>
        </array>

 

Thanks!  Should Enabled be true?

[Cyberdevs]

32 minutes ago, deeveedee said:

Thanks!  Should Enabled be true?

Yes it should, I just copied the block section from the reference page in OpenCore Legacy Patcher and it's set to false there, might be a mistake.

Thanks for the correction.

[deeveedee]

9 minutes ago, Cyberdevs said:

Yes it should, I just copied the block section from the reference page in OpenCore Legacy Patcher and it's set to false there, might be a mistake.

Thanks for the correction.

I don't think it's a mistake on the OCLP reference page.  That config.plist looks like a template for all MacModels.  OCLP must use that config.plist template to create the customized config.plist for each specific Mac Model.

[Cyberdevs]

5 minutes ago, deeveedee said:

I don't think it's a mistake on the OCLP reference page.  That config.plist looks like a template for all MacModels.  OCLP must use that config.plist template to create the customized config.plist for each specific Mac Model.

That makes sense

[surenmunoo]

3 hours ago, deeveedee said:

I was inspecting the OCLP Wi-Fi patching and see what appears to be a dependency on SMBIOS Model.

 

OCLP is designed for Real Macs, so OCLP patching adheres to the configs of real SMBIOS MacModels.  Could some of the Wi-Fi issues being reported here be because some hacks are using Wi-Fi chipsets that are not the same as their real Mac counterparts?

 

For those who want to review this, here is the commit.

I use BCM4360 which is listed for real Macs but cannot boot with changes. I am using the mod OC and created a new EFI with no Fork/Mod and I managed to boot Sonoma with the changes but when I try to enable the patch it says no patches available

[deeveedee]

3 hours ago, Cyberdevs said:

Another addition:

If you use the nightly GUI app it might not work because it's few commits behind so I suggest to build from the last commit. The GUI didn't apply Haswell Graphics patches to my 2013 MacBook Pro but the manual build did.

 

It doesn't make sense to me that anyone should need to manually build the patcher.  Are you saying that you downloaded OCLP from here (link labeled Nightly.link: OpenCore-Patcher.app (Sonoma Development) ) and that did not work for you?  

 

EDIT: I do see that there were Haswell commits yesterday.  Others (not Haswell) who need the patcher today should be ok with the OCLP nightly build.

Edited July 25, 2023 by deeveedee