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

[CaseySJ]

@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.

 

[Stork]

It would be good to check trim time anyway, as follows:

log show --last boot | grep “trims took”

Press CTRL-C after a few seconds to stop the check.

Didn't work for me using Monterey.

log show --last boot | grep “trims took”
grep: took”: No such file or director

 

[CaseySJ]

Didn't work for me using Monterey.

log show --last boot | grep “trims took”
grep: took”: No such file or director

Oops, that was my iPad that replaced standard quotation mark (") with open-and-close quotation marks.

Please try:

log show --last boot | grep "trims took"

 

[Stork]

Oops, that was my iPad that replaced standard quotation mark (") with open-and-close quotation marks.

Please try:

log show --last boot | grep "trims took"

Much better. I should have noticed that. (I've just refilled my COFFEE!! cup to get more morning CAFFEINE!)

Here's my result for the two Sabrient Rocket Q and an emtpy, formatted Sabrient SSD:

2021-12-11 08:36:59.499008-0500 0x7b3      Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk3 scan took 4.906053 s, trims took 4.516540 s
2021-12-11 08:37:09.181678-0500 0x97e      Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk2 scan took 4.819900 s, trims took 4.606822 s
2021-12-11 08:37:31.491819-0500 0x12fa     Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk7 scan took 0.281385 s, trims took 0.273405 s

I'm currently running Monterey on disk3.

 

[CaseySJ]

Much better. I should have noticed that. (I've just refilled my COFFEE!! cup to get more morning CAFFEINE!)

Here's my result for the Sabrient Rocket Q:

2021-12-11 08:36:59.499008-0500 0x7b3      Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk3 scan took 4.906053 s, trims took 4.516540 s
2021-12-11 08:37:09.181678-0500 0x97e      Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk2 scan took 4.819900 s, trims took 4.606822 s
2021-12-11 08:37:31.491819-0500 0x12fa     Default     0x0                  0      0    kernel: (apfs) spaceman_scan_free_blocks:3153: disk7 scan took 0.281385 s, trims took 0.273405 s

Looks good -- all normal.

 

[sbushman18]

Any issues with my RX570, big performances for me on Monterey 12.0.1 & OpenCore 0.7.4, see my Geekbench results

That's what I am aiming for. Yours look great. I have two cards here, a RX570 Nitro Plus and RX 570 Gaming X. Both do around 30-33 in Open CL and should be closer to 40. Not sure why.

Cards were looking just fine in Windows.

I am using OC 0.7.6 on Monterey and 0.7.5 on Catalina. Scores are the same regardless of which boot drive I use.

 

[suren6791]

It would be good to check trim time anyway, as follows:

log show --last boot | grep "trims took"

Press CTRL-C after a few seconds to stop the check.

After doing doing CTRL-C and the reboot it now sits here for the same time, just under a minute. I tried turning off kexts and seeing if that helps but it does not. In my Spare drive I installed Big Sur again and that boots within seconds.

 

[CaseySJ]

After doing doing CTRL-C and the reboot it now sits here for the same time, just under a minute. I tried turning off kexts and seeing if that helps but it does not. In my Spare drive I installed Big Sur again and that boots within seconds.

What was the result from the "trims took" log entry? How long did the trim operation take?

 

[suren6791]

What was the result from the "trims took" log entry? How long did the trim operation take?

Where would I find the log? After pressing CTRL-C it just moved through verbose and sat at this place I posted above. It now does not get stuck at trim but bootroot now.

 

[CaseySJ]

Where would I find the log? After pressing CTRL-C it just moved through verbose and sat at this place I posted above. It now does not get stuck at trim but bootroot now.

Did you open Terminal and type in the "log show" command? The output from that command tells us the trim time.