macOS 12 Monterey on Unsupported Macs Thread

[borp99]

The latebloom.kext thread and this forum are both currently attracting many posts about BT problems. My upgraded 'internal' Wifi/BT4.2 card (BCM943602CDP) also stopped working with Monterey. Member kronokernel says we need to force the OS to use the EHCI controller for BT, rather than the increasingly-unstable OHCI controller, by using a separate USB hub or PCIe riser card [as an intermediary].

As many, like me, have added a miniPCIe adapter card to use these newer Wifi/BT cards, we have already soldered USB data +/- wires to the orig internal BT plug and run them across to the adapter card. If, instead, these data wires were otherwise soldered to a USB plug lead - for running outside the case to an external hub (USB 2...or 3?), are the 5v and Gnd wires on the plug lead required to be connected as well (...to where I have no idea), in order to get this EHCI controller to 'see' the 'internal' upgraded BT card as being plugged into the hub, or are just the 2 data wires sufficient?

 

[44quattrosport]

My BCM94360CD seems to be fine ...luckily

 

[Ausdauersportler]

Talking about BT and Monterey B4:

Finally got an external USB BT 5.0 dongle working with these additional tools injected via OpenCore using OCLP 0.2.2. To get it working it as to be plugged in on boot. Basically it the same solution @chris1111 proposed in this post just with a different hardware.

At the same time I am using a RealTek based USB WiFi dongle using this solution (kernel extensions injected via OC, too).

​

 

[MontereyGuy]

MBP 10,1 Late 2012. OTA Upgrade from beta 3 to beta 4 with OCLP 0.2.3 freezes install on second boot. I have tried restarting holding option to select the EFI partition, but get the same result. Any hints ? OTA upgrade from b2 to b3 went very smoothly

EDIT: OK On my third attempt, even though the installer progress still bar never moved past half way, just under the apple logo, it booted into beta 4. I downloaded OCLP 0.2.4, patched and rebooted again. All seems good. Wi-Fi is working fine, I don’t know about Bluetooth.

As the Installer never finished, do I have some half installed OS ?

 

[Ausdauersportler]

MBP 10,1 Late 2012. OTA Upgrade from beta 3 to beta 4 with OCLP 0.2.3 freezes install on second boot. I have tried restarting holding option to select the EFI partition, but get the same result. Any hints ? OTA upgrade from b2 to b3 went very smoothly

Why not trying to enable verbose or using the debug version of OC to get a slightly better description than it does not work.

Honestly I am always using the verbose (CMD+V on boot or adding -v to the OC boot-args) when installing early Beta versions on unsupported hardware.

 

[steverae]

Same problem here with iMac 13,2 late 2012 and b4: no bluetooth.
Only basic functions of keyboard and trackpad are working.

Yep - confirmed - keyboard and trackpad only basic functions on 13,2 iMac. However, Wifi is working still

Hopefully this can be fixed somehow by the patcher at some point ... no other issues to report - updated via software update, went smoothly as before with beta 3.

Can also confirm the NVidea/Safari issue is now fixed.

 

[amaze1499]

MBP 10,1 Late 2012. OTA Upgrade from beta 3 to beta 4 with OCLP 0.2.3 freezes install on second boot. I have tried restarting holding option to select the EFI partition, but get the same result. Any hints ? OTA upgrade from b2 to b3 went very smoothly

EDIT: OK On my third attempt, even though the installer progress still bar never moved past half way, just under the apple logo, it booted into beta 4. I downloaded OCLP 0.2.4, patched and rebooted again. All seems good. Wi-Fi is working fine, I don’t know about Bluetooth.

As the Installer never finished, do I have some half installed OS ?

Check the build using "About this Mac":It should show 21A5294g if Beta 4 was installed properly.

I saw the same happening with Beta 3 and Beta 4 on my MBP 9,2. I held power button. Selected the correct EFI and the installation went through eventually.

 

[vince22]

Is bt working? I have the same machine. Mine isn't working.

Bluetooth, airdrop,handoff and apple watch unlock all working for me.

 

[legsp]

Talking about BT and Monterey B4:

Finally got an external USB BT 5.0 dongle working with these additional tools injected via OpenCore using OCLP 0.2.2. To get it working it as to be plugged in on boot. Basically it the same solution @chris1111 proposed in this post just with a different hardware.

At the same time I am using a RealTek based USB WiFi dongle using this solution (kernel extensions injected via OC, too).

View attachment 1812003​

Hey @Ausdauersportler, thanks for the tip! I want try doing the same thing but I've looked everywhere for a guide on how to inject kexts using OCLP but couldn't find one. Could you help me out or point me in the right direction? Thanks!

 

[khronokernel]

