Contribute
Register

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

skittlebrau said:
Does lowering to 2666MHz have to be done in UEFI or can we set it via Clover so that it affects macOS only?
Click to expand...
CaseySJ said:
Oh, that's a good question! Anyone want to try it? (It will take me a few days to get around to it.)
Click to expand...
jhahn said:
@skittlebrau @CaseySJ Unfortunately you will have to change it in UEFI. Setting it in Clover will not work, already tried that.
Click to expand...
As I've stated before, this works in mobo BIOS (UEFI). The changes in Clover Configurator spoof About This Mac and System Report. But, if you run Geekbench (I'm on v4), the output score only reflects what you have set in UEFI. Changes in SMBios don't do a thing, and the Eject error still occurs.
It seems that except cosmetically in About This Mac / System Report, the computer still runs on UEFI / Mobo BIOS, as if the the motherboard supersedes clover.

I'm wondering if then this means that it is an issue with the motherboard itself... Or a combination of that and some kind of power management issue (either with the motherboard or Mac profile (iMac 19,1 or iMac Pro). These setting all affect sleep, too. So who knows. It could possibly not even be a memory limit or some kind of power limit. My logic tells me that wake from sleep I limited by actual power somehow. For instance, faster memory draws more power, so the system compensates with eject.
Now, I'm not 100% sure and can't confirm because I'm having trouble getting a reply from these folks, but I believe Mojave 10.14.3 (+/-) didn't have remounting issues and ejects were *possibly solved somehow. Perhaps Apple disabled the remount command or the ability for the system to see drives that have been Ejected/unmounted (*** ALSO WHY JETTISON DOESN'T WORK TO REMOUNT - it only ejects before sleep, but will not remount).

**EDIT1**: It may also compensate with disabling "remount", to make sure the computer has enough power to wake. The issue is, even after wake-up, I can't manually mount the USB drives again. They show up in jettison, but terminal can't see them.. So perhaps, the Eject/Unmount commands are *permanent* somehow, as to force someone to re-plig the drives. And/or, the motherboard could be interpreting it as permanent eject command... If this is the case, perhaps it wasn't the case with earlier version of the UEFI bios, however I believe earlier versions also didn't allow higher memory speeds anyway (not sure this is true, but feel free to correct me), so it wouldn't matter much.

This is still a mystery to me except setting the memory to 2666 MHz. (2700 MHz works for eject issues, but one of you reported it still causes other sleep issues. If you could please clarify if that just means you have to still use darkwake settings in Clover or not).

Anyhow, I'm still waiting on replies from people elsewhere with builds on 10.14.3 to reply to me, to see if there was something specifically that they odd that fixed it, or if it worked on 10.14.3 and fell apart when updating to a newer OS revision.
 
Last edited:
CN7 said:
As I've stated before, this works in mobo Bios (UEFI). The changes in clover configurator spoof About This Mac and System Report, but if you run Geekbench (I'm on v4), the output score only reflects what you have set in UEFI. Changes in SMBios don't do a thing, and the Eject error still occurs.
It seems that except cosmetically in About This Mac / System Report, the computer still runs on UEFI / Mobo BIOS, as if the the motherboard supersedes clover.

I'm wondering if then this means that it is an issue with the motherboard itself... Or a combination of that and some kind of power management issue (either with the motherboard or Mac profile (iMac 19,1 or iMac Pro). These setting all affect sleep too so who knows. It could possibly not even be a memory limit or some kind of power limit. My logic tells me that wake from sleep I limited by actual power somehow. For instance, faster memory draws more power, so the system compensates with eject.
Now, I'm not 100% sure and can't confirm because I'm having trouble getting a reply from these folks, but I believe Mojave 10.14.3 (+/-) didn't have remounting issues and ejects were *possibly solved somehow. Perhaps Apple disabled the remount command or the ability for the system to see drives that have been Ejected/unmounted (*** ALSO WHY JETTISON DOESN'T WORK TO REMOUNT - it only ejects before sleep, but will not remount).

**EDIT1**: It may also compensate with disabling "remount", to make sure the computer has enough power to wake. The issue is, even after wake-up, I can't manually mount the USB drives again. They show up in jettison, but terminal can't see them.. So perhaps, the Eject/Unmount commands are *permanent* somehow, as to force someone to re-plig the drives. And/or, the motherboard could be interpreting it as permanent eject command... If this is the case, perhaps it wasn't the case with earlier version of the UEFI bios, however I believe earlier versions also didn't allow higher memory speeds anyway (not sure this is true, but feel free to correct me), so it wouldn't matter much.

Anyhow, this is still a mystery to me except setting the memory to 2666 MHz. (2700 MHz works for eject issues, but one of you reported it still causes other sleep issues. If you could please clarify if that just means you have to still use darkwake settings in Clover or not).

Anyhow, I'm still waiting on replies from people elsewhere with builds on 10.14.3 to reply to me, to see if there was something specifically that they odd that fixed it, or if it worked on 10.14.3 and fell apart when updating to a newer OS revision.
Click to expand...

The issue is not motherboard related. I have the same issue with a Z390 Aorus Master Board.
 
Would be interesting to see if other brands are also affected.
 
  • Like
Reactions: CN7
CN7 said:
As I've stated before, this works in mobo Bios (UEFI). The changes in clover configurator spoof About This Mac and System Report, but if you run Geekbench (I'm on v4), the output score only reflects what you have set in UEFI. Changes in SMBios don't do a thing, and the Eject error still occurs.
It seems that except cosmetically in About This Mac / System Report, the computer still runs on UEFI / Mobo BIOS, as if the the motherboard supersedes clover.

