- Joined
- Jan 23, 2018
- Messages
- 16
- Motherboard
- Asus Z370-I
- CPU
- Intel 8700
- Graphics
- EVGA 1080 ti
for those getting a blacks screen using HDMI, switch to your DisplayPort adapter instead and see if that works. It did for me.
Sunrise point/union point
So other boards should be able to use the latest Nvidia drivers, no problem? Where did you find that it only affects these boards in specific? (I don't see a mention of that elsewhere in these replies.)
Sunrise point/union point
It has been mentioned and you can read the hardware in users' profiles.I don't see a mention of that elsewhere in these replies.
The 387 driver is broken on Skylake+ (100 through 300 series) - use the 378 driver for these systems.So Intel 87/97, Lynx Point, are fine?
Your CSR value is ok. Unless you are seeing errors when rebuilding the prelinked kernel the problem might be unrelated to the caches - could be either the Nvidia driver isn't starting, or it is starting and the login window isn't working. Double check EmuVariableEFI setup/nvda_drv variable/NvidiaWeb true in config plist, note that using the Clover entry menu and booting without the nvidia driver option checked will clear nvda_drv=1 from NVRAM. You should see 'NVDAStartup: Web' in the console messages if the driver is starting.
I'm on 8700K, High Sierra 10.13.3 (specs in my signature) and had the same graphics lag issue with web driver version 387.10.10.10.25.156. I managed to fix it by installing older web driver version: 378.10.10.10.25.104.
The way to install an older version of the web driver on a later version of MacOS is to first find the URL of the web driver and then use a command line tool called webdriver.sh to install it. You can download webdriver.sh from here or install it via homebrew. Nvidia has a page that lists web drivers per MacOS build version. In case of .104 on MacOS 10.13.3 (Build 17D47) you need to execute the following commands in Terminal:
sudo webdriver.sh -u https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.25.104.pkg
sudo webdriver.sh -m 17D47
Once that's done, restart your computer.
If you already have a newer version of the web driver installed, you can use the tool to uninstall it like so:
sudo webdriver -r
And restart once it's done.
How to find your MacOS build number? Go to About this Mac -> System Report -> Software. You'll see it listed there under system version. It shows macOS 10.13.3 (17D47) in my case.
It would appear that some display-related configuration becomes invalidated and the login window doesn't appear on the connected display. Couple of times i have experienced similar, once apparently caused by incomplete HDMI audio property injection (only injecting connector-type for connected displays) but was able to connect a monitor on a different port, once 'solved' by deleting monitor preferences for a single user account that was unable to log in. The common thing is a previously working configuration stops working, at some point the configuration becomes valid and after that things work as they did previously with no obvious changes made by the user e.g. some report logging in via remote screen and making minimal changes to display preferences e.g. arbitrary resolution change - enables normal login, or even no changes made and the next day 'just worked'.Do you have any proposal on how to debug it?
Thanks again!!!
Keep CsrActiveConfig = 0x67 and use this script to install 106 https://github.com/Benjamin-Dobell/nvidia-update4. reboot with NvidiaWeb enabled and CsrActiveConfig = 0x67
Maybe something in /var/db or /Library.I am not sure which file it would read.