Contribute
Register

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

That looks correct. The scaled resolution will be 2560x1440 @ 60Hz. On a 4K monitor we scale the graphics to 2560x1440 instead of displaying them at 3840x2160 (which would be too small to see).

yeah sure for usual work 2560x1440 it's ok, but sometimes we need 4k resolution for other things, for example to watch the movie in 4k 3840x2160 etc...
 
Last edited:
Also try disabling XMP Profile 1 from BIOS Setup. You can manually select Memory Multiplier 29.33 for 2933 MHz memory. See if this configuration is more stable.
Could not replicate the exact original activity (random cores firing off around 60 to 100% usage at idle) with either XMP Profile 1 disabled or selected . The only thing I noticed - just after wake from monitor sleep (not system) is with XMP Profile 1 Disabled-the CPU usage shows just a flicker on one core at idle. Enabled - seems like it wakes with a bit of cpu usage then just a few flickers on 3 to 4 cores before settling down (to just a flicker on 1 core).
Memory Multiplier remained set to 'auto'
confirmed time machine is off
 
Vermeer might make me build another one... especially if big Navi will be supported on Mac. I might do a small form factor AMD build though...

Also, have you seen this? Vision D RTX 3080 is coming. Far sexier than other boards I’ve seen thus far.
View attachment 488551
Source:https://videocardz.com/newz/gigabyte-geforce-rtx-3080-vision-oc-pictured

here’s to hope that a similar big Navi AIB comes too.
That is awesome! Would love to see Big Navi in similar clothing.
 
I'm no final authority but I can describe my novice understanding so far. LLC is used to counter Vdrop. Vdrop is the voltage drop you see when the processor is under load. You might set 1.4v as Vcore in BIOS but under load the processor might actually be at 1.3v. You can see this under HWinfo in Windows. You use LLC to deal with this Vdrop.

The ground is muddy because there are a lot of different variables for determining what voltage your processor is getting. VID is generally ignored because that's what the processor thinks it wants. VCore is what you fix and what the MB tries to give but it retains the right to adjust it if needed. VR Vout is generally the measurement of the voltage just before the processor gets it but not every motherboard has the ability to measure it. Vision G and Vision D should be able to measure VR VOUT.

One major issue is that most overclockers use an ASUS board for tuning this. Thus mapping ASUS LLC values to Gigabyte is tough.

One resource to learn about LLC -

Overclocking and undervolting the 10700k specifically - https://www.overclock.net/threads/overclocking-i7-10700k-results-comparisons-discussions.1748774/

So I watched the vid and seems that he recommends a Load Line Calibration setting of ‘Medium’ if you’re really pushing your cpu. Which fits very nicely with my findings... so I feel better.

My question is what the heck does the “auto” setting do. It seems that rather than a Vdroop, it actually boosts voltage as load increases, which increases temps. I’m fine with the outcome at ‘medium’ with a relatively cool 77 degrees under load at 5.1 GHz.
 
Hello @LX45682,

Welcome to the forum. We intentionally disabled HS14, but it is very easy to enable it. Simply disable SSDT-UIAC-VISION-D-V2.aml in OpenCore Configurator, and add SSDT-UIAC-VISION-D-HS14.aml attached below. Be sure to copy the file into OC/ACPI folder and add an entry in OpenCore Configurator.
Sorry, I just forgot to indicate that my computer's motherboard model is msi z490i unify. After trying it, it can't work on this motherboard. In addition, I changed it back to iMac19, 1 and found that there is no HS14 port. Even if you use USBInjectAll version 0.7.5 or 0.7.6, there is no customized USB port. Very confused, I don't know where the problem is. . I want to try to reinstall the system tomorrow. Thank you very much for your reply.
At the same time, I saw that you have customized the TB3 mod for the msi motherboard. Is there a way to flash the firmware under windows? Thanks
 
I noticed that your profile says TRX40 with Threadripper 3970X. Are macOS patches available now for both TRX40 and 3970X or are you using a Rube Goldberg machine that layers VM over VM?

My daughter's machine died so I gave her my Gigabyte Z390 Hack. I fancied another challenge so went with the Gigabyte Xtreme TRX40 and the 3970X. This gives macOS the full 64 threads that it can use. I was going to use Proxmox to start with but was never happy with the resultant VMs.