I'm wondering if then this means that it is an issue with the motherboard itself... Or a combination of that and some kind of power management issue (either with the motherboard or Mac profile (iMac 19,1 or iMac Pro). These setting all affect sleep too so who knows. It could possibly not even be a memory limit or some kind of power limit. My logic tells me that wake from sleep I limited by actual power somehow. For instance, faster memory draws more power, so the system compensates with eject.
Now, I'm not 100% sure and can't confirm because I'm having trouble getting a reply from these folks, but I believe Mojave 10.14.3 (+/-) didn't have remounting issues and ejects were *possibly solved somehow. Perhaps Apple disabled the remount command or the ability for the system to see drives that have been Ejected/unmounted (*** ALSO WHY JETTISON DOESN'T WORK TO REMOUNT - it only ejects before sleep, but will not remount).

**EDIT1**: It may also compensate with disabling "remount", to make sure the computer has enough power to wake. The issue is, even after wake-up, I can't manually mount the USB drives again. They show up in jettison, but terminal can't see them.. So perhaps, the Eject/Unmount commands are *permanent* somehow, as to force someone to re-plig the drives. And/or, the motherboard could be interpreting it as permanent eject command... If this is the case, perhaps it wasn't the case with earlier version of the UEFI bios, however I believe earlier versions also didn't allow higher memory speeds anyway (not sure this is true, but feel free to correct me), so it wouldn't matter much.

Anyhow, this is still a mystery to me except setting the memory to 2666 MHz. (2700 MHz works for eject issues, but one of you reported it still causes other sleep issues. If you could please clarify if that just means you have to still use darkwake settings in Clover or not).

Anyhow, I'm still waiting on replies from people elsewhere with builds on 10.14.3 to reply to me, to see if there was something specifically that they odd that fixed it, or if it worked on 10.14.3 and fell apart when updating to a newer OS revision.
Click to expand...
I'm sorry but what exactly is the readers digest of the issue? If you run your memory faster then 2666 you start seeing shutdown / sleep problems??
 
At 2666MHz and below, there is no USB eject issue and darkwake settings are not necessary in Clover.

Above that, darkwake settings must be set and USB drives eject improperly during sleep and don't remount, regardless of using a script or an app like Jettison.
 
Rulebreaker01 said:
The issue is not motherboard related. I have the same issue with a Z390 Aorus Master Board.
Click to expand...
That is also a Gigabyte board. Same brand as the Designare.
 
Alright guys, so first time PC builder and I ordered all the recommended parts. Especially i9 9900K and RX580 with 32 GB of Ram. Everything worked in first attempt. Thanks guys for providing very detailed guide. It makes installing Hackintosh without a hitch. In my system, Thunderbold shows no driver found but I have nothing to test if thunderbold works or not. One thing I am not sure was where to find the EFI folder on the system drive. I had it on USB where I formatted it during installation but don't see on local drive.
 
albertaguy said:
Alright guys, so first time PC builder and I ordered all the recommended parts. Especially i9 9900K and RX580 with 32 GB of Ram. Everything worked in first attempt. Thanks guys for providing very detailed guide. It makes installing Hackintosh without a hitch. In my system, Thunderbold shows no driver found but I have nothing to test if thunderbold works or not. One thing I am not sure was where to find the EFI folder on the system drive. I had it on USB where I formatted it during installation but don't see on local drive.
Click to expand...
Thunderbolt should show under the PCI section in System Report.

Apparently som devices like Antelope audio interfaces might not work if they need "Thunderbolt Thunderbolt Bus / Thunderbolt Local Node" (which I beliece would cause Thunderbolt to show up under the Thunderbolt section of the System Report). By contrast, Universal Audio interfaces *should* work on a Hackintosh with working Thunderbolt.
 
double post
 
Last edited:
Speaking of USB, I have seen a mix of "PCI" screenshots from the system report. My PCI section only shows two entries for the Thunderbolt, nothing about USB. Is this correct, or am I messed up with UBS somewhere? It happens if I use the SSDT from the original path and USBInjectAll, as well as the customer SSDT with USBPorts. I do see a couple of USB hubs under "USB", but the highest Power Available is 900ma.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top