Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 OpenCore Big Sur: Random loss of Bluetooth functionality
- Thread starter TECK
- Start date
- Sort by reaction score
All the dumps I'm getting are extremely dirty and fragmented, with multiple occurrences of several NVRAM variables. Up to now, no one with a clean NVRAM is having Bluetooth problems.
@TECK did you ever had a recurrence?
@TECK did you ever had a recurrence?
Last edited:
No, these are binwalk reports against my own signatures and tools.
Binwalk is a framework for binary inspection, you have to instruct it to do exactly what you want or it will do nothing. You have to describe exactly what you want to search/inspect using signature files and scripts.
Last edited:
Used romtool to create bootrom file from my 4,1->5,1 and can open it in a hex editor, but understand none of it. Would you help before it bombs?
I would be glad if you could have a look at the BootROM’s from my two 5,1’s. I have no problem now, but I would like to know your recommendation after looking at them. The dual proc I got when my workplace got rid of their Mac Pro’s the video guys had used. Might be some history of NVIDIA web-drivers…
Hi all,
Have the same problem on a cMP 5.1(4.1) Single socket. The bluetoth card was upgraded as the same user @TECK.
I can use the Wifi but the bluetooth it's totally missing even on the hardware specs.
I have catalina on my main NVME installed and This is on a SATA hdd as a TEST before migrate production. Open core 0.64 and change the config.plist name as the Big Sur Guide says.
Hope that this issue can be solved soon
Have the same problem on a cMP 5.1(4.1) Single socket. The bluetoth card was upgraded as the same user @TECK.
I can use the Wifi but the bluetooth it's totally missing even on the hardware specs.
I have catalina on my main NVME installed and This is on a SATA hdd as a TEST before migrate production. Open core 0.64 and change the config.plist name as the Big Sur Guide says.
Hope that this issue can be solved soon
If you look closely at the system info you will realize yours is a USB device too (internal). It just does not have the supported product id for that patch:
Wi-Fi is connected via PCIe, but Bluetooth is connected via USB, thats why you always have Wi-Fi.Hi all,
Have the same problem on a cMP 5.1(4.1) Single socket. The bluetoth card was upgraded as the same user @TECK.
I can use the Wifi but the bluetooth it's totally missing even on the hardware specs.
I have catalina on my main NVME installed and This is on a SATA hdd as a TEST before migrate production. Open core 0.64 and change the config.plist name as the Big Sur Guide says.
View attachment 1696245
Hope that this issue can be solved soon
Big Sur and MP5,1 USB2.0 controllers are a problem right now, but people that never had Big Sur still have the same BT random loss and from all BootROM dumps sent up to now it seems to confirm that the multiple bluetoothActiveControllerInfo occurrences inside the main VSS store of the NVRAM are the real offender here.
Last edited:
What I meant was that the patch directory does not contain your product it. So it does not apply for you. Did you check the power connector/cables to the Bluetooth?
Yes, everything is okay. I have Bluetooth functional, only when I switch from Mojave disk to Big Sur, I lose Bluetooth and gain it back after a reboot.
I would also like to have more info on diagnosing my 2010 MacPro 5,1 BootRom. When you have time can you PM me the instructions and have a look at it for me. Thank You for all your work in this forum it has helped me many times.
also had a buddy with Big Sur Bluetooth Trouble dumped his rom (deleted unrelated and private data):
Code:
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
24972 0x618C CRC32 polynomial table, little endian
35787 0x8BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
243908 0x3B8C4 "EFI Release 144.0.0.0.0 (MP51.88Z.F000.B00.1904121248)"
524288 0x80000 UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
549260 0x8618C CRC32 polynomial table, little endian
560075 0x88BCB mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
768196 0xBB8C4 "EFI Release 144.0.0.0.0 (MP51.88Z.F000.B00.1904121248)"
1048576 0x100000 UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1064960 0x104000 UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1065216 0x104100 Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1077504 0x107100 Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1085696 0x109100 Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1114112 0x110000 UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1130496 0x114000 UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1130752 0x114100 Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1143040 0x117100 Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1151232 0x119100 Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1179648 0x120000 UEFI PI Firmware Volume, volume size: 196608, header size: 1, revision: 0, Variable Storage, GUID: FFF12B8D-7696-4C8B-85A9-2747075B4F50
1179719 0x120047 "Begin of 1st VSS Stream"
1192807 0x123367 "BluetoothActiveControllerInfo"
1199663 0x124E2F "BluetoothActiveControllerInfo"
1200201 0x125049 "BluetoothActiveControllerInfo"
1206988 0x126ACC "BluetoothActiveControllerInfo"
1207526 0x126CE6 "BluetoothActiveControllerInfo"
1213883 0x1285BB "BluetoothActiveControllerInfo"
1214421 0x1287D5 "BluetoothActiveControllerInfo"
1227601 0x12BB51 "BluetoothActiveControllerInfo"
1228291 0x12BE03 "BluetoothActiveControllerInfo"
1245255 0x130047 "Begin of 2nd VSS Stream"
1258343 0x133367 "BluetoothActiveControllerInfo"
1343500 0x14800C "override Base 21"
1343511 0x148017 "Begin of Base blob"
1345179 0x14869B "Base 21"
1345189 0x1486A5 "ssn", 11 bytes, xxx
1345207 0x1486B7 "HG3 - Mac Pro (Mid 2010)"
1345215 0x1486BF "son", 8 bytes, 625-9417
1345536 0x148800 0x28800! "Begin of Gaid Stream"
1345548 0x14880C "Gaid tsth 08"
1376256 0x150000 UEFI PI Firmware Volume, volume size: 2686976, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1416828 0x159E7C "EFI Release 144.0.0.0.0 (MP51.88Z.F000.B00.1904121248)"
4063232 0x3E0000 UEFI PI Firmware Volume, volume size: 65536, header size: 1, revision: 0, GUID: E3B980A9-5FE3-48E5-929B-2798385A9027
4128768 0x3F0000 UEFI PI Firmware Volume, volume size: 65536, header size: 0, revision: 0, Apple Boot Volume, GUID: 04ADEEAD-61FF-4D31-BAB6-64F8BF901F5A
4128876 0x3F006C "Bootblock from 141.0.0.0.0 - rebuilt Firmware"
4194032 0x3FFEF0 "LBSN_BD sector" Build Date YYMMDDYYMMDD : xxx LBSN: xxx
I also seem to be running into the same issue with Big Sur & bluetooth with a BCM943602CS from a 2015 MBP in my 5,1. I lack the experience to really troubleshoot the ROM but PM'ing you a ROM dump @tsialex in case it helps you look into things. Booting back into Mojave w/o OC after resetting everything seemed to do the trick (for now).
Hi Alex, I also would like to have more info on diagnosing my 2010 MacPro 5,1 BootRom. When you have time available, appreciated if you can PM me the instructions and have a look at it for me. Thanks for your contribution and hard work on this forum. I learn a lot from guys like you
@tsialex I have a dump that may be of interest ? I had before these issues were known a few EFI installs of Win 8 on my cMP 5.1 I think.
I have only just updated to 144.0.0.0 and made a dump immediately after flashing unfortunately I may of chosen the wrong flash chip. I have just made another dump after installing OC and WIN 10 with the correct chip.
I had some strange booting issues while installing OC and I wonder if I am suffering. If these are of interest I can send them over. I also have updated the WiFi adapter with a BCM94360CD just before the upgrade.
Are these corruption issues persistent after upgrading the BootROM ?
Thanks
I have only just updated to 144.0.0.0 and made a dump immediately after flashing unfortunately I may of chosen the wrong flash chip. I have just made another dump after installing OC and WIN 10 with the correct chip.
I had some strange booting issues while installing OC and I wonder if I am suffering. If these are of interest I can send them over. I also have updated the WiFi adapter with a BCM94360CD just before the upgrade.
Are these corruption issues persistent after upgrading the BootROM ?
Thanks
It's not upgrade related unless you have an early-2009.
I've explained in detail the problems on the OC thread, please read my explanation there - it's not upgrade related, but directly related to the long term usage of the NVRAM, it's "filesystem" is not robust enough for 12 years usage.
Last edited:
Hey, it appears that I am having the same Bluetooth issues on my 5,1 machine (4,1 upgraded to 5,1). I put in an AirPort card from another newer Mac and it worked fine until I upgraded to Big Sur 11.1 (currently on 11.2). Seemed to work ok under 11.0.1 and all previous versions of macOS. I would be interested to see if my BootROM is also corrupted. I am currently running OC 0.6.6 following the guide from the OpenCore on Mac Pro thread. My BootROM is the latest 144.0.0.0.0, however the new OC guide spoofs it to 9999.0.0.0.0 to prevent accidental firmware flashing which is why it comes up as such in the hardware overview. All other OS functions seem to be ok. Regardless of how many times I reboot into Big Sur the issue persists.
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 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)