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

[osxfr33k]

Sorry for confusing you, I updated my post as well. You need to remove if you have any PCIE USB 3.0 card(s). There is no need of unplugging Bluetooth card. Original BT card is plugged internally on motherboard on 1.1, so it’s not the problem. Buy externally powered 2.0 usb hub. After installation, when you install root patcher make sure it shows USB1.1 patch installed. Don’t install PCIE USB 3.0 card back. There is no physical modification needed to BT module of machine.

Do I need to do a clean install of Ventura v13.3 again or revert root patching and re-patch or that is not enough to have re-patch install usb1.1 patches? Also does OCLP nightly v0.6.3 have better support for USB v1.1 patches?

Thanks

Edited a few minutes later:

No clean install necessary revert root patch reboot re-patch reboot finally BT working hurray!!!

 

[rajazeeshan]

Do I need to do a clean install of Ventura v13.3 again or revert root patching and re-patch or that is not enough to have re-patch install usb1.1 patches? Also does OCLP nightly v0.6.3 have better support for USB v1.1 patches?

Thanks

Edited a few minutes later:

No clean install necessary revert root patch reboot re-patch reboot finally BT working hurray!!!

Great to hear that it helped. I believe latest opencore legacy is needed for latest Mac OS as they dropped further stuff out.

 

[haralds]

Is the lack of compatibility a fundamental issue of the current patch also present in manual OpenCore configurations and is there hope of a fix?
I need my USB3 connections. Running a dongle is a real PITA booting between Monterey and Ventura since devices have to be re-paired.

 

[Macschrauber]

Is the lack of compatibility a fundamental issue of the current patch also present in manual OpenCore configurations and is there hope of a fix?
I need my USB3 connections. Running a dongle is a real PITA booting between Monterey and Ventura since devices have to be re-paired.

you can unplug the data cable of the internal Bluetooth board to use the dongle exclusively.

 

[haralds]

you can unplug the data cable of the internal Bluetooth board to use the dongle exclusively.

The external dongle seems less reliable than the internal card. I'll leave it for now.
If I remember correctly, the BlueTooth and WiFi are on the same card. That would also be an issue.

 

[bookemdano]

The external dongle seems less reliable than the internal card. I'll leave it for now.
If I remember correctly, the BlueTooth and WiFi are on the same card. That would also be an issue.

They are on the same card (assuming you have upgraded to one of the newer Airport cards), but only the bluetooth radio connects via USB. The WiFi connects via the miniPCI pins on the card. So unplugging the bluetooth cable won't affect the WiFi at all.

 

[SemoTech]

I was experimenting with Ventura and have upgraded to a flashed RX580 Metal card as well as swapped the original WiFi and Bluetooth cards for the all-in-one BCM943602CDP Bluetooth v4.2 & WiFi card w/ the slot adapter. I then got a simple $10 USB 3.0 Hub connected to the back of the Classic Mac Pro on one of the ports. This is an "unpowered" or bus-powered hub. I kept reading that it should be powered, but in reality it seems it does not.

The Mac's on-board USB controller supports both USB 1.1 and USB 2.0 and defaults to the highest speed of the connected device. It therefore connected the USB Hub at USB 2.0, which is great. With my keyboard connected to the hub I was able to get an OCLP boot picker and keyboard support before the OS initialized. Afterwards keyboard and wired mouse, as well as WiFi worked a treat in Ventura.

Now I do have a USB 3.0 PCIe card installed, so the USB 1.1 OCLP drivers were not installed, and that's OK. However this caused the new BCM943602CDP Bluetooth v4.2 not to work, as it is still still connected to the Mac motherboard USB header for D+ and D- and thus was still detected as USB 1.1

What I wanted to do is find a female adapter that matches the one used by Apple on the motherboard which I believe is called a "Molex PicoBlade" connector, and thus mate to the original data cable, but has a regular USB-A on the other end. I could then get the USB-A end outside the case and plug it into this USB 2.0 Hub. This way there will be no cutting of cables or matching polarity and should work.

I also have to figure out how to get the cable out of the case ideally without drilling holes as all my PCI slots are full/taken...

4/11/2023 SUCCESS UPDATE:

