USB-Map(-Tahoe)?.kext issues

[mcdmaster]

Hello OCLP-Mod Experts,

Thank you all for your great work in every moment on this.
I am using it with a self-built copy of sources from GitHub here upon MBP9,1 a.k.a. mid-2012.
Now I wanted to make a brief porposal so that its USB functions can be kept smart.

1. Multiple USB-Map*.kext's are problematic: we can use OS-named property variables (kUSB*) for sleaker Info*.plist configs across OS versions;
2. The Key item cannot contain comma in its own: Something like <key>MacBookPro9,1-EHCI</key> has been figured out as non-working; it incurs entire disability of keyboard input (e.g. logon User/Pass) and all the mouse actions/moves.

I am going to give it a fix as a Pull Request. I wolud like it to be reviewed and adopted to the future Release if it finds okay on your end.

[laobamac]

Hello, thank you for your contribution to this project.

I don't have outdated Mac hardware myself, so I can't test the relevant logic of OpenCore generation. All content is synchronized from the original warehouse of OCLP.

As far as I know, USB-Map.kext has set MacKernel to 24.99.99, and USB-Map-Tahoe.kext has set MinKernel to 25.0.0, which should only be loaded on macOS 26. What do you mean by "error loading"? I hope you can provide me with more information.

[5T33Z0]

I think there is an issue with the patcher itself introduced in the version 3.x. If you enable the option to install the USB fixes in the advanced settings, macOS Tahoe no longer boots. I've tested it on 2 different systems (Hackintoshes) and the OS just hangs or crashes early after applying patches and rebooting. Safe boot doesn't work here so there's pretty much no way to uninstall OCLP Mod once that happens. And the fact that all text is now Chinese complicates things even more.

I have to clean-install Tahoe 26.3 beta again and patch it with OCLP v 2.6.9 for AppleHDA and USB Options to verify.

[laobamac]

In fact, since the first addition of the USB old version patch, the files related to this patch have never changed.

[5T33Z0]

Okay, then it must be something else.

[laobamac]

Are you choosing to install the old version USB environment extension because you need to use a USB wireless network card?

[5T33Z0]

No, I need it to get the BT portion of my internal Intel AC-9560 WiFi/BT card to work. Otherwise BT cannot be enabled.

[laobamac]

Oh my friend, this is an extremely wrong approach. This patch is definitely not the correct solution to solve Bluetooth problems, even if it happens to achieve this effect due to some special reasons.

You may not have customized your USB port correctly. Please try using the latest development version 1.0.7 OC and check XHCPortLimit. After customizing the USB correctly, try again.

Don't forget to add the two Bluetooth related parameters in the NVRAM and reset the NVRAM

[5T33Z0]

Forget what I said about Bluetooth. Bluetooth works fine. I confused it with something else. But I see what's the problem now: the new version of OCLP Mod (3.x.x) wants to apply root patches for Broadcom Cards:

But the systems I recently patched use Intel Cards. So, where can I disable this patch?

[laobamac]

Are you saying that installing a patch for a Broadcom network card on a host with an Intel network card installed?

Just start installing directly. The patch files for both are the same and will not affect the functionality. Perhaps it's just a detection issue.

[5T33Z0]

Yes, your latest version of OCLP mod applies root patches to systems with Intel cards installed. And if these patches are applied, it breaks the installation (tested on 2 differnt systems with differnet Intel Cards).

I just now installed a new clean version of Tahoe 26.3 beta on one of the machines and patched it with OCLP Mod 2.6.9 to get Audio working again and it works fine.

So there there is probably a detection issue. So maybe you could add a switch to enable/disable the bcm patch or refine the detection of broadcom cards. Maybe by vendor-id which ich clearly differnet between both.

[y4shg]

Yes, your latest version of OCLP mod applies root patches to systems with Intel cards installed. And if these patches are applied, it breaks the installation (tested on 2 differnt systems with differnet Intel Cards).

I just now installed a new clean version of Tahoe 26.3 beta on one of the machines and patched it with OCLP Mod 2.6.9 to get Audio working again and it works fine.

So there there is probably a detection issue. So maybe you could add a switch to enable/disable the bcm patch or refine the detection of broadcom cards. Maybe by vendor-id which ich clearly differnet between both.

Same situation here, It recognizes as a BCM and breaks my installation.

[y4shg]

I've found that this video has helped me quite a lot. Click to Watch Video on Youtube

[5T33Z0]

I tried another System (Lenovo T530) which actually uses a Broadcom Wifi/BT Card. But OCLP breaks macOS Tahoe too after applying root patches. As an experienced Hackintosh user, it's easy for me to recover from this by booting from a different volume. But for the average Mac user this might be a different story…