Contribute
Register

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

makspaints said:
CaseySJ, I have no idea how to do that. I removed Word quote from my post. I just click reply not the quote button.
Click to expand...
Reply does the same thing as Quote except that Reply quotes the post and allows you to add coments. Quote allows you to select several posts to quote and apply them in your response.
 
makspaints said:
Casey i have no idea how to do that , i removed Word quote from my post , i just click reply not the quote button.
Click to expand...
System administrators edited your post and removed the guide.

All of the guides in this thread are subject to frequent change and error correction. When you quote the entire guide, some people will refer to that instead of going to the original guide. Because this thread is over 1500 pages long, people will just follow the first guide they find without looking for the original. But if the original has changed, they will miss out on all the changes.

Quoting the full guide also adds unnecessary duplication and storage/transmission overhead. It makes the thread messy and needlessly repetitive. The web was designed for hyperlinks, not for duplication.
 
Last edited:
I just checked my MSR, and it was 0x1 again. I didn't reset the BIOS. I did unlock again. I will create another USB , and report back. I hope it works. Thank you.
 
Casey, thank you! I think I'm getting on to what you are saying.
 
dgsga said:
Just an update on the Hades Canyon NUC and thunderbolt. Out of simple curiosity I took the latest iMac18,3 Alpine Ridge firmware update binary from the Catalina 10.15.4 updater, padded it with 0xFF's until it was exactly 1Mb in size and then flashed it with a programmer to the Thunderbolt chip. Much to my amazement it works 100% apart from one bug which I've had with all the patched firmwares. I have a LaCie 2big Dock (Thunderbolt 3 RAID box) which works fine apart from not powering off completely when I shut the NUC down. The drives spin down, the computer shuts off then right at the very end the drives spin up again. Has anyone else had this powering down problem with their patched firmwares? It powers off properly in Windows with the native thunderbolt firmware (v33)
@CaseySJ attached is the updated v41.4 padded binary to add to the firmware repo if you so desire...
Click to expand...
@dgsga--I used your previous version of NUC8 Thunderbolt firmware to flash my NUC. The only TB device I have, an old Seagate TB1 hard disk dock, is working fine. I assume there's no reason to flash your new version.
Thanks!
 
Hey, guys! I've been working on this a couple of days, but its probably an obvious fix. I can boot fine using the install media as a boot manager, but once I get to the step to copy the UEFI files from the USB boot media to the UEFI partition of the OS drive, I just get a blank screen after loading the OS.

I am using the IGPU. HDMI only works for the post phase, and then it stops working as macOS loads, and then only Thunderbolt works. Well, until I try to boot just off the macOS drive and then neither works.
 
I tried it again as Casey has suggested. It looks like my MSR was locked again even after doing it and checking if it worked. This time I did it again. I checked it and then restarted and checked again and so far I'm in installation. I will let you know how it goes. All with the proper guide for 10.15.4
 
Last edited:
lambusser said:
Looking into the real reason OSX thinks there is a UPS attached.

Turns out it is the Corsair "Commander Pro" (or two in my case) that OSX is picking up as a UPS. I found a few articles that powerd/ioupsd look at the name "Commander Pro" (which is a name of a UPS) and thus the reason all this is happening.

pmset -g batt yields the following:

Now drawing from 'UPS Power'
-Commander PRO (id=21102592) charging present: true
-Commander PRO (id=21102593) charging present: true

I'm worried there's no real (easy) way to deal with this at the OS level. The challenge is that sleep won't work until we can get ioupsd out of the picture.

An easy way would be to hide HS12 but I'm assuming if we did that all of those devices would not be available, correct?

Lam
Click to expand...

So a great find on StackExchange about dealing with daemons in general gave me this!

#!/bin/sh
while sleep 999999999; do :; done

So the good news is that powerd only cares that ioupsd is running and doesn't look for specific output from it. Replacing ioupsd with the above script is working perfectly. System performance is as-expected (powerd is happy that it sees ioupsd running) and all devices are available for passthrough and control (if desired) to a Win10 VM.

Steps:

1) sudo su -
2) sudo mount -uw / (Mount the root filesystem as RW)
2) cd /usr/libexec
3) mv ioupsd ioupsd.ORIG (Rename ioupsd for safekeeping)
4) Create a new file named "ioupsd" using for favorite editor. Two lines below...that's all you need!

#!/bin/sh
while sleep 999999999; do :; done

3) Save that file
4) chmod a+x ioupsd (Do a "ls -la ioupsd" and make sure it is readable and executable for everyone)
5) Reboot (must be done to in order to re-mount the root FS as RO)
4) sudo mount -ur / (Mount the root filesystem as RO)

Positives / Issues:

* This allows any/all Corsair devices to remain attached to your system and you can pass them through (if you wish) to a Win10 VM and control everything from there

* The above method tricks the powerd daemon into thinking everything's ok with ioupsd

* You will NOT be able to use a UPS attached to the system via USB or Serial as ioupsd is effectively "missing"

* Sleep is still in issue as the Corsair components are chatty and they keep waking up the system right after it goes to sleep

Help?

Can anyone help with the right "aml" changes so the system ONLY wakes using the power button?

Hope this helps some folks :)

Lam
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top