MP 1,1-5,1 OpenCore Big Sur: Random loss of Bluetooth functionality

[TECK]

Hello All,

I had the same issue with Bluetooth that solved after a new restart.


What I've done to solve this issue was a new disk with catalina + upgrade to Big Sur (all in the main NVMe Drive on the SLOT 3).
After that I restore my data, and now only have on drive on NVME with Big Sur (OC latest version)

I did a clean install of Big Sur and the issue was present when switching to Mojave then back to Big Sur.

Even with the latest OC 0.6.6, I’m still forced to reboot twice in order to get back Bluetooth functionality in Big Sur 11.2 release. Any thoughts on this @h9826790 @startergo @cdf?

 

[startergo]

I did a clean install of Big Sur and the issue was present when switching to Mojave then back to Big Sur.

Even with the latest OC 0.6.6, I’m still forced to reboot twice in order to get back Bluetooth functionality in Big Sur 11.2 release. Any thoughts on this @h9826790 @startergo @cdf?

Similar behavior on my machine too

 

[h9826790]

Similar behavior on my machine too

I am still wondering if a full USB port mapping, or the BrcmBluetoothInjector can help.

Even though we shouldn't need them on the cMP, but if that actually make some differences. That little bit difference may able to avoid this bug.

 

[cdf]

I do not experience this on my machine. However, I have a small internal USB hub connected to the Bluetooth USB header that provides a connection to both the GC-TITAN RIDGE and the wireless card. We know that hubs correct the USB 1 issue, so maybe this explains why I haven't experienced any issues with Bluetooth...

 

[startergo]

I am still wondering if a full USB port mapping

I experimented a lot with USB mapping. Does not seem to have any impact on this issue, or the USB hub issue.

 

[MacForumsUser]

For what it's worth, I had originally created my OC config.plist manually. Apparently I did it correctly, because I could boot Big Sur, and everything was good. The OpenCanopy graphical boot menu worked, and I would occasionally boot Catalina, then Big Sur. No issues. Bluetooth was working properly in Big Sur.

Then, one day, my cMP5,1 would only boot Windows 10. So I thought to first rebuild my config.plist, and this time, I thought I would use the automated OpenCore Installer tool from Axivo. Everything was working fine with Catalina, but my Mac would still only boot straight to Windows 10. I could get into Big Sur if I removed all other drives. Bluetooth was working properly at this time in both OS's.

Seeing as the issue [booting straight to Windows 10] wasn't fixed, I took to searching and found I should send my BootROM to the man, the myth, the legend, @tsialex! He cleaned it up - thanks again my friend! - and upon first reboot, I was taken into Mojave, as expected. I rebooted into Recovery and blessed the OC EFI on my NVMe housing Big Sur. The very next reboot, the machine booted Big Sur and no bluetooth. I rebooted again, and bluetooth magically returned.

 

[Macschrauber]

Interesting.

Maybe thats the reason why I dont have seen usb problems with Big Sur - as I also cleaned the rom of the machines before installing Big Sur.

 

[MacForumsUser]

Also, FWIW, I just rebooted into Windows 10 (by removing my NVMe with Big Sur on it), and when I did, no bluetooth. I had to reinstall the Broadcom Bluetooth Enabler from Brigadier, and it worked.

 

[TECK]

I had to reinstall the Broadcom Bluetooth Enabler from Brigadier

Yes, you need that. Thank you for pointing it out, see #33 at the bottom of the post for additional Apple Magic hardware driver install.

 

[djtransa]

@tsialex I'm having all sorts of trouble with not only bluetooth, but random internal USB failures. This results in Big Sur not booting at all, getting the prohibited logo etc. PRAM reset usually sorts it temporarily. My machine is a 4,1 flashed to 5,1 with OC 0.6.6 using Martin's package. If you're interested in my ROM, please go ahead an DM & I'll provide you whatever you need.

 

[tsialex]

@tsialex I'm having all sorts of trouble with not only bluetooth, but random internal USB failures. This results in Big Sur not booting at all, getting the prohibited logo etc. PRAM reset usually sorts it temporarily. My machine is a 4,1 flashed to 5,1 with OC 0.6.6 using Martin's package. If you're interested in my ROM, please go ahead an DM & I'll provide you whatever you need.

USB problems are not exactly related with the Bluetooth problems that people are having on the thread.

Big Sur has very poor support for legacy USB controllers, both problems exist and you can solve the BT issue with BootROM clean-up/reconstruction while for USB you have to upgrade to OC 0.6.7 and 11.2.2, where things are a little better with legacy USB support.

 

[tsialex]

Post moved to the BootROM thread. Please ask BootROM related Bluetooth questions there.

 

[MacForumsUser]

9 NVRAM bluetoothActiveControllerInfo variables, while should be just one, AFAIK it's the worst to date,

Darn. Dethroned!

 

[TECK]

@tsialex Is it possible to keep this on topic? More than half of this thread is about ROM details, which has nothing to do with the OP issue. There is a thread for BootROM issues.

 

[Macschrauber]

This bluetoothActiveControllerInfo has in some circumstance to do with bluetooth trouble, too.

Thats my experience. I do firmware reconstructions on the local board and it helped some in the same boat.

 

[TECK]

@Macschrauber I understand but how is detailing the errors found in a BootROM helps fixing the Bluetooth issue? IMO, people who visit this thread would like to read a fix for current issue.

 

[Macschrauber]

