Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

This just showed up on my Z490 Vision D hack. Should I reinstall 12.0.1? The OSX side of this Dual boot machine has been wildly unstable. OSX 12.0.1 freezes almost daily. The Windows 11 side runs like a champ w/ no issues. I'm convinced it's a software / config issue. I just update OpenCore to 0.7.6 and the only change I made to Casey's EFI was to remove boot argument agdpmod=pikera (for my Vega 64) and set AAPL,ig-platform-id to 0300C89B (for headless Comet Lake iGPU). Any advice would be appreciated I've been troubleshooting this build for a week and I'm stumped. My BIOS is exactly as specified by the guide, I'm on Firmware F5.
Just an update for all those following from home...

I flashed my BIOS from F5 to F20 as recommended by "lewys" and all my troubles have gone away.
Monterey 12.0.1 has been up and running flawlessly ever since. My Bluetooth issues have sorted themselves out as well.

For the record my Z490 Vision D has an Intel Core i9-10850K, 32GB of G.Skill Trident Z Neo RAM @ 3600MHz, WD_BLACK 500GB SN750 NVMe SSD, CORSAIR RM850X 850W Power Supply, Radeon Vega 64 Video Card and a Be Quiet Dark Rock Pro 4 (+ 3 case fans) to keep things chill. (it's idling at 34 degrees C)

I'm on OpenCore 0.7.6 running Monterey 12.0.1 & Windows 11.

Big Thanks to "Casey SJ" for the guide and a special shout out to "Lewys" for tip on F20...
 

Attachments

  • Screen Shot 2021-12-11 at 5.42.17 PM.png
    Screen Shot 2021-12-11 at 5.42.17 PM.png
    558.8 KB · Views: 36
@mntbighker

The Asus BT400 is using a Broadcom Bluetooth module. In the Kernel section of your confit.plist are three kexts called:
  • BlueToolFixup
  • BrcmFirmwareData
  • BrcmPatchRAM3
Are all three of these enabled? We should enable them.
For some reason I thought the OC 0.7.5 downloaded from this thread would have those enabled already. Presumably now I can use either the BT400 or the on-board. But with the BT400 plugged in and the built-in with no antenna attached, the built-in seems to be the active interface.

edit: Scratch that, unplugging the BT400 kills BT. By the desc. in the System Info it appeared to me the built-in was the active interface. So if the system is stable, and it still dual boots with Win11 I think I'm good. I guess next I should update to 0.7.6.
 
Last edited:
For some reason I thought the OC 0.7.5 downloaded from this thread would have those enabled already. Presumably now I can use either the BT400 or the on-board. But with the BT400 plugged in and the built-in with no antenna attached, the built-in seems to be the active interface.

edit: Scratch that, unplugging the BT400 kills BT. By the desc. in the System Info it appeared to me the built-in was the active interface. So if the system is stable, and it still dual boots with Win11 I think I'm good. I guess next I should update to 0.7.6.
The built-in device is an Intel module on HS14. We have disabled that USB port so it will not show up in macOS. Intel Bluetooth is not natively supported in macOS, but works with OpenIntelWireless drivers which are installed separately.
 
Did you open Terminal and type in the "log show" command? The output from that command tells us the trim time.
Below is what I get from Terminal
Screen Shot 2021-12-12 at 12.25.23 PM.png
 
Below is what I get from Terminal
View attachment 536985
We can see that disk4 took 61 seconds, but disk3 took only 6.6 seconds. If they are both Crucial M.2 then I'll need to add a warning against their use in Monterey. Which Crucial M.2 drives are you using (the model name)?
 
We can see that disk4 took 61 seconds, but disk3 took only 6.6 seconds. If they are both Crucial M.2 then I'll need to add a warning against their use in Monterey. Which Crucial M.2 drives are you using (the model name)?
Below are the 3 M.2 that I have. The 2TB is the one for Monterey, the 1TB is Windows 11 and the Kingston 500gig is Big Sur now.
Screen Shot 2021-12-12 at 12.35.22 PM.png

Screen Shot 2021-12-12 at 12.35.15 PM.png

Screen Shot 2021-12-12 at 12.35.02 PM.png
 
We can see that disk4 took 61 seconds, but disk3 took only 6.6 seconds. If they are both Crucial M.2 then I'll need to add a warning against their use in Monterey. Which Crucial M.2 drives are you using (the model name)?
I noticed that the actual M.2 is disk 2 but the container disk is disk 4, maybe that is the issue
Screen Shot 2021-12-12 at 12.39.16 PM.png
Screen Shot 2021-12-12 at 12.39.29 PM.png
 
I noticed that the actual M.2 is disk 2 but the container disk is disk 4, maybe that is the issue
The best way to sort this out is as follows (in Terminal):
Bash:
log show --last boot | grep "trims took"
(then press CTRL-C after 5 or so seconds)

diskutil list
Then simply post the output.
 
The best way to sort this out is as follows (in Terminal):
Bash:
log show --last boot | grep "trims took"
(then press CTRL-C after 5 or so seconds)

diskutil list
Then simply post the output.
Is this what you need
Screen Shot 2021-12-12 at 2.35.06 PM.png
 
Back
Top