OK, great news, did this today and it was really simple, I just cut a thin USB-A cable, snaked it through one of the holes at the back of the Mac Pro (under the Ethernet ports) and on the USB-A end connected it externally to the USB 2.0 Hub I mentioned above. This is a non-destructive solution since I can always remove the USB cable and you'd never know it was there. Also I thought that using a very thin and unshielded cable will cause issues but none so far.

Anyway, on the other end of the "internal & external" USB cable I connected the Green (D+) and White (D-) data lines to the upgraded BCM943602CDP card adapter's 2 pins.

As of now the keyboard works pre-boot and both Monterey and Ventura see the BCM943602CDP card, so I have WiFi, Bluetooth, Apple Mouse 2, Continuity, Handoff, Unlock with Apple Watch, etc... with both OS'!
I am including some screenshots for reference. Hope this helps y'all out and with OCLP and Ventura we can hold off to upgrade our great MacPros 5,1 for at least a few more years...

 

[rajazeeshan]

For me, I didn’t need to do any modifications to my upgraded internal Airport card in MacPro 5,1. I didn’t need USB 3.0 , therefore I removed PCIE USB 3.0 card. I clean install Ventura and applied root patch and everything is working like a charm. The only reason BT wasn’t working for me was because of USB 3.0 PCIE card. It appears root patcher doesn’t apply USB1.1 patching when it sees that card. So anyone who doesn’t need USB 3.0 just remove your PCIE card and move on. All functionality Apple Watch unlock, air drop, sharing pointer between Mac and iPad works. There is no need of doing this mutiny of running wires out of case if you don’t need usb 3.0 and can live with usb 2.0. You need to buy a externally powered usb hub and plug it into usb2.0 and use that to install OS.

 

[Macschrauber]

For me, I didn’t need to do any modifications to my upgraded internal Airport card in MacPro 5,1. I didn’t need USB 3.0 , therefore I removed PCIE USB 3.0 card. I clean install Ventura and applied root patch and everything is working like a charm. The only reason BT wasn’t working for me was because of USB 3.0 PCIE card. It appears root patcher doesn’t apply USB1.1 patching when it sees that card. So anyone who doesn’t need USB 3.0 just remove your PCIE card and move on. All functionality Apple Watch unlock, air drop, sharing pointer between Mac and iPad works. There is no need of doing this mutiny of running wires out of case if you don’t need usb 3.0 and can live with usb 2.0. You need to buy a externally powered usb hub and plug it into usb2.0 and use that to install OS.

this is expected and reported:

Legacy UHCI/OHCI support in Ventura and newer · Issue #1021 · dortania/OpenCore-Legacy-Patcher

In macOS Ventura, Apple removed support for all USB 1.1 drivers leaving some older Macs unable to use USB 1.1 peripherals. The main drivers removed where those of UHCI and OHCI controllers: AppleUS...

github.com

 

[SemoTech]

For me, I didn’t need to do any modifications to my upgraded internal Airport card in MacPro 5,1. I didn’t need USB 3.0 , therefore I removed PCIE USB 3.0 card. I clean install Ventura and applied root patch and everything is working like a charm. The only reason BT wasn’t working for me was because of USB 3.0 PCIE card. It appears root patcher doesn’t apply USB1.1 patching when it sees that card. So anyone who doesn’t need USB 3.0 just remove your PCIE card and move on. All functionality Apple Watch unlock, air drop, sharing pointer between Mac and iPad works. There is no need of doing this mutiny of running wires out of case if you don’t need usb 3.0 and can live with usb 2.0. You need to buy a externally powered usb hub and plug it into usb2.0 and use that to install OS.

Correct, but most people do need USB 3.0/3.1 so in order to get both USB 3.0/3.1 and Bluetooth you must disconnect the Bluetooth data lines from the motherboard, and connect them to an external USB 2.0 Hub. Also the hub does NOT need to be powered!
The process is really quick & simple and non-destructive, using the Bluetooth slot adapter which provides the data pins. It also does not shortchange one from having EVERYTHING working at the same time.

 

[wandan]

Actually, it's not difficult. I've already made the necessary changes。Modify the joint, don't worry about the reverse connection of d+and d -。After modification, OCPL must be reinstalled，BT will only work。

 

[SemoTech]