The latebloom.kext thread and this forum are both currently attracting many posts about BT problems. My upgraded 'internal' Wifi/BT4.2 card (BCM943602CDP) also stopped working with Monterey. Member kronokernel says we need to force the OS to use the EHCI controller for BT, rather than the increasingly-unstable OHCI controller, by using a separate USB hub or PCIe riser card [as an intermediary].

As many, like me, have added a miniPCIe adapter card to use these newer Wifi/BT cards, we have already soldered USB data +/- wires to the orig internal BT plug and run them across to the adapter card. If, instead, these data wires were otherwise soldered to a USB plug lead - for running outside the case to an external hub (USB 2...or 3?), are the 5v and Gnd wires on the plug lead required to be connected as well (...to where I have no idea), in order to get this EHCI controller to 'see' the 'internal' upgraded BT card as being plugged into the hub, or are just the 2 data wires sufficient?

The issue in this thread and the latebloom are a bit different. Specifically the latebloom thread more refers to MacPro3,1-5,1 which use the OHCI controller for USB 1.1 devices

• Remember that Sandy Bridge and newer Macs don't have OHCI, only EHCI and XHCI (if USB3.0)

This thread is discussing issues with the Bluetooth module attached to the BCM94331 likely amounting to oversight on Apple's end of some sort (as the Bluetooth stack does recognize the BCM20702 module even in beta 4, however the rest of the OS has issues communicating)

• From my quick research, looks to be a power state issue. The OS tries to send power state commands but fails. Ofc the device is already on and active in most cases, so I believe macOS is misreporting the device's state and so infinitely tries to "power on" again

For a bit of clarity, the BCM94360 and BCM94331 both use the BCM20702 chipset so it's unlikely Apple intentionally wants to cause issues (remember that the naively supported iMac17,1 is also using a BCM20702 chipset)

For the 2012 machines, I would recommend downgrading to beta 3 until we can confirm these issues have been fixed. For MacPro31-5,1, I doubt there will be a fix without some heavy amount of reversing to understand the USB stack better and better support OHCI in macOS. Recommend forcing the EHCI controller if possible

 

[MontereyGuy]

Check the build using "About this Mac":It should show 21A5294g if Beta 4 was installed properly.

I saw the same happening with Beta 3 and Beta 4 on my MBP 9,2. I held power button. Selected the correct EFI and the installation went through eventually.

Yes the beta 4 build version is showing in the system about box.

Beta 3 was very stable for me together with XCode 13 b3. Monterey Beta 2 had various background processes and deamons core dumping regularly, which I didn’t get at all in beta 3.

In a couple of hours use of this beta 4 plus XCode 13 b4, I’ve had a few core dumps of XCode build chain processes, but no system processes so far.

 

[Tockman]

naively supported iMac17,1

?

 

[amaze1499]

Out of curiosity: Can someone try to explain the how a Bluetooth card can stop working after upgrading from Beta 3 to beta 4?
I’ve seen so many posts where an upgrade on external solution is suggested, however on my MacBook Pro 9,2 Bluetooth is working fine when booted from USB installer.

 

[khronokernel]

Out of curiosity: Can someone try to explain the how a Bluetooth card can stop working after upgrading from Beta 3 to beta 4?
I’ve seen so many posts where an upgrade on external solution is suggested, however on my MacBook Pro 9,2 Bluetooth is working fine when booted from USB installer.

Generally RecoveryOS (the OS used in both Installers and Recovery) are usually a version or 2 behind the latest beta. So it's common that beta 4's recoveryOS is actually identical to beta 3 and so the Bluetooth bug would not appear

 

[KennyW]

Successful update directly from High Sierra to Monterey beta3 in my iMac 2010 RX480 with USB3 mod (see my signature) via OCLP 0.2.4 nightly build (27/7) on SD card and beta3 macOS installer on USB drive.

Also able to complete incremental update from beta3 to beta4 from Software Update afterward.



Sound, Wifi, Ethernet, Apple TV+, even my added USB3 ports, all work in the latest betas (3 & 4), but BlueTooth (v4.2 - BCM943602CDP) NOT.

Another observation is that it takes close to 10 to 15 minutes to boot into Monterey. Otherwise, the GUI is as responsive as that of Big Sur.

 

[davemp88]

So question; I think I’ve figured out the best solution to my problem of the software I need to use to fix the Apple Watches is ironically, PC only. I keep a spare ****** PC with me, but then I remembered about Boot-Camp Partitioning. I’m currently running macOS Monterey Beta 3 on my unsupported 2012 MBP A1278. From what I’ve read, everything says it’s fine to do, I guess I was just wondering what peoples thoughts were about installing the boot camp partition while also on an unsupported beta macOS?

 

[borp99]

The issue in this thread and the latebloom are a bit different. Specifically the latebloom thread more refers to MacPro3,1-5,1 which use the OHCI controller for USB 1.1 devices

• Remember that Sandy Bridge and newer Macs don't have OHCI, only EHCI and XHCI (if USB3.0)

