Contribute
Register

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

...
The Big Sur Disk is showing up on the OpenCore Boot GUI named as 'Preboot'. Also when I boot Catalina I just see a folder called update and no Big Sur Disk.
Both of these are normal. Big Sur introduces enhancements to APFS that are not recognized in Catalina.
I am still seeing my Catalina Disk named a 'parallels' on the OpenCore Boot GUI.

Where are these strange names being stored?
Probably good to raise this issue over at Insanely Mac in the OpenCore thread.
 
I have all three M2 slots filled and I am having constant problems with boot. The vision D hangs either right before the bios setup message or after. I usually need to turn off the power supply to get it to boot. At first boot in the morning it starts up normally. From cpu slot to last; Samsung 970 1 TBwindows, Sabret 2 TB, Catalina, Samsung 970 2TB, AV drive. Last PCEI Slot, M2adapter with 500GB Sabret NVMe.
Have you contacted Gigabyte Tech Support?

I received a new Silicon Power 512GB NVMe SSD couple of days ago that I can install into the M2A slot and see what happens.

Current Config:
  • M2A - empty
  • M2M - Silicon Power 256GB NVMe (Big Sur)
  • M2P - Sabrent Rocket 256GB NVMe (Catalina)
New Testing Config (for later today):
  • M2A - Silicon Power 512GB NVMe
  • M2M - Silicon Power 256GB NVMe (Big Sur)
  • M2P - Sabrent Rocket 256GB NVMe (Catalina)
 
Last edited:
...
From cold boot to Picker Menu (I've got the splash screen disabled) : 20s
From OC to Login: 44s
From Login to Desktop: <15s

According the the logs the main culprit appears to be IONVMeFamily (23s). I'm using a 1tb 970 evo for the Mac side of things - could that be the issue?
Hello @crossmoid,

Can you please post the subsection of log messages that points to IONVMeFamily.
 
I have all three M2 slots filled and I am having constant problems with boot. The vision D hangs either right before the bios setup message or after. I usually need to turn off the power supply to get it to boot. At first boot in the morning it starts up normally. From cpu slot to last; Samsung 970 1 TBwindows, Sabret 2 TB, Catalina, Samsung 970 2TB, AV drive. Last PCEI Slot, M2adapter with 500GB Sabret NVMe.
Have you contacted Gigabyte Tech Support?

I received a new Silicon Power 512GB NVMe SSD couple of days ago that I can install into the M2A slot and see what happens.

Current Config:
  • M2A - empty
  • M2M - Silicon Power 256GB NVMe (Big Sur)
  • M2P - Sabrent Rocket 256GB NVMe (Catalina)
New Testing Config (for later today):
  • M2A - Silicon Power 512GB NVMe
  • M2M - Silicon Power 256GB NVMe (Big Sur)
  • M2P - Sabrent Rocket 256GB NVMe (Catalina)
Well, I'm pleased to report that the system is working perfectly fine with all three M.2 slots occupied. Just had to perform a Reset NVRAM (always a good idea when changing disk configuration).

This system also has:
  • AMD RX 580 in PCIe slot 1
  • Fenvi FV-T919 in short slot
  • GC-Titan Ridge Thunderbolt 3 card in bottom PCIe slot
In addition:
  • Silicon Power 256GB SATA SSD connected to internal SATA port (Windows 10)
  • Silicon Power 256GB SATA SSD connected to internal SATA port (Kubuntu 20.04 Linux)
So it's running:
  • Catalina
  • Big Sur
  • Windows
  • Linux
Be sure to remove the blue plastic wrap behind each of the M.2 covers/heat sinks.

All slots occupied.jpg

Screen Shot 2020-08-15 at 10.45.45 AM.pngScreen Shot 2020-08-15 at 10.49.56 AM.png
 
Last edited:
Hey
I'm planning to buy a new PC and to dual boot Windows for gaming and macOS for programming
So I just wanted to make sure my components are compatible and that it would be suitable for this guide before I order :)

CPU i5 10600K 4.1Ghz Turbo 4.8Ghz 12MB Cache TRAY
CPU Cooler NH-D15 Chromax Black 140MM 1500RPM 82CFM Model
Motherboard Gigabyte Z490 Vision D LGA1200 10th Gen Only DDR4 HDMI
RAM Ripjaws V Series 16GB 8GBX2 KIT DDR4 3600Mhz CL16
GPU Gigabyte Gaming OC RX 5700 XT 8GB GDDR6 HDMI 3xDP
SSD (Windows) XPG AS40G-512GT-C XPG Spectrix S40G RGB 3500MB 512GB M.2 NVMe
SSD (macOS) Samsung MZ-V7S500BW 970 EVO Plus Series 500GB M.2 NVMe
HDD (Share for both OS) Toshiba P300 2TB 7200RPM 64MB SATA 3.5" 6.0GBPS
Case NX800 RGB 1X120MM ARGB + 2X200MM ARGB Mid Tower
PSU Corsair RM750x RMx Series 750W Active PFC with 135MM fan


Thanks!
 
Hey
I'm planning to buy a new PC and to dual boot Windows for gaming and macOS for programming
So I just wanted to make sure my components are compatible and that it would be suitable for this guide before I order :)

CPU i5 10600K 4.1Ghz Turbo 4.8Ghz 12MB Cache TRAY
CPU Cooler NH-D15 Chromax Black 140MM 1500RPM 82CFM Model
Motherboard Gigabyte Z490 Vision D LGA1200 10th Gen Only DDR4 HDMI
RAM Ripjaws V Series 16GB 8GBX2 KIT DDR4 3600Mhz CL16
GPU Gigabyte Gaming OC RX 5700 XT 8GB GDDR6 HDMI 3xDP
SSD (Windows) XPG AS40G-512GT-C XPG Spectrix S40G RGB 3500MB 512GB M.2 NVMe
SSD (macOS) Samsung MZ-V7S500BW 970 EVO Plus Series 500GB M.2 NVMe
HDD (Share for both OS) Toshiba P300 2TB 7200RPM 64MB SATA 3.5" 6.0GBPS
Case NX800 RGB 1X120MM ARGB + 2X200MM ARGB Mid Tower
PSU Corsair RM750x RMx Series 750W Active PFC with 135MM fan


Thanks!


970 Evo Plus is known to take longer for booting in macOS. The latest firmware fixed the ability to use it but it still has longer boot times (1m vs 30s) compared to other SSDs.

NH-D15 is incompatible with Vision D - https://noctua.at/en/mainboard/Gigabyte_Z490_Vision_D
It blocks the first PCIe slot which might be a deal breaker for hackintoshing (now or in the future)
 
Is the situation any better with FileVault (FV2) disabled?

So the cause was not FV2 but an incorrect slide value choosen by opencore. I have to set "ProvideMaxSlide" in config.plist to ensure that OC does not choose a value from a range which results in the error.

My particular Vision G's memory layout has only 187 valid of possible 256 values. Between 0-156/159 and 223/229-255. These values keep on changing but if OC chooses a random value from the 229-255, then booting is a no go. I have so far set ProvideMaxSlide=120 but I still need to check for higher values.

For those who land on this later, use the debug version of opencore to see what slide values are calculated by OC if you have a Halting on Critical Error with something like
AAPL: [EB|‘LD:LKC] } Err(0x9)
 
Both of these are normal. Big Sur introduces enhancements to APFS that are not recognized in Catalina.

Probably good to raise this issue over at Insanely Mac in the OpenCore thread.

Thanks.

I have done that but no response yet.
 
Back
Top