Contribute
Register

USB drives getting ejected when Hackintosh wakes from sleep with XMP enabled

Status
Not open for further replies.
ziggenpuss said:
Have you checked the Rehabman's USB post?
Click to expand...

No, but CaseySJ posted here that SSDT doesn't work
www.tonymacx86.com

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

CaseySJ's Coffee Lake in Phanteks Evolv X ATX Case: Gigabyte Designare Z390 - i7-9700K - UHD 630 - AMD RX 580 (Please do not quote this build guide in its entirely. Post a link instead.) (See this post for how to refer to a Guide or Mini-Guide.) URGENT: Please avoid Clover 5123 and newer for...
www.tonymacx86.com www.tonymacx86.com
 
I can also confirm that the Jettison utility does not work unless I set my memory to 2400 MHz memory! At 3600 MHz, Jettison will eject USB sticks on sleep, but not remount them on wake!
 
I Followed the CaseySJ post to tweek my new build - however it made things worse. Unless there was something I haven't done or missed etc. On my old build the rehab man method worked. Albeit a bit confusing at first, I wonder if I'll need to do the same on this build as I'm having the USB eject issue as well.
 
Last edited:
My Build
Z390 DESIGNARE |  i9 9900K |  Radeon Other
I'm on F6n with the I9-9900K R0 processor.
Haven't tried F7 yet. Might try it today.
 
CN7 said:
I can also confirm that the Jettison utility does not work unless I set my memory to 2400 MHz memory! At 3600 MHz, Jettison will eject USB sticks on sleep, but not remount them on wake!
Click to expand...

Just to update this, if I set my memory to 2666 MHz it works also.
 
ziggenpuss said:
I Followed the CaseySJ post to tweek my new build - however it made things worse. Unless there was something I haven't done or missed etc. On my old build the rehab man method worked. Albeit a bit confusing at first, I wonder if I'll need to do the same on this build as I'm having the USB eject issue as well.
Click to expand...
Please keep us updated on anything you find on the eject issue.

I'm not sure, but from what I've read, I don't think people on Mojave 10.14.3 or earlier had the issue, but I'm not sure. This is is just from deductive reasoning. Perhaps afterwards, Apple changed the way "remount" works (or disabled it), rendering the script ineffective.
Whatever the case, setting memory to 2666 MHz an below solves eject and other sleep issues (clover dark wake settings can be removed - at 2700 MHz, the eject issue is solved, but *maybe* dark wake settings still have to be set. I have not had the time to confirm each setting).
 
CN7 said:
Please keep us updated on anything you find on the eject issue.

I'm not sure, but from what I've read, I don't think people on Mojave 10.14.3 or earlier had the issue, but I'm not sure. This is is just from deductive reasoning. Perhaps afterwards, Apple changed the way "remount" works (or disabled it), rendering the script ineffective.
Whatever the case, setting memory to 2666 MHz an below solves eject and other sleep issues (clover dark wake settings can be removed - at 2700 MHz, the eject issue is solved, but *maybe* dark wake settings still have to be set. I have not had the time to confirm each setting).
Click to expand...
Hi CN7 - just wondered what make and model of RAM you have and how much 16, 32, 64.. Also what Aptiofix are you running? I'm still in exactly the same boat as yourself - I haven't tried the lowering to 2666 method yet but have been having some mixed results with other settings, BIOS, Clover SSDTs, etc..
 
My Build
Z390 DESIGNARE |  i9 9900K |  Radeon Other
ziggenpuss said:
Hi CN7 - just wondered what make and model of RAM you have and how much 16, 32, 64.. Also what Aptiofix are you running? I'm still in exactly the same boat as yourself - I haven't tried the lowering to 2666 method yet but have been having some mixed results with other settings, BIOS, Clover SSDTs, etc..
Click to expand...

What other issues are you experiencing?

Try lowering the momory. It could fix the USB eject and perhaps sleep issues. In my case, I have darkwake set to 8, but someone reported that darkwake settings in clover are not necessary anymore at 2666 MHz memory and below.

The other fix is to have the machine never sleep, but that is a no-go for me. I use my machine sporadically and need quick access to it, so never-sleep uses too much energy and wears out the machine. I might actually need to sleep it from hours at a time to days at a time, with no set usage schedule.

The memory I am using is 64GB Kingston HyperX Predator Black 3600 MHz (16GB X 4), which is on the approved list for the motherboard.

*This could actually be an issue with the motherboard / BIOS itself. The issue has been reported to have been fixed on at least one ASUS board with a BIOS update, but I don't know the specifics.* Because of this, I think it could be useful to notify Gigabyte tech support about the issue at this point.

I went the lazy way and used someone else's setup. I considered starting from scratch, but for this problem, I haven't seen a solution from people more knowledgeable than me, so I haven't taken that route, and otherwise, I haven't run into too many other serious problems so far.

My other potential issues could be:

1) Running with something like an Antelope audio interface (which I planned to do, but might have to go UAD because it's been reported in CaseySJ's golden build thread that Antelope require "local node" for thunderbolt to work properly, but apparently, TB shows up as PCI in macOS System Report.

2) Using 5k Thunderbolt monitor (although I think that may have been resolved, and I have yet to upgrade my monitor from Apple Cinema 1440p.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top