This thread is discussing issues with the Bluetooth module attached to the BCM94331 likely amounting to oversight on Apple's end of some sort (as the Bluetooth stack does recognize the BCM20702 module even in beta 4, however the rest of the OS has issues communicating)

• From my quick research, looks to be a power state issue. The OS tries to send power state commands but fails. Ofc the device is already on and active in most cases, so I believe macOS is misreporting the device's state and so infinitely tries to "power on" again

For a bit of clarity, the BCM94360 and BCM94331 both use the BCM20702 chipset so it's unlikely Apple intentionally wants to cause issues (remember that the naively supported iMac17,1 is also using a BCM20702 chipset)

For the 2012 machines, I would recommend downgrading to beta 3 until we can confirm these issues have been fixed. For MacPro31-5,1, I doubt there will be a fix without some heavy amount of reversing to understand the USB stack better and better support OHCI in macOS. Recommend forcing the EHCI controller if possible

Sorry if my previous post misinterpreted your great clarifications. I should have read up about USB protocols more deeply before commenting. From what you say, I deduce that the original 3,1-5,1 BT card USB feed was always only USB 1,1 (via the small plug on the backplane) and, as such, got handled by the OHCI controller. As Monterey has dropped USB 1,1 support (or OHCI support has become flaky), that's why many of us are finding our upgrade cards on a mPCIe adapter (fed by the original BT data wires) are now useless.

So, also deduced, the only way we can use these cards (in 3,1-5,1's) beyond Big Sur is to route them via a USB 2 hub. Will one of the native (non-hub) USB 2 ports also work? As asked previously: if we do feed the adapter card with data feeds from a USB 2 hub (or port?) via a doctored USB cable, does anyone know if just the 2 data wires will be recognised [ie. without the 5v and Gnd wires being routed/connected through the hub(/port?) as well]?

 

[steverae]

What is strange though to me is that on my iMac 13,2 (which I believe is a late 2012 model) the keyboard and trackpad both still work for basic functions which are Bluetooth are they not ?

let’s see what comes with beta 5, I had no issues with beta 3 so may return to that for the time being if I find the lack of track pad functions to become annoying

 

[khronokernel]

Will one of the native (non-hub) USB 2 ports also work?

So with MacPro3,1-5,1, each physical USB port has 2 controllers hooked up: OHCI (USB 1.1) and EHCI (USB 2.0)
The idea is that lower bandwidth devices won't take resources up from the EHCI controller and so behind the scenes the OHCI will take over that device. When you add an explicit USB 2.0 Hub (or 3.0), the EHCI controller must take over that port. OHCI and EHCI cannot both be active on the same port.

This leads to the second point of trying to route the USB data lines to a USB 2.0 port. Unfortunately this would partially work (you don't need the 5v and Ground present) but the OHCI controller will still take over the port. This is the reason we need a USB 2.0 device/hub in-between the chain to force the hardware into using the EHCI controller

Whether you can force the EHCI solely via software is unknown, I have some experiments planned this week to see if it can be done via macOS (similar to how FakePCIID_XHCIMux.kext functions, only in reverse)

 

[khronokernel]

still work for basic functions which are Bluetooth are they not ?

As the Bluetooth module in 2012 machines is HID Proxy compliant, they're able to be active from UEFI and have easy hand off once macOS loads. This explains why keyboard and mice work however connecting new devices does not

As I noted earlier, the bluetooth stack is still functional and fully detects and recognizes the module and bluetooth devices already connected. Just somewhere in the chain the OS **** itself and refuses to function besides with already connected devices

 

[amaze1499]

deleted.

 

[amaze1499]

deleted.

 

[steverae]

As the Bluetooth module in 2012 machines is HID Proxy compliant, they're able to be active from UEFI and have easy hand off once macOS loads. This explains why keyboard and mice work however connecting new devices does not

As I noted earlier, the bluetooth stack is still functional and fully detects and recognizes the module and bluetooth devices already connected. Just somewhere in the chain the OS **** itself and refuses to function besides with already connected devices

Thank you for this update - I have taken the advice from above and reverted back to Beta3 until this issue can be resolved as not having full control over the track pad was a real nuisance.

Thank you everyone for the continued support and assistance provided on this site - lets see what comes with beta 5 - hopefully this BT issue especially on the 2012 machines can be resolved.

 

[Ausdauersportler]

Another Bluetooth story with Monterey Beta 4:

Lost BCM943602CDP BT part with this update on my iMac11,3 - was just curious to confirm the result @KennyW posted some hours ago. Will wait until Beta 5 shows up with further experiments.

Could enable a simple USB BT dongle for mouse and keyboard, but no HandOff, and no Continuity.

 

[davemp88]

Bluetooth, airdrop,handoff and apple watch unlock all working for me.

View attachment 1812059

What is apple watch unlock? Might I inquire?