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

[jjsenecal]

@CaseySJ Are there any known pitfalls switching from an AMD GPU to the Intel iGPU? I planned to use HackinDROM to update my EFI. I need to pull my 6900XT for my new rig, but want to keep my current Hackintosh running. Thanks in advance.

 

[CaseySJ]

@CaseySJ Are there any known pitfalls switching from an AMD GPU to the Intel iGPU? I planned to use HackinDROM to update my EFI. I need to pull my 6900XT for my new rig, but want to keep my current Hackintosh running. Thanks in advance.

We noticed a number of graphics glitches with Mojave, fewer with Catalina, and almost none with Big Sur and Monterey. Hence it's okay to use iGPU.

 

[phrfpeixoto]

Please do the following:

• Compress and post the OpenCore 0.6.0 EFI folder (but remove serial numbers from config.plist)
• Compress and post the OpenCore 0.7.3 EFI folder (also remove serial numbers)

Also confirm if the following list of issues is still correct for 0.7.3 (with Catalina):

• Pink lines during boot (which is a problem during VRAM test and was fixed by WhateverGreen)
• Blank video signal when using DisplayPort from RX 580 (but HDMI is okay)
  • Are you using a DP-to-DP cable (no adapters)
  • If you enable CSM Support in BIOS, does DP work?
• Unable to wake fully from sleep
  • In this case, please disable CpuTscSync.kext from the Kernel section of OpenCore Configurator, then reboot and try again. Does wake-from-sleep work now?
• Is VT-D enabled in BIOS? Ideally, it should be when using OpenCore 0.7.3.

nvram.plist is an artifact of Clover. In OpenCore we use native NVRAM, which requires disabling "CFG-Lock" in BIOS. Is the backup disk using Clover?

I'm sorry for the delay. It took me a long time to get a break from work so I could test this again.

Now that OpenCore 0.74 is out I tried that version instead, and so far everything seems to be running smooth.
Manually sleeping MacOS Catalina works, and so does waking it up.

Historically I've had issues with very long periods of sleep (IE, the whole weekend), but I'll need time to test that out.

nvram.plist was likely never removed since I used clover from the initial build (before OC was widespread). Took this time to do that.

Just answering your questions:
Yes, I'm using DP-to-DP cable. No adapters.
CSM Support is still disabled, but I've also taken this chance to enable VT-d
CpuTscSync.kext is now disabled by default, as you mentioned, so maybe that has played a role.

Thanks again for all the support.

Quick Question: Can I use the Fractal R6 SSDT from post #1 on OpenCore 0.7.4 SSDT section here?

 

[CaseySJ]

...

Quick Question: Can I use the Fractal R6 SSDT from post #1 on OpenCore 0.7.4 SSDT section here?

Yes, absolutely. Only one USB SSDT can be used at a time so simply uncheck the existing one when adding a new entry for the Fractal Design.

 

[CaseySJ]

Hi all, I have been using this build with a Vega 56 for about a year now and would like to substantially upgrade my graphics. Does anyone know if a Radeon W6800 workstation card would work here? I believe the drivers are already in Bug Sur since the W6800X can be had in the Mac Pro.

Just saw your post...

The Radeon W6800 should work with Big Sur. It's best to be on OpenCore 0.7.4 because WhateverGreen was recently updated to allow GPU device ID spoofing. This means that if your W6800 uses a non-standard device-id, we can easily spoof it to work.

 

[qsxl]

@qsxl,

Your SSDT and config.plist both look okay. But IOReg shows that the SSDT did not work. With both SSDT-TB3.aml and SSDT-DTPG.aml enabled, let's look at the boot log. In Terminal, type this:

log show --last boot | head -1500 > ~/Documents/bootlog.txt

This will create a file in Documents folder called bootlog.txt. Please post that file.

Ref post.

Update: Fixed an error -- changed "tail" to "head".

How can I modify my file or how to operate it.

 

[CaseySJ]

How can I modify my file or how to operate it.

Please run this command (it is different from before) and post the file “bootlog.txt”:

log show --last boot | head -1500 > ~/Documents/bootlog.txt

 

[andrai886]

The latest version of Big Sur is 11.6.1. Do you specifically want to install 11.5.2 instead?

There is a solution to your problem that works when all other methods fail, but it requires another Mac or Hack that is not old enough (i.e. on which Big Sur is supported by Apple). That method goes like this:

• We take the NVMe SSD out of the non-working Hackintosh and install it in a USB 3.0 enclosure.
  • Alternatively we can use a 2.5" SATA SSD in a USB 3.0 enclosure and later clone it to the internal NVMe SSD on the non-working Hackintosh.
• We connect this USB 3.0 enclosure to a working Mac or Hack.
• We run Install macOS Big Sur application on the working Mac or Hack.
• When the installer starts, select the external USB 3.0 disk as the destination.
• The installer should be able to complete the installation. A couple of reboots will take place, which is okay.
• When the process is done, copy the OpenCore 0.7.4 EFI to the EFI partition of the external USB 3.0 disk.
• Disconnect and mount the USB 3.0 disk to the non-working Hackintosh.
• Boot the non-working Hackintosh and press F12 at the Gigabyte splash screen.
• Select the USB 3.0 disk.
• When OpenCore appears, boot Big Sur from the USB 3.0 disk itself.
• If it works, use Carbon Copy Cloner to clone the USB 3.0 disk to the internal NVMe SSD.
  • Be sure to use Legacy Bootable Backup and Allow CCC to erase the backup disk
• Then manually mount the EFI partitions of the external USB 3.0 disk and internal NVMe SSD.
  • Copy the EFI folder from USB 3.0 disk to internal NVMe SSD.

Used this method. Everything is working great. The only issue I have, using the IntelWiFI, my bluetooth keyboard and mouse are not connecting.

 

[CaseySJ]

Used this method. Everything is working great. The only issue I have, using the IntelWiFI, my bluetooth keyboard and mouse are not connecting.

The Intel Bluetooth drivers are not as robust as Apple’s Broadcom drivers, but they are quite good. What are the names/models of your keyboard and mouse? Have you tried unpairing and re-pairing them? If you have Windows, it will interfere with Bluetooth, so it’s necessary to do a full shutdown (power off and flip switch on PSU to off) before booting macOS.

 

[qsxl]

Please run this command (it is different from before) and post the file “bootlog.txt”:

log show --last boot | head -1500 > ~/Documents/bootlog.txt

I have run the release in attachment 1.txt above