Yes, I see the same behavior. When system sleeps, the devices on all USB ports are ejected. I believe this causes the ITE Tech controller to reset itself. Even though we've configured HS12 as Type 255 (internal), it gets ejected during sleep.
May be sleepwatcher (brew install sleepwatcher) can help...Yes, I see the same behavior. When system sleeps, the devices on all USB ports are ejected. I believe this causes the ITE Tech controller to reset itself. Even though we've configured HS12 as Type 255 (internal), it gets ejected during sleep.
Currently we use LaunchDaemon to run a liquidctl script at boot. Wondering if that script can also be run after wake-from-sleep...
led8. The driver supports the ITE Tech 0x5702 controller found on Z490 Vision D and Vision G, and also the ITE Tech 0x8297 controller found on Gigabyte's X570 motherboards. Not every motherboard supports all 8 channels. One of the first operations we should do is to map out channel names to their physical ports. This has already been done for the Z490 Vision D, as follows:
|led1||This is the LED next to the IO panel|
|led2||This is one of two 12V RGB headers|
|led3||This is the LED on the PCH chip ("Designare" on Vision D)|
|led4||This is an array of LEDs behind the PCI slots on *back side* of motherboard|
|led5||This is second 12V RGB header|
|led6||This is one of two 5V addressable RGB headers|
|led7||This is second 5V addressable RGB header|
|led8||Not in use|
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
brew install liquidctl
liquidctl list Device ID 0: Gigabyte RGB Fusion 2.0 (experimental) Device ID 1: NZXT Smart Device V2 (experimental)
-dargument, or any part of the device name with the
-margument. Because device IDs might change, it is strongly recommended to use device name instead.
/usr/local/bin/liquidctl -m NZXT initialize
/usr/local/bin/liquidctl -m RGB initialize
-mcan specify any part of the device name, not just the first few characters.
liquidctl, we create a script will be used to configure each of the compatible devices automatically when the system boots up and when it wakes from sleep. Open the spoiler below for instructions.
#!/bin/bash # initialize the device before use /usr/local/bin/liquidctl -m Gigabyte initialize /usr/local/bin/liquidctl -m NZXT initialize # set all color channels on Gigabyte RGB Fusion 2.0 device to "color-cycle" /usr/local/bin/liquidctl -m Gigabyte set sync color color-cycle # set color on NZXT 'led2' color channel to 'spectrum-wave' /usr/local/bin/liquidctl -m NZXT set led2 color spectrum-wave
#!/bin/bashtells macOS to use the 'bash' shell to run the scripts. We can save this file to /Users/Shared/liquidctl-startup.sh and enable file execute permissions by typing this in Terminal:
chmod +x /Users/Shared/liquidctl-startup.sh
cd /Users/Shared ./liquidctl-startup.sh
brew install sleepwatcher
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>de.bernhard-baehr.sleepwatcher</string> <key>ProgramArguments</key> <array> <string>/usr/local/sbin/sleepwatcher</string> <string>-V</string> <string>-w /Users/Shared/liquidctl-wakeup.sh</string> </array> <key>RunAtLoad</key> <true/> <key>KeepAlive</key> <true/> </dict> </plist>
#!/bin/bash /usr/local/bin/liquidctl -m Gigabyte set sync color static FFFF00
liquidctlcommands may be added to control each channel independently.
cd /Users/Shared chmod +x liquidctl-wakeup.sh
brew services start sleepwatcher
cd /Users/Shared ls -l liquidctl*
-rwxr-xr-x 1 casey wheel 79 Jun 14 04:12 liquidctl-startup.sh -rwxr-xr-x 1 casey wheel 79 Jun 14 04:28 liquidctl-wakeup.sh
-rwxr-xr-xpermissions. This is necessary.
brew update liquidctl
brew remove liquidctl
brew services stop sleepwatcher
brew remove sleepwatcher
Hello @JBX,Hello CaseySJ
May I ask on your MSI Armor RX580 that you link too, dose the DVI port work? Since I have not built a hackintosh in years I am trying to catch up on my research before purchasing hardware. So I had read online MSI Radeon GPU's not showing apple screen on boot up, but they do finally arrive at login/desktop... is this true or am I misinformed as those were real Apple hardware users posting? (I have been running an MSI Envidia for years and would like to stick wth the brand)
This copy of the Install macOS Catalina application is damaged, and can’t be used to install macOS.
An error occurred validating the installer data. The download is either damaged or incomplete. Redownload the installer and try again.
When we remove the CMOS battery, it's possible that the date reverts to something very old. So we should set the correct date and time in BIOS.Super suggestion, thanks @CaseySJ and @alchymista! That fixed the issue entirely: after a (lengthy) CMOS reset, removing all cables etc, my GPU was recognized in the BIOS and I got display directly from the GPU HDMI port. Solved!
After formatting the NVME drive, I hit the error
View attachment 475880
I was able to fix this easily following the suggestion that the system date might be the problem, using Terminal:
Then the installer proceeded.Code:
I'm now hitting this bump in installation with two minutes left to completion:
This may be just a usual install issue—and perhaps I should follow the simple direction to redownload—but I wondered if this was something you'd bumped into before, and if you had any specific suggestions. Any chance the date issue above is related?