Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Feartech

Moderator
Joined
Aug 3, 2013
Messages
24,214
Motherboard
Asus N752VX-OpenCore
CPU
i7-6700HQ / HM170
Graphics
HD 530 1920 x 1080
Mac
  1. iMac
Mobile Phone
  1. iOS
I've also removed your serial numbers from the config.plist I posted above.
may be worth disabling:
Code:
<key>AppleDebug</key>
            <true/>
            <key>ApplePanic</key>
            <true/>

and removing:
keepsyms=1 debug=0x100
which should result in a quicker boot
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,213
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
** Experiencing Slow Boot Times in Monterey? **

Please try this and report your results:
  • In Terminal, type:
Bash:
log show --last boot | grep "trims took"
  • Give it a few seconds to run then press CTRL-C to stop.
  • Post the output.
Here's the result from my Z490 Vision D with release version of Monterey:
Code:
kernel: (apfs) spaceman_scan_free_blocks:3153: disk3 scan took 1.913441 s, trims took 1.786507 s
kernel: (apfs) spaceman_scan_free_blocks:3153: disk2 scan took 2.299866 s, trims took 2.262432 s
Note that both operations took less than 3 seconds.
 
Joined
Jul 22, 2016
Messages
250
Motherboard
Gigabyte B550 Vision D
CPU
Ryzen 7 3700X
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
  4. Mac Pro
Mobile Phone
  1. iOS
@CaseySJ @manfriday

I have noticed a significant increase in boot times with my Z390 Designare (flashed TB chip) with every beta release of Monterey. I thought with the final release version there might be an improvement, but that is not the case.

I have two 500 GB Samsung 970 EVO SSDs. I confirmed both have the latest firmware. One for macOS and one for Windows. I have never experienced any slow boot issues with any OS I have run.

I have an external TB3 enclosure that contains a 1TB Samsung 970 EVO SSD, with the latest firmware, that I plug into the Z390's TB port to hold bootable backups of Big Sur and Monterey. I decided to also time the boot time using TB.

All boot times listed are using the same EFI folder using OC 0.7.4. Tweaks suggested in prior thread posts to improve boot times were tried, but made no significant difference:

Big Sur 11.6 - 34 Seconds
Monterey 12.0.1 (internal SSD) - 68 Seconds
Monterey 12.0.1 (external TB3) - 34 Seconds

During the Monterey boot using the internal SSD, booting stalls at one point for about 35 seconds. This accounts for all the additional boot time. This screen shot shows the stall point. A Mac expert may be able to decipher why this is happening.

Boot Stall.JPG

When booting Monterey from the TB external drive it flies right through this code.

Here's the System Report for the TB Device Tree.

Thunderbolt.jpg

Here's the System Report for the NVMExpress:

NVMExpress.jpg

This info seems to indicate that Monterey has introduced some compatibility issue between the NVMe board hardware and the Samsung 970 EVO.

What's a surprise to me is the boot performance of the Samsung 970 EVO over TB3.

Boot times are not very important for me as it is easy enough to sleep the system.
 
Joined
Mar 2, 2011
Messages
159
Motherboard
Gigabyte Designare Z390
CPU
i9-9900K
Graphics
RX 5700 XT
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
  4. Mac Pro
Mobile Phone
  1. iOS
These cards can sometimes be tricky. We should try moving them to a different PCIe slot, enabling or disabling CSM Support, performing CMOS Reset (then configure BIOS parameters again), etc. Before giving up on the card you have, it would be good to go through some or all of these steps.

Unfortunately there isn’t a newer version of the Fenvi that is natively supported in macOS. I do hope they release a Broadcom-based WiFi 6 / BT 5.x card though.
CSM on/off didn't change anything for me unfortunately. I also tried Platform Power Management in BIOS enabled/disabled, which also doesn't see to affect anything.

I realize that this card should work natively, but I decided to add this kext - https://github.com/acidanthera/AirportBrcmFixup/releases/tag/2.1.3
to OC 0.7.4.

Now Airdrop works for some reason. Sees my devices, initiates the transfer about 80% of the time. Weird.

