Contribute
Register

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

  • When the system wakes up automatically, does it go back to sleep within 30 to 60 seconds?
  • If so, is that acceptable?
  • If not acceptable, then one has to go through this procedure:
  • The suggestions here are straightforward.
  • Also have a look at the first bullet under Suggestions Contributed by Users.
It does go to sleep but only if Intel Power Gadget is not opened before it tries to sleep.


I honestly wouldn't mind if it wakes up then goes back to sleep but looks like its preventing that. Anyway around it besides remembering to quit the app? :lolno:
 

Attachments

  • Screen Shot 2021-05-05 at 4.07.56 PM.png
    Screen Shot 2021-05-05 at 4.07.56 PM.png
    60.2 KB · Views: 52
  • Screen Shot 2021-05-05 at 4.08.45 PM.png
    Screen Shot 2021-05-05 at 4.08.45 PM.png
    89.9 KB · Views: 49
It does go to sleep but only if Intel Power Gadget is not opened before it tries to sleep.


I honestly wouldn't mind if it wakes up then goes back to sleep but looks like its preventing that. Anyway around it besides remembering to quit the app? :lolno:
IPG prevents sleep while it is running. Should auto sleep after quit. UserEventAgent can be killed in the terminal, which will usually restore auto sleep function.
Code:
ps -ef | grep UserEventAgent | grep -v grep | awk '{print $2}'| sudo xargs kill -9
 
IPG prevents sleep while it is running. Should auto sleep after quit. UserEventAgent can be killed in the terminal, which will usually restore auto sleep function.
Code:
ps -ef | grep UserEventAgent | grep -v grep | awk '{print $2}'| sudo xargs kill -9
Sweet! ok so just to clarify for myself...

Do I need to quit IPG every time I want to put it to sleep or will the code you posted be a full fix needing to only be run once and from there on I can keep IPG running every time in the background before sleep?

Also incase it has negative effects, what is the code to reverse what the line of code does that you posted?
 
Dear @CaseySJ, today I was trying to overclock my i5-9600K. When I restarted, macOS didn’t start. Then I restarted it again and the BIOS got stuck. So I decided to make it another day. I put back the BIOS as before. But, when I restarted macOS, some software didn’t work anymore, properly, such Cubase; it was not running some VST and then crashed multiple times. Any thought. Thanks.
 
Last edited:
Nope. They said it doesn’t matter if the firmware is flashed or not, and they said they need to remote control the computer. Honestly, for a price of a base Mac mini I don’t think it’s a fair trade.
Apparently they are laughing. Let's wait until no one pays them, or pays them so little that they think twice.
 
Hey guys,

Is the Fully Bootable Backup Procedure for BIG SUR identical to the Catalina version as stated in the Mini Guide or is there some changes to be aware of? I searched but could not find anything related.

Trying it ATM. Cant break anything I guess.

Thank you
 
Last edited:

Just getting around to trying the "Radeon Speed Boost" kext on my z390 designaire, Vega 64, OC 0.69, MacOS 11.3 build. So far so bad. My machine refused to boot w/ SSDT-Z390-Vega64-Slot-1.aml & RadeonBoost-v1-4+Vega.kext and WEG enabled. I did add entries to my OC config.plist to the best of my abilities (which I assume where correct).

My question is pretty basic: Which Slot on the board is considered 1 or 2 for the .aml?
This is what my Z390 Manual looks like. I'm GUESSING the (PCIEX16) Slot is labeled "1" somewhere that I'm unaware of?

Thanks,
 

Attachments

  • Screen Shot 2021-05-06 at 10.37.54 AM.png
    Screen Shot 2021-05-06 at 10.37.54 AM.png
    344.2 KB · Views: 57
Hey guys,

Is the Fully Bootable Backup Procedure for BIG SUR identical to the Catalina version as stated in the Mini Guide or is there some changes to be aware of? I searched but could not find anything related.

Trying it ATM. Cant break anything I guess.

Thank you
The backup procedure for Big Sur is the same as for Catalina. There is one weird thing to note about Big Sur, however:
  • The first backup of Big Sur uses Apple's "APFS Replication" tool to duplicate both the System and User volumes.
  • The second and all subsequent backups will only clone the User volume.
  • So if the first backup was done with Big Sur 11.3, for example, and you make another backup after installing Big Sur 11.4, the System volume on the backup disk will still be 11.3.
    • If you would like to backup 11.4 to the same backup disk, it will be necessary to erase the backup disk in Disk Utility and then run CCC again.

Update: Modified the Carbon Copy Cloner guide:

Screen Shot 2021-05-06 at 9.30.52 AM.png
 
Last edited:

Just getting around to trying the "Radeon Speed Boost" kext on my z390 designaire, Vega 64, OC 0.69, MacOS 11.3 build. So far so bad. My machine refused to boot w/ SSDT-Z390-Vega64-Slot-1.aml & RadeonBoost-v1-4+Vega.kext and WEG enabled. I did add entries to my OC config.plist to the best of my abilities (which I assume where correct).

My question is pretty basic: Which Slot on the board is considered 1 or 2 for the .aml?
This is what my Z390 Manual looks like. I'm GUESSING the (PCIEX16) Slot is labeled "1" somewhere that I'm unaware of?

Thanks,
Correct -- the PCIEX16 slot is Slot 1.
 
Good job!


Unfortunately we're not aware of any solution for this (yet) with the Intel Bluetooth module. But if you connect Apple Mouse and Keyboard via USB cable, then they should work.

I use Logitech wireless mouse and keyboard, which work in BIOS and OpenCanopy with no issues.
If you're using an Apple Magic Mouse 2, which has a lightning port on it, you can use the keyboard in BIOS if you connect a lightning cable to it from your computer. It will work as a USB keyboard.
 
Back
Top