Contribute
Register

[SUCCESS] ASUS TUF Z390M-PRO GAMING - i7 9700K - RX 580

Status
Not open for further replies.
Thanks @NZRichard

I completely agree with you on this. I went through similar process for various builds and selected a 650w/750w 80+ Corsair and an EVGA and I monitor the actual usage as well. Will update my previous message to ensure the 450w comment isn't mis-understood

@dlgoodchild

FYI



Don't skimp on the PSU and go for 650 Watts or more. As a double check run through the Seasonic Wattage Calulator

In practice there is more to selecting a PSU than wattage - look for a top quality brand that features Japanese capacitors in the build. If in doubt check the reviews on Jonny Guru
 
So, I finally received the last of the parts on Friday.

I've literally spent all weekend trying to get either Mojave or Catalina installed. Both keep freezing at the 2 minute mark during the first stage of the install. Any one experience that?

To minimise duplication I posted full details here: https://www.tonymacx86.com/threads/...and-nvram-support.275272/page-28#post-2112221
The two builds are very similar.

UPDATE-01
Finally got the installation completed with the help of post #1 and #6 of this thread.
If I boot the macOS using the USB, everything works great and it boots very quickly.

After having used MultiBeast the system simply won't boot, the progress bar shows and advances extremely slowly, but never finally boots. I left it some 30 minutes just to see what would happen.

This is now fixed by applying the ASUS_ACPI patch to the SSD EFI, just as was required by the USB EFI.

UPDATE-02
There appears to be only one remaining issue. If the system enters sleep, it crashes and restarts.
For now, the automatic sleep has been disabled in "Energy Saving" options.
 
Last edited:
Any ideas?

OK - you have made good progress. Now about the system not booting after MultiBeast:

First, know that your USB includes Clover which is working fine - "everything works great and it boots very quickly."

Something in your MultiBeast is hanging up the boot. So try this:

1. Copy the EFI folder from your USB drive

2. Delete the files in the EFI folder on your internal (SSD) drive

3. Paste the EFI folder from your USB drive to the EFI folder on the SSD

Let us know how it goes.
 
OK - you have made good progress. Now about the system not booting after MultiBeast:

First, know that your USB includes Clover which is working fine - "everything works great and it boots very quickly."

Something in your MultiBeast is hanging up the boot. So try this:

1. Copy the EFI folder from your USB drive

2. Delete the files in the EFI folder on your internal (SSD) drive

3. Paste the EFI folder from your USB drive to the EFI folder on the SSD

Let us know how it goes.

Thanks @NZRichard... I've not long worked out the issue, quite a silly mistake on my part. I hadn't applied the ASUS_ACPI patch to the SSD EFI which I had done earlier against the USB EFI. Doing this has fixed the boot issue. My next step was going to be to do as you described, but it looks like that's not necessary. It's booting very quickly and in general feels quite stable to use.

My only remaining issue so far, to my knowledge, is sleep crashing the system. So in the meantime I've disabled the ability for it to automatically sleep. At this point it feels successful enough for me to be happy using it, but I will try to fix that. I need to take a break from it and come at it fresh, it's quite an exhausting experience if you're completely new to this.
 
I've not long worked out the issue

Be sure to archive the EFI folder that is now working - may come in handy. Now, about the sleep crashing issue:

First of all could you please clarify the following:
1. Mac OS Catalina version and build number, e.g., About This Mac: Version 10.15.4 (Build 19E287)
2. Clover Version? Installed from tonymacx86 Clover Builds or downloaded from Sourceforge.net?
3. Are you using emulated NVRAM from tonymacx86 Clover Builds? or downloaded and configured manually? or no?

In an earlier post you mentioned you were not sure what solved the "2 minute freeze" install problem - most likely it was the EmuVariableUefi-64 kext, which enables NVRAM that seems to be missing from the Z390M Pro mobo.

When the Z390M Pro was released in 2018 it took a while to figure out how to use emulated NVRAM, which solved the "2 minute freeze" that is really a restart problem. It also solved a sleep-crash issue. That's why i asked if you are using Clover with emulated NVRAM. As well as installing EmuVariableUefi-64 it was also recommended to install RC scripts.

If you can shut down and also restart your system OK while still having issues with sleep it's possible that you either need emulated NVRAM or you don't have it configured properly.

Your comments may help others.
 
I've now archived both the USB EFI and the SSD EFI.

1. macOS Catalina 10.15.4 (19E287), Kernel Darwin 19.4.0
2. I used UniBeast 10.1.0 and MultiBeast 12.1.0, the Clover version is 5107 on both USB and SSD EFI. I never installed Clover directly, should I have done? I'm going to reboot to check the Clover version that shows from the SSD.
3. I believe I used emulated NVRAM via "EmuVariableUefi-64" on the USB. In MultiBeast I selected the SSDT "Z390 Series NVRAM Support", which I believe was the SSDT attached to @MacMan's original post?

Regarding:
> it was also recommended to install RC scripts
I don't know what these RC scripts are, I've not come across them?

Within MultiBeast I definitely selected the "Clover UEFI Boot Mode", and not the option with emulated NVRAM.

Discovered a new issue. Restarting/shutting down is now also causing BIOS to go into safe mode.
I've made no further changes to my configuration. Currently the BIOS safe mode annoys me more than the lack of sleep-mode.

Maybe I'll experiment and move to using the Emulated NVRAM and drop the SSDT Z390 version just to see if there's any change there.
 
Last edited:
Maybe I'll experiment and move to using the Emulated NVRAM and drop the SSDT Z390 version just to see if there's any change there.

Experimenting is good!

In your post #172 you mentioned "Within MultiBeast I definitely selected the "Clover UEFI Boot Mode", and not the option with emulated NVRAM," which sounds like you may NOT have NVRAM configured on your SSD.

Here's something to try:
1. Boot the system from the USB (not the SSD) - you know the drill:
- from a cold boot enter the BIOS (Hold Delete key) -> go to Boot Menu and select the UEFI on the USB drive ....
- boot the SSD from Clover (now you are in Catalina using the Clover from your USB which has NVRAM, right?)

2. Try putting system to sleep - does it crash or wake up on a mouse click or key press? Can you restart without a crash? Can you shut down and then boot system?

3. Now restart your system with USB removed, i.e. boot from the SSD using the Clover on the SSD. Repeat #2.

Any difference between the two Clover boot loaders?
 
I don't know what these RC scripts are, I've not come across them?

This was recommended when we were just starting to figure out NVRAM for the Z390M Pro using older versions of Clover, e.g., v2.4k r4741 (November 2018). Think you can ignore this with the later versions of Clover.

Update 1:
According to tonymacx86 RC scripts were originally installed in the MultiBeast for Emulated NVRAM option.
 
Last edited:
Status
Not open for further replies.
Back
Top