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

[FormerUser-594785]

I was using HWMonitorSMC2 v2.4.9, but just upgraded to v2.6.1 from CloverHackyColor (click here). This version is even better. Not only does it display iGPU and AMD GPU statistics, but it also displays comprehensive voltages for Designare Z390:

I don't understand, however, why the Uhd 630 marks 7GB of VRAM!

 

[n19htz]

Why do \Aamazon trailers not working in Chrome, but work in Safari?

 

[lambusser]

I was just cleaning up my EFI volume and noticed that I had a copy of "ApfsDriverLoader.efi" in both EFI/CLOVER/DRIVERS/BIOS and EFI/CLOVER/DRIVERS/UEFI. But they are different sizes so that worries me a little. Any way to look at versions on those?

Thanks!
Lam

 

[iRamon]

My hundred million dollar question is, does any of it still work if you boot in to Windows? Meaning, does the Thunderbolt 3 bus work properly, and can you load the appropriate drivers from BootCamp to get the monitor up and working? Getting the Thunderbolt Display working in windows was always a challenge even on a real Mac, but I did have it successfully working for two years.

Main thing I guess is really the Thunderbolt Controller with the modifications loaded on the Winbond, is that recognized properly and is it functional under Windows?

Hello @svendive,

Wish I could give you an answer, but I don't have Windows installed on my hackintosh.

I plan on installing Windows in the near future, and it will only be for playing F1 2020 to at least experience a virtual Dutch Grand Prix in Zandvoort this year. Once I have Windows installed, I'll test Thunderbolt functionality on Windows and whether the Apple Thunderbolt Display works or not.

There is some information in this thread on Thunderbolt functionality in Windows with patched firmware. What I remember is that Windows won't recognize TB on a cold boot, but that it will after booting into macOS first and then warm rebooting into Windows. I did a quick search and found this (below) from Casey:

Just looked into this on my primary system that has both Windows and macOS (and flashed Thunderbolt firmware).

• On a cold boot (after PSU has been flipped OFF or power cable unplugged from the wall) Thunderbolt does not work under Windows.
• If we boot into macOS and then warm boot into Windows, Thunderbolt is operational. It remains operational until power is again completely shut off (i.e. unplugged from wall or PSU flipped off).
• However, I don't have a Thunderbolt monitor...at least not yet. I would be very tempted by a mini-LED version of a 4K or 5K Thunderbolt 3 monitor.

It's also mentioned in the Repository of Patched Thunderbolt files:

Hope that helps!

Thanks, and congratulations you deserve this to be done for now...

Thank you!

 

[AlexComputerWiz]

@CaseySJ, I made an oopsie. Luckily all my files I care about are in iCloud so I don't care much. When I was following the MSR guide, I accidentally replaced the wrong EFI folder on the wrong EFI that was mounted and now clover doesn't pop up at boot, nor can I boot onto my NVMe with the OS. Should I just go to a clean install now? I only have Win10 on another drive.

Note: I already did all the other steps in the upgrade guide so I have the .plist file I was using and all the correct kexts and efi files on my USB still.

 

[CaseySJ]

I just tried this version, there's no GPU info for me, neither for the iGPU nor for my RX480. Do I need an extra .kext for this?

Select Use the IOKit monitoring for GPUs from the Preferences pane (the little gear icon on the bottom left corner of the window).

I don't understand, however, why the Uhd 630 marks 7GB of VRAM!

The previous version 2.4.9 also reports 7GB VRAM for the iGPU. I'm willing to look the other way. These things get sorted out eventually.

After installing Intel Power Gadget and checking the eponymous box in Preferences, we get a whole bunch more statistics:

 

[CaseySJ]

Why do \Aamazon trailers not working in Chrome, but work in Safari?

Just checked -- Amazon Prime trailers work fine in Chrome. I'm using shikigva=80 in Boot Arguments.

 

[CaseySJ]

I was just cleaning up my EFI volume and noticed that I had a copy of "ApfsDriverLoader.efi" in both EFI/CLOVER/DRIVERS/BIOS and EFI/CLOVER/DRIVERS/UEFI. But they are different sizes so that worries me a little. Any way to look at versions on those?

Thanks!
Lam

Fortunately this is nothing to worry about. In fact you may safely delete the entire BIOS folder. Modern motherboards have moved from BIOS to UEFI, so only the UEFI folder is needed. Technically, when we say "BIOS Setup" we are using the wrong terminology. We should be saying "Firmware Setup". The BIOS world went extinct a decade or more ago.

 

[CaseySJ]

@CaseySJ, I made an oopsie. Luckily all my files I care about are in iCloud so I don't care much. When I was following the MSR guide, I accidentally replaced the wrong EFI folder on the wrong EFI that was mounted and now clover doesn't pop up at boot, nor can I boot onto my NVMe with the OS. Should I just go to a clean install now? I only have Win10 on another drive.

Note: I already did all the other steps in the upgrade guide so I have the .plist file I was using and all the correct kexts and efi files on my USB still.

Because you have the EFI folder on the USB install disk, simply boot from that:

• Insert disk and press F12 at BIOS splash screen.
• Select the USB disk.
• At Clover, select Boot macOS from <name of internal SSD>.

 

[AlexComputerWiz]

Because you have the EFI folder on the USB install disk, simply boot from that:

• Insert disk and press F12 at BIOS splash screen.
• Select the USB disk.
• At Clover, select Boot macOS from <name of internal SSD>.

But I still have 10.14.5 installed on the machine, but I have the EFI ready for 10.15.4. I just tried to boot to my M.2 and it just gets stuck on the Apple logo. Because I have no way to get the M.2 as an external drive and just restore the EFI onto the disk, I'm thinking I should just clean install?