@Macschrauber I understand but how is detailing the errors found in a BootROM helps fixing the Bluetooth issue? IMO, people who visit this thread would like to read a fix for current issue.

The fix could be a deep nvram reset to reduce the amount of the bluetooth vars.

but if the bootrom is not in decent condition those errors could appear again.

this must not be _the_ fix but sometimes it helps.

if dumping the rom and counting the bluetoothactivecontrollerinfo vars give more than 1 per stream it probably leads to solving the problem.

wont argue, but nvram and bluetooth problems are in some cases in relationship.

 

[TECK]

Honestly, I opened this thread to get a solution for lost Bluetooth in Big Sur, everything works perfect in Catalina. The clean BootROM venue was proven it does not fix the issue for several people. I would like to get your help on fixing the Bluetooth bug, not analyze BootROMs.

 

[tsialex]

Honestly, I opened this thread to get a solution for lost Bluetooth in Big Sur, everything works perfect in Catalina. The clean BootROM venue was proven it does not fix the issue for several people. I would like to get your help on fixing the Bluetooth bug, not analyze BootROMs.

I've asked moderation to remove several of my posts and I respect that you want to focus on the legacy USB support side of Big Sur, but your conclusions are wrong.

There are two very different things at play here that we can right now really solve one, read my post #25 where I explain what is going on.

BTW, @cdf post about the BT hub is not really related to the problem, since he have a reconstructed BootROM.

 

[TECK]

@tsialex I understand your explanation but it is proven that having a freshly reconstructed BootROM does not fix the double reboot required to gain back Bluetooth functionality in Big Sur. Also, my card is a Bluetooth 4.2 pulled from an iMac, I don't know if should be considered legacy. I just flashed again today your reconstructed BootROM with OC disabled.

After a NVRAM reset, I was able to access fine the Mojave installation without issues and I blessed in recovery the Big Sur disk OC partition + SMC reset, gaining access to multiple disks boot picker. The interesting thing is Bluetooth works from chime to recovery screen as well boot picker, I'm holding the ESC key to get the menu and I change between disks with my Apple Bluetooth Magic keyboard without issues.

Once I select in boot picker the Big Sur disk and boot the OS, Bluetooth is broken. I have to force a shutdown with the power button and after the second reboot, the issue is solved and I have functional Bluetooth. This occurs only in Big Sur.

Another interesting note is that I was not required to re-login into iCloud in Big Sur after I flashed the reconstructed ROM, all my information was stored.

 

[TECK]

The very next reboot, the machine booted Big Sur and no bluetooth. I rebooted again, and bluetooth magically returned.

That is the issue we are trying to solve.

 

[tsialex]

@tsialex I understand your explanation but it is proven that having a freshly reconstructed BootROM does not fix the double reboot required to gain back Bluetooth functionality in Big Sur. Also, my card is a Bluetooth 4.2 pulled from an iMac, I don't know if should be considered legacy. I just flashed again today your reconstructed BootROM with OC disabled.

After a NVRAM reset, I was able to access fine the Mojave installation without issues and I blessed in recovery the Big Sur disk OC partition + SMC reset, gaining access to multiple disks boot picker. The interesting thing is Bluetooth works from chime to boot picker, I'm holding the ESC key to get the menu and I change between disks with my Apple Bluetooth Magic keyboard without issues.

Once I select in boot picker the Big Sur disk and boot the OS, Bluetooth is broken. I have to force a shutdown with the power button and after the second reboot, the issue is solved and I have functional Bluetooth. This occurs only in Big Sur.

Another interesting note is that I was not required to re-login into iCloud in Big Sur, all my information was stored.

Like I’ve explained, it’s not just one cause and I understand that you want to focus with the Big Sur only side, but people are having this since at least Mojave and someone that is suffering with BT loss with previous releases and find this thread is not going to restrict to just your side of it.

Anyway, this topic is better suited elsewhere.

 

[TECK]

@tsialex I don't understand all this back and forward. Can we focus on the actual issue confirmed by several people, where Bluetooth magically starts working after a second OC Big Sur reboot? I think this is unique to Big Sur, I never had Bluetooth issues prior this OS.

 

[Stex]

Darn. Dethroned!

Yes indeed, @RicheeThree -- I would like to add that, despite the very serious and important challenges articulated in this thread, my cMP 4,1 (flashed to 5,1 of course!) has proven itself to be exceptional!!! I am almost (...almost) tempted not to flash it at all and let those "bluetoothActiveControllerInfo" pile up like sand dunes in a vast desert! 😄😔 Thanks @tsialex and @TECK (and all the other cMP experts here), -- we have learned and continue to learn a great deal from you!!! OH and we continue to have an amazing desktop computer which in all honesty I hope to continue using up until... 2029!!! 🙏

 

[Macschrauber]

Big Sur 11.2.3

I tried today a Bluetooth 4.0 Stick (CSR 8510 A10) registering as USB 1.1 in a customer MP5,1

I could not get it to work in a "normal" USB2 port, no front, no back, even after re-plugging.

but it worked
-thru a passive USB Hub connected to the front USB,
-thru the Apple USB Keyboard Hub (the ideal position is for mice and trackpads)
-thru the hub of the Cinema HD Display
-thru a Innateck KT4004 USB 3 PCI card

deep NVRam reset didnt changed things.

With Mojave the Bluetooth Stick worked in all USB ports, plugged and unplugged a few times.

Have the same dongle in my main machine for years. (but dont use Big Sur with it).