Glasgood's macOS Mojave [SUCCESS][GUIDE] for Aorus Z390 Pro

[glasgood]

17 minutes ago, BSouza said:

I had some problems while doing the process:

1 - my external hd apparently worked on USB 3.0 ports

2 - sleep is not working, after I click on sleep, the screen goes black and the pc is still on, after a period it turned the screen back on its own, but the mouse click did not work nor the keyboard keys

3 - After locking in sleep I was forced to manually turn off the pc, and the motherboard lights do not turn off after the forced shutdown.

PS. I did not have a kernel panic.

 

No problem with sleep on, POST-INSTALL Aorus Pro Z390 EFI - RX580. I don't personally use intel, so was not inclined to test sleep fully. Try enabling XPRW change Method(GPRW... in config.plist below. It will stop wake from sleep.

You will have to press power on button on Hackintosh to wake from sleep when patch is enabled.

 

 

 

@BSouza

 

What BIOS version are you running ?

[glasgood]

@BSouza

 

Have a look at section in guide ==> SLEEP  – Sleep and Automatic Sleep have a look at my power info in Hackintool Power tab. 

 

 

[BSouza]

5 minutes ago, glasgood said:

 

No problem with sleep on, POST-INSTALL Aorus Pro Z390 EFI - RX580. I don't personally use intel, so was not inclined to test sleep fully. Try enabling XPRW change Method(GPRW... in config.plist below. It will stop wake from sleep.

You will have to press power on button on Hackintosh to wake from sleep when patch is enabled.

 

 

 

@BSouza

 

What BIOS version are you running ?

Bios F9

Ok, sleep is not so important, I'll leave it to solve this when I get to rx580. The most important is about USB. Is there any way to verify that all usbs are being recognized and working normally? Because it seems to me that something strange, if I connect my keyboard (k68 rgb) to a USB 3.0 port, restarting the system the keyboard stops working.

[glasgood]

11 minutes ago, BSouza said:

Bios F9

Ok, sleep is not so important, I'll leave it to solve this when I get to rx580. The most important is about USB. Is there any way to verify that all usbs are being recognized and working normally? Because it seems to me that something strange, if I connect my keyboard (k68 rgb) to a USB 3.0 port, restarting the system the keyboard stops working.

 

Use IORegistryExplorer.app to view USB. ( below )  in the past, I did use a Corsair K65 rgb keyboard an used this ==> driver 

 

 

[BSouza]

13 minutes ago, glasgood said:

 

Use IORegistryExplorer.app to view USB. ( below )  in the past, I did use a Corsair K65 rgb keyboard an used this ==> driver 

 

 

correct?

[adamsor]

Just wanted to post to say THANK YOU Glasgood. After struggling a lot with getting a Mojave boot drive set up, I finally switched out my Pro Wifi for a Pro, and your EFI packages have worked beautifully. Thanks again!!

[glasgood]

7 minutes ago, adamsor said:

Just wanted to post to say THANK YOU Glasgood. After struggling a lot with getting a Mojave boot drive set up, I finally switched out my Pro Wifi for a Pro, and your EFI packages have worked beautifully. Thanks again!!

 

Thanks for the feedback,  much appreciated ! 

[AudioGod]

Hello Bro I hope your good my friend.

I have made a very important discovery about our motherboards.

If you have a profile or overclock running on your memory then please disable VTD in the bios as it makes your memory unstable. Memtestx86 cant see it but if you run memtest or any other memory stress test program within windows with vtd enabled its gonna fail your ram and call them unstable. I have just been though 3 sets of memory thinking they were bad when all the time it was VTD being enabled.(this was with using the memory standard profile) Please test on your side and see for yourself buddy or just trust me on this one and disable VTD asap. What a nightmare that was for me and thank goodness I got to the bottom of it. Phew!

Edited June 21, 2019 by AudioGod

[glasgood]

10 minutes ago, AudioGod said:

Hello Bro I hope your good my friend.

I have made a very important discovery about our motherboards.

If you have a profile or overclock running on your memory then please disable VTD in the bios as it makes your memory unstable. Memtestx86 cant see it but if you run memtest or any other memory stress test program within windows with vtd enabled its gonna fail your ram and call them unstable. I have just been though 3 sets of memory thinking they were bad when all the time it was VTD being enabled.(this was with using the memory standard profile) Please test on your side and see for yourself buddy or just trust me on this one and disable VTD asap. What a nightmare that was for me and thank goodness I got to the bottom of it. Phew!

 

@AudioGod

 

Howdy ,

 

Ok thats good to know, I don't have any overclocks on my board so possibly why I not encountered any problems with VTD enabled. Will put a side note next to guide about it. Though disabling VTD may stop some Virtual Machines, VM ware from running properly for some.

 

 

 

[AudioGod]

33 minutes ago, glasgood said:

 

@AudioGod

 

Howdy ,

 

Ok thats good to know, I don't have any overclocks on my board so possibly why I not encountered any problems with VTD enabled. Will put a side note next to guide about it. Though disabling VTD may stop some Virtual Machines, VM ware from running properly for some.

 

 

 

 

