MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[Gustav Holdoff]

Can you try this test: try enabling Voice Control (System Preferences > Accessibility > Voice Control).

I experimented to see what works best for archicad, twinmotion, UE5 or blender.
about voice control:
I don't use it at all.
and had a bad experience when I tried after several posts to test its work in early Monterey -
I badly damaged the system then I had to completely reformat the disk and restore all the files from the archive,
but what can I say for sure:
in the initial versions of monterey, my sleep/wakeup got corrupted when the thunderbolt ssdt was on,
but in version 12.5.1 this problem disappeared for me
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.0/0.8.3, mac os 12.5.1

 

[Dewdman42]

I hear you. The reason I asked is because that is one of the tests to find out of the AVX patch is still needed.

 

[Dewdman42]

So I just removed avxpel to try out. I immediately attempted the voice-control test and sure enough it did panic again. Here is the report, but nothing new there

Spoiler: panic report

panic(cpu 12 caller 0xffffff801efd07e3): Kernel trap at 0xffffff80203e7090, type 6=invalid opcode, registers:
CR0: 0x000000008001003b, CR2: 0x00007ff8507bbfe8, CR3: 0x00000015532c217e, CR4: 0x00000000000226e0
RAX: 0x0000000000000000, RBX: 0x0000000000002664, RCX: 0x0000000000000000, RDX: 0xffffff9a9f1db008
RSP: 0xfffffff841b1b520, RBP: 0xfffffff841b1b9e0, RSI: 0x0000000000000200, RDI: 0xfffffff841b1b980
R8:  0xffffff9a9edec008, R9:  0x0000000000000000, R10: 0x0000000000000702, R11: 0x0000000000000702
R12: 0xffffff9a9f1db008, R13: 0x000000000000dd55, R14: 0xffffff9a9edec008, R15: 0xfffffff841b1b780
RFL: 0x0000000000010246, RIP: 0xffffff80203e7090, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007ff8507bbfe8, Error code: 0x0000000000000000, Fault CPU: 0xc, PL: 0, VF: 0

Panicked task 0xffffff910593aa20: 4 threads: pid 1139: com.apple.Speech
Backtrace (CPU 12), panicked thread: 0xffffff9a9c64e540, Frame : Return Address
0xfffffff841b1aed0 : 0xffffff801ee7fd6d
0xfffffff841b1af20 : 0xffffff801efe1086
0xfffffff841b1af60 : 0xffffff801efd03f3
0xfffffff841b1afb0 : 0xffffff801ee1fa70
0xfffffff841b1afd0 : 0xffffff801ee8013d
0xfffffff841b1b0f0 : 0xffffff801ee7f8f6
0xfffffff841b1b150 : 0xffffff801f714e03
0xfffffff841b1b240 : 0xffffff801efd07e3
0xfffffff841b1b3c0 : 0xffffff801efd04c6
0xfffffff841b1b410 : 0xffffff801ee1fa70
0xfffffff841b1b430 : 0xffffff80203e7090
0xfffffff841b1b9e0 : 0xffffff80203ea4c2
0xfffffff841b1b9f0 : 0xffffff80203f2429
0xfffffff841b1bab0 : 0xffffff80203f1b25
0xfffffff841b1bb40 : 0xffffff801f175412
0xfffffff841b1bcc0 : 0xffffff802215e808
0xfffffff841b1bd70 : 0xffffff801f14eb72
0xfffffff841b1bdf0 : 0xffffff801f14d8e0
0xfffffff841b1be50 : 0xffffff801f4868f2
0xfffffff841b1bee0 : 0xffffff801f4866d0
0xfffffff841b1bf40 : 0xffffff801f58918b
0xfffffff841b1bfa0 : 0xffffff801ee20236
      Kernel Extensions in backtrace:
         com.apple.filesystems.apfs(1934.141.2)[A4D6592B-135F-3622-BBFA-2FB698814463]@0xffffff8022107000->0xffffff8022285fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[7201FB4A-CE2A-3EDA-92DE-053285346974]@0xffffff80203b2000->0xffffff80203bbfff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[53D12D3C-8326-3B2E-8FD6-204D97AEEF08]@0xffffff80203c8000->0xffffff80203cdfff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[752EFEA5-C07D-3246-AC42-A2C447402B68]@0xffffff80208d3000->0xffffff80208dafff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[24743B95-072D-31C4-A59D-7FF38502C0C4]@0xffffff8021b78000->0xffffff8021b8efff
            dependency: com.apple.kec.corecrypto(12.0)[864DE2A3-7343-32A3-AC76-68DF89128C87]@0xffffff80222bf000->0xffffff802233ffff
            dependency: com.apple.security.AppleImage4(4.2.0)[C55B9734-D46F-3F23-9B96-13FD4402B872]@0xffffff802044f000->0xffffff8020467fff
         com.apple.AppleFSCompression.AppleFSCompressionTypeZlib(1.0)[E2FCB200-0C9C-35DC-B9CD-E5FB1CB24159]@0xffffff80203e5000->0xffffff80203f6fff

