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

[CaseySJ]

Thanks, I just opened up the RX580 and looked for a switch and also changed the thermal paste while it was opened, no switch, I will try the CSM and see.

I experienced a similar issue several years ago where an RX 580 with a cryptocurrency VBIOS would not turn on during BIOS. After restoring the original VBIOS, the card performed normally.

 

[Azimuth1]

HELP!

I was trying to rebuild my system from scratch in the occasion of upgrading my GPU from a Radeon VII to a Sapphire Nitro Rx6800XT and I'm trying to install macOS Big Sur (tried with 11.5.1 and 11.4) on a new 500GB WD Black SN750 (bought after reading a Vit9696's post in which it suggest this model for full trim support, as @CaseySJ wrote in your 1st post of this guide) and I keep having panic on IONVMEController ... the sysdef is iMacPro1,1 ... I didn't change a bit my BIOS settings so... I've truly no clue on the possible solution...

 

[CaseySJ]

HELP!

I was trying to rebuild my system from scratch in the occasion of upgrading my GPU from a Radeon VII to a Sapphire Nitro Rx6800XT and I'm trying to install macOS Big Sur (tried with 11.5.1 and 11.4) on a new 500GB WD Black SN750 (bought after reading a Vit9696's post in which it suggest this model for full trim support, as @CaseySJ wrote in your 1st post of this guide) and I keep having panic on IONVMEController ... the sysdef is iMacPro1,1 ... I didn't change a bit my BIOS settings so... I've truly no clue on the possible solution...

There have been some reports of incompatibility with WD SN750 NVMe SSDs. Sometimes moving this SSD to a different M.2 slot can help.

Three suggestions:

1. Try disabling NVMeFix.kext from the Kernel section of OpenCore Configurator. Reboot and check if the problem still occurs.
2. If problem still occurs, try moving the SSD to a different M.2 slot.
3. If that also does not help, physically remove the SN750 and temporarily use a different NVMe SSD or even a cheap SATA 2.5" SSD.
   • If macOS installs and runs smoothly on the temporary SSD, then it might be best to return the WD SN750 and purchase an alternative instead.
   • The NVMe SSDs I recommend are:
     • ADATA SX series
     • Silicon Power
     • Sabrent Rocket series
   • Other brands are also good, but to be safe I would suggest staying away from:
     • Samsung
     • WD

 

[CaseySJ]

Use Vision D already, U are the expert of this Motherbroad, Big Thanks for ur effort safe every Vision D owner!

Thank You Sir! Updated

Because you are also using WD SN750, please try the same suggestions mentioned in the post directly above.

 

[Azimuth1]

There have been some reports of incompatibility with WD SN750 NVMe SSDs. Sometimes moving this SSD to a different M.2 slot can help.

Three suggestions:

1. Try disabling NVMeFix.kext from the Kernel section of OpenCore Configurator. Reboot and check if the problem still occurs.
2. If problem still occurs, try moving the SSD to a different M.2 slot.
3. If that also does not help, physically remove the SN750 and temporarily use a different NVMe SSD or even a cheap SATA 2.5" SSD.
   • If macOS installs and runs smoothly on the temporary SSD, then it might be best to return the WD SN750 and purchase an alternative instead.
   • The NVMe SSDs I recommend are:
     • ADATA SX series
     • Silicon Power
     • Sabrent Rocket series
   • Other brands are also good, but to be safe I would suggest staying away from:
     • Samsung
     • WD

ok thanks 1st of all @CaseySJ !!!

I report back: I have also my old Samsung 970 Pro and I had the same issue . Which weird because I bought that before Catalina was out and never had a problem with it and MacOS.

Disabling NVMEFix.kext doesn't help at all.
I tried also my old GPU (Sapphire Radeon VII) instead of the new RX6800XT but it didn't help at all.

So I got an old Kingston SSD 120GB as you suggested and finally I was able to pass over the verbose initial phase of booing up, reached the graphical interface, format in APFS the Kingston SSD (I previously erase it to have it back to its initial stage) and then I got the message in the pic attached.

Useless to say I remade the USB stick for three times and I also re-downloaded the OS (with gibMacOS) two times, and always got the same error... any further hint?

 

[suren6791]

Some RX580s have a BIOS switch to flip between OC and Silent modes. If yours has a switch, try both positions.

Also try enabling CSM Support in BIOS.

Beyond that I’m not sure what else to suggest.

Thanks mate, CSM did the trick.

 

[suren6791]

I experienced a similar issue several years ago where an RX 580 with a cryptocurrency VBIOS would not turn on during BIOS. After restoring the original VBIOS, the card performed normally.

Yeah I'm gonna try that this evening

 

[nss]

• Does this monitor support HDR (high dynamic range)?
• If so, is HDR turned on in System Preferences --> Displays?
• Are you using HDMI-to-HDMI or DisplayPort-to-DisplayPort connection?
• Are there any adapters/converters involved, such as DP-to-HDMI or DP-to-DVI, etc.?

1. Yes, it supports HDR
2. I don't see it in System Preferences -> Displays. But it's disabled in my monitor options menu. It says HDR Mode -> Off.
3. I'm using a DisplayPort-to-DisplayPort connection.
4. No adapters/converters involved whatsoever.

 

[CaseySJ]

ok thanks 1st of all @CaseySJ !!!

I report back: I have also my old Samsung 970 Pro and I had the same issue . Which weird because I bought that before Catalina was out and never had a problem with it and MacOS.

Disabling NVMEFix.kext doesn't help at all.
I tried also my old GPU (Sapphire Radeon VII) instead of the new RX6800XT but it didn't help at all.

So I got an old Kingston SSD 120GB as you suggested and finally I was able to pass over the verbose initial phase of booing up, reached the graphical interface, format in APFS the Kingston SSD (I previously erase it to have it back to its initial stage) and then I got the message in the pic attached.

Useless to say I remade the USB stick for three times and I also re-downloaded the OS (with gibMacOS) two times, and always got the same error... any further hint?

Sometimes we can fix this problem by setting csr-active-config in NVRAM section of OpenCore Configurator to 67000000 and rebooting / re-starting the macOS update. Please see:

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

** Calling all Owners of Good Quality Hackintosh Builds ** We would like to add your OpenCore EFI folders to the HackinDROM database! Do you have a well configured Hackintosh based on a motherboard that is not listed below? ASRock X570 Taichi Asus X99 Deluxe II Gigabyte B550 Vision D Gigabyte...

www.tonymacx86.com

 

[Azimuth1]

Sometimes we can fix this problem by setting csr-active-config in NVRAM section of OpenCore Configurator to 67000000 and rebooting / re-starting the macOS update. Please see:

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

** Calling all Owners of Good Quality Hackintosh Builds ** We would like to add your OpenCore EFI folders to the HackinDROM database! Do you have a well configured Hackintosh based on a motherboard that is not listed below? ASRock X570 Taichi Asus X99 Deluxe II Gigabyte B550 Vision D Gigabyte...

www.tonymacx86.com

Unfortunately, this time it didn't work!

The weird thing is that in the subsequent reboot I used the ClearNVRAM EFI module of OC, and, then, I got what you can see in the first pic attached. Then, after another reboot, I got what you see in the 2nd pic attached. In the 3rd reboot it passed the verbose initial phase, and I got the graphical interface. But, during the install process, it stopped again with the message of damaged installer... I don't know... but I have the feeling it's an NVRAM issue. But I cannot resolve it!