Nicely done @wandan, however I found no need to re-install OCLP. I just powered off, swapped the data pins and powered back on, and Bluetooth was active. Also, I like your mod to add a USB-A female plug to an existing PCIe card. However with your setup you must always keep that card, as replacing it requires the mod to be re-done on the new card, which may not be possible if it does not have the free bracket space. Also running the USB cable across the Video card seems impractical and prone to problems if you work on your video card.
Anyway, I find that just running the USB-A cable though an existing case hole at the bottom, and out of the way, a lot simpler and quicker with no modifications needed, and no impact to the PCIe cards and slots.

 

[wandan]

Provide an idea, but I did identify BT after reinstalling OCPL

Nicely done @wandan, however I found no need to re-install OCLP. I just powered off, swapped the data pins and powered back on, and Bluetooth was active. Also, I like your mod to add a USB-A female plug to an existing PCIe card. However with your setup you must always keep that card, as replacing it requires the mod to be re-done on the new card, which may not be possible if it does not have the free bracket space. Also running the USB cable across the Video card seems impractical and prone to problems if you work on your video card.
Anyway, I find that just running the USB-A cable though an existing case hole at the bottom, and out of the way, a lot simpler and quicker with no modifications needed, and no impact to the PCIe cards and slots.

 

[RAMtheSSD]

I am more than a bit confused. Why would having the USB3 PCI card keep OCLP from installing a patch for something that would have always been there? If the external USB ports work, why wouldn’t the Bluetooth connection work —as it seems to if I remove the USB3 PCI card— if it is ~ to the external USB 2? Most confusing of all, if taking the card out and redoing OCLP works, why does putting it back in afterwards brick the installation?

As I understand it, the Broadcom Bluetooth in the replacement Bluetooth card is the same that was used in more recent iMacs that would have been Ventura compatible?? The only difference is the actual physical connector on the motherboard of those machines??

 

[bookemdano]

You're talking about two distinctly separate, yet related problems.

The first problem is that Apple removed USB 1.1 drivers from Ventura. Your Mac Pro's built-in bluetooth radio is a USB 1.1 device and therefore can only negotiate a connection @ USB 1.1. Even though all of your cMP's USB ports are 2.0, plugging in a USB 1.1 device (like the bluetooth radio) negotiates that connection at USB 1.1 speed, which requires the USB 1.1 drivers in the OS, which are no longer included.

One workaround is by using a USB 2.0 hub in between. That way, the hub negotiates the USB connection with the cMP at USB 2.0 speed (which uses Ventura's USB 2.0 driver), and the hub itself then handles translating the USB 1.1 communications with the bluetooth radio. This should solve the problem, but just keep in mind there can be other sneaky USB 1.1 devices too--mainly some mice and keyboards. So those too would need to be plugged in via a USB 2.0 hub the same way or replaced with different ones that use USB 2.0 natively (I don't know, but I assume there must be some out there).

The second problem is that, for whatever reason, USB 1.1 and USB 3 drivers have some conflict when running at the same time in Ventura (which is understandable since in Ventura USB 1.1 drivers are not supposed to be there). I do not know the specific nature of the conflict, but obviously there is some reason that the two cannot coexist in memory. So when OCLP patches the OS to re-include the USB 1.1 drivers, it breaks the ability to load the USB 3.0 drivers. So you have to pick one or the other.

I think the BCM94360CD replacement Airport cards we use in the cMP come from 2013 iMacs, which are definitely not supported on Ventura. Remember it's really mainly only 2017 and newer Macs that are officially Ventura-capable. I'm sure all officially Ventura-compatible Macs have newer bluetooth chips that use USB 2.0, which is why Apple was safe to drop USB 1.1 support from that OS.

Hope that helps make sense of it.

 

[Macschrauber]

a link to the OCLP site was posted just a few messages before: https://forums.macrumors.com/thread...lling-ventura-with-oclp.2378654/post-32094297

 

[tsialex]

You're talking about two distinctly separate, yet related problems.

The first problem is that Apple removed USB 1.1 drivers from Ventura. Your Mac Pro's built-in bluetooth radio is a USB 1.1 device and therefore can only negotiate a connection @ USB 1.1. Even though all of your cMP's USB ports are 2.0, plugging in a USB 1.1 device (like the bluetooth radio) negotiates that connection at USB 1.1 speed, which requires the USB 1.1 drivers in the OS, which are no longer included.