Process name corresponding to current thread (0xffffff9a9c64e540): com.apple.SpeechRecognitionCore.
Boot args: -v chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G83

Kernel version:
Darwin Kernel Version 21.6.0: Wed Aug 10 14:25:27 PDT 2022; root:xnu-8020.141.5~2/RELEASE_X86_64
Kernel UUID: D0DC2052-71F4-3DCB-B189-BEE5A59B3B42
KernelCache slide: 0x000000001ec00000
KernelCache base:  0xffffff801ee00000
Kernel slide:      0x000000001ec10000
Kernel text base:  0xffffff801ee10000
__HIB  text base: 0xffffff801ed00000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 188076718052
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x0000002bca3f0235
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000269f030f14 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: 0xffffff8101a81000 - 0xffffffa101a81000
  . PGZ   : 0xffffff8101a81000 - 0xffffff810da82000
  . VM    : 0xffffff810da82000 - 0xffffff85d8a81000
  . RO    : 0xffffff85d8a81000 - 0xffffff8771a81000
  . GEN0  : 0xffffff8771a81000 - 0xffffff8c3ca81000
  . GEN1  : 0xffffff8c3ca81000 - 0xffffff91

What I can surmise at this point is the following:

1. Apple has not removed any dependencies on AVX from 12.5.1. So running without any patch at all, you do at your own risk. Its possible many people are not using specific use-cases where the AVX call is encountered.
   
   
2. The panic report above is different then the one I have been getting randomly the past few days, always while away from my computer. Note I have not yet tried to reset the RTC by removing the battery for 10 minutes, but plan to when I get a chance. Unfortunately I don't have a multimeter here in temporary housing and it may be a while before I could check the battery to see if that is involved. In any case it has KP'd 3 times on me, always while away. I have tried to manually put the computer to sleep, works no problem. I have auto sleep disabled. I have seen the screen saver work many times no problem. I will continue to try to keep an eye out for what might be happening at the time the KP's are happening.
   
   
3. I have avxpel removed for now in order to see if I get one of the above KP's again, notwithstanding patch removed.

 

[danallen]

rom your screenshot, it looks like you are going through Software Update.

100% agree. but looks can be deceiving. I followed some instructions about how to download the correct version of Mohave for making a bootable installer. Those instructions included a link to Apple for downloading Mojave. I found that link on OSX Daily, and this is the link I found, under a heading that looked like it was for MojoveL

The download that that led to the image I posted, showing the Mac software update utility on Catalina came from this page:

 

[danallen]

I'm having issues with 12.5.1 even with fully supported Macs, from the get go I've noticed that the boot time with a MacPro6,1 at least doubled, so, I don't think that this one is a MacPro5,1 related issue (or just a MacPro5,1 issue).

While I don't have much time available right now to track/debug, I double checked my config.plist and enabled verbose boot hoping that I stumble with some clue as where the problem is located at least, you should do the same.

Well that about does it. If you are icing osx upgrades, ain't no way no how I am going to risky killing my old computer for a minor upgrade.

Someday, the end of an era will come. Who will die first, my cheese grater or me? At this point, I would say it is a tossup.

 

[Dewdman42]

We will get to the bottom of it but I’m quite sure Monterey will be the last on mine. After that I will run winblows on it or even Linux, the life of this machine is far from over

 

[Bmju]

