Contribute
Register

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

Please see last sentence of my previous reply. Or just state which version of Lilu you are using. If it's the latest version then it's compatible with CommanderProFix, in which case it would be best to continue troubleshooting with the developer of CommanderProFix.


Unfortunately, "it did not work" does not help us help you.
Hackintool shows OC 0.6.9 loaded and HackinDROM shows OC 0.7.0 EFI but only OC 0.6.9 loaded.

Screenshot 2021-06-13 at 18.54.29.png

Screenshot 2021-06-13 at 18.54.43.png
 
Hackintool shows OC 0.6.9 loaded and HackinDROM shows OC 0.7.0 EFI but only OC 0.6.9 loaded.
If your system has multiple disks with EFI partition, it is possible that the system might be booting from the wrong disk. It could be booting from an EFI partition with OpenCore 0.6.9. We can check this by pressing F12 at the Gigabyte splash screen to open the BIOS Boot Menu and selecting the correct boot disk.

The correct startup disk can also be selected from System Preferences --> Startup Disk.

However, if your system has only one disk with an EFI partition, then let's do the following:
  • Mount EFI partition and expand EFI/BOOT and EFI/OC folders inside that partition. Post screenshot so we can see the date/time of BOOTX64.efi and OpenCore.efi.
  • Also try Reset NVRAM by pressing space bar at OpenCanopy Picker. This will reset the startup disk, so it will have to be selected again from System Preferences --> Startup Disk.
 
If your system has multiple disks with EFI partition, it is possible that the system might be booting from the wrong disk. It could be booting from an EFI partition with OpenCore 0.6.9. We can check this by pressing F12 at the Gigabyte splash screen to open the BIOS Boot Menu and selecting the correct boot disk.

The correct startup disk can also be selected from System Preferences --> Startup Disk.

However, if your system has only one disk with an EFI partition, then let's do the following:
  • Mount EFI partition and expand EFI/BOOT and EFI/OC folders inside that partition. Post screenshot so we can see the date/time of BOOTX64.efi and OpenCore.efi.
  • Also try Reset NVRAM by pressing space bar at OpenCanopy Picker. This will reset the startup disk, so it will have to be selected again from System Preferences --> Startup Disk.
Thanks Casey. You were spot on.

I have a multi boot system, Windows 10 Pro, Catalina and Big Sur so I must have been booting from the Catalina EFI partition which was indeed OC 0.6.9. Both are OC 0.7.0 now so OC booting correctly on 0.7.0 for both.

I haven't figured yet why some kexts are not loading and HackinDROM only lists some of the kexts in the kexts folder as loading including CommanderProFix as we discussed previously (I will troubleshoot with the developer as you suggested) but there are other kexts that are not loading. Is there a reason for that?
 

Attachments

  • Screenshot 2021-06-13 at 22.43.04.png
    Screenshot 2021-06-13 at 22.43.04.png
    49.4 KB · Views: 37
  • Screenshot 2021-06-13 at 22.46.16.png
    Screenshot 2021-06-13 at 22.46.16.png
    42.2 KB · Views: 44
Thanks Casey. You were spot on.

I have a multi boot system, Windows 10 Pro, Catalina and Big Sur so I must have been booting from the Catalina EFI partition which was indeed OC 0.6.9. Both are OC 0.7.0 now so OC booting correctly on 0.7.0 for both.
That's better!

I haven't figured yet why some kexts are not loading and HackinDROM only lists some of the kexts in the kexts folder as loading including CommanderProFix as we discussed previously (I will troubleshoot with the developer as you suggested) but there are other kexts that are not loading. Is there a reason for that?
  • SmallTree-Intel-211 is not needed because the Z490 Vision D does not have that port. We can remove it.
  • Codeless kexts (those that only have Info.plist, but no compiled code) don't show up in the list of running kexts.
  • I think the only issue here is why CommanderProFix is not working.
 
Hi guys,

Do you know if we can disable the NVMe slots from the BIOS? I know we can turn on or off the SATA but I can't find anything in the BIOS for NVMe. I need to reinstall Windows 10 but would like to avoid taking the NVMes out (need to remove the video card, remove the NVMe disks, etc., just a pain). So, if I can disable them in the BIOS, then it is even better.
 
Last edited:
That's better!


  • SmallTree-Intel-211 is not needed because the Z490 Vision D does not have that port. We can remove it.
  • Codeless kexts (those that only have Info.plist, but no compiled code) don't show up in the list of running kexts.
  • I think the only issue here is why CommanderProFix is not working.
Thanks for explaining. It's really useful to know that. I will continue to follow up on CommanderProFix.
 
I posted about this a little while ago but didn’t get an responses. Is anyone else getting the “default” Big Sur background on the initial login screen, that will then switch to your actual desktop background after logging in? This was never an issue before I upgraded to 11.4 - it was always my desktop background
 
I posted about this a little while ago but didn’t get an responses. Is anyone else getting the “default” Big Sur background on the initial login screen, that will then switch to your actual desktop background after logging in? This was never an issue before I upgraded to 11.4 - it was always my desktop background

Hi there.

I haven't seen this except ...

Are you the only User registered with macOS?

As each User can have their own settings and customizations, that might explain the default behaviour you are seeing before the User is selected.

:)
 
I posted about this a little while ago but didn’t get an responses. Is anyone else getting the “default” Big Sur background on the initial login screen, that will then switch to your actual desktop background after logging in? This was never an issue before I upgraded to 11.4 - it was always my desktop background
This occasionally happens to me at random on one of my two screens.
 
Hi there.

I haven't seen this except ...

Are you the only User registered with macOS?

As each User can have their own settings and customizations, that might explain the default behaviour you are seeing before the User is selected.

:)
Yes i’m the only user. Its very strange as on the 11.4 beta it was fine. Soon as I upgraded to the 11.4 official, I get the default Big Sur screen on initial login.
 
Back
Top