Contribute
Register

The everything works Asus Z390-I Gaming * i7-8700K * SAPPHIRE NITRO+ Radeon RX Vega 64 Build

Okay, no harm no foul. Download Modmikes SSDT-UAIC.aml file. Then start clover configurator and mount the EFI partition on your hard drive with Mojave on it. Then choose open the EFI partition. Copy the SSDT-UAIC.aml file to the folder EFI/Clover/ ACPI/ Patched. Reboot and then test sleep again. If that doesn't work then we can try to remove the port limit patch from the config.plist.
Looks like that did it. I did as you suggested (copied over the ssdt-uaic.aml) file and rebooted. Sleep works, however my RGB ram and motherboard RGB stay on. Any idea how to have those go dark too when in sleep?

Is there any downside to having copied over the ssd-uaic.aml? @ModMike mentioned something about crippling USB speed. Do I have no reduced speeds?
 
Looks like that did it. I did as you suggested (copied over the ssdt-uaic.aml) file and rebooted. Sleep works, however my RGB ram and motherboard RGB stay on. Any idea how to have those go dark too when in sleep?

Is there any downside to having copied over the ssd-uaic.aml? @ModMike mentioned something about crippling USB speed. Do I have no reduced speeds?
You can test it but no that shouldn't be an issue, its more common to use SSDT than patching the config.plist or it seems like it to me from all the various forums and advice I've read. Updates in OSX can break the patches, not so with the SSDT. The lights are controlled by software that interacts with the bios (I think) and that's available and works in Windows. There are ways to do that in Mojave but I'm not familiar with how aorta's what works and why doesn't.
 
You can test it but no that shouldn't be an issue, its more common to use SSDT than patching the config.plist or it seems like it to me from all the various forums and advice I've read. Updates in OSX can break the patches, not so with the SSDT. The lights are controlled by software that interacts with the bios (I think) and that's available and works in Windows. There are ways to do that in Mojave but I'm not familiar with how aorta's what works and why doesn't.
Should I install Parallel so I can install windows and then control the lights through that?
 
Okay, no harm no foul. Download Modmikes SSDT-UAIC.aml file. Then start clover configurator and mount the EFI partition on your hard drive with Mojave on it. Then choose open the EFI partition. Copy the SSDT-UAIC.aml file to the folder EFI/Clover/ ACPI/ Patched. Reboot and then test sleep again. If that doesn't work then we can try to remove the port limit patch from the config.plist.

No problems with sleep ever and read my whole article on the whole USB thing.

Just installed Catalina and will be releasing new EFI in a day or two with latest BRCM patches that will help with Bluetooth issues.
 
Okay, no harm no foul. Download Modmikes SSDT-UAIC.aml file. Then start clover configurator and mount the EFI partition on your hard drive with Mojave on it. Then choose open the EFI partition. Copy the SSDT-UAIC.aml file to the folder EFI/Clover/ ACPI/ Patched. Reboot and then test sleep again. If that doesn't work then we can try to remove the port limit patch from the config.plist.

Looks like I celebrated too early. My sleep doesn't work anymore. I don't know if sleep worked that one time (cause I got lucky) or I did something to mess it up again (I installed parallels, and subsequently deleted it).

When you say remove the port limit patch from the config.plist, I see there are 3 patches in Kernel and Kext Patches: com.apple.iokit.IOUSBHostFamily (USB port Limit Patch 1), com.apple.driver.usb.AplleUSBXHCI (USB port Limit Patch 2), com.apple.iokit.IOUSBHostFamily (USB port Limit Patch 3)
Should I delete all three or just one? What will this do if I remove them? If after I delete them, I want to add them again, how would I do that?

Update:
so I noticed that one of my two front panel USB does not work anymore after adding the SSDT-UAIC.aml file. I have gaming steel series headphones with DAC plugged in and the DAC isn't on when plugged into the USB. When I try and sleep, I successfully sleep the computer. If I move the DAC to the USB that does work, my sleep wakes up immediately.

1) Why did I loose one of my USB ports?
2) Why does plugging in my steelseries DAC into a functional USB port mess with sleep?
3) Ideas of what I should do?
 
Last edited:
Should I install Parallel so I can install windows and then control the lights through that?
I don't think that works...at least it didn't for me using the Corsair software.
 
Looks like I celebrated too early. My sleep doesn't work anymore. I don't know if sleep worked that one time (cause I got lucky) or I did something to mess it up again (I installed parallels, and subsequently deleted it).

When you say remove the port limit patch from the config.plist, I see there are 3 patches in Kernel and Kext Patches: com.apple.iokit.IOUSBHostFamily (USB port Limit Patch 1), com.apple.driver.usb.AplleUSBXHCI (USB port Limit Patch 2), com.apple.iokit.IOUSBHostFamily (USB port Limit Patch 3)
Should I delete all three or just one? What will this do if I remove them? If after I delete them, I want to add them again, how would I do that?

Update:
so I noticed that one of my two front panel USB does not work anymore after adding the SSDT-UAIC.aml file. I have gaming steel series headphones with DAC plugged in and the DAC isn't on when plugged into the USB. When I try and sleep, I successfully sleep the computer. If I move the DAC to the USB that does work, my sleep wakes up immediately.

1) Why did I loose one of my USB ports?
2) Why does plugging in my steelseries DAC into a functional USB port mess with sleep?
3) Ideas of what I should do?
Maybe Mike will help you now. I am going to sign off. You probably have a conflict using both methods of port limit patching. Don't fool around with any of the next patches, its lines in the config.plist that need to be removed
 
@Leesureone thanks for your help up to this point. @ModMike, any ideas on my current issue, and how to solve it?

To recap:
Looks like I celebrated too early. My sleep doesn't work anymore (when I have my Steelseries Headphone DAC plugged into a USB port). Sleep works if I remove the DAC from the USB port, but not with it in.

Also, I noticed that one of my two front panel USB does not work anymore after adding the SSDT-UAIC.aml file.

1) Why did I loose one of my USB ports?
2) Why does plugging in my steelseries DAC into a functional USB port mess with sleep?
3) Ideas of what I should do?

Troubleshooting observations:
I deleted the SSDT-UAIC.aml patch and rebooted, and regained my front panel USB port, however sleep does not work anymore (even when unplugging the USB Steelseries DAC altogether).
I once again added the SSDT-UAIC.aml patch and rebooted and lost the front panel USB port (one of them), and sleep works, as long as the USB Steelseries DAC is unplugged.
 
Last edited:
Looks like I celebrated too early. My sleep doesn't work anymore. I don't know if sleep worked that one time (cause I got lucky) or I did something to mess it up again (I installed parallels, and subsequently deleted it).

When you say remove the port limit patch from the config.plist, I see there are 3 patches in Kernel and Kext Patches: com.apple.iokit.IOUSBHostFamily (USB port Limit Patch 1), com.apple.driver.usb.AplleUSBXHCI (USB port Limit Patch 2), com.apple.iokit.IOUSBHostFamily (USB port Limit Patch 3)
Should I delete all three or just one? What will this do if I remove them? If after I delete them, I want to add them again, how would I do that?

Update:
so I noticed that one of my two front panel USB does not work anymore after adding the SSDT-UAIC.aml file. I have gaming steel series headphones with DAC plugged in and the DAC isn't on when plugged into the USB. When I try and sleep, I successfully sleep the computer. If I move the DAC to the USB that does work, my sleep wakes up immediately.

1) Why did I loose one of my USB ports?
2) Why does plugging in my steelseries DAC into a functional USB port mess with sleep?
3) Ideas of what I should do?

Just hit disable in Clover Configurator.
 
Back
Top