100% agree. but looks can be deceiving. I followed some instructions about how to download the correct version of Mohave for making a bootable installer. Those instructions included a link to Apple for downloading Mojave. I found that link on OSX Daily, and this is the link I found, under a heading that looked like it was for MojoveL

View attachment 2047270




The download that that led to the image I posted, showing the Mac software update utility on Catalina came from this page:

View attachment 2047271

Iirc those instructions were broken as ****! You are better off finding a reliable processes from elsewhere for building an installer for an earlier macOS†, and then upgrading it using the Mojave download from here https://support.apple.com/en-gb/HT211683 .

†The 'Original answer' section from here worked for me (for El Capitan, and can be modified in fairly obvious ways, even for Lion): https://apple.stackexchange.com/a/389830/113758

 

[Gustav Holdoff]

Iirc those instructions were broken as ****! You are better off finding a reliable processes from elsewhere for building an installer for an earlier macOS†, and then upgrading it using the Mojave download from here https://support.apple.com/en-gb/HT211683 .

†The 'Original answer' section from here worked for me (for El Capitan, and can be modified in fairly obvious ways, even for Lion): https://apple.stackexchange.com/a/389830/113758

I fully support this opinion
I encountered it myself a few days ago when I asked tsialex to clean my nvram.
I had to do a high Siera installer and then upgrade to mojave.
other options didn't work

 

[358]

Hey guys does anyone have a known good EFI for stock dual cpu 5.1. Can you share please. I’m trying to debug intermittent issues with the titan ridge Thunderbolt card, which either hangs (black screen on boot) or boots up but functionality of the Thunderbolt Display is only limited to video (no webcam/speakers/usb ports) and at other times it just boots up properly and everything works. I just need to know that my base opencore is solid so I’m not questioning it every time

 

[Gustav Holdoff]

