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

[brousseau6933]

NVMe is Samsung 970 Pro. Never heard of issues with it.
During the boot the HDD led on the case flashes like crazy, so something is definitely happening.

Well, looks it’s affected by the TRIM bug, see here: https://github.com/dortania/bugtracker/issues/192

If you use OC, you could try to disable TRIM just to confirm.

 

[phrfpeixoto]

Well, looks it’s affected by the TRIM bug, see here: https://github.com/dortania/bugtracker/issues/192

If you use OC, you could try to disable TRIM just to confirm.

YEP! That did the trick!
I've set SetApfsTrimTimeout to 0 and it now boots instantly!
What are the consequences of not having TRIM?

 

[brousseau6933]

YEP! That did the trick!
I've set SetApfsTrimTimeout to 0 and it now boots instantly!
What are the consequences of not having TRIM?

It could potentially slow down and affects the lifespan of the NVMe if you write a lot of stuff so I would advise:

1 - to replace it with a WD Black something (750, 850) or:
2 - if not within your budget, reserve at least 10-15% of free space (make a free space partition) for over-provisioning so, at least, the integrated controller could process its own data garbage collection.


TRIM + garbage collection are essential (IMHO) for any SSD so, in my case, I would go for 1.

 

[MacMarshall]

When I changed from Clover to OC I think my Fractal R6 USBT SSDTs got replaced, front panel USB-C is working with some but not all USB 3 devices (works with drive enclosures and USB drives, but not an Insta360 camera, and I think maybe I can't boot to EFI or OS on a drive plugged in to that port).

Should I grab any of the Fractal R6 files from Post 1 and drop them into my EFI?

The instructions in Post 1 also referenced a SSDT for a RX 580 in slot 1, which I have, and had, but that file is not in the zip bundle.

Here is what is in my EFI now (running OC 0.8.9, Ventura 13.2.1):

 

[phrfpeixoto]

It could potentially slow down and affects the lifespan of the NVMe if you write a lot of stuff so I would advise:

1 - to replace it with a WD Black something (750, 850) or:
2 - if not within your budget, reserve at least 10-15% of free space (make a free space partition) for over-provisioning so, at least, the integrated controller could process its own data garbage collection.


TRIM + garbage collection are essential (IMHO) for any SSD so, in my case, I would go for 1.

Can I simply re-enable TRIM and suck it up slow boot times? Maybe try to update the firmware?

It is certainly possible to do an in-place upgrade from Monterey to Ventura, but we must first do this:

• Make a full bootable backup of Monterey. Things can fail during major (and even minor) macOS upgrades!! We *must* have a full backup to save us!
• Update to OpenCore 0.8.8. This can be done with HackinDROM app (click here for details)
• Check if SecureBootModel in config.plist -> Misc -> Security is set to Default (not Disabled)
• Check if SIP is enabled in config.plist -> NVRAM section (csr-active-config should be 00000000)
• Then reboot Monterey to make sure it still works properly

Now you're ready to perform in-place upgrade to Ventura.

@CaseySJ I did the update, and now I have been experiencing reboots. I think it's when the computer tries to sleep. It's really random kernel panics. Added a log

I did have to change the SecureBootModel and SIP configs you mentioned.
I also had to change the following settings as per HackinDROM/OCC validation:

Also, HackinDROM updated my OC to 0.8.9 instead of 0.8.8.
I'm attaching my EFI here. I wonder if you need specific logs...

Spoiler: Kernel panic

panic(cpu 4 caller 0xffffff800790a046):  initproc exited -- exit reason namespace 2 subcode 0xa description: none

Thread 1 crashed

RAX: 0x0000600000a12108, RBX: 0x0000600000a12100, RCX: 0x0000600000a2d080, RDX: 0x0000600000a156b8
RSP: 0x000070000a643770, RBP: 0x000070000a643790, RSI: 0x0000600000a12100, RDI: 0x0000000000000000
R8:  0x0000000000000000, R9:  0x0000600002850b40, R10: 0x00000000000a3a7c, R11: 0x0060000000000000
R12: 0x0000000000000000, R13: 0x0000600002850b40, R14: 0x00007f81f6010400, R15: 0x0000600000a12100
RFL: 0x0000000000010202, RIP: 0x000000010380eac0, CS:  0x000000000000002b, SS:  0x0000000000000023

Thread 0: 0xffffff9558f580c8
    0x00007ff805c432d6
    0x00007ff805b0e3e6

Thread 1: 0xffffff95555a90c8
    0x000000010380eac0
    0x00000001038042fd
    0x000000010381ff3b
    0x00007ff805afca44
    0x00007ff805aff500
    0x00007ff805b10dff
    0x00007ff805b02964
    0x00007ff805b035b4
    0x00007ff805b0dad7
    0x00007ff805c78ce3
    0x00007ff805c77c67

Thread 2: 0xffffff9556e540c8
    0x00007ff805c3ecb2
    0x00007ff805c77c67

Thread 3: 0xffffff955750bb30
    0x00007ff805c3d53e
      Could not read LR from frame at 0x000070000a6c6f18

Thread 4: 0xffffff9555a910c8
    0x00007ff805c3d53e
      Could not read LR from frame at 0x000070000a749f18

Thread 5: 0xffffff9556d2cb30
    0x00007ff805c77c58

Thread 6: 0xffffff9556d0eb30
    0x00007ff805c3d53e
    0x00007ff805afd3d7
    0x00000001037dff71
    0x00007ff805c7c259
    0x00007ff805c77c7b


Mac OS version:
22D68

Kernel version:
Darwin Kernel Version 22.3.0: Mon Jan 30 20:42:11 PST 2023; root:xnu-8792.81.3~2/RELEASE_X86_64
Kernel UUID: 10E5D254-4A37-3A2A-B560-E6956A093ADE
roots installed: 0
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: YES
Panic diags file available: YES (0x0)

 

[CaseySJ]

Can I simply re-enable TRIM and suck it up slow boot times? Maybe try to update the firmware?

Unfortunately this won’t help because macOS does not support the Samsung NVMe controller.

@CaseySJ I did the update, and now I have been experiencing reboots. I think it's when the computer tries to sleep. It's really random kernel panics. Added a log

Could there be any third party drivers that are not compatible with Ventura? If Monterey was stable then Ventura should also be stable unless there’s an incompatible third party component installed.

If the Monterey system was itself upgraded from an earlier version of macOS, the chances of an incompatible component are higher.

One option is to perform a fresh install of Ventura on a spare SSD or by creating a new APFS volume on an existing SSD. If the fresh install is stable, then we know that a third party component is affecting the main install.

BIOS version can also make a difference. We recommend F9g or F9i.

I did have to change the SecureBootModel and SIP configs you mentioned.
I also had to change the following settings as per HackinDROM/OCC validation:

View attachment 564030
Also, HackinDROM updated my OC to 0.8.9 instead of 0.8.8.
I'm attaching my EFI here. I wonder if you need specific logs...

OpenCore 0.8.9 is okay. Those LoadEarly warnings need to be fixed by simply editing the config.plist -> UEFI -> Drivers section.

 

[6rollo6]

Recently I'm getting random crashes at boot time, error report and EFI folder (serials removed) attached.
Maybe someone can have a look at it and point me in the right direction? Thanks.

 

[phrfpeixoto]

Unfortunately this won’t help because macOS does not support the Samsung NVMe controller.

I did re-enable it, and it's back to slow AF. What triggers me is that I have been using this rig for a good portion of 5 years now, and this didn't use to happen.

Could there be any third party drivers that are not compatible with Ventura? If Monterey was stable then Ventura should also be stable unless there’s an incompatible third party component installed.

If the Monterey system was itself upgraded from an earlier version of macOS, the chances of an incompatible component are higher.

One option is to perform a fresh install of Ventura on a spare SSD or by creating a new APFS volume on an existing SSD. If the fresh install is stable, then we know that a third party component is affecting the main install.

Yes. I have been doing in-place updates for the past few versions.
Is there a way that I can list all installed drivers somehow (my EFI is attached, and I haven't really added any drivers to it)? I wouldn't like to perform a fresh install, as that would require A LOT of time re-configuring all the software I need, so that would be my last resource.

BIOS version can also make a difference. We recommend F9g or F9i.

I believe I'm on F9b. Can I safely update to F9i without worrying about the CFG lock thing? I did that waaaay ago...

OpenCore 0.8.9 is okay. Those LoadEarly warnings need to be fixed by simply editing the config.plist -> UEFI -> Drivers section.

I did that.

 

[trs96]

What triggers me is that I have been using this rig for a good portion of 5 years now, and this didn't use to happen.

The Samsung drives will work fine with HFS+ but not with APFS. Especially since Monterey was released. What many people do is clone their Samsung drive to a WD Black NVMe and then boot from that. Prices have come way down the last few months so it's very inexpensive to do this.

 

[phrfpeixoto]

The Samsung drives will work fine with HFS+ but not with APFS. Especially since Monterey was released. What many people do is clone their Samsung drive to a WD Black NVMe and then boot from that. Prices have come way down the last few months so it's very inexpensive to do this.

Yeah, I think I'll have to bite the bullet and do that. Unfortunately, it's not so inexpensive where I live.