Jump to content
9 posts in this topic

Recommended Posts

Hi

I updated my z170-deluxe build from Big Sur 11.6.1 to Monterey 12.2, after restarting it stuck at apple logo with an empty bar(verbos screenshot is attached). it does however let the os load randomly once every two or three attempts (and it's Monterey, apparently) but one of my hard disks can't be identified and bluetooth doesn't work.

I'm using clover 5142 which I also attached to this post and installed Monterey using an old version I had downloaded long ago but never got the chance to install.

I may have to go for a clean install but I need to know for sure what's wrong first. Thanks in advance.

photo_2022-03-29 16.28.28.jpeg

CLOVER.zip boot-log.rtf

Link to comment
https://www.insanelymac.com/forum/topic/351291-monterey-updated-with-problems/
Share on other sites

At first glance, looks like AirportBrcmFixup is most likely the culprit. What model of Broadcom wifi module is being used here? You mentioned OS boots intermittently...is this behavior persistent when AirportBrcmFixup kext is omitted from kexts folder?

Edited by aben

I am not sure about your issue. I have similar hardware and I have similar stop in Monterey with kext BlueToolFixup. 

Try to exclude it and other kexts one by one to find a wrong kext.

Clover GUI permit you to temporary disable any kext from folders Other and enable kext from folder Off.

Press "Space" and see something like this

Screenshot 2022-03-29 at 19.14.06.png

  • Like 1

I moved all the kexts except Lilu, virtualsmc, whatevergreen, AppleALC and two usb map kexts to library/extendions, and now everything's fine except bluetooth, but this time I know exactly what the problem is. Monterey has detected the wrong chipset (it has detected the right one as well but it doesn't work):

Screen Shot 2022-03-29 at 10.27.36 PM.png

Screen Shot 2022-03-29 at 10.28.14 PM.png

@Mr. Teleporter 

Quite strange coz as per your screenshot, the device ID shown [0b05:180a] appears to be supported by BrcmPatchRAM and its plugins however no firmware is being uploaded to the device for some weird reason. You could try warm booting from Windows into macOS after successful upload of BT firmware on Windows, maybe try connecting a device or two if available, this approach sometimes works as a one-way ticket but also depends on your system's firmware implementation.

Note: Even if you do happen to get bluetooth working on Monterey with this non-native card, be advised the overall functionality will be quite limited compared to Big Sur due to massive changes in Monterey's BT stack which is why BlueToolFixup was developed in the first place to help alleviate issues around 3rd party card's compatibility with macOS 12 however the current state of support is still partially broken due to complexity of the new stack. You will still require, either a Fenvi BCM94360NG or one of Apple's original Airport cards listed here if you wish to have the full native OOB experience on macOS 12 however getting these cards adapted to a non-M.2 PCIe slot can be quite dicey, sometimes even impossible depending on the situation.

Edited by aben

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...