It is Bare Metal now running Catalina 10.15.6 and the latest Big Sur Public Beta. There are a group of us, on an Italian Forum (thankfully our thread is in English:)) that are slowly getting everything up and running. Unfortunately I know nothing about SSDTs so rely on the likes of Pavo (who has posted on this site) and iGPU when it comes to that side of things. There is still a lot of debate as to what SSDTs are needed, some use none, others half a dozen or more. Kexts are pretty standard - the twin 10G network ports on the Xtreme work fine as does the onboard Bluetooth. I haven't played much with the alpha/beta wireless bits yet - I use a wired connection so there is not much need for me but I would eventually like to get it working as it is there anyway. Sound works fine, no need for AppleACL or any other kext for it. NVRAM is working.

A chap called @Fabiosun started the thread and is gathering OC configs for the various boards. A number use MSI and Asrock boards and a few of us have Gigabyte. There is even one or two running the Gigabyte TRX40 Designare.

I started with a fresh install of Catalina but then tried a CCC of the Z390. It worked a treat. Big Sur is running on a separate NVMe.

The Vanilla AMD patch list is quite long but we have, or should I say @iGPU worked it out, cut it down to only 14 patches now!

The Big Sur release of yesterday has broken it ATM but those with a VM have managed to install it OK I believe. There are a number of people working on a new patch or two so I haven't attempted an update to it yet.

If you need any more info, just ask, and have a look at the other forum.
 
You may not like this advice, but I have to ask:
  • Do you have any other monitors? Specifically, recent monitors with HDMI 1.4+ or DisplayPort 1.1+?
  • Do you have a flatscreen TV close by with HDMI?
  • If so, do those monitors display video over HDMI and/or DisplayPort cables?
View attachment 488514

I tried to connect a regular modern display via DisplayPort cable, but it was the same outcome.
I am now trying out different EFI combinations (other people's EFI folders). But even Catalina does not display a picture. :-/
 
I tried to connect a regular modern display via DisplayPort cable, but it was the same outcome.
I am now trying out different EFI combinations (other people's EFI folders). But even Catalina does not display a picture. :-/
  • Do you have a valid ROM as shown below? Feel free to click the Generate button inside the red box to create a new one.
  • Is Serial Port disabled in BIOS?
Screen Shot 2020-09-18 at 12.46.14 PM.png

  • Also try deleting DMAR table:
    Screen Shot 2020-09-18 at 12.50.13 PM.pngScreen Shot 2020-09-18 at 12.50.20 PM.png
 
  • Do you have a valid ROM as shown below? Feel free to click the Generate button inside the red box to create a new one.
  • Is Serial Port disabled in BIOS?
View attachment 488581

OH MY GOODNESS!
IT WORKS! :clap:

I started completely fresh with the OC 0.6.1 set, applied the changes for Vision G, generated an iMac20,2 model and rom and then needed to do some funky stuff with the plist to be able to add an entry to the "Delete" section under ACPI. (Had to copy an example entry from another config into your template)
Then I dropped the DMAR table.
Catalina installer did not want to display any picture, but my existing Big Sur Beta 6 install FINALLY booted.
Serial port is in fact disabled in BIOS. I wish I could use it at some point, but this is a low priority.

Thank you so much. I will now see how stable the system is and if I will keep the graphics card.
I am just so happy there is FINALLY a picture. Same old monitor...

All the best!
schreiberstein
 
It seems that rather than a Vdroop, it actually boosts voltage as load increases, which increases temps. I’m fine with the outcome at ‘medium’ with a relatively cool 77 degrees under load at 5.1 GHz.

This is probably the BIOS being conservative. It wants to maintain stability but it does not know what is stable for your particular chip. Gigabyte had X samples of a processor and they basically averaged across all the samples. This average is generally higher than what you actually have on hand. By default, Gigabyte boards push 1.4-1.5V on the 10th gen processors. Many people have been able to run things fine at 1.2-1.3V. My OOB temps on the 10700k @ 4.7Ghz full load were 88-90C because the Vcore was 1.45V. Changing the voltage to 1.2V gave me 65-70C. Now I'm running at 1.3V for 5Ghz all-core for a max temp of 86C. The auto mode is compensating for your low Vcore.

You'll have to manually tune everything based on your silicon lottery. The auto settings just assume a bad lottery from what I've read.

If you are getting 77C at 5.1 Ghz all core, then you probably won the silicon lottery.
 
Back
Top