I wasnt running my overclock on the ram or cpu when  I tested. I was running everything at stock other then having the memory profile switched on bringing it up too 3200mhz but again this is factory OC and nothing to do with me...lol

As for VTD messing with virtual machines if its switched off. I don't think that would be the case as Virtual machines within windows still work with it disabled. I'm trying to remember a scenario where VTD has a real world use but I'm struggling (completed my mcsa and mcse over 20 years ago)....lol, I will have a word with der8auer about it when I next talk to him as my work has an account with casekings in Germany so im matey with him.

Edited June 21, 2019 by AudioGod

[glasgood]

1 minute ago, AudioGod said:

 

I wasnt running my overclock on the ram or cpu when  I tested. I was running everything at stock other then having the memory profile switched on bringing it up too 3200mhz but again this is factory OC and nothing to do with me...lol

As for VTD messing with virtual machines if its switched off. I don't think that would be the case as Virtual machines within windows still work with it disabled. I'm trying to remember a scenario where VTD has a real world use but I'm struggling (completed my mcsa and mcse over 20 years sgo)....lol, I will have a word with der8auer about it when I next talk to him as my work has an account with casekings in Germany so im matey with him.

 

lol, you went further than me, I did MCP ( 70-210, 70-215 ) and A+ Certifications 20 years ago . 

[AudioGod]

QUOTE -  "If you are just running VirtualBox, VM Player, and just need to run an additional occasional OS... then VTD is not that important. If you are providing a virtual service, hosting guests, running something where you need the performance of running on metal ... then very important"

 

So basically for the majority of people you don't need it and if you overclock in anyway shape or form or use high speed memory then your best bet is too just disable it.

 

I've taken over a system at work and I'm running the same tests I'm running at home and kicking up the same errors under the same workloads so it sure ain't my motherboard or builds fault.

The testing goes on!

Edited June 21, 2019 by AudioGod

[glasgood]

3 minutes ago, AudioGod said:

QUOTE -  "If you are just running VirtualBox, VM Player, and just need to run an additional occasional OS... then VTD is not that important. If you are providing a virtual service, hosting guests, running something where you need the performance of running on metal ... then very important"

 

So basically for the majority of people you don't need it and if you overclock in anyway shape or form it use high speed memory then your best bet is too just disable it.

 

I've taken over a system at work and I'm running the same tests I'm running at home and kicking up the same errors under the same workloads so it sure ain't my motherboard or builds fault.

The testing goes on!

 

Was just checking to see if my CPU ( i7-8700 ) had VT-d capabilities, it does! Apparently was reading, if your CPU has no VT-d then option in BIOS has no effect if enabled.  

So definitely specialist virtualisation option in BIOS and not going to cause problems with VMWare / Parallels for Mac.

 

 

 

 

 

 

@AudioGod

 

Will update BIOS screendump images soon to indicate VT-d setting as disabled. Cheers!

[glasgood]

@AudioGod

 

What problem did you initially have that made you track this down as cause of fault or was it just through mem test ?

Edited June 21, 2019 by glasgood

[AudioGod]

20 minutes ago, glasgood said:

@AudioGod

 

What problem did you initially have that made you track this down as cause of fault or was it just through mem test ?

I was about to put my ram too what it can overclock safely too (3600mhz) but I thought I would do a burn in test on the ram beforehand and that's when I discovered the problem as my memory wouldn't pass a run via windows memory or hci memtest (including the replacement mobiles I tried) until u disabled vtd and then it all snapped back to normal and passed all tests. I then at work did the same test with vtd on via hci memtest and the same thing happened and this was using a asus x299 board and a 7900x with quad channel memory.

As it's just been pointed out to me though the errors its chucking out wouldn't cause a system failure and you wouldnt notice it in the real world and that's why memtest86 passes it but still when you have OCD like I do you cant just leave it at that and for the sake of something your never gonna use just turn it off I say...lol

[soniferous_fox]

I managed to get the USB ports all sorted using your other guide, so thanks for that! I have 14 and all seem to be working. Took me a while to figure out that you need use both the SS and the HS for a particular port if you want to be able to plugin both 3.0 and 2.0, but I got there!

 

Unfortunately, the sleep disk eject fix still doesn't't work for me  - I guess I will be trying Jettison after all. 

 

Thanks again for all your help. 

[soniferous_fox]

If anyone is interested I did some more digging on the sleep/eject thing, seeing as I couldn't't fix it with the script. I found this interesting thread: https://www.tonymacx86.com/threads/usb-drives-getting-ejected-when-hackintosh-wakes-from-sleep-with-xmp-enabled.251488/

 

Sure enough, if I disable the XMP profile in the BIOS the issue goes away. Don't really want to do that though so may have to live with it, unless I can figure out how to do the manual clock in the BIOS! Would be nice to figure out exactly why the memory frequency effects things, and if clover could fix it in any way, but that is totally beyond me!

[glasgood]

13 hours ago, soniferous_fox said:

If anyone is interested I did some more digging on the sleep/eject thing, seeing as I couldn't't fix it with the script. I found this interesting thread: https://www.tonymacx86.com/threads/usb-drives-getting-ejected-when-hackintosh-wakes-from-sleep-with-xmp-enabled.251488/

 