One workaround is by using a USB 2.0 hub in between. That way, the hub negotiates the USB connection with the cMP at USB 2.0 speed (which uses Ventura's USB 2.0 driver), and the hub itself then handles translating the USB 1.1 communications with the bluetooth radio. This should solve the problem, but just keep in mind there can be other sneaky USB 1.1 devices too--mainly some mice and keyboards. So those too would need to be plugged in via a USB 2.0 hub the same way or replaced with different ones that use USB 2.0 natively (I don't know, but I assume there must be some out there).

The second problem is that, for whatever reason, USB 1.1 and USB 3 drivers have some conflict when running at the same time in Ventura (which is understandable since in Ventura USB 1.1 drivers are not supposed to be there). I do not know the specific nature of the conflict, but obviously there is some reason that the two cannot coexist in memory. So when OCLP patches the OS to re-include the USB 1.1 drivers, it breaks the ability to load the USB 3.0 drivers. So you have to pick one or the other.

I think the BCM94360CD replacement Airport cards we use in the cMP come from 2013 iMacs, which are definitely not supported on Ventura. Remember it's really mainly only 2017 and newer Macs that are officially Ventura-capable. I'm sure all officially Ventura-compatible Macs have newer bluetooth chips that use USB 2.0, which is why Apple was safe to drop USB 1.1 support from that OS.

Hope that helps make sense of it.

That's not it. All USB 1.1 devices are still supported with Ventura, even with Apple Silicon.

What Apple removed, starting with Monterey, is support for old Intel UHCI USB controllers (and RTMHs).

With older Macs, like Mac Pro early-2009 to mid-2012, the Intel south bridge have two different USB controllers, the UHCI controller for USB 1.0 and 1.1 devices and another for USB 2.0 devices, the EHCI controller. Monterey and Ventura only support EHCI controllers, that's why we can workaround the missing UHCI forcing the EHCI connection via a USB 2.0/3.0 hub.

 

[tsialex]

Btw, the Bluetooth of BCM94360CD/BCM943602CDP AirPort Extreme cards are fully supported with Ventura once you have it connected via the USB 2.0/3.0 hub workaround (forcing the connection to be EHCI instead of the missing UHCI).

 

[bookemdano]

That's not it. All USB 1.1 devices are still supported with Ventura, even with Apple Silicon.

What Apple removed, starting with Monterey, is support for old Intel UHCI USB controllers (and RTMHs).

With older Macs, like Mac Pro early-2009 to mid-2012, the Intel south bridge have two different USB controllers, the UHCI controller for USB 1.0 and 1.1 devices and another for USB 2.0 devices, the EHCI controller. Monterey and Ventura only support EHCI controllers, that's why we can workaround the missing UHCI forcing the EHCI connection via a USB 2.0/3.0 hub.

Maybe my explanation was not clear enough, but what you said is exactly what I was trying to explain. That's why I said that his bluetooth radio will work fine in Ventura once it's connected through a USB 2.0 hub.

When I said that USB 1.1 drivers are missing in Ventura I was referring to the USB 1.1 controller/host drivers, not the drivers for USB 1.1 client devices.

 

[tsialex]

Next OCLP release will remove the USB3.0 incompatibility of the previous legacy UHCI Ventura patches:

Enhancement - Enable USB 3 expansion card support on Legacy USB 1.1 machines by Jazzzny · Pull Request #1055 · dortania/OpenCore-Legacy-Patcher

This PR disables the USB 3.0 blacklist found in the USB 1.1 patch detection, as the new USB 1.1 patches are compatible with PCIe USB 3.0 chips from Fresco Logic and AsMedia. This resolves USB 3 exp...

github.com

 

[RAMtheSSD]

Next OCLP release will remove the USB3.0 incompatibility of the previous legacy UHCI Ventura patches:

Enhancement - Enable USB 3 expansion card support on Legacy USB 1.1 machines by Jazzzny · Pull Request #1055 · dortania/OpenCore-Legacy-Patcher

This PR disables the USB 3.0 blacklist found in the USB 1.1 patch detection, as the new USB 1.1 patches are compatible with PCIe USB 3.0 chips from Fresco Logic and AsMedia. This resolves USB 3 exp...

