Contribute
Register

[SOLVED] GTX980 won't wake if screens sleep with video left fullscreened in Safari

Status
Not open for further replies.
Joined
Aug 22, 2015
Messages
15
Motherboard
ASUS X99A-USB3.1
CPU
Intel 5820K @ 4.5GHz (OC)
Graphics
Gigabyte NVIDIA GTX980 4GB
Mac
  1. MacBook Pro
Hello... was wondering if anyone else has experienced this issue on 10.13.5 (17F77) with NVIDIA Web Driver 387.10.10.10.35.106. It's the only remaining glitch with my system.

Problem: if the displays are allowed to sleep overnight with Safari left open with a video fullscreened... then they refuse to wake up the next morning. Hibernate and system sleep are both disabled but I have set the displays to sleep after 15min in System Preferences. As far as I can tell, the system is still running... it is just the display subsystem that fails to wake up.

Another strange thing: fresh after a reboot, I cannot set the secondary display to HIDPI. But if the displays are allowed to sleep overnight (without a video fullscreened which would prevent them waking again), then the next morning I can enable HIDPI on the secondary display using SwitchResX, and it works.

Something screws up when the display/ graphics subsystem is allowed to sleep for a couple hours. There's no problem if the displays only sleep for 20 or 30 minutes.

Base system:
Code:
ASUS X99A-USB3.1
   with Intel 5820K

Gigabyte NVIDIA GTX980 4GB
   with primary display NEC PA322UHD @ 3360x1890 60Hz HIDPI on DisplayPort (4K actual on the monitor)
   with secondary display Dell UP2716D @ 2560 x1440 60Hz on DisplayPort

Current driver: 387.10.10.10.35.106
Running on: macOS 10.13.5 (17F77)
SMBIOS: MacPro6,1

EFI/Clover/kexts/Other:
Code:
$ bdmesg | grep -i 'extra kext'
9:120  0:000  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC_ACPISensors.kext (v.1787)
9:123  0:002  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC_CPUSensors.kext (v.1787)
9:124  0:001  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC_GPUSensors.kext (v.1787)
9:128  0:003  Extra kext: EFI\CLOVER\kexts\Other\NullCPUPowerManagement.kext (v.1.0.0d2)
9:131  0:003  Extra kext: EFI\CLOVER\kexts\Other\VoodooTSCSync.kext (v.1.1)
9:132  0:001  Extra kext: EFI\CLOVER\kexts\Other\NvidiaGraphicsFixup.kext (v.1.2.7)
9:136  0:003  Extra kext: EFI\CLOVER\kexts\Other\IntelMausiEthernet.kext (v.2.4.0)
9:138  0:002  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC_LPCSensors.kext (v.1787)
9:175  0:037  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext (v.1787)
9:179  0:003  Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext (v.1.2.3)
9:182  0:003  Extra kext: EFI\CLOVER\kexts\Other\X99_Injector USB 3.kext (v.1.1)

EFI/CLOVER/drivers64UEFI:
Code:
$ ls -l /Volumes/EFI/EFI/CLOVER/drivers64UEFI/
total 724
-rwxrwxrwx  1 Ainz  staff   17280 29 May 20:49 AppleImageCodec-64.efi
-rwxrwxrwx  1 Ainz  staff    5312 29 May 20:49 AppleKeyAggregator-64.efi
-rwxrwxrwx  1 Ainz  staff    2400 29 May 20:49 AppleUITheme-64.efi
-rwxrwxrwx  1 Ainz  staff   29024  8 Dec  2017 CsmVideoDxe-64.efi
-rwxrwxrwx  1 Ainz  staff    5696 29 May 20:49 DataHubDxe-64.efi
-rwxrwxrwx  1 Ainz  staff   22560 29 May 20:49 EmuVariableUefi-64.efi
-rwxrwxrwx  1 Ainz  staff   21984 29 May 20:49 FSInject-64.efi
-rwxrwxrwx  1 Ainz  staff    7232 29 May 20:49 FirmwareVolume-64.efi
-rwxrwxrwx  1 Ainz  staff   18240 26 May  2016 OsxAptioFix2Drv-free2000.efi
-rwxrwxrwx  1 Ainz  staff   24192 29 May 20:49 OsxAptioFixDrv-64.efi
-rwxrwxrwx  1 Ainz  staff  583736  8 May 18:59 apfs.efi

Clover boot options:
Code:
-v darkwake=0 npci=0x2000 nv_spanmodepolicy=1 keepsyms=1 debug=0x100


Despite reading that darkwake=1 is required for ASUS motherboards... I found that it caused the displays not to wake after sleep whether or not a video was left fullscreened. That problem disappeared after I changed to darkwake=0

But the issue of non-wakeability remains if a video is left fullscreen in Safari while the displays are allowed to sleep for a couple hours.

Has anyone else experienced this?
 
Last edited:
The solution to this was to enable CSM in BIOS
 
The solution to this was to enable CSM in BIOS

How did you discover this! I was experiencing the same thing for a week now and finally...
 
How did you discover this! I was experiencing the same thing for a week now and finally...
User kgp suggested it... I'm using his X99 EFI. I get the feeling that CSM may need to be enabled or disabled depending on chosen SMBIOS and exact graphics hardware. I had it disabled on my rig from Yosemite right through to Sierra.

Glad to hear that the info helped you out, anyway!
 
Status
Not open for further replies.
Back
Top