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

[CaseySJ]

I put these back in Clover\Other and rebooted, to no avail. Still GFX readings are stuck.

As I wrote, F6. OK?

I'm still on Mojave, 10.14.6

I would upgrade to F9b if you're okay with the new UI. BIOS settings are in Post #1 with screenshots of the new GUI. Always start with Load Optimized Defaults because BIOS setting in Post #1 only specify the changes needed from the optimized defaults configuration.

Also check that there's no VirtualSMC.kext or FakeSMC.kext in /Library/Extensions. Probably good to do this in Terminal: sudo touch /Library/Extensions. Then reboot. Keep a bootable backup disk handy.

 

[zipb]

I would upgrade to F9b if you're okay with the new UI. BIOS settings are in Post #1 with screenshots of the new GUI. Always start with Load Optimized Defaults because BIOS setting in Post #1 only specify the changes needed from the optimized defaults configuration.

Also check that there's no VirtualSMC.kext or FakeSMC.kext in /Library/Extensions. Probably good to do this in Terminal: sudo touch /Library/Extensions. Then reboot. Keep a bootable backup disk handy.

Well, the Gigabyte UI's are always ugly. But as long as it gets the job done, I don't care. Still, I don't think this will fix my GFX readings.
USB implementation may improve, will try after dinner.
Thanks!

 

[CaseySJ]

@CaseySJ would you mind turning to this message? #19,669
thanks!

We've struggled with Antelope Audio drivers for a while and they just don't work! We recommend (a) yelling at Antelope Audio, (b) purchasing a real Mac, or (c) switching to Universal Audio Devices. For proof, please search this site for posts by @qthegaijin. Poor guy has struggled with this issue for an eternity.

To slightly paraphrase Jack Nicholson from A Few Good Men, "we must handle the truth!"

 

[ncrispi]

Have you tried clearing NVRAM at the Picker?

Boot settings are stored in both NVRAM and config.plist, but those in NVRAM seem to take precedence. So it's good to clear NVRAM.

I had to go back to an old 0.5.6 EFI to boot properly - very strange.

Two questions:

for the Intel UHD630 IGPU, does that work if I have internal graphics on auto for BIOS?

For the intel Bluetooth/WiFi, what is the need for the v8 designare UIAC file if I custom mapped my USBs?

 

[akanewb]

We've struggled with Antelope Audio drivers for a while and they just don't work! We recommend (a) yelling at Antelope Audio, (b) purchasing a real Mac, or (c) switching to Universal Audio Devices. For proof, please search this site for posts by @qthegaijin. Poor guy has struggled with this issue for an eternity.

To slightly paraphrase Jack Nicholson from A Few Good Men, "we must handle the truth!"

I have (c) and will do (a).
In the meantime, I'll use it via USB.

 

[CaseySJ]

I had to go back to an old 0.5.6 EFI to boot properly - very strange.

Two questions:

for the Intel UHD630 IGPU, does that work if I have internal graphics on auto for BIOS?

It won't work unless monitor stays connected to iGPU. It should be set to enabled.

For the intel Bluetooth/WiFi, what is the need for the v8 designare UIAC file if I custom mapped my USBs?

This is explained in the mini-guide.

 

[ncrispi]

It won't work unless monitor stays connected to iGPU. It should be set to enabled.

This is explained in the mini-guide.

I’m not too familiar with the IGPU vs rx5700 xt graphics card for hackintosh. Why would I want to use the IGPU instead of graphics card - are there any benefits?

 

[ncrispi]

@CaseySJ -- okay so as part2 of this saga - i was able to restore from backup with a 0.5.6 opencore EFI folder. I used to be able to use your NDK fork EFI folder (0.5.7 OC) and just change the 5 required sections. Now, however, when I use that as my EFI I am getting stuck at boot here. do you know what this means?
(It’s also happening with your normal 0.5.7 opencore file as well)

 

[zipb]

So now I am on BIOS F9b(unlock MSR again, reset RAM to 2666 MHz), but unfortunately I still have the low power usb problem, and my GFX readings in IPG are stuck.

Lots of tweaking and zero results. Oh well.

 

[CaseySJ]

@CaseySJ -- okay so as part2 of this saga - i was able to restore from backup with a 0.5.6 opencore EFI folder. I used to be able to use your NDK fork EFI folder (0.5.7 OC) and just change the 5 required sections. Now, however, when I use that as my EFI I am getting stuck at boot here. do you know what this means?
(It’s also happening with your normal 0.5.7 opencore file as well)

Looks like MSR 0xE2 may have been re-locked.