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

[svandive]

** Confirmed: Native NVRAM in Clover **​

...

Just curious what the real advantage here is with native NVRAM? Other than making this closer to a real MAC, are there other advantages (boot time, consistency, stability)? Thanks,

 

[manfriday]

If you're on F9b, please go through the full procedure to determine the Var Offset.

F9b uses 0x5C1 as well


0x3E6C5 One Of: CFG Lock, VarStoreInfo (VarOffset/VarName): 0x5C1

 

[Racke]

Just curious what the real advantage here is with native NVRAM? Other than making this closer to a real MAC, are there other advantages (boot time, consistency, stability)? Thanks,

Easy to answer:
1)The less extra kexts, efi´s and scripts you need the better the system stability.
2) The more you know about your System, the better it works

I don't build a hackintosh because it's cheaper but because I am interested in and proud if it works. That's what's always in my mind when I do my real work on my build. Every time I boot the system to mix a song, cut a video or even write my bills, I think "Great - now it has native NVRAM because WE found it"

 

[AlexD]

Dear @CaseySJ , I believe there's a little mistake in your Native NVRAM guide.
By default, MSR 0xE2 CFG Lock is 0x1 (it means it's locked, turned on).
In order to unlock MSR we actually need to change it to 0x0 (lock is removed, turned off).

So, when we confirm value change, we should see 0x0 instead of 0x1.
Just want to avoid confusion and any potential problems people may face with this very advanced mod.

 

[CaseySJ]

Dear @CaseySJ , I believe there's a little mistake in your Native NVRAM guide.
By default, MSR 0xE2 CFG Lock is 0x1 (it means it's locked, turned on).
In order to unlock MSR we actually need to change it to 0x0 (lock is removed, turned off).

So, when we confirm value change, we should see 0x0 instead of 0x1.
Just want to avoid confusion and any potential problems people may face with this very advanced mod.

You're absolutely right.

So much for waking up at 3:00am every morning and trying to get some work done before work!

 

[hussar]

here's something interesting...
May be of use to some video editors out there.

I recently updated [on MOJAVE 10.14.6]
LILU and WEG from 1.4.0 and 1.3.5
to
1.4.1 and 1.3.6 respectively.

I immediately noticed a slow down in my system.

I have a vega64 in slot 1
and
R9 270X in slot 2

my 4k monitor is plugged into the Vega with displayport
my 1080 ref monitor is plugged via HDMI to the r9 270x in slot 2

I noticed this slowdown while I was generating optimized media in Davinci Resolve16 [4k mon] and playing a youtube video in the 1080p monitor

DaVinci crawled
youtube playback was choppy and after a while stopped showing an image

HW Monitor showed 0% utilisation for the Vega and around 32% for the 270x

So I reverted back to 1.4.0 and 1.3.5
and everything is back to normal-
Generating optimized media is fast and youtube plays back correctly

activity on the HWMonitor is consistent with Vega being the primary card utilised
and the 270X minimally used.

Hopefully this helps one of you guys out there!

UPDATE:
moved to Catalina 10.15.3 with NVRAM and the latest WEG+LILU work correctly here

 

[CaseySJ]

F9b uses 0x5C1 as well


0x3E6C5 One Of: CFG Lock, VarStoreInfo (VarOffset/VarName): 0x5C1

Thank you -- post updated.

 

[CaseySJ]

For easier reference to NVRAM guide (for Clover)​

Mojave Build Guide:

---

Catalina Mini-Guide:

 

[zipb]

Thank you -- post updated.

I just unlocked my CFG register(never felt the need before) and enabled NVRAM. I think it works. Nice one!
Thanks for the easy step-by-step guide, CaseySJ.

 

[tdcam]

here's something interesting...
May be of use to some video editors out there.

I recently updated [on MOJAVE 10.14.6]
LILU and WEG from 1.4.0 and 1.3.5
to
1.4.1 and 1.3.6 respectively.

I immediately noticed a slow down in my system.

I have a vega64 in slot 1
and
R9 270X in slot 2

my 4k monitor is plugged into the Vega with displayport
my 1080 ref monitor is plugged via HDMI to the r9 270x in slot 2

I noticed this slowdown while I was generating optimized media in Davinci Resolve16 [4k mon] and playing a youtube video in the 1080p monitor

DaVinci crawled
youtube playback was choppy and after a while stopped showing an image

HW Monitor showed 0% utilisation for the Vega and around 32% for the 270x

So I reverted back to 1.4.0 and 1.3.5
and everything is back to normal-
Generating optimized media is fast and youtube plays back correctly

activity on the HWMonitor is consistent with Vega being the primary card utilised
and the 270X minimally used.

Hopefully this helps one of you guys out there!

Yeah I just tried this and reverted and single core Geekbench went up over a 100 points ! Thanks for the tip !