github.com

So, while I still do not understand why there would be a conflict or why some people seem to have been able to patch it, not ”sheetmetal and bailing wire” cut and splice wires —although, some, I will admit, are, as elegant a solution as one could imagine under the circumstances— all I have to do is wait until next Monday? Is there a way to get a “pre-release” version?

 

[tsialex]

all I have to do is wait until next Monday?

AFAIK there is no release date set yet, even more so with 0.6.4 being released just five days ago.

Is there a way to get a “pre-release” version?

You can try the nightly or compile yourself the branch with the new drivers, see the instructions on the GitHub main project page.

 

[startergo]

Here is the nightly build:

Spoiler: USB3,1 along with 1.1 patch

 Bluetooth Controller:
  Address:    44:2A:60:D0:E2:27
  State:    On
  Chipset:    THIRD_PARTY_DONGLE
  Discoverable:    Off
  Firmware Version:    v8656 c518
  Product ID:    0x0001
  Supported services:    0x382039 < HFP AVRCP A2DP HID Braille AACP GATT Serial >
  Transport:    USB
  Vendor ID:    0x004C (Apple)
  Not Connected:
  Creative T60:
  Address:    00:02:3C:8F:F4:CD
  Vendor ID:    0xE003
  Product ID:    0x3528
  Firmware Version:    0.0.1
  Minor Type:    Headset

BRCM2046 Hub:

  Product ID:    0x4500
  Vendor ID:    0x0a5c  (Broadcom Corp.)
  Version:    1.00
  Manufacturer:    Apple Inc.
  Location ID:    0x5a100000

Bluetooth USB Host Controller:

  Product ID:    0x8215
  Vendor ID:    0x05ac (Apple Inc.)
  Version:    2.08
  Serial Number:    442A60D0E227
  Manufacturer:    Apple Inc.
  Location ID:    0x5a110000

Bluetooth USB Host Controller:

  Product ID:    0x8215
  Vendor ID:    0x05ac (Apple Inc.)
  Version:    2.08
  Serial Number:    442A60D0E227
  Manufacturer:    Apple Inc.
  Location ID:    0x5a110000

  Software Versions:
  CoreWLAN:    16.0 (1657)
  CoreWLANKit:    16.0 (1657)
  Menu Extra:    17.0 (1728)
  System Information:    15.0 (1502)
  IO80211 Family:    12.0 (1200.12.2b2)
  Diagnostics:    11.0 (1163)
  AirPort Utility:    6.3.9 (639.16)
  Interfaces:
en2:
  Card Type:    Wi-Fi  (0x14E4, 0x8E)
  Firmware Version:    Broadcom BCM43xx 1.0 (5.106.98.100.24)
  MAC Address:    c8:bc:c8:f4:92:33
  Locale:    FCC
  Country Code:    US
  Supported PHY Modes:    802.11 a/b/g/n
  Supported Channels:    1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165
  Wake On Wireless:    Supported
  Status:    Connected

1d:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
0f:00.0 USB controller: ASMedia Technology Inc. ASM2142/ASM3142 USB 3.1 Host Controller
11:00.0 USB controller: ASMedia Technology Inc. ASM2142/ASM3142 USB 3.1 Host Controller

 

[RAMtheSSD]

I spent last night trying to get OCLP to build so I could run it from source and I kept getting stuck at building "wheel." This morning, a fresh download of the nightly build and python and --I have no idea what happened!!-- SMC and PRAM reset, build, reinstall, and reboot... everything works! Ok, nope, one thing is really weird, when I try to connect the iPad, all the buttons under Bluetooth disappear, spinning spokes, connection failed. So, right now, handoff works but universal control and sidecar do not. 🤔🤩

 

[RAMtheSSD]

Undoubtedly, in the frustrations from the very problems we are trying to solve here, many of us forget to thank the people that solve the problems and answer the questions; Bookemdano, Tsialex, and Startergo, thank you for your help, know that it is appreciated.

To the developers that create things like OCLP, thank you, an extraordinary number of people the world over owe you their gratitude for keeping their Macs running securely year after year. We all owe you our further gratitude because, whenever a problem arrises, you do more still. Words are a start.

MacRumors, thank you for maintaining this very active and responsive forum that helps so many people the world over.