Not sure what's going on, but it seems that the new kexts work?
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,213
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
...
Big Sur 11.6 - 34 Seconds
Monterey 12.0.1 (internal SSD) - 68 Seconds
Monterey 12.0.1 (external TB3) - 34 Seconds
...
Can you run this command in Terminal:
Bash:
log show --last boot | grep "trims took"

... and press CTRL-C after about 15 seconds. I'd like to see if there are any trim operations that consume either 68 or 34 seconds to account for the delays you experienced.
 
Joined
Jul 3, 2010
Messages
295
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900K
Graphics
RX 5700 XT
Mac
  1. MacBook Pro
  2. Mac mini
  3. Mac Pro
Mobile Phone
  1. iOS
Please post screenshot of OpenCore Configurator --> Kernel. This will show the kext configuration.
Screen Shot 2021-10-26 at 7.07.07 PM.png

Please note, my machine won't boot if I enable the IntelBluetoothinjector. It's been this way from the outset. Thanks.
 
Joined
Jan 21, 2018
Messages
227
Motherboard
Gigabyte Z390 Aorus Xtreme
CPU
i9-9900K
Graphics
Vega 64
** Experiencing Slow Boot Times in Monterey? **

Please try this and report your results:
  • In Terminal, type:
Bash:
log show --last boot | grep "trims took"
  • Give it a few seconds to run then press CTRL-C to stop.
  • Post the output.
Here's the result from my Z490 Vision D with release version of Monterey:
Code:
kernel: (apfs) spaceman_scan_free_blocks:3153: disk3 scan took 1.913441 s, trims took 1.786507 s
kernel: (apfs) spaceman_scan_free_blocks:3153: disk2 scan took 2.299866 s, trims took 2.262432 s
Note that both operations took less than 3 seconds.
Hi @CaseySJ... hope you are fine....

I'm definitively with problems on my boot time on Monterey, which is taking way too long... here's my output:

kernel: (apfs) spaceman_scan_free_blocks:3153: disk3 scan took 204.819595 s, trims took 204.469358 s
kernel: (apfs) spaceman_scan_free_blocks:3153: disk6 scan took 4.581236 s, trims took 4.018021 s
kernel: (apfs) spaceman_scan_free_blocks:3153: disk4 scan took 42.122163 s, trims took 41.525545 s
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,213
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
View attachment 532134
Please note, my machine won't boot if I enable the IntelBluetoothinjector. It's been this way from the outset. Thanks.
Have you tried replacing BlueToolFixup.kext in EFI/OC/Kexts folder with the one in this post:
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,213
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Hi @CaseySJ... hope you are fine....

I'm definitively with problems on my boot time on Monterey, which is taking way too long... here's my output:

kernel: (apfs) spaceman_scan_free_blocks:3153: disk3 scan took 204.819595 s, trims took 204.469358 s
kernel: (apfs) spaceman_scan_free_blocks:3153: disk6 scan took 4.581236 s, trims took 4.018021 s
kernel: (apfs) spaceman_scan_free_blocks:3153: disk4 scan took 42.122163 s, trims took 41.525545 s
Hello @ummario,

Are you using Samsung NVMe SSD? If so, which model?

In Terminal can you please type diskutil list and post the output? Disk3 is taking way too much time!
 
Joined
Jul 22, 2016
Messages
250
Motherboard
Gigabyte B550 Vision D
CPU
Ryzen 7 3700X
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
  4. Mac Pro
Mobile Phone
  1. iOS
Can you run this command in Terminal:
Bash:
log show --last boot | grep "trims took"

... and press CTRL-C after about 15 seconds. I'd like to see if there are any trim operations that consume either 68 or 34 seconds to account for the delays you experienced.
@CaseySJ

Trims Took.jpg

Yes, there was a long trim for disk3, the Monterey 970 EVO boot drive, and disk4 the external 970 EVO TB3 boot drive.

So Monterey trim is burning up boot time. This is even with the -1 changed to 999 in config.plist. Same drives in Big Sur apparently take much less trim time.
 
Top