Contribute
Register

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

If your workflow requires you to put the computer to sleep regularly, then lowering memory speed to 2666 MHz can prevent "disk not ejected" errors when sleep is invoked. It can also reduce wake-up time and allow you to remove darkwake completely and still wake with a single keypress.

If your workflow does not require frequent sleep, just keep your memory at its full rated speed.

Does lowering to 2666MHz have to be done in UEFI or can we set it via Clover so that it affects macOS only?
 
Yes, this is the 64 thousand dollar question. If anyone has any suggestions, please let us know.

In “About this Mac” there is a Memory tab that graphically depicts memory slots. What do you see there?

In my other post I stated that tab didn't exist and I posted a dump of system info.

I did come up with the closest test I could think of. I figured that regardless of SMBIOS, if I overcommitted more RAM than the system actually had (after all, I can lie to it and make everything I've checked think there is 128GB if I want), things would go bad quickly.

So with a 96GB SMBIOS and 96GB of actual RAM, I used a RAM Disk Creator to make a 64GB RAM Disk. If my 2 32GB UDIMMs were completely unusable and somehow bypassed, this would mean that I only had 32GB Memory and that RAM Disk would be double the memory. If the SMBIOS hack made Mac only utilize 16GB on each 32GB UDIMM then that RAM Disk would be 100% of system memory.

So I created it successfully and copied as many files as I could. Only 3.7MB left on the RAM Disk. I then ran CleanMyMac's free RAM. The files were retained. That feature usually does cause a bit of swap space to be created, but right now it's only 65MB in use according to iStats Menus.

I'm going to let it run for awhile and see if it behaves reasonably. Should I really be using the RAM as expected, that means I should have 32GB not taken up by the RAM Disk right now, which is what I'd have max if I didn't have the 2 32GB UDIMMs installed and that was enough to use the system normally. My 2012 iMac is maxed out at 32GB and my 2019 iMac at work has 40GB.
 
If your workflow requires you to put the computer to sleep regularly, then lowering memory speed to 2666 MHz can prevent "disk not ejected" errors when sleep is invoked. It can also reduce wake-up time and allow you to remove darkwake completely and still wake with a single keypress.

If your workflow does not require frequent sleep, just keep your memory at its full rated speed.

I use darkwake zero and only have internal disks...so than thats no matter to me, thanks for pointing that out
 
Ive completed this build, but I have a few issues related to the display. I'm using a 43" 4K TV. In Windows this display works great. I have used it with my MacBook Pro, and it's decent. I scaled the OS down to 1080 and ran some Terminal lines to help with the font rendering. It still bothers my eyes in a short amount of time. Can this be corrected further?

Also, Chrome and youtube via Chrome look poor. Playing video back is decent but the thumbnails are are messed up. If you are playing a video and grab the window to resize, the picture drops out until the window is let go.

Also, I'm noticing some glitchiness with the mouse pointer. I'm using a cheap Logitech wireless combo. I had no issue in Window 10 with this combo.
Here are some general tips for connecting this system to a flatscreen TV:
  • If the TV has a low-latency HDMI port designated for gaming consoles or computer connections, use that port.
  • Disable UHD Color, HDR, and similar functions. Consult the TV's manual to determine if there's a section for computer connections. Many Samsung TV manuals contain such a section.
  • Connect the AMD GPU to the TV instead of the built-in HDMI on rear IO panel.
  • In Preferences --> Displays, specify a lower resolution (1080p is good) and lower refresh rate such as 30Hz or 24Hz. Consult the TV user's manual for a list of supported resolutions and refresh rates.
 
Does lowering to 2666MHz have to be done in UEFI or can we set it via Clover so that it affects macOS only?
Oh, that's a good question! Anyone want to try it? (It will take me a few days to get around to it.)
 
In my other post I stated that tab didn't exist and I posted a dump of system info.

I did come up with the closest test I could think of. I figured that regardless of SMBIOS, if I overcommitted more RAM than the system actually had (after all, I can lie to it and make everything I've checked think there is 128GB if I want), things would go bad quickly.

So with a 96GB SMBIOS and 96GB of actual RAM, I used a RAM Disk Creator to make a 64GB RAM Disk. If my 2 32GB UDIMMs were completely unusable and somehow bypassed, this would mean that I only had 32GB Memory and that RAM Disk would be double the memory. If the SMBIOS hack made Mac only utilize 16GB on each 32GB UDIMM then that RAM Disk would be 100% of system memory.

So I created it successfully and copied as many files as I could. Only 3.7MB left on the RAM Disk. I then ran CleanMyMac's free RAM. The files were retained. That feature usually does cause a bit of swap space to be created, but right now it's only 65MB in use according to iStats Menus.

I'm going to let it run for awhile and see if it behaves reasonably. Should I really be using the RAM as expected, that means I should have 32GB not taken up by the RAM Disk right now, which is what I'd have max if I didn't have the 2 32GB UDIMMs installed and that was enough to use the system normally. My 2012 iMac is maxed out at 32GB and my 2019 iMac at work has 40GB.
This seems like a very reasonable methodology. You can even create a larger RAM disk. For example, an 80GB RAM disk ensures that some part of all 4 memory modules will be used.
 
hey y'all.
I'm on clover 4.9.2.0 and I see that 5.5.0.0 has released.
Is it really worth it to update it?
I'm worried that the update will mess with a perfect/stable build!
Thanks
In general, it's best not to modify a stable system. That being said, the tinkerers and rebels among us will want to update to the latest and greatest. To do that, one should have a full bootable backup in place and be comfortable with the procedure for updating Clover and switching from CLOVER/drivers64UEFI folder to CLOVER/drivers/UEFI folder.
 
@skittlebrau @CaseySJ Unfortunately you will have to change it in UEFI. Setting it in Clover will not work, already tried that.
 
Thank you @CaseySJ this helped me tremendously.

2 notes:
- the aptio fix free2000 shouldn’t be used since the developer explained that it will eventually kill your hardware at a point in time, could be now or in five years, but it will kill it.
- for using igpu in headless mode with the Radeon VII you should leave the Device - Properties tab in Clover empty and use the 19.1 Smbios. Using an ID in properties won’t work. But also you need the dangerous aptio fix. So at this point in time the only wise thing to do is to disable igpu and use the Imac pro smbios (still keeping all Device Properties empty).
 
Back
Top