Sure enough, if I disable the XMP profile in the BIOS the issue goes away. Don't really want to do that though so may have to live with it, unless I can figure out how to do the manual clock in the BIOS! Would be nice to figure out exactly why the memory frequency effects things, and if clover could fix it in any way, but that is totally beyond me!

 

@soniferous_fox

 

 

Interesting,

 

I have never had XMP enabled, so without XMP enabled and without using fixUSB.sh script ( on my hack ) the "disk did not eject properly" message persists. But when using the fixUSB.sh script with XMP disabled then "disk did not eject properly" is fixed.

 

 

Edited June 22, 2019 by glasgood

[glasgood]

20 hours ago, AudioGod said:

I was about to put my ram too what it can overclock safely too (3600mhz) but I thought I would do a burn in test on the ram beforehand and that's when I discovered the problem as my memory wouldn't pass a run via windows memory or hci memtest (including the replacement mobiles I tried) until u disabled vtd and then it all snapped back to normal and passed all tests. I then at work did the same test with vtd on via hci memtest and the same thing happened and this was using a asus x299 board and a 7900x with quad channel memory.

As it's just been pointed out to me though the errors its chucking out wouldn't cause a system failure and you wouldnt notice it in the real world and that's why memtest86 passes it but still when you have OCD like I do you cant just leave it at that and for the sake of something your never gonna use just turn it off I say...lol

 

Just turned off VT-d on my own hack and updated guide, new BIOS screenshot uploaded. Cheers!

[micllave]

thank you Glasgood!

 

this has been the only successful process i had in building my Hackintosh.. super comprehensive and easy to follow! cheers!

[glasgood]

6 minutes ago, micllave said:

thank you Glasgood!

 

this has been the only successful process i had in building my Hackintosh.. super comprehensive and easy to follow! cheers!

 

Enjoy your hackintosh! 

Cheers 

[soniferous_fox]

15 hours ago, glasgood said:

Interesting,

 

I have never had XMP enabled, so without XMP enabled and without using fixUSB.sh script ( on my hack ) the "disk did not eject properly" message persists. But when using the fixUSB.sh script with XMP disabled then "disk did not eject properly" is fixed.

 

Fixed it!! Through another simpler script I found, some googling, trial & error in terminal, I figured out that it was the number of disks I have that was the problem. Basically I have 5 internal disks and some are partition and RAID, so all of my external disks were being given numbers of 10 or above and the script that the fixUSB.sh script uses will only find disks 0-9. So after reading up on the grep command, I discovered that you needed to write it as [0-9][0-9] to return double figures, and now it finds disks 10 and above and works! I couldn't figure out how to get it to look for anything below 10 though, but for me I don't think will be a problem.

[AudioGod]

Morning Buddy,

I just updated clover to the newest stable version and finally got around to updating my pci info now I've changed my gpu to the Vega56. only strange thing that's started happening since my gpu swap is the clover startup gui is no longer going to the resolution I set it too and is defaulting to a big and ugly res...lol

this happened as soon as I swapped the cards out and before I made any changes too clover. any ideas what it could be?

I've included my bootleg, will you flick your wise eyes though it and see if it all looks ok please buddy or I can send you my efi folder if you prefer?

 

bootlog.txt

[glasgood]

1 hour ago, AudioGod said:

Morning Buddy,

I just updated clover to the newest stable version and finally got around to updating my pci info now I've changed my gpu to the Vega56. only strange thing that's started happening since my gpu swap is the clover startup gui is no longer going to the resolution I set it too and is defaulting to a big and ugly res...lol

this happened as soon as I swapped the cards out and before I made any changes too clover. any ideas what it could be?

I've included my bootleg, will you flick your wise eyes though it and see if it all looks ok please buddy or I can send you my efi folder if you prefer?

 

bootlog.txt

 

Afternoon ,

 

You could try and disable CSM Support in BIOS, then reboot and see if resolution changes. If resolution is unchanged, then enter Screen Resolution in Clover Config.plist in the Gui section and reboot and test.

 

 

 

 

 

Again if resolution still remains unchanged then you could try the following:

 

Enable CSM, and download CsmVideoDxe:

 

 

These are the only areas that I can think that will change resolution. 

 

 

I read that as of macOS Moajave 10.14.5, the fan issue with vega cards has been resolved, is that the case ?

 

Best!

 

 

 

Edited June 23, 2019 by glasgood

[glasgood]

1 hour ago, AudioGod said:

Morning Buddy,

I just updated clover to the newest stable version and finally got around to updating my pci info now I've changed my gpu to the Vega56. only strange thing that's started happening since my gpu swap is the clover startup gui is no longer going to the resolution I set it too and is defaulting to a big and ugly res...lol

this happened as soon as I swapped the cards out and before I made any changes too clover. any ideas what it could be?

I've included my bootleg, will you flick your wise eyes though it and see if it all looks ok please buddy or I can send you my efi folder if you prefer?

 

bootlog.txt

 

Glad you got this fixed.