Jump to content

AudioGod's Aorus Z390 Pro Patched DSDT Mini Guide and Discussion


AudioGod
5,966 posts in this topic

Recommended Posts

Now I'm on Bios F10

with dual boot

and everything is working pretty good!

my config is on signature below

 

Ok so this is question:

Should I update bios to rev 12d ?

I'm just scared of messing things that now are working :cry:

 

In case I have to update bios and EFI

 

what is the best way of doing it?

maybe explained step by step please :)

 

thank you!

 

 

Link to comment
Share on other sites

Hello,


I have a serious question about what hardware and SMBios I should I use. I'm planning on either purchasing 9900k or RX5700. I use this system for my work (design, video editing) and I have a big project coming up. Please advise if possible.

My current build is i5 9400F (no iGPU) + RX580 with iMac Pro 1.1 SMBios on 10.15.2. F11 Motherboard Bios.

 

While everything is super stable except hardware acceleration for video encoding/decoding in 4k is clearly not working properly. 
GPU is not utilized to its full potential while exporting 4k 8bit 4:2:0 video, but it's used to almost 100% when exporting the same file to 1080p. The file itself is very common from Sony A7III and it's supported by VCE in RX580 and iGPU UHD630.


In Premiere Pro without any effects or color grading:

 

4k 8 bit 4:2:0 file export to 4k uses about 30% of GPU and it's about 1 to 1 in speed. 1 minute of video renders out in 1 minute real time. This is roughly the same speed as my previous Haswell build with iGPU (HD4600).

4k 8 bit 4:2:0 file export to 1080p uses 90-100% of GPU and it's blazingly fast. CPU load is under 10%.
4k Prores Proxy 4:2:2 to 4k exhibits the same issue. GPU is simply stuck at ~30% utilization.

Scrubbing on the timeline in 4k apparently uses mostly CPU to decode the video instead of GPU. Every time I quickly scrub it causes apparent dropped frames and stutters and spikes CPU utilization to 70%+.

This issue is simply not present in 1080p. Scrolling through the video is buttery smooth, hopping from point A to point B on the timeline does not cause spikes in CPU usage and I get much higher GPU utilization.

On top of that Final Cut Pro X has extremely slow render time. 2-3 times slower than Premiere Pro. 5 minute project takes about 13-15 minutes to render. 


This leads me to believe that Video Coding Engine (VCE for hardware acceleration) is not working properly with 4k files for some reason.


Please advise what should I change in the build and the config in order to utilize GPU to 100% with 4k files.
I thought about purchasing RX5700 since it has a new engine for hardware acceleration, but in AudioGod's guide it says "Please Note, If you use a 5700 or 5700XT then SMBios 1,1 in unstable using the Navi GPUs so please stick to 19,1 with igpu enabled."
Does this mean I won't be able to use it to properly accelerate video decoding/encoding AND I'll have to change my processor to one that has iGPU?


What route should I take? Buying an i9 9900k first or rx5700? I wanted to use dedicated GPU for video hardware acceleration, because apparently it's much faster than iGPU (UHD 630).

 

Is there any information about development for this motherboard of Mac Pro 7,1 SMBios with RX5700/RX5700XT since it's going to use Radeon Pro W5700X card which is essentially a RX5700?
From Apple website:

Coming soon: Radeon Pro W5700X with 16GB of GDDR6 memory

 

Thank you.

Edited by Tlait
Link to comment
Share on other sites

 
 
 
1
6 hours ago, Tlait said:

What route should I take? Buying an i9 9900k first or rx5700? I wanted to use dedicated GPU for video hardware acceleration, because apparently it's much faster than iGPU (UHD 630).

Keep in mind that the new Metal Engine for FCPX is in its early stages and does not yet use supported GPUs for all of its encoding chores.  That should change over the next few point releases.  But for right now, Quick Sync remains important.

  • Like 1
Link to comment
Share on other sites

22 hours ago, texem said:

i give up, sry. Basic knowledge is required here. Google for macserial .

 

 

Sorry, about my lack of knowledge.

 

I am simply trying to trouble shoot why I am getting the error I am getting, and from my understanding the items you listed would not be responsible/are fixed POST install. Am I correct here, or did I miss a section that states those needed to be changed in order to get a bootable disk up and working?

 I would think keeping it as close to what Audio God provided would be the best way to trouble shoot this? 

 

 

 

 

Link to comment
Share on other sites

43 minutes ago, stavidawg said:

Sorry, about my lack of knowledge.

 

I am simply trying to trouble shoot why I am getting the error I am getting, and from my understanding the items you listed would not be responsible/are fixed POST install. Am I correct here, or did I miss a section that states those needed to be changed in order to get a bootable disk up and working?

 I would think keeping it as close to what Audio God provided would be the best way to trouble shoot this? 

The EFI released works perfectly provided you set up your system as he suggested. Get a proper macOS installer without errors. This is crucial as people use all sorts of dumb ways to make the stick, either pulling an incompatible version or an assortment of errors that either fubar the install process or leave you with a non-working system.

 

Stop and take a step back. Make a USB installer on a real macOS running the latest OS. Ensure it's good and error free. Update your BIOS to the latest revision (F12d for the Pro and F12c for the Pro WIFI, both work with this EFI).

 

Set up the BIOS properly. You need to first enable the dGPU, save settings and reboot, then go right back into the BIOS and finish setting it up. Only then will it list the following settings:

 

 Settings -> IO Ports -> DVMT Pre-Allocated -> 64M

 Settings -> IO Ports -> DVMT Total GFX0-Allocated -> 256M

 Settings -> IO Ports -> Aperture Size -> 256MB

 

That's mostly it. Unplug all your hardware that's not necessary. If you have some kind of radiator cooling system, then you may need to do some fiddling as there are known issues with lots of fancy cooling (by fancy I mean coming from traditional air cooling like the Notcua DH-14). macOS doesn't support anything other than traditional air cooling systems (fan + heatsink).

 

You're throwing up a ton of info, way too much. I get what you're trying to do, but this EFI is bulletproof. You just toss in your EFI partition and you're good. Truly.

  • Like 2
Link to comment
Share on other sites

Hey all, newly commenting here, though I’ve lurked until I had enough gear to get started. I still await a (final choice on) graphics card, but was happy to see the UHD 630 EFI for UEFI firmware version F12D on the Z390 Aorus Pro, so thought I’d try it on my very slightly different setup:

 

I have a Z390 Aorus Pro WiFi paired with a 9700K & 16GB RAM across slots A1 & B1. I’ve also updated to UEFI version F12C (there’s no F12D for the WiFi, apparently, though GigaByte version notes on it are the same as for the Pro’s F12D… and yes, I saw glasgood’s comment for Mojave to disable HS14 in boot args, so I can use the Bluetooth on the Fenvi T919 I’m eventually going to install rather than on the Intel CNVI chip).

 

So the slightly different board/UEFI version might be my first issue, but I was able to enter all the UEFI config steps suggested, Save & Exit. Windows & Linux Mint share a separate NVMe drive, both work fine (grub overrules the Windows Boot Manager, but keeps Windows as a boot option). I’ve kept the NVMe drive onto which I plan to install macOS blank so far.

 

But attempting to install from the macOS Catalina Installer USB with AudioGod’s very considerate provision of a UHD630 EFI gets somewhere between 1/2 and 2/3 through the progress bar and pops up a “forbidden” or “prohibited” symbol & hangs indefinitely. Adding “-v” as a boot arg so I can see in verbose mode what’s going on just pixelates all the text out under the symbol when it pops up, yielding no info.

 

One last potential diagnostic bit is that the Catalina 10.15.3 installer copy I have, was downloaded as part of dosdude1’s efforts, as I also have a real Mac that needs help running the latest. It has not been used to create install media or patches for an older real Mac yet; it should still be as Vanilla a copy as our favorite fruit company sends them out (without the EFI flecks of vanilla bean we like to add to get it running on systems they should have built, or should still build).

 

Should I switch to getting it through gibmacOS, or is my copy good & there’s something else going on with UEFI, NVRAM (reset, run, then re-configured a few times, all to no avail), etc.?

 

Thanks for any insight you can share!

Edited by juan e. jot
Link to comment
Share on other sites

1 hour ago, juan e. jot said:

I saw glasgood’s comment for Mojave to disable HS14 in boot args, so I can use the Bluetooth on the Fenvi T919

This is accomplished by turning off wifi in the BIOS. It effectively turns the board into a regular Pro. No difference.

  • Like 1
Link to comment
Share on other sites

I also have a question is there any way to manually control the fans?

Mac Fan control displays 65535-65535 values and doesn't allow to adjust the fans.
On top of that it doesn't read GPU (RX580) temperature and GPU becomes a jet engine under 70%+ load. 

Link to comment
Share on other sites

19 hours ago, Tiem said:

The EFI released works perfectly provided you set up your system as he suggested. Get a proper macOS installer without errors. This is crucial as people use all sorts of dumb ways to make the stick, either pulling an incompatible version or an assortment of errors that either fubar the install process or leave you with a non-working system.

 

Stop and take a step back. Make a USB installer on a real macOS running the latest OS. Ensure it's good and error free. Update your BIOS to the latest revision (F12d for the Pro and F12c for the Pro WIFI, both work with this EFI).

 

Set up the BIOS properly. You need to first enable the dGPU, save settings and reboot, then go right back into the BIOS and finish setting it up. Only then will it list the following settings:

 

 Settings -> IO Ports -> DVMT Pre-Allocated -> 64M

 Settings -> IO Ports -> DVMT Total GFX0-Allocated -> 256M

 Settings -> IO Ports -> Aperture Size -> 256MB

 

That's mostly it. Unplug all your hardware that's not necessary. If you have some kind of radiator cooling system, then you may need to do some fiddling as there are known issues with lots of fancy cooling (by fancy I mean coming from traditional air cooling like the Notcua DH-14). macOS doesn't support anything other than traditional air cooling systems (fan + heatsink).

 

You're throwing up a ton of info, way too much. I get what you're trying to do, but this EFI is bulletproof. You just toss in your EFI partition and you're good. Truly.

 

Did as you said, and for some bizarre reason keyboard and mouse just won't make the connection. Tried this on two separate usb drives having clean install of the the newest Catalina installer.

 

On a hunch (see below) I added USBInjectALL.ktext to the EFI and Viola. This leads me to believe the DSDT is not taking correctly on my build for some bizzare reason?

 

I found that my bluetooth also doesn't work, even though I'm using a BCM94360CS2 card which should/has work OOB (adaptor installed in PCIEX 1_3 just as Audio God).

 

I ran Mojave stable for a long time, and then recently tried to update to Catalina and had many issues. I did find an EFI folder that while "made" for Aorus z390 still used usbinject all which I wanted to get away from in the first place. The reason I am looking for new EFI is because when I tried to update to 10.15.3, the update failed and made my Catalina no longer bootable.

 

I would like to thank all you for you help, but it seems my MOBO is perhaps just an outlier. 

 

 

Link to comment
Share on other sites

OpenCore 0.5.5 was just released. Runs great outside of it messing up the boot screen resolution (both Windows and macOS are under resolution and stretched). YMMV.

 

Get to updating ;)

Link to comment
Share on other sites

19 hours ago, Tiem said:
This is accomplished by turning off wifi in the BIOS. It effectively turns the board into a regular Pro. No difference.


Thanks for the tip, Tiem! I’ll try that vs clambering further around in the config.plist, once I get macOS up & running. For the other OSes, I’ve gotten Linux to use Broadcom drivers before, and I’m sure Windows will either auto-download & apply such, or I’ll just manually get it from Fenvi’s website.
The Pro is what I had planned on anyway for Handoff & Continuity; both NewEgg & Amazon just had a deal with the WiFi for $10 cheaper for a while, so I jumped on it (deal over now).
 

Edited by juan e. jot
Remove weird double-post
Link to comment
Share on other sites

Read me reply to stavidawg above. You must ensure your USB installer is free of errors and the correct one for your machine. Pulling it from a real Mac is the best way to do this. If you used any other method, the problems you face are most likely a bad installer.

 

The EFI can be tested just by booting up the USB installer. Once you replace the default EFI with the one from AudioGod, and boot using the stick, then you are essentially already running it. If all your peripherals are working during the install, then there is no issues with the EFI. It's you. Something on your end.

 

If I had to guess, you had too much clutter. There is no way to disable the M.2 slots on this board. And if you installed other OSes before macOS, then you may have to deal with errors or complications. I installed macOS first but when I installed Windows (onto a separate SATA SSD), it threw it's EFI onto the M.2 partition that macOS had created. Kinda a pain, but it illustrates how complications can easily arise.

 

Unplug everything. If you have other OSes installed on other physical drives, unplug them. Even the M.2 slot, you would do much better if you took the card out to avoid collisions. Triple booting can be a pain as each boot loader has it's own quirks and set of pitfalls.

 

Also, please add your hardware details to your signature.

 

 

Link to comment
Share on other sites

21 hours ago, juan e. jot said:
attempting to install from the macOS Catalina Installer USB with AudioGod’s very considerate provision of a UHD630 EFI gets somewhere between 1/2 and 2/3 through the progress bar and pops up a “forbidden” or “prohibited” symbol & hangs indefinitely. Adding “-v” as a boot arg so I can see in verbose mode what’s going on just pixelates all the text out under the symbol when it pops up, yielding no info.

 


Further research confirms that building the installer from a gibmacos-downloaded copy of 10.15.3 (with AudioGod’s unmodified UHD630 EFI in the EFI partition of the installer USB stick) yields the same “forbidden” or “prohibited” symbol about 1/2 to 2/3 through the progress bar. Interestingly, when I add “-v” to the boot args to get an output of what it’s doing, the symbol still pixelates the text “under” it, but these couple of times (see below) I tried it, I let it run for long enough to see some text continuing to come across non-pixelated in patches, but not an entire line to read, and the text definitely continued to scroll (very slowly) line by line towards the top of the screen, with only black screen being added, and a white cursor in the lower left. So it’s continuing to do… something.

Lastly, I tried this both in the case’s front USB 3.0 port, and one of the motherboard’s USB 2.0 ports, using a USB 2.0 stick; same behavior either way.

Any thoughts as to what might be causing this, any fix; or if the continued activity means it’ll get to the macOS installer screen, how long to wait? It’s been scrolling slowly up the screen for at least an hour and a half now.

FURTHER UPDATE: taking a RAM stick out of B1, and then out of A1, so starting up in either case with only 8GB in a single-channel configuration, still yields the same result as above.

 

FURTHER UPDATE #2: Reading Tiem’s above suggestion, removed m.2 with the other OSes on it & attempted install again. Same result.

 

Since not address by username, I’m not absolutely sure whether Tiem’s most recent post addresses me or another poster, but if me: yes, I’ve noticed the double-posts, was unsure if others saw them (apparently they do; sorry). I think it’s something about the Tapatalk app, and I’ll likely drop its use.
 

Sorry to double-bombard so far, anyway! I’d still appreciate any insight, and don’t plan to throw any money at having someone else just do it; I’m building a Hackintosh to learn. I’m asking here because I was under the impression it’s a shared resource.

 

Thanks!

Edited by juan e. jot
Add yet more additional info, clean up rest of weird double-post
Link to comment
Share on other sites

Sorry dude, from your continual double posted replies I'm thinking this is just beyond you. I think you may be lacking in some very important foundational knowledge and are getting spun around.

 

You may just want to put an ad out in your local area asking for someone who can come over and set it up for you. Tossing them even $100 for the effort seems like a way better use of time vs. cost.

  • Like 2
Link to comment
Share on other sites

Juan,

If you wipe everything you've done to date, reset your BIOS to factory settings and let someone else with some technical acumen (previous Hackintosh skills a bonus!)  come in with a fresh pair of eyes and none of your preconceptions, let them work the guide and you just watch what they do., it might be both a solution and a learning experience.

That might be the easiest way to find out what steps you've been missing or doing incorrectly.

Just don't give them advice or tell them what you think is wrong.  Let them approach it clean.

Of course, you do what you think best, but that's what I would do if I were in your shoes.  Good luck, my friend!

Edited by map002
Clarity
  • Like 2
Link to comment
Share on other sites

1 hour ago, WizeMan said:

Hi @AudioGod & @texem

 

Is there some particular reason that SIP is disabled on the OpenCore variant?


<key>csr-active-config </key>
<data>ZwAAAA==</data>

➜  ~ csrutil status
System Integrity Protection status: disabled.
➜  ~ 

Will it hurt if I enable it? 

 

 

https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&amp;comment=2674754

  • Like 1
Link to comment
Share on other sites

Hi...

Very nice and useful guide.

Had to change my mobo from Asus to the Z390 Aorus Ultra due a crash on the Asus.

I followed your guide and everything was good..

Except that I'm getting a boot failure on restart. After that (switching OFF and ON again on) but shows this KP message..

May be you can help to discover why?? Been fighting with this for the past 2 days....

Installation was clean and i9 9900K, Z390 Aorus Ultra, 64 gb mem, Radeon 64 8gb. boot on Nvme Samsung 970 pro 1tb.

Attached the kernel

 

thank you for your time and help

 

Marcelo

Screen Shot 2020-02-04 at 6.52.51 PM.png

  • Confused 1
Link to comment
Share on other sites

×
×
  • Create New...