Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[CaseySJ]

Oh excellent! I didn't see SSP1 or SSP2 so I assumed something was wrong. So essentially, as long as the USB3 side of the USB-C port is working, Thunderbolt will too?

Most likely, yes.

 

[RandC]

Casey,

I keep having Sleep/Wake issues especially since updating to Big Sur. I tried some suggestions from the Sleep/Wake thread. Here is what I found out.

1. I unplugged all USB devices even from the motherboard. Sleep/Wake appears to work normally.
2. I then plugged all USB devices back in except for the YOBO WiFi card, because this is what I expect is causing Sleep/Wake to fail. Sleep/Wake appears to work normally.
3. I then plugged in the YOBO WiFi into the card header USB 1/3 (it had been previously plugged into USB 2/4). Sleep/Wake failed plugged into either motherboard USB port.

The pmset log shows what I think caused the wake:

2020-12-01 10:16:22 -0600 Wake Wake from Normal Sleep [CDNVA] : due to XDCI USBW/User Using AC (Charge:0%) 168 secs

So it looks like the YOBO card is triggering wake via the SSDT-USBW ACPI which is the one included in your download. My guess as a NOOB anyway.

So my question is, not knowing anything about SSDT-USB configuration, is there a way to modify the SSDT-USBW to prevent wake on USB 1/3 or USB 2/4 or both?

Thanks again for your great instruction and help with issues!

Rand

Hey Casey,

I just realized (duh) that if I turn Sleep/Wake off on that USB port, then I've turned it off for WiFi and BlueTooth and can only wake with power button. I can turn off BlueTooth wake in System Preferences->Bluetooth->Advanced and uncheck Bluetooth Wake. I'll see what that does, never tried that.

 

[RandC]

Please try disabling (a) SSDT-USBW.aml in OpenCore Configurator --> ACPI, and (b) USBWakeFixup.kext in OpenCore Configurator --> Kernel. Then reboot and try sleep again.

Ok will try that also and let you know what I experience (see previous comment about System Preferences and Bluetooth wake).

Thanks

Rand

 

[RandC]

Hey Casey,

I just realized (duh) that if I turn Sleep/Wake off on that USB port, then I've turned it off for WiFi and BlueTooth and can only wake with power button. I can turn off BlueTooth wake in System Preferences->Bluetooth->Advanced and uncheck Bluetooth Wake. I'll see what that does, never tried that.

Turning Bluetooth Wake off in Bluetooth preferences fixed Sleep/Wake. I tested it twice. It would turn the screen off and then about 20 seconds later the hard drives would spin down and then at about 30 - 35 seconds the machine would go to sleep and stay asleep. Of course now I cannot use my wireless mouse to wake it up .

 

[RandC]

Going to try turning off SSDT-USBW.aml and USBWakeFixup.kext (per your suggestion) and turn back on Bluetooth wake and see what happens.

 

[hughythomas]

Hi guys

I'm at my wits end with Windows and really can't handle it any more.

I only really use the Windows drive for gaming...everything else is done in Catalina.

My question is if I nuke my Windows drive in favour of something like Steam OS is there any chance Opencore will mess up or screw up my Catalina install?

It's important I don't mess it up as Catalina is used for my work!

Thanks in advance!

 

[RandC]

Going to try turning off SSDT-USBW.aml and USBWakeFixup.kext (per your suggestion) and turn back on Bluetooth wake and see what happens.

1. Turned off both SSDT-USBW and USBWakeFixup but left Bluetooth wake on. Sleep/Wake did not work properly. Went to sleep then immediately woke up.

2. Left SDDT-USBW and USBWakeFixup off and also turned off Bluetooth wake. Sleep/Wake seems to work properly (tested twice).

So the issue appears to be with Bluetooth wake being turned on which in turn would be caused by a USB connected WiFi/Bluetooth card. I don't appear to need SSDT-USBW or USBWakeFixup but will turn back on since configuration was delivered that way.

I'm using an Apple Wireless Mouse....May try the DELL Wireless mouse again to see what happens before I turn SSDT-USBW and USBWakeFixup back on.

Rand

 

[RandC]

1. Turned off both SSDT-USBW and USBWakeFixup but left Bluetooth wake on. Sleep/Wake did not work properly. Went to sleep then immediately woke up.

2. Left SDDT-USBW and USBWakeFixup off and also turned off Bluetooth wake. Sleep/Wake seems to work properly (tested twice).

So the issue appears to be with Bluetooth wake being turned on which in turn would be caused by a USB connected WiFi/Bluetooth card. I don't appear to need SSDT-USBW or USBWakeFixup but will turn back on since configuration was delivered that way.

I'm using an Apple Wireless Mouse....May try the DELL Wireless mouse again to see what happens before I turn SSDT-USBW and USBWakeFixup back on.

Rand

Ok new test,

SSDT-USBW and USBWakeFixup turned off. Bluetooth wake turned on. Apple Wireless Mouse disconnected and turned off. DELL wireless mouse connected in place of Apple Wireless Mouse. Computer sleeps and doesn't wake again until I hit the DELL mouse or Apple Wireless Keyboard. Tested this twice. So Sleep/Wake appears to work with DELL mouse.

So my issue appears to be the fact that I'm using an Apple Wireless Mouse. Suspect Apple does something special with it's wireless mouse that doesn't happen with other wireless mice (but that is just a guess). Don't appear to need SSDT-USBW and USBWakeFixup but will turn back on since your download is delivered that way. Don't think it will make any difference but will test.

Thanks Casey!

Rand

 

[Macintoshist]

Hello Casey, just a personal battle I have here, as I find a lot of people having new systems with Intel K CPUs that are throttling because of CPU or VRM temperatures (when they go liquid they often forget to cool down VRMs area) you could maybe add a suggestion about skipping the K and go with the plain 10900?

As I stated before, these are the power/performance tests I carried out using Cinebench r15 on Windows with no undervolt

10900 engineering sample: 110w, 2240 points

10900 standard : 190w, 2460 points

10900k : 320w, 2650 points

The scores on macos are usually a couple percent points slower.

These are all on Vision D builds. The es can go with a 120mm cooler, the standard needs a 140mm, the K ... I can't imagine anyone running that thing for continuous workload, and the system will throttle it down to 180w after 28seconds thus providing same performance as the stock model.

Even though the 10900 is rated at 65w, z490 boards will set it unlimited anyway, so it will always run 4,4ghz all core and ther's where it takes around 190w .

The integrated cooler in the 10900 is useless, but it's nice to have a spare.

Does any one has a K version and if yes, is it worth ? Planning to buy a 10850k, but not sure whether it will be an issue or not. Quite confused about this throttling thing. And if I go ahead with the 10850k, what can I do to check whether it is throttling or not ? Thanks

 

[emistral]

At this point it makes sense to boot with OpenCore 0.6.1 again to re-verify that Windows will launch from the Picker. Alternatively, try removing all entries from the NVRAM --> Delete section, then reboot, Reset NVRAM, and then try booting Windows through the OC 0.6.3 Picker.

@CaseySJ tried your suggestion. It boots from 0.6.1 but same issue when I reinstall 0.6.3 OC with no entries in NVRAM->delete.
Not really sure what to do now.
Out of curiosity, do I need to add those entries back in NVRAM->delete?