Based on this, you should include agdpmod=pikera even in Monterey, at least initially. For the initial setup, it's best to include this as a boot argument rather than a device property (just add it like the -no_compat_check argument in the basic config) and determine whether it is actually needed. If you've determined that it is indeed needed, then you can try including it as a device property and clean up your NVRAM variables for a more permanent setup (note that with some graphics cards, device properties don't work, so you can test this as well with your card).

Make sure to keep us posted on how things go!

thanks to cdf for the detailed method for installing opencore
regarding my post and your answer:
The fears of the syncretic about the bootargument "pikera" for the correct operation of the GPU6x00 turned out to be in vain, at least in my case for the Radeon Pro W6800.
I use GPU in macOS 12.5.1 with your method (although I couldn’t patch RadeonProW6800 myself - I had to ask for help from the author of the patch- thanks syncretic)
Although I ran it on opencore 0.8.0 with Martin Lo's config and tested the work first in that configuration
AND
- I did not like the multiple cloned mdworker processes - (I did not have them with the same Martin's OC but with the Radeon Pro W5700 or RX580)
- there is probably some interaction of the patched GPU rom and system- i will test the system behavior later
- and I also got an unpleasant bug: I booted into opencore from USB and after booting into macOS I booted into windows, and when I tried to reboot back into macOS - I didn’t succeed - a non-competable disk appeared, and i couldn't boot into windows too (I already encountered similar behavior a few days ago - but I tested and found out that this happened in my case with the GPU SSDT <true>, and the problem disappeared if the SSDT was <false>)
- I had to drop smc and nvram - after that, opencore did not want to boot from USB
- I had to put opencore on ssd connected instead of CD and now I work with OC 0.8.3
what happens when i try to reboot again in windows i will check later (this weekend)

also later I will try to use SSDT to replace the default bridge names, as recommended by startergo (I had a very impressive experience with SSDT for GPU bridge - the improvement in GPU performance was immediately noticeable in the case of my previous W5700)
I also want to thank tsialex for cleaning my nvram (also a very useful experience in understanding the operation of the hardware and the system)
I hope that all hardware upgrades and other manipulations will be able to extend the work of cMP for a long time

My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w6800, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, OC 0.8.0 and 0.8.3, mac os 12.5.1

 

[Gustav Holdoff]

Unfortunately, not everything turned out so well in the end:
1. I boot into the macos with the patched W6800 -ok
2. twinmotion and UE5 write that my computer does not meet the minimum requirements - nonsense! programs do not understand that I have a W6800
3. reboot into windows ok
reboot into macos - error
4. again again or macos or windows- kernel panic

resetting smc
booting macOS - noncompatable disk, but booting

and this happens now all the time if I have a patched W6800
only 2 reboot cycles, then crash and panic
it doesn't matter which version of opencore is 0.8.3 or 0.8.0

I am attaching two panic reports

EDITED
in order not to kill macpro, I decided to clear nvram again using the tsialex method
since the crashes (during testing new GPU compatibility with hardware and software)
and since resets of nvram in a strange way led to the fact that I could no longer reset nvram with the keyboard
- cMP did not reset nvram, but simply loaded the macOS without reacting to keyboard commands in any way

while I was performing the nvram cleaning procedures
I tested the W6800 on my second cMP - almost the same, only single-processor and without a thunderbolt card, but with USB-3
tests were successful on the second cmp - no crashes,
rebooting windows/macOS many times did not lead to failures
Then I replaced the cpu tray (to check if I have something with the cpu) and again did multiple tests, accompanying each reload with rendering in blender - because yesterday I made sure (thank's startergo) that the blender in fact used only CPU during renderings test scenes (due to the fact that after crashes and reboots, despite the fact that the GPU rendering option was selected in the blender, in reality the GPU did not do any work at all)
but why doesn't blender recognize CPU after crashes?

there were no crashes throughout the night of intensive testing
Therefore, several reasons can be ruled out:
- patched GPU seems to work
- does not conflict with processors on both cmp
- does not conflict with Windows (probably)
- does not conflict with 12.3.1 + os 0.8.0 too (probably)

two suspects left
1) 12.5.1 + OC 0.8.0 and 12.5.1 + OC 0.8.3 +patched W6800
2) alpine ridge thunderbolt &SSDT + patched W6800+ windows

I decided to remove windows for a while until I find the causes and solutions

as a result, I worked in tests for the whole night, there were no more crashes (because I removed the ability to boot into windows from 12.5.1 +opencore)

on my cMP 4.1/5.1 the gpu runs on macOS
on my second cMP 4.1/5.1 W6800 additionally works on both windows and macos 12.3.1

Thunderbolt (with ssdt) + GPU working together on windows with a reboot on macos 12.5.1 requires careful testing in the future

My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w6800, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, OC 0.8.0 and 0.8.3, mac os 12.5.1

 

[OVERKILL338LM]

100% agree. but looks can be deceiving. I followed some instructions about how to download the correct version of Mohave for making a bootable installer. Those instructions included a link to Apple for downloading Mojave. I found that link on OSX Daily, and this is the link I found, under a heading that looked like it was for MojoveL

View attachment 2047270




The download that that led to the image I posted, showing the Mac software update utility on Catalina came from this page:

View attachment 2047271

Easy way to grab the installers is through the munki python scripts:

GitHub - munki/macadmin-scripts: Scripts of possible interest to macOS admins

Scripts of possible interest to macOS admins. Contribute to munki/macadmin-scripts development by creating an account on GitHub.

github.com

This is referenced in the OpenCore install guide:

OpenCore-Install-Guide/installer-guide/mac-install.md at master · dortania/OpenCore-Install-Guide

Repo for the OpenCore Install Guide. Contribute to dortania/OpenCore-Install-Guide development by creating an account on GitHub.

github.com

Which also gives you the exact commands to paste into a terminal to get a full installer that you can put on a USB stick using:

sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

 

[amarmot]

Hey all. I'm hoping to get some advice from the OpenCore gurus in the forum on how best to configure a Mac Pro 5,1 with unflashed Navi 10XT card that must quad boot Monterey, Windows, Linux and Mojave. I recently updated to OCLP 0.4.10 (which spoofs MacPro 7,1 by default), but I found out the hard way this breaks Mojave (prohibited symbol at startup). Other than physically removing the disk with OC, is there a way to bypass OC to boot into Mojave natively?

 

[mode11]

In any case it has KP'd 3 times on me, always while away. I have tried to manually put the computer to sleep, works no problem. I have auto sleep disabled. I have seen the screen saver work many times no problem. I will continue to try to keep an eye out for what might be happening at the time the KP's are happening.

My MP has a similar spec to yours, and also has a ‘KP when away’ issue. With me, it freezes up at the login screen after being woken from sleep (edit: or perhaps just display sleep - can’t recall). Always after I’ve tapped in the first two characters of my password. There’s no KP message on screen, just freezes up to the point where the mouse cursor disappears, and I have to force power off the computer to bring it back to life. Note that it can go days in between doing this, with many successful wakes from sleep (though I do generally put the computer to sleep manually if I‘m going to be away from it). Screen saver (Aerial) seems to work fine (has never crashed during screensaver).

I replaced my clock battery with a brand new BR2032 6 months ago. Northbridge Tdiode is a constant 75C. MacOS 12.5.1.

When you say you ‘have auto sleep disabled’, does this mean your Mac crashes whilst awake, after a period of inactivity? How long, would you estimate? Is the display sleeping? It doesn’t sound like it happens whilst the screensaver is running. Is this at the login screen, or desktop? Do you see the multi-language KP screen, or does your Mac just freeze up?

My MP has screen saver > display sleep > system sleep (I’m away from my computer, so can’t check timings for each). What processes might kick in after e.g. 15 mins of user inactivity? TRIM?

 

[Macschrauber]

Hey all. I'm hoping to get some advice from the OpenCore gurus in the forum on how best to configure a Mac Pro 5,1 with unflashed Navi 10XT card that must quad boot Monterey, Windows, Linux and Mojave. I recently updated to OCLP 0.4.10 (which spoofs MacPro 7,1 by default), but I found out the hard way this breaks Mojave (prohibited symbol at startup). Other than physically removing the disk with OC, is there a way to bypass OC to boot into Mojave natively?

add -no_compat_check to the list of boot-args to run Mojave.

 

[Dewdman42]

My MP has a similar spec to yours, and also has a ‘KP when away’ issue.

Thanks for this feedback!

With me, it freezes up at the login screen after being woken from sleep (edit: or perhaps just display sleep - can’t recall). Always after I’ve tapped in the first two characters of my password. There’s no KP message on screen, just freezes up to the point where the mouse cursor disappears, and I have to force power off the computer to bring it back to life. Note that it can go days in between doing this, with many successful wakes from sleep (though I do generally put the computer to sleep manually if I‘m going to be away from it). Screen saver (Aerial) seems to work fine (has never crashed during screensaver).

For me I come back to my desk after being away or asleep for a while...and the screen is black, but the light on the front of the computer next to the power button is still on. I try clicking the mouse and hitting all manner keys and get no response. when I click the power button (not hold it down), the machine powers off immediately. On boot up I will be presented a panic report...unless of course it freezes during boot up, which it did once without avxpel, then the panic report gets tossed.

I replaced my clock battery with a brand new BR2032 6 months ago. Northbridge Tdiode is a constant 75C. MacOS 12.5.1.

I replaced mine last year. I am doubtful that is the issue, but I am going to try to take out the battery and reset the RTC, I am just trying different things in a methodical way to try to help pinpoint what might be causing it.

When you say you ‘have auto sleep disabled’, does this mean your Mac crashes whilst awake, after a period of inactivity?

yes. I never use SLEEP feature, not for the whole OS and not for the screen either. I have it set to never go to sleep and normally a screensaver comes up. This morning when I got up, the screen saver was performing as expected, for example. So period of inactivity...though to be honest while I'm away, there are various things always happening or could happen a scheduled backup or something like that..hard to say for sure. My web brower is always open to the last thing I was using...and there is no telling what kind of web based javascript activity might be happening, for example. So its not really true inactivity. I can only say it has not KP'd on me while I was here using it, every time I was away from the computer...so might be related to the screen saver.

I am now testing the NoAVXCompression kext to see if that cures the problem.

How long, would you estimate? Is the display sleeping? It doesn’t sound like it happens whilst the screensaver is running. Is this at the login screen, or desktop? Do you see the multi-language KP screen, or does your Mac just freeze up?

See above, when it KP's I see black screen when get up in the morning instead of running screen saver.

My MP has screen saver > display sleep > system sleep (I’m away from my computer, so can’t check timings for each). What processes might kick in after e.g. 15 mins of user inactivity? TRIM?

In my case there are all kinds of things that could happen even while I'm away from the computer. Really hard to say for sure.

 

[mode11]

Seems we have quite different symptoms, though it’s possible there is a similar root cause, as we operate our computers in quite different ways with regards to sleep. It‘s never crashed at a black screen to me, and when I have rebooted after a freeze, it gives me a crash report that refers to the window server.

Edit: it was crashing at a black screen for me on 12.4: #3,707

I’ll pay attention in future to whether the Mac itself is asleep when I go to use it, or whether merely the screens were sleeping.

Certainly it’s been better for me on 12.5.1 than 12.4 (touch wood). I subsequently uninstalled a bunch of unneeded apps and some leftover .plists and launch daemons / agents from various previous apps, which may have helped. It’s currently fairly rare, but annoying and I could potentially lose work.

I have had an intermittent issue with spinning beach balls as well, with applications being unresponsive. Then the problem seems to clear and the machine works normally. As with all intermittent faults, it’s a pain to diagnose. I have a lot of menu items loaded - Hidden Bar, MonitorControl, Mega, DropBox, OneDrive, Little Snitch, LogiTune, Amphetamine, iStat, WD Discovery, Adobe CC, AltStore, Elgato Control Centre, Wacom Preferences, Multi Monitor Wallpaper, Sophos Home, Bitwarden, MiniWOL, XMenu and my work VPN, so it could be one (or more) of those.

 

[358]

Hey guys so in configs in Opencore are the Xeons in 5.1 consistent with ivy bridge or sandy bridge (i know they are neither, but which settings are you using for quirks etc

 

[cdf]

Hey guys so in configs in Opencore are the Xeons in 5.1 consistent with ivy bridge or sandy bridge (i know they are neither, but which settings are you using for quirks etc

If you are doing a manual OpenCore setup, you might want to take a look at the first post of this thread for some recommended settings.

 

[358]

Hi guys, I really need your help as i'm completely stuck and have spent days on this and getting nowhere.

I have cMP 4,1 flashed to 5,1 dual CPU

with titan ridge TB flashed card installed

Running macOS 12.5.1 and OC 8.3

1) i cannot get wifi to work, even after setting to true as per Martin Lo instructions I have tried both stock BCM94322MC and BCM94360CD cards with the same occurrence, it is sowing that wifi is on but cannot see any networks. the bluetooth works with both cards

2) the Apple thunderbolt display only intermittently works properly, meaning on some boots i get video/sound/camera/ports working, on other boots i get just the video and nothing else and yet another version is where everything works except the video.

I attach the config.plist (saves as txt)

Some guidance please.

 

[PeterHolbrook]

i cannot get wifi to work

Are you still using the stock Wi-Fi and Bluetooth components or have you upgraded those to a modern Wi-Fi/Bluetooth module?

 

[358]

Are you still using the stock Wi-Fi and Bluetooth components or have you upgraded those to a modern Wi-Fi/Bluetooth module?

yes using the stock BCM94322MC

 

[PeterHolbrook]

yes using the stock BCM94322MC

I'm not absolutely sure, but in that case you might be out of luck. You might want to upgrade to something like a a BCM94360CD or BCM943602CDP. Bear in mind that the Bluetooth of some of these modules (the second one at least, for certain) will consistently fail on the first boot to Catalina, Big Sur or Monterey after having booted Mojave or earlier. So, if you are multi-booting and have run, for instance, Mojave, you won't have Bluetooth on the first boot to Monterey. That is solved by simply rebooting once more to Monterey. The issue will reappear each time you run Mojave and then go back to Monterey.

 

[358]

I'm not absolutely sure, but in that case you might be out of luck. You might want to upgrade to something like a a BCM94360CD or BCM943602CDP. Bear in mind that the Bluetooth of some of these modules (the second one at least, for certain) will consistently fail on the first boot to Catalina, Big Sur or Monterey after having booted Mojave or earlier. So, if you are multi-booting and have run, for instance, Mojave, you won't have Bluetooth on the first boot to Monterey. That is solved by simply rebooting once more to Monterey. The issue will reappear each time you run Mojave and then go back to Monterey.

I installed a BCM94360CD card with the same occurrence as the stock, it is showing that wifi is on but cannot see any networks. the bluetooth works with both cards

 

[PeterHolbrook]

^Are the antenna wires attached as intended? Is the module receiving power from the motherboard?