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.
How do you clean HDMI audio properties?
My situation was i was injecting the connector type only for the 2 ports i was using. Removing the properties displays worked again (but without audio). Injecting the properties for all 6 displays, everything worked. Not sure why, although its re-creatable the dark display issues make it frustrating to investigate.
 
Last edited:
My situation was i was injecting the connector type only for the 2 ports i was using. Removing the properties displays worked again (but without audio). Injecting the properties for all 6 displays, everything worked. Not sure why, although its re-creatable the dark display issues make it frustrating to investigate.

Ok Vulgo,

I installed fresh again, this time left it at (0x67) for everything. With the intention of a definite bork so i could try your new 120 script. As soon as i got to the Desktop the first time I enabled screen sharing and file sharing then I installed .120 got the error and kept going. On reboot I got the blank but initialized monitors.

Tried to VNC in. It connected and I got a blurry HS screen (like the login) at low res but it had no log in prompt. I rebooted again and tried VNC-ing in. This time I got the log on screen. I logged in VNC and the displays started working. They were set to mirror the 1440p display. I set to Separate Display instead of Mirrored and my secondary display (the 1440P at the time) stayed on but the primary one didn't. I messed with the display properties and changed which display was primary. Set the 1440p as primary, the one that was working, and saw that it was set as scaled. I changed form Scaled to Default. The other display came on. Rebooted. Both display on. Ugh. So no SIP enabled, no Library validation kext, just had to VNC in and mess with the display settings. How bizarre. But there would be no way to do this without having screen sharing on. It would seem like it completely borked. I wonder if it would just work if I only had one display connected throughout the install.

Oh, and 6 displays? You should be ashamed of yourself. XD
 
Last edited:
Mine path to success was a bit strange.

I turned on SIP. Just SIP. Crash. Tried at Clover to boot with a pre SIP change config copy. Crash.

So I turned off unprotected kext signing in Clover at boot. It booted with NVIDIA drivers working and with acceleration. Checked terminal csrutil status --> enabled

I was then able to update to the new drivers. Changed back to 0x67 and everything (so far) is working.
 
So no SIP enabled, no Library validation kext, just had to VNC in and mess with the display settings. How bizarre. But there would be no way to do this without having screen sharing on. It would seem like it completely borked. I wonder if it would just work if I only had one display connected throughout the install.
Looking in /var/log/displaypolicyd.stdout.log i see
Code:
ERROR: WARNING: Cache is invalid: 1 (bit 0:header, 1-4:mtdd magic, 5:platform, 6:size, 7:checksum, 8-9:vendor version)
ERROR: WARNING: Cache is invalid: 1 (bit 0:header, 1-4:mtdd magic, 5:platform, 6:size, 7:checksum, 8-9:vendor version)
The creation/modification dates seem to coincide with my initial web driver installation. You wouldn't happen to have anything there? And it was never my intention to imply i had 6 displays. Maybe 6 ports.
 
Looking in /var/log/displaypolicyd.stdout.log i see
Code:
ERROR: WARNING: Cache is invalid: 1 (bit 0:header, 1-4:mtdd magic, 5:platform, 6:size, 7:checksum, 8-9:vendor version)
ERROR: WARNING: Cache is invalid: 1 (bit 0:header, 1-4:mtdd magic, 5:platform, 6:size, 7:checksum, 8-9:vendor version)
The creation/modification dates seem to coincide with my initial web driver installation. You wouldn't happen to have anything there? And it was never my intention to imply i had 6 displays. Maybe 6 ports.


Yup. Same exact one!

only entry-

ERROR: WARNING: Cache is invalid: 1 (bit 0:header, 1-4:mtdd magic, 5:platform, 6:size, 7:checksum, 8-9:vendor version)

Date/time the file was created seems like the time of that OS install and the date/time last modified was 11 minutes after.


So... what does this all mean? --- besides the cache became corrupted/invalid
 
Yup. Same exact one!

only entry-

ERROR: WARNING: Cache is invalid: 1 (bit 0:header, 1-4:mtdd magic, 5:platform, 6:size, 7:checksum, 8-9:vendor version)

Date/time the file was created seems like the time of that OS install and the date/time last modified was 11 minutes after.


So... what does this all mean? --- besides the cache became corrupted/invalid
There's also the /var/log/displaypolicy folder where i see
Code:
u>16328762 PolicyEngine started: 7800020000000000, Time: Thu Sep 28 08:24:08 2017
u>16329565 ERROR: Vendor driver reports invalid portmap 0x3f01 mst 0x400 ddc 0x3b00 aux 0x400
u>16330474 NOTICE: accepted enter mode ...
u>16330496 NOTICE: accepted exit mode ...
u>16330512 LinkUpdate: 0.0 event: Remove [1]
u>16330524 LinkUpdate: 8.0 event: Remove [1]
u>16564438 NOTICE: Addr: 0.0 event: Remove [1] source: 0
u>16564477 ERROR: Vendor delivered event 1 on port 3f00:0
u>16564485 NOTICE: Addr: 8.0 event: Remove [1] source: 0
u>17095530 NOTICE: inject FB[2] change
u>13517033 PolicyEngine started: 7800020000000000, Time: Thu Sep 28 08:31:17 2017
u>13683685 ERROR: Vendor driver reports invalid portmap 0x3f01 mst 0x400 ddc 0x3b00 aux 0x400
u>13836590 NOTICE: accepted enter mode ...
u>13836614 NOTICE: accepted exit mode ...
u>14318428 NOTICE: inject FB[2] change
basically getting the same 'Vendor driver reports invalid port map' repeatedly (must have been all those reboots), but only for the time when i was getting the blank screen issues, up until the HDMI audio properties got changed in my case.
 
There's also the /var/log/displaypolicy folder where i see
Code:
u>16328762 PolicyEngine started: 7800020000000000, Time: Thu Sep 28 08:24:08 2017
u>16329565 ERROR: Vendor driver reports invalid portmap 0x3f01 mst 0x400 ddc 0x3b00 aux 0x400
u>16330474 NOTICE: accepted enter mode ...
u>16330496 NOTICE: accepted exit mode ...
u>16330512 LinkUpdate: 0.0 event: Remove [1]
u>16330524 LinkUpdate: 8.0 event: Remove [1]
u>16564438 NOTICE: Addr: 0.0 event: Remove [1] source: 0
u>16564477 ERROR: Vendor delivered event 1 on port 3f00:0
u>16564485 NOTICE: Addr: 8.0 event: Remove [1] source: 0
u>17095530 NOTICE: inject FB[2] change
u>13517033 PolicyEngine started: 7800020000000000, Time: Thu Sep 28 08:31:17 2017
u>13683685 ERROR: Vendor driver reports invalid portmap 0x3f01 mst 0x400 ddc 0x3b00 aux 0x400
u>13836590 NOTICE: accepted enter mode ...
u>13836614 NOTICE: accepted exit mode ...
u>14318428 NOTICE: inject FB[2] change
basically getting the same 'Vendor driver reports invalid port map' repeatedly, but only for the time when i was getting the blank screen issues, up until the HDMI audio properties got changed in my case.


In that directory, I have 2 logs but I didn't see anything like that.

Mostly
Code:
u>6648351 PolicyEngine started: 7800020000000000, Time: Mon Oct 16 22:52:48 2017
u>6654517 NOTICE: accepted enter mode ...
u>6654526 NOTICE: accepted exit mode ...
u>7236123 NOTICE: inject FB[2] change
u>7498209 ERROR: DP synchronous link training begin failed, falling back to async ...
u>7498216 NOTICE: Async LinkTrain Port: 10: SST, 4 lanes @ HBR2
u>7533743 NOTICE: inject FB[3] change




In the PEG0 log.
 

Attachments

  • dplogs.zip
    2.7 KB · Views: 70
Last edited:
Updated Post #2. Update dated upon boot up. Still got the error message, but clicked Continue and install went as intended. I also uninstalled the drivers and reinstalled them; with he exception of the error message, the installation went as expected. Upon reboot, all seems well.

Phew! What a PITA to get to this point. The good news is that I'm just testing 10.13.0 on a test system, and will not upgrade production systems until 10.13.3.
 
Status
Not open for further replies.
Back
Top