- Feb 21, 2017
- HP Envy 17-U275CL
- GTX MX150 / HD 620, 1920x1080
- Mobile Phone
Thanks for the information. I've made a script that uninstalls previous web driver, downloads the driver package then tries to user-approve the kexts before installing and rebuilding the caches, hoping this might allow for clean installs without changing the SIP settings which is not really ideal. Credit to Pike R Alpha's for his documentation here.
Ok so I found a situation where I could use your script.
Not sure what number install this is but -
I install fresh again to an SSD. This time I used my same EFI but went through the Install with SIP Enabled 0x0.
Everything went fine, I turned on screen sharing and file sharing, then installed the latest web drivers (.120) and got the Gatekeeper warning. I allowed for that and rebooted.
No boot loop, my displays initialized but were blank. I was able to VNC in.
Everything looked good and after logging in my displays showed for a moment, long enough for me to set Use Separate Displays. They went blank again. Checked VNC yeah, it showed 2 displays there.
Thinking it may be something with booting with SIP enabled (0x0), i changed CSRActive Config to 0x67 -- same thing blank screens / VNC worked. I added NVWebDriverLibValFix.kext to kexts/other rebooted. Still those blank initialized displays. I rebooted a couple times going back and forth with 0x0 and 0x67 and ditched NVWebDriverLibValFix.kext. Then I rebooted again 0x67 same thing So, I ran your script sudo-ed (I noticed it downloaded .117) it said success - rebooted blank initialized screens.
Weird. This is practically the same way I installed before. The exception installing .120 from scratch and not having .117 on there first.
From VNC if I change my display settings to Mirrored - the displays activate. Then if I change to Separate the displays go blank and through VNC I go to a log in. I log in switch to Mirrored - displays activate. WTF. I think I am going to wipe and install again. Using the usual 0x67 then 0x0 to install web drivers. Maybe going with .117 first then .120. IDK fam.
Ok so I installed fresh again with the same EFI using 0x67.
Then booted 0x0 to install .120 web drivers. So gatekeeper security warning and allowed. Continued with the install then changed back CSRActive Config and rebooted with 0x67 - initialized display but screens were blank.
I did not bother setting up screen sharing this time. I rebooted into a working Sierra and manually removed all the Nvidia Web drivers. That being anything in S/L/E L/E which had nvidia and or geforce with web references. Wow there were a lot. Two of the same ones. More than when installing .117.
Rebooted into High Sierra to make sure I could get in. I was in. Rebooted with 0x0. Installed Web drivers .117 (no Gatekeeper notification cause I already allowed them during the .120 install). Set CsrActive Config and rebooted with 0x67. All good displays were on but they were mirrored. Set to separate All good!
Something is up with the .120 drivers when installing fresh.
I rebooted again with 0x0, and used the Control Panel applet to install .120 rebooted with 0x67 . BOOM Displays for days!