Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

fhturner

macrumors 6502a
Original poster
Nov 7, 2007
631
413
Birmingham, AL & Atlanta, GA
Hey Y'all—

Sorry if this has been covered...there's a dizzying amount of different bits about OpenCore and its different variants, and I simply haven't had time to continue reading every post of every thread in an ongoing fashion...

I use Martin's OpenCore config to enable AMD Hardware Acceleration on my MP5,1, and it works great. I even was able to install Monterey and that seems to work quite well so far also. The only think I'm missing is Bluetooth support for the original card.

I see that OCLP version 0.2.5 and later fixes legacy BT support for Mac Pros and other systems, so perhaps that can correct it for me.

What I'm unsure about is how to integrate the BT fix from OCLP w/ the OpenCore config I'm already using from Martin. Is there a post or resource that discusses how to add one w/o disrupting the other?

Thx,
Fred
 

sfalatko

macrumors 6502a
Sep 24, 2016
639
364
Hey Y'all—

Sorry if this has been covered...there's a dizzying amount of different bits about OpenCore and its different variants, and I simply haven't had time to continue reading every post of every thread in an ongoing fashion...

I use Martin's OpenCore config to enable AMD Hardware Acceleration on my MP5,1, and it works great. I even was able to install Monterey and that seems to work quite well so far also. The only think I'm missing is Bluetooth support for the original card.

I see that OCLP version 0.2.5 and later fixes legacy BT support for Mac Pros and other systems, so perhaps that can correct it for me.

What I'm unsure about is how to integrate the BT fix from OCLP w/ the OpenCore config I'm already using from Martin. Is there a post or resource that discusses how to add one w/o disrupting the other?

Thx,
Fred
I would try the OCLP discord. It is apparently very active and the developers are online frequently.
 

sfalatko

macrumors 6502a
Sep 24, 2016
639
364
Okay, thanks. I just wondered if that ground had already been covered here somewhere...
I don't know - I recall seeing some info about getting legacy bluetooth working but as I've upgraded my bluetooth/wifi adapter I didn't focus on it so I would suggest searching and the OCLP discord.
 

maosmurf

macrumors newbie
Apr 10, 2010
6
0
Same here.
My newly bought BCM943602CDP from osxwifi does not work in Monterey.
Wifi is fine. Also BT works on fresh Big Sur, so not a HW issue.
 

maosmurf

macrumors newbie
Apr 10, 2010
6
0
Same here.
My newly bought BCM943602CDP from osxwifi does not work in Monterey.
Wifi is fine. Also BT works on fresh Big Sur, so not a HW issue.

Update: I just removed my Inateck USB3 card, BCM943602CDP works smoothly also with BT!
On OCLP v0.4.3 and Monterey 12.3.1

Edit: after reboot, while having all 3 items connected to back USB (mouse, keybord and an external SSD) teh bluetooth was gone again. After removing the external SSD and rebooting, bluetooth is back again :)
 
Last edited:

motiontrack

macrumors newbie
Jan 18, 2023
15
1
Hey Y'all—

Sorry if this has been covered...there's a dizzying amount of different bits about OpenCore and its different variants, and I simply haven't had time to continue reading every post of every thread in an ongoing fashion...

I use Martin's OpenCore config to enable AMD Hardware Acceleration on my MP5,1, and it works great. I even was able to install Monterey and that seems to work quite well so far also. The only think I'm missing is Bluetooth support for the original card.

I see that OCLP version 0.2.5 and later fixes legacy BT support for Mac Pros and other systems, so perhaps that can correct it for me.

What I'm unsure about is how to integrate the BT fix from OCLP w/ the OpenCore config I'm already using from Martin. Is there a post or resource that discusses how to add one w/o disrupting the other?

Thx,
Fred
Did you ever resolve this by chance? I'm trying to figure out a similar situation. Using ML's OC 0.8.8 package but lost BT/WF when I upgraded to Monterey on my cMP 5,1 with original card. Was trying to figure out how/if I could use the OCLP root patcher to get BT/WF back. Thanks for any leads you can offer.
 

fatespawn

macrumors regular
Feb 22, 2009
244
112
Chicagoish
If you don't mind an ugly but very functional fix, I bought this bluetooth/wifi PCI card:


...and this cable:


The Fenvi Wifi card comes with a cable that is supposed to connect to a motherboard USB header. But the MP's don't have one. So you use the extension cable to create an actual USB plug. Then route the USB cable out the back of your computer and plug it into a USB port. You just have to disconnect the internal bluetooth/wifi cards - I just unplugged them and put some electrical tape over the ends so they wouldn't short.

The nice thing is you get bluetooth 4.0 and 802.11ac wifi. The bad thing is you have to drill one hole (I did it in the card itself) and unplug your internal stuff. But it works great. I just airdropped this picture from my phone to the MP to post this.

IMG_2545.JPG
 

_LiveSorcerer_

macrumors newbie
Oct 10, 2018
25
4
Itu-SP/Brazil
Hi everyone, I'm not having as much luck with OCLP as I am with Martin's OC. I tried to boot MacOS with Martin's OC, without success, and I managed with OCLP, but I'm having a problem with the Boot Loading Apple not appearing when I restart, and I'm having to turn off the machine completely, wait 10 seconds and turn it on again. I'm still having a problem with the Titan Ridge that appears in the report but even connecting the TB3 device it doesn't recognize it. The following error occurs, when I have to initialize the system, after the reboot did not work.

panic(cpu 0 caller 0xffffff8010bcdd43): Kernel trap at 0xffffff8010b97182, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff80fffffe1c, CR3: 0x000000001565f000, CR4: 0x00000000000226e0
RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0xffffff80153cb771, RDX: 0x0000000000000fee
RSP: 0xfffffff58cae29e0, RBP: 0xfffffff58cae3a60, RSI: 0x0000000000001011, RDI: 0x0000000000000000
R8: 0x0000000000000000, R9: 0x000000000000ff01, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x00000000000000f2, R13: 0xffffff80153c6000, R14: 0xffffff80fffffe1c, R15: 0xffffff80153c7021
RFL: 0x0000000000010246, RIP: 0xffffff8010b97182, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0xffffff80fffffe1c, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1

Panicked task 0xffffff95c5425670: 136 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff90f9c86aa0, Frame : Return Address
0xfffffff58cae2390 : 0xffffff8010a7bebd mach_kernel : _handle_debugger_trap + 0x41d
0xfffffff58cae23e0 : 0xffffff8010bde5e6 mach_kernel : _kdp_i386_trap + 0x116
0xfffffff58cae2420 : 0xffffff8010bcd953 mach_kernel : _kernel_trap + 0x4d3
0xfffffff58cae2470 : 0xffffff8010a1ba70 mach_kernel : _return_from_trap + 0xe0
0xfffffff58cae2490 : 0xffffff8010a7c28d mach_kernel : _DebuggerTrapWithState + 0xad
0xfffffff58cae25b0 : 0xffffff8010a7ba46 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xfffffff58cae2610 : 0xffffff80113148b3 mach_kernel : _panic + 0x84
0xfffffff58cae2700 : 0xffffff8010bcdd43 mach_kernel : _sync_iss_to_iks + 0x2c3
0xfffffff58cae2880 : 0xffffff8010bcda26 mach_kernel : _kernel_trap + 0x5a6
0xfffffff58cae28d0 : 0xffffff8010a1ba70 mach_kernel : _return_from_trap + 0xe0
0xfffffff58cae28f0 : 0xffffff8010b97182 mach_kernel : _vc_display_lzss_icon + 0x2a2
0xfffffff58cae3a60 : 0xffffff80112d8946 mach_kernel : _PE_display_icon + 0x56
0xfffffff58cae3a80 : 0xffffff80112a7394 mach_kernel : _IOFindBSDRoot + 0x4d4
0xfffffff58cae3b00 : 0xffffff8011005309 mach_kernel : _set_rootvnode + 0x2909
0xfffffff58cae3e70 : 0xffffff8010ab2dcd mach_kernel : _max_valid_stack_address + 0x142d
0xfffffff58cae3fa0 : 0xffffff8010a1b19e mach_kernel : _call_continuation + 0x2e

Process name corresponding to current thread (0xffffff90f9c86aa0): kernel_task
Boot args: keepsyms=1 debug=0x100 -lilubetaall -btlfxallowanyaddr ipc_control_port_options=0 -nokcmismatchpanic -disable_sidecar_mac

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 21.6.0: Mon Dec 19 20:44:01 PST 2022; root:xnu-8020.240.18~2/RELEASE_X86_64
Kernel UUID: 33C30416-3302-3FFF-9686-A557DED28C5B
KernelCache slide: 0x0000000010800000
KernelCache base: 0xffffff8010a00000
Kernel slide: 0x0000000010810000
Kernel text base: 0xffffff8010a10000
__HIB text base: 0xffffff8010900000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0

System uptime in nanoseconds: 62356280284
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000000e84b95868
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000019d1712e88 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff80f5bb1000 - 0xffffffa0f5bb1000
. PGZ : 0xffffff80f5bb1000 - 0xffffff80fdbb2000
. VM : 0xffffff80fdbb2000 - 0xffffff85c954b000
. RO : 0xffffff85c954b000 - 0xffffff876287e000
. GEN0 : 0xffffff876287e000 - 0xffffff8c2e217000
. GEN1 : 0xffffff8c2e217000 - 0xffffff90f9bb0000
. GEN2 : 0xffffff90f9bb0000 - 0xffffff95c5549000
. GEN3 : 0xffffff95c5549000 - 0xffffff9a90ee3000
. DATA : 0xffffff9a90ee3000 - 0xffffffa0f5bb1000
Metadata: 0xffffffa0f5bc1000 - 0xffffffa115bc1000
Bitmaps : 0xffffffa115bc1000 - 0xffffffa12dbc1000
 

jggorman

macrumors newbie
Jul 4, 2011
29
7
My upgraded card is working very well. I did three things. I turned on both BlueToolFixUp and BlueTooth-Spoof kext as per the video at the link below. I also had to enter the boot argument in the terminal and restart: sudo nvram bluetoothHostControllerSwitchBehavior=always.


I realize all three things may not be needed but it is working consistently and flawlessly for what I need, so I am reluctant to change anything (I haven't tried handoff/continuity).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.