MP 1,1-5,1 Bluetooth does not work after installing Ventura with OCLP.

[zozomester]

Why does the original Bluetooth module not work after installing Ventura?
I installed the Roth Patch, but it doesn't work. Wifi works flawlessly, but Bluetooth does not. It still worked at Monterey.....
Does anyone know the solution?
Thanks!

 

[jedijiver]

Same issue here.

I upgraded my MacPro5,1 from Monterey to Ventura yesterday. I used OCLP 0.6.1. The install was smooth and easy. I applied the post patches. Everything works great except I have no Bluetooth. I found this on the OCLP site. I missed it before I did the upgrade:

========================================

Currently Unsupported/Broken Hardware in Ventura . . .

USB 1.1 (OHCI/UHCI) Support
For Penryn systems and pre-2013 Mac Pros, USB 1.1 support was outright removed in macOS Ventura. While USB 1.1 may seem unimportant, it handles many important devices on your system. These include:

Keyboard and Trackpad for laptops
IR Receivers
Bluetooth

With OpenCore Legacy Patcher v0.6.0, basic support has been implemented via Root Volume patching. However due to this, users will need to use a USB hub for installation and post-OS updates when patches are cleaned.

========================================

The above quote can be found in context here: https://dortania.github.io/OpenCore-Legacy-Patcher/VENTURA-DROP.html#newly-dropped-hardware

I'm wondering if the reason I have no Bluetooth is because I used one of the front USB ports for the Flash drive install. If I had connected a USB 2.0 or higher hub and inserted the flash installer there, would that have made aa difference? Perhaps the presence of a USB 2.0 or higher hub would have made the installer install different USB drivers. It's unclear as stated on the OCLP site.

Bluetooth was fine on the same machine running Monterey. BTW my Bluetooth card has the BCM_4350C2 chipset. I believe it is the original card, not the Wifi 802.11ac a/b/g/n/ac & Bluetooth 4.0 upgrade card Apple sold at one time. Perhaps that's the issue - again, unclear based on the OCLP site.

My Mac specs: Mac Pro (Mid 2012) • 2 x 3.46 GHz 6-Core Intel Xeon • 128 GB RAM • 12+3+4 TB HDDs • 2TB + 1TB PCIe SSDs • 2 x SuperDrives • Radeon RX 580 8 GB • 1 x 30" + 2 x 20" Cinema Displays

 

[zozomester]

Same issue here.

I upgraded my MacPro5,1 from Monterey to Ventura yesterday. I used OCLP 0.6.1. The install was smooth and easy. I applied the post patches. Everything works great except I have no Bluetooth. I found this on the OCLP site. I missed it before I did the upgrade:

========================================

Currently Unsupported/Broken Hardware in Ventura . . .

USB 1.1 (OHCI/UHCI) Support
For Penryn systems and pre-2013 Mac Pros, USB 1.1 support was outright removed in macOS Ventura. While USB 1.1 may seem unimportant, it handles many important devices on your system. These include:

Keyboard and Trackpad for laptops
IR Receivers
Bluetooth

With OpenCore Legacy Patcher v0.6.0, basic support has been implemented via Root Volume patching. However due to this, users will need to use a USB hub for installation and post-OS updates when patches are cleaned.

========================================

The above quote can be found in context here: https://dortania.github.io/OpenCore-Legacy-Patcher/VENTURA-DROP.html#newly-dropped-hardware

I'm wondering if the reason I have no Bluetooth is because I used one of the front USB ports for the Flash drive install. If I had connected a USB 2.0 or higher hub and inserted the flash installer there, would that have made aa difference? Perhaps the presence of a USB 2.0 or higher hub would have made the installer install different USB drivers. It's unclear as stated on the OCLP site.

Bluetooth was fine on the same machine running Monterey. BTW my Bluetooth card has the BCM_4350C2 chipset. I believe it is the original card, not the Wifi 802.11ac a/b/g/n/ac & Bluetooth 4.0 upgrade card Apple sold at one time. Perhaps that's the issue - again, unclear based on the OCLP site.

My Mac specs: Mac Pro (Mid 2012) • 2 x 3.46 GHz 6-Core Intel Xeon • 128 GB RAM • 12+3+4 TB HDDs • 2TB + 1TB PCIe SSDs • 2 x SuperDrives • Radeon RX 580 8 GB • 1 x 30" + 2 x 20" Cinema Displays

If the USB hub is the problem, then it might be my problem. I installed it via USB HUB..... Can anyone confirm this?

 

[jedijiver]

If the USB hub is the problem, then it might be my problem. I installed it via USB HUB..... Can anyone confirm this?

I decided to start over and do a clean install. I used a USB 3 hub. It did NOT make a difference with Bluetooth - I still have none. System Report shows my Bluetooth card as being present, but both State and Discovereble show as off. The Bluetooth menu bar icon has a line through it as if there is no Bluetooth hardware. The toggle switch in the Bluetooth menu bar menu can be turned on, but the line through the icon does not go away. The Bluetooth toggle in System Stetting will not turn on. So the second try with a hub was pretty much a waste of time. However, before Ventura when my MacPro was on OCLP Monterey any time I connected a USB drive it would take a couple of minutes to access and mount the drive. This clean install of OCLP Ventura cured that problem. Now USB drives mount quickly like they should.

 

[zozomester]

I don't understand because it works for many people. I have the same configuration as you (3x Cinema Display, 2x 20" and 1x 30"). It could be something with the USB hubs, which is also included in the Cinema Display.
View attachment 2151591 View attachment 2151591

 

[tommy chen]

not the best idea to operate a cMP openly, as the necessary wind tunnel no longer works here!

 

[zozomester]

not the best idea to operate a cMP openly, as the necessary wind tunnel no longer works here!

It is not open, with Plexi side panels.....

 

[tsialex]

Simple to understand, Venture finally removed all support for Mac Pro ancient USB controllers. This removal started piece meal with Big Sur, now is completely gone.

OCLP solution to re-add USB support for Ventura have several shortcomings, read about in the change logs/issue pages.

Mac Pro BT controller is a USB v1.1 device, look at System Information / USB, the workaround is to disconnect the USB controller from the backplane and also connect it to a USB v2.0/3.0 HUB, forcing a OHCI connection - problem solved.

 

[zozomester]

Simple to understand, Venture finally removed all support for Mac Pro ancient USB controllers. This removal started piece meal with Big Sur, now is completely gone.

OCLP solution to re-add USB support for Ventura have several shortcomings, read about in the change logs/issue pages.

Mac Pro BT controller is a USB v1.1 device, look at System Information / USB, the workaround is to disconnect the USB controller from the backplane and also connect it to a USB v2.0/3.0 HUB, forcing a OHCI connection - problem solved.

The strange thing is that several people indicated that the original Bluetooth card on the Ventura works for them.

 

[rajazeeshan]

Simple to understand, Venture finally removed all support for Mac Pro ancient USB controllers. This removal started piece meal with Big Sur, now is completely gone.

OCLP solution to re-add USB support for Ventura have several shortcomings, read about in the change logs/issue pages.

Mac Pro BT controller is a USB v1.1 device, look at System Information / USB, the workaround is to disconnect the USB controller from the backplane and also connect it to a USB v2.0/3.0 HUB, forcing a OHCI connection - problem solved.

This all makes sense. I had upgraded my Mac Pro 5,1 to Wi-Fi Bluetooth combo. Based on your suggestion of workaround I am not able to understand how to convert Bluetooth connection cable to USB 2.0+ as it’s a custom connector on board I believe?

 

[vsc]

Simple to understand, Venture finally removed all support for Mac Pro ancient USB controllers. This removal started piece meal with Big Sur, now is completely gone.

OCLP solution to re-add USB support for Ventura have several shortcomings, read about in the change logs/issue pages.

Mac Pro BT controller is a USB v1.1 device, look at System Information / USB, the workaround is to disconnect the USB controller from the backplane and also connect it to a USB v2.0/3.0 HUB, forcing a OHCI connection - problem solved.

Is using an external USB bluetooth controller plugged into a USB v2.0/3.0 hub an option, perhaps after unplugging the internal (V1.1) BlueTooth controller's USB connection?

 

[tsialex]

Is using an external USB bluetooth controller plugged into a USB v2.0/3.0 hub an option, perhaps after unplugging the internal (V1.1) BlueTooth controller's USB connection?

Yes, you can modify a USB cable and connect the internal BT to your USB v2.0/3.0 hub.

Btw, if you are doing this, better to upgrade to a BCM94360CDP AirPort Extreme and completely eliminate the unsupported factory BT module. This way you eliminate two problems in one go.

 

[jedijiver]

Simple to understand, Venture finally removed all support for Mac Pro ancient USB controllers. This removal started piece meal with Big Sur, now is completely gone.

OCLP solution to re-add USB support for Ventura have several shortcomings, read about in the change logs/issue pages.

Mac Pro BT controller is a USB v1.1 device, look at System Information / USB, the workaround is to disconnect the USB controller from the backplane and also connect it to a USB v2.0/3.0 HUB, forcing a OHCI connection - problem solved.

As

Yes, you can modify a USB cable and connect the internal BT to your USB v2.0/3.0 hub.

Btw, if you are doing this, better to upgrade to a BCM94360CDP AirPort Extreme and completely eliminate the unsupported factory BT module. This way you eliminate two problems in one go.

Are you saying that if I upgrade my stock WiFi and Bluetooth cards using one of these ( https://www.ebay.com/itm/274475421781 ) then I'll get my bluetooth back without having to deal with the USB 1.1 contoller issue?

 

[tsialex]

As

Are you saying that if I upgrade my stock WiFi and Bluetooth cards using one of these ( https://www.ebay.com/itm/274475421781 ) then I'll get my bluetooth back without having to deal with the USB 1.1 contoller issue?

No.

Let me be crystal clear, if you gonna have all the trouble to make a custom cable from the BT controller to your USB v2.0/3.0 hub, upgrade your factory AirPort Extreme to an AirPort Extreme BCM94360CDP already, since the connections will be different and it's a lot easier to do the cable for the BCM94360CDP than to the factory BT module.

Even with late-2013 Mac Pro, the BCM94360CDP BT module is USBv1.1.

 

[jedijiver]

No. Let me be crystal clear, if you gonna have all the trouble to make a custom cable from the BT controller to your USB v2.0/3.0 hub, upgrade your factory AirPort Extreme to an AirPort Extreme BCM94360CDP already, since the connections will be different and it's easier to do the cable for the BCM94360CDP than to the factory BT module.

Thanks. That is clearer for sure.

I don't use WiFi on my MacPro, never have. I use Ethernet, so I don't care about WiFi. If the upgrade card still involves a cable conversion, then I see little point in spending the money for the upgrade. Before Ventura I was on OCLP Monterey and my Bluetooth worked perfectly for my mouse, keyboard, AirPods, and Bose headphones.

Do know of any detailed instructions for converting the original stock Bluetooth card's cable? Something like an iFixit guide with step-by-steps and pictures would be ideal? I checked iFixit and din't find anything. I'm 100% confident I can do it, I just need some instruction. Thanks again.

BTW, I've had a PCI USB 3.0 card in my MacPro5,1 for years. It works well and continues to do so under Ventura. Does that play into this at all?

 

[tsialex]

Thanks. That is clearer for sure. Do know of any detailed instructions, like an iFixit guide with step-by-steps and pictures to do the cable conversion? I'm 100% confident I can do it, I just need some instruction. Thanks again.

I don't know if someone did this tutorial already, but the adapters for BCM94360CDP usually have the pin-out of the USB pins on the solder mask, at least the three models that I have, so, it's easy to do a cable.

BTW, I've had a PCI USB 3.0 card in my MacPro5,1 for years. It works well and continues to do so under Ventura. Does that play into this at all?

USB3.0 cards are only available AFTER macOS is fully loaded, so, you have to connect to the Mac Pro native USB v2.0 to have keyboard/mouse working before macOS is fully loaded, i.e. when selecting the default boot disk with BootPicker.

Read the OCLP Ventura installation notes to know about the problems with USB v3.0 controllers if you patch for USB v1.1 support.

 

[tsialex]

I don't use WiFi on my MacPro, never have. I use Ethernet, so I don't care about WiFi. If the upgrade card still involves a cable conversion, then I see little point in spending the money for the upgrade.

Both the factory BT module and the AirPort Extreme BCM94360CDP will need a custom cable.

BCM94360CDP BT controller is BT v4.0, BCM943602CD is BT v4.2. Just that is already worth for a lot of people that need better audio codecs for headsets.

 

[jedijiver]

Both the factory BT module and the AirPort Extreme BCM94360CDP will need a custom cable.

BCM94360CDP BT controller is BT v4.0, BCM943602CD is BT v4.2. Just that is already worth for a lot of people that need better audio codecs for headsets.

If I understand this correctly, I need to disconnect the Bluetooth cable from the motherboard and the BT module and use it to create a custom cable FROM the Bluetooth module TO an external USB 2.0 or higher hub, yes? If yes, then I need to keep the end that plugs into the BT module intact and splice the other end into a USB A male cable. I took a picture of the cable and attached it. So I want to keep the end circled in red, yes?

if I've got the concept correct, can you please provide a detail of the correct pin layout - which pin on the BT module connector goes to which wire on a standard Apple brand USB extension cable. I figure I'll leave the USB A male end intact and clip the female off - splice from there.


Thanks

 

[rajazeeshan]

Both the factory BT module and the AirPort Extreme BCM94360CDP will need a custom cable.

BCM94360CDP BT controller is BT v4.0, BCM943602CD is BT v4.2. Just that is already worth for a lot of people that need better audio codecs for headsets.

I had upgraded my mac pro 5,1 to newer card that has BT and Wi-Fi on it. It is able to air drop and unlock with Apple Watch. It doesn’t work with Ventura. Is there any guide how to convert it to USB 2? Or only option is to disconnect it and buy a usb adapter and attach to hub for BT? If yes any recommendations?

 

[tsialex]

I had upgraded my mac pro 5,1 to newer card that has BT and Wi-Fi on it. It is able to air drop and unlock with Apple Watch. It doesn’t work with Ventura.

You should ask on OCLP discord server about Continuity/Air Drop/Unlock with Apple Watch.

Is there any guide how to convert it to USB 2?

As far as I know, no one did a tutorial yet about how to connect the BT controller to a USB v2.0/3.0 hub. I've just answered that.

Or only option is to disconnect it and buy a usb adapter and attach to hub for BT?

Yes, it's the only option, since the OCLP patch for adding USB v1.1 support to Ventura doesn't work well and has several unwanted effects, such as incompatibility with USB v3.0.

If yes any recommendations?

I doubt that anything that I have access locally will be of help to anyone in another country, so, I don't do recomendations.

 

[rajazeeshan]

As far as I know, no one did a tutorial yet. I've just answered that.



I've already answered that multiple times in this thread. Yes, it's the only option, since the OCLP patch for adding USB v1.1 support to Ventura doesn't work well and has several unwanted effects, such as incompatibility with USB v3.0.



I doubt that anything that I have access locally will be of help to anyone in another country, so, I don't do recomendations.

I was assuming you are in US?

 

[tsialex]

If I understand this correctly, I need to disconnect the Bluetooth cable from the motherboard and the BT module and use it to create a custom cable FROM the Bluetooth module TO an external USB 2.0 or higher hub, yes?

Yes.

If yes, then I need to keep the end that plugs into the BT module intact and splice the other end into a USB A male cable. I took a picture of the cable and attached it. So I want to keep the end circled in red, yes?

Edit: You need to slice the connector that goes to the backplane and keep the end that goes to the BT module intact.

if I've got the concept correct, can you please provide a detail of the correct pin layout - which pin on the BT module connector goes to which wire on a standard Apple brand USB extension cable. I figure I'll leave the USB A male end intact and clip the female off - splice from there.


Thanks

You can get the pin out of the factory BT cable below, you will need to connect all four pins, not just D+ and D-.

802.11ac, BT 4.0, Continuity, and Handoff Working on Mac Pro 2010

-------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------------- News&Updates: (I will...

forums.macrumors.com

 

[jedijiver]

Yes.



Don't matter which end of the factory BT module cable you will splice, the pin-out is the same for both ends.



You can get the pin out of the factory BT cable below, you will need to connect all four pins, not just D+ and D-.

802.11ac, BT 4.0, Continuity, and Handoff Working on Mac Pro 2010

-------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------------- News&Updates: (I will...

forums.macrumors.com

OK, but I'm sstill comfused. If I am going FROM the BT Module TO an external USB 2.0+ hub, then it DOES MATTER which end of the factory cable I splice into. The factory cable has a different connector on both ends. It seems to me that I need to save the end that goes into the BT Module and splice a USB A type male into it, yes?

Thanks for the link to the pin map. Much appreciated.

 

[tsialex]

OK, but I'm sstill comfused. If I am going FROM the BT Module TO an external USB 2.0+ hub, then it DOES MATTER which end of the factory cable I splice into. The factory cable has a different connector on both ends. It seems to me that I need to save the end that goes into the BT Module and splice a USB A type male into it, yes?

Thanks for the link to the pin map. Much appreciated.

You are right and I edited my previous post, the MacPro5,1 factory BT module cable have different two different connectors in each end, you will remove the connector that goes to the backplane.

You will slice the end with the Molex PicoBlade connector, this end will be where you will splice the wires from the USB-A cable.

 

[rajazeeshan]

OK, but I'm sstill comfused. If I am going FROM the BT Module TO an external USB 2.0+ hub, then it DOES MATTER which end of the factory cable I splice into. The factory cable has a different connector on both ends. It seems to me that I need to save the end that goes into the BT Module and splice a USB A type male into it, yes?

Thanks for the link to the pin map. Much appreciated.

I am using a Wi-Fi BT combo card that was needed few years back for continuity features. Once you figure out all pins and conversion, I will try to do that on the combo card. The BT cable connector that plugs into motherboard probably is same as the one in original Bluetooth card. I will appreciate if you can post pictures and detailed tutorial once you figure everything out!