Contribute
Register

NVIDIA Releases Alternate Graphics Drivers for macOS High Sierra 10.13.0 (378.10.10.10.15)

Status
Not open for further replies.
If you have invalid cache errors you could try deleting any files in /var/db/displaypolicyd apart from the 'pid' file - any errors in files in the /var/log/displaypolicyd folder?

So I must have been looking in the wrong place before. The /var/db/displaypolicyd folder is empty.

I added lilu.kext and NvidiaGraphicsFixup.kext to my EFI partition and there was no change.

I attached a copy of my latest config.plist file. Maybe I'm missing something? It's a 10.12 installation that I upgraded to 10.13.
 

Attachments

  • config 10.20.plist
    3.6 KB · Views: 215
So I must have been looking in the wrong place before. The /var/db/displaypolicyd folder is empty.

I added lilu.kext and NvidiaGraphicsFixup.kext to my EFI partition and there was no change.

I attached a copy of my latest config.plist file. Maybe I'm missing something? It's a 10.12 installation that I upgraded to 10.13.
The logs are in /var/log, still don't know what errors you saw. The monitor preferences appear to be stored in your home folder ~/Library/Preferences/ByHost/com.apple.windowserver.UUID.plist - maybe trashing this could help.

edit: corrected path to plist
 
The logs are in /var/log, still don't know what errors you saw. The monitor preferences appear to be stored in your home folder ~/Library/Preferences/ByHost/com.apple.windowserver.UUID.plist - maybe trashing this could help.

edit: corrected path to plist

I trashed the monitor preference files, and there is no change

Perhaps a driver issue? It's so strange because I can't see any reason why it shouldn't work
 
I trashed the monitor preference files, and there is no change

Perhaps a driver issue? It's so strange because I can't see any reason why it shouldn't work
Somethings changed recently, possibly around new external GPU support, or maybe something else. No open source graphics on macOS so we can't just use google for insights into what is different. Clicky was able to get get a second monitor back by changing the display settings via remote login. If you have an 'invalid port map' displaypolicyd error maybe check for graphics card property injection e.g. SSDTs

There's a file at /var/db/.com.apple.iokit.graphics that stores information on your displays. displaypolicyd stores at /var/db/displaypolicyd/*, though your folder was empty, and deleting the windowserver preferences didn't help either. Somewhere there may be some newly-incompatible display-related configuration that needs to be flushed. Otherwise there is trying different combinations of ports, and seeing if you can get things to work that way.
 
Just took the plunge.. Went smoothly, though a bit longer than I thought.

When updating the NVIDIA drivers it complained of encountering some error, but allowed me to continue anyway. I did and alll is fine. if anything, everything looks sharper and more colorful. I'm sure its all in my head. :)

Big thanks to all the helpers on the board.
 
Have a read from page ~60 of this thread, posts from @Clicky - add here that i've had trouble booting with 2 monitors attached since at least 10.12


Hey Vulgo,

So I was bored again. I have a 120GB SSD in a SATA to USB 3.1 Gen 2 dock. It is cool cause whatever device is in the dock is what the BIOS and OS see's. It is never seen as an enclosure.

Anyway, I got bored and made a 16 GB partition on it and created a High Sierra installer on that partition, dropped in my current EFI then installed High Sierra to the remaining free space. So it is a self-contained Hackintosh drive.

Anyway, so I installed HS with both displays connected to the Nvidia card, same EFI as always, and CSRActive Config 0x67 all the way through.

But I didn't install the web drivers right away. Thinking maybe if they were installed right after you got to the desktop the first time, that could cause a problem when dual displays are in use.

The install finishes.

I turned on screen sharing and file sharing. But this time, I decided to change the General Security settings so auto login was allowed and no password prompt from sleep. Installed the iTunes 12.7 update. Rebooted a couple of times without changing anything else - then I installed the .120 drivers. I got the error during install and rebooted. Blank non initialized monitors but after a while they initialized but were blank. No problem, I'll just VNC in. WRONG. Just a black screen. I rebooted twice trying to VNC in each time. Same thing VNC showed a black rectangle and sometimes the connection would drop.

Next step, I dropped in NvidiaGraphicsFixup and Lilu onto the EFI, keep in mind I use SMBIOS 18,3 so no AGDP foolery is needed. But the new NvidiaGraphicsFixup also added library validation and some other goodies. Booted up. BOOM! right in with both monitors on. Ok cool. Removed NvidiaGraphicsFixup and Lilu from the EFI and rebooted. Nope blank non initialized monitors that initialize after a bit but stay blank. I drop NVWebDriverLibValFix.kext onto the EFI. Reboot. BOOM back in with dual displays. Remove NVWebDriverLibValFix.kext and reboot. WTF Now it is in a gIOScreenLockState Loop.

- see here -


Put back in NVWebDriverLibValFix.kext to EFi and reboot. BOOM all good.

I rebooted a few times with and without NVWebDriverLibValFix.kext just to confirm that was the kext allowing me to "get in".

So now I have 2 High Sierras installed on the same hardware with the same EFI.

One never enabled SIP at anytime to install the Web drivers and requires NVWebDriverLibValFix.kext or NvidiaGraphicsFixup and Lilu to boot dual displays.

The other, had SIP enabled at some point during the web driver install and boots fine without them.


Not sure if this helps anyone. Just sayin'
 
I rebooted a few times with and without NVWebDriverLibValFix.kext just to confirm that was the kext allowing me to "get in".
Maybe an unintended consequence of the library validation patch is allowing the kexts to load without approval, as macOS recognises them as platform binaries. Though the current web drivers on High Sierra don't actually need the library validation patch...
 
Maybe an unintended consequence of the library validation patch is allowing the kexts to load without approval, as macOS recognises them as platform binaries. Though the current web drivers on High Sierra don't actually need the library validation patch...
Yeah. It was also interesting that with auto-logon, I couldn't use the VNC method to log in and change the display preferences.
 
Hey Vulgo,
Next step, I dropped in NvidiaGraphicsFixup and Lilu onto the EFI, keep in mind I use SMBIOS 18,3 so no AGDP foolery is needed. But the new NvidiaGraphicsFixup also added library validation and some other goodies. Booted up. BOOM! right in with both monitors on. Ok cool. Removed NvidiaGraphicsFixup and Lilu from the EFI and rebooted. Nope blank non initialized monitors that initialize after a bit but stay blank. I drop NVWebDriverLibValFix.kext onto the EFI. Reboot. BOOM back in with dual displays. Remove NVWebDriverLibValFix.kext and reboot. WTF Now it is in a gIOScreenLockState Loop.

One never enabled SIP at anytime to install the Web drivers and requires NVWebDriverLibValFix.kext or NvidiaGraphicsFixup and Lilu to boot dual displays.
I'm having the same problem with both screens going blank if I boot into Sierra or High Sierra with both monitors connected, if I boot with one then log in and plug in the 2nd it's all ok.

Did you have the same issue as me before you did the above steps ? Can you now boot with both monitors connected ?

I also had the blank screen after installing the web drivers and fixed it using VNC and changing display settings.

Vulgo - you also mention you have blank screens if you boot with dual monitors connected - is this still the case ? Have you tried the above ?

I also looked at my ~/Library/Preferences/ByHost/com.apple.windowserver.UUID.plist & confusingly I see the 2 monitors that are connected however there is 5 entries (3 for the first monitor and 2 for the second). If I look in IOReg I can see 5 entries for the 5 ports on my graphics card, however only 2 of them have a display connected - and these map to the same as the plist. Attached is the plist.
 

Attachments

  • com.apple.windowserver.plist
    4.3 KB · Views: 94
Last edited:
I'm having the same problem with both screens going blank if I boot into Sierra or High Sierra with both monitors connected, if I boot with one then log in and plug in the 2nd it's all ok.

Did you have the same issue as me before you did the above steps ? Can you now boot with both monitors connected ?

I also had the blank screen after installing the web drivers and fixed it using VNC and changing display settings.

Vulgo - you also mention you have blank screens if you boot with dual monitors connected - is this still the case ? Have you tried the above ?

I also looked at my ~/Library/Preferences/ByHost/com.apple.windowserver.UUID.plist & confusingly I see the 2 monitors that are connected however there is 5 entries (3 for the first monitor and 2 for the second). If I look in IOReg I can see 5 entries for the 5 ports on my graphics card, however only 2 of them have a display connected - and these map to the same as the plist.


I never had the problem with both displays not working with Sierra on my current motherboard.

If you have problems with this on Sierra it could be completely unrelated to the problems I experienced.

Yes, with each High Sierra install I was always able to boot with both displays connected in the end. But there were different things I had to do to make it work. VNC, Library Validation or SIP. Single display no issues.
 
Status
Not open for further replies.
Back
Top