2855416 Posted October 5, 2017 Share Posted October 5, 2017 A43SV GT540M/K43SV GT630M also get a blank screen Link to comment Share on other sites More sharing options...
MICKHAEL Posted October 5, 2017 Share Posted October 5, 2017 I don't know if it will help this case but perhaps take a look at this Clover config element. Have a read of this - it explains it better than I could here. i will try. and one more info - DVI-D works and DVI-I NOT unable to complete all spaces Link to comment Share on other sites More sharing options...
Gurqn Posted October 5, 2017 Share Posted October 5, 2017 Becarefull with the supplemental update breaks unmodified web drivers. 4 Link to comment Share on other sites More sharing options...
Mockletoy Posted October 5, 2017 Share Posted October 5, 2017 Becarefull with the supplemental update breaks unmodified web drivers. And I stupidly hit update on a fresh install BEFORE installing the drivers at all, so now I can’t install at all. And I knew better,and just got careless. Link to comment Share on other sites More sharing options...
Vampirexx Posted October 5, 2017 Share Posted October 5, 2017 Anyway to fix it please? My hack keep rebooting before the login Link to comment Share on other sites More sharing options...
Badruzeus Posted October 6, 2017 Share Posted October 6, 2017 Anyway to fix it please? My hack keep rebooting before the login I think the old methods should to work, though I my self not test it yet, nor even updating my hSierra. You may forgot that Supplemental Update uses a newer build: "17A405" which is required by NVDAStartupWeb to loads? So, temporarily try these (or wait till Nvidia would give us an update): 1. Boot ur hSierra with nv_disable=1 boot-arg 2. Terminal: sudo nano /Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist 3. Change these values: From... <key>NVDARequiredOS</key> <string>17A365</string> to... <key>NVDARequiredOS</key> <string>17A405</string> 4. [nano] Ctrl+O: Save | Ctrl+X: Exit. 5. Terminal: sudo nvram -c && sudo purge && sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force 6. Reboot ur mach, then boot hSierra w/o nv_disable=1 boot-arg. Good luck & DWYOR..!!! 4 Link to comment Share on other sites More sharing options...
Vampirexx Posted October 6, 2017 Share Posted October 6, 2017 Thank you Buddy! I tried manually write the updated number of new build inside this kext but didnt solve the problem. Then i tried change my boot graphics option from peg to igd to use my intel 630 to boot, but clover only show me a blank cursor with black screen and after 30 seconds it just reboot. Why??? Anyway i try your solution step by step im desperate. Thank you Link to comment Share on other sites More sharing options...
Badruzeus Posted October 6, 2017 Share Posted October 6, 2017 Thank you Buddy! I tried manually write the updated number of new build inside this kext but didnt solve the problem. Then i tried change my boot graphics option from peg to igd to use my intel 630 to boot, but clover only show me a blank cursor with black screen and after 30 seconds it just reboot. Why??? Anyway i try your solution step by step im desperate. Thank you Nah, the problem is we don't know yet that Web Drivers are loaded or not under 17A405. And U said that only gotta blackscreen with cursor (not blackscreen with signal which is usually related to AGDP, or have U checked that Supplemental update rolled-back / replaced this kext with a newer one if u were previously using AGDPFix?). Prematurely assumed, but it might "something" prevents Web Drivers (or even windowserver, if not dependency issue) to be loaded; at least after we read this. Then how if: 1. Clover user, SIP: Enabled. <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x00</string> <key>CsrActiveConfig</key> <string>0x00</string> ... </dict> 2. Reinstall Web Driver following above article (with SIP: Enabled). 3. Repeat methods above. 4. Reboot ur mach, but it' s still with SIP: Enabled. 5. If Web Drivers are properly loaded; then reboot again with SIP: Disabled: <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x67</string> ... </dict> 6. The last is, if above workarround doesn't fix the problem, trust me: I think be patient is way better, and give Nvidia a little bit time updating their driver. 1 Link to comment Share on other sites More sharing options...
camillionario Posted October 6, 2017 Share Posted October 6, 2017 The only way is to uninstall NvidiaWeb before upgrading, or waiting for new driver Link to comment Share on other sites More sharing options...
Vampirexx Posted October 6, 2017 Share Posted October 6, 2017 If i try to boot with nvidia disable in stuck with the spin gear before login, maybe problem with my intel 630? Help buddies please Link to comment Share on other sites More sharing options...
arsradu Posted October 6, 2017 Share Posted October 6, 2017 If i try to boot with nvidia disable in stuck with the spin gear before login, maybe problem with my intel 630? Help buddies please Actually, no. It's a mess. Nvidia driver for High Sierra is a mess. I can't boot with nv_disable=1 (probably outdated boot arg?) because of stuck loading bar + spinning wheel (so no, you're not alone), I can't boot with the regular nvda_drv=1 (I heard that's not in use anymore) because..new MacOS build which doesn't work with current Nvidia driver. Not to mention NvidiaGraphicsFixup doesn't seem to do anything anymore (black screen for SMBIOS 17,1) Etc etc etc. Oh, and have I mentioned I can't boot without EmuVariableUEFI anymore? Yeah, that too. So...yeah. Awesome. That's why I love my home build. Old video card, supported OOB, no Nvidia drivers needed, no such issues. I'm soo glad I did all my testing on a copy of MacOS installed on an old HDD. Haven't installed this on my main system. Somehow I had a feeling things will go south with this update. They always do. 2 Link to comment Share on other sites More sharing options...
Vampirexx Posted October 6, 2017 Share Posted October 6, 2017 Damn you right buddy, we miss old Uncle Steve Jobs, now we have a much more buggy release Link to comment Share on other sites More sharing options...
William Parker Posted October 6, 2017 Share Posted October 6, 2017 Actually, no. It's a mess. Nvidia driver for High Sierra is a mess. I can't boot with nv_disable=1 (probably outdated boot arg?) because of stuck loading bar + spinning wheel (so no, you're not alone), I can't boot with the regular nvda_drv=1 (I heard that's not in use anymore) because..new MacOS build which doesn't work with current Nvidia driver. Not to mention NvidiaGraphicsFixup doesn't seem to do anything anymore (black screen for SMBIOS 17,1) Etc etc etc. Oh, and have I mentioned I can't boot without EmuVariableUEFI anymore? Yeah, that too. So...yeah. Awesome. That's why I love my home build. Old video card, supported OOB, no Nvidia drivers needed, no such issues. I'm soo glad I did all my testing on a copy of MacOS installed on an old HDD. Haven't installed this on my main system. Somehow I had a feeling things will go south with this update. They always do. Long time friend . Hope you're doing great. Sensible and both feet on terra firma ! Good. I did erase my SSD and tried the HS install and eventually restored 10.12.6 from TM backup, with same conclusions as you list. Guess we'll meed to wait some more. Link to comment Share on other sites More sharing options...
phi777 Posted October 6, 2017 Share Posted October 6, 2017 New Driver !https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.15.117.pkg(Compatible with BuildVersion 17A405, still ProductVersion: 10.13) EDIT: Didn't expact this till monday, THANKS NVIDIA DEVELOPERS and wish you a very good weekend!!! 9 Link to comment Share on other sites More sharing options...
Gurqn Posted October 6, 2017 Share Posted October 6, 2017 New Driver ! https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.15.117.pkg Yeap, returned back! 2 Link to comment Share on other sites More sharing options...
Vampirexx Posted October 6, 2017 Share Posted October 6, 2017 Awesome works like a charm finally!! Thanx to all mates 2 Link to comment Share on other sites More sharing options...
chris1111 Posted October 6, 2017 Share Posted October 6, 2017 Works here latest Package 2 Link to comment Share on other sites More sharing options...
camillionario Posted October 6, 2017 Share Posted October 6, 2017 Works here latest Package Have you had problems with the installation of NvidiaWeb ?. (error installation) Link to comment Share on other sites More sharing options...
chris1111 Posted October 6, 2017 Share Posted October 6, 2017 Have you had problems with the installation of NvidiaWeb ?. (error installation) No I mode the preinstall script EDIT** preinstall script I have SIP Disable and no warning 2 Link to comment Share on other sites More sharing options...
Porkserver Posted October 7, 2017 Share Posted October 7, 2017 Are the black screens you described WITH a signal (just showing black) or with NO signal (monitor eventually turns off)? In my case, I had a black screen with signal at boot due to my 10-bit color settings being retained from Sierra - it seems the web driver for HS doesn't support 10-bit (as yet). I had to screenshare in to my hack from my laptop and change the screen resolution in System Prefs, which reduced it to 8-bit color and brought signal back. This did the trick,,,, I had black screens with signal and sure enough the screen sharing switch solved it all Now I can write a guide for my mobo install 2 Link to comment Share on other sites More sharing options...
TrustAugustus Posted October 7, 2017 Share Posted October 7, 2017 Here is what worked for me: First, I downloaded and installed the update package.At boot disabled "Allow untested kexts" in clover settingsBooted from the installerRebooted and once again "allow untested kexts"Installed the updated driver Reboot and everything is running nicely Link to comment Share on other sites More sharing options...
MacDavePro Posted October 7, 2017 Share Posted October 7, 2017 It's a mess. Nvidia driver for High Sierra is a mess. Nope - Nvidia driver works perfectly. It just needs to be installed correctly. Did you ignore the warning during installation? I can't boot with nv_disable=1 (probably outdated boot arg?) because of stuck loading bar + spinning wheel (so no, you're not alone) Not outdated. nv_disable=1 stops nvda_drv being written to (emulated) nvram. It works just fine. Whenever you have issues booting your should boot with the verbose (-v) boot arg to have more idea of what is not working. I can't boot with the regular nvda_drv=1 (I heard that's not in use anymore) nvda_drv=1 has been deprecated but it continues to work as of Clover v2.4 r4322. Without knowing all of your details I speculate that you possibly installed the WebDriver with SIP disabled which will prevent the MTL plugins loading (GateKeeper blocks them as untrusted). new MacOS build which doesn't work with current Nvidia driver. The driver works with 17A405 - but the NVDAStartupWeb kext needs to be modified to prevent that kext from disabling the driver. you@your_mac% sudo sed -e "s/17A365/17A405" /Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist Not to mention NvidiaGraphicsFixup doesn't seem to do anything anymore (black screen for SMBIOS 17,1) NvidiaGraphicsFixup isn't needed for iMac17,1 SMBIOS. That SMBIOS doesn't black screen because of AppleGraphicsDisplayPolicy - only MacPro6,1 does. Your black screen is most likely caused by the nvidia driver not loading - not AGDP. My 1080Ti on X299 works perfectly with no Lilu, no NvidiaGraphicsFixup and no AGDP patches. Oh, and have I mentioned I can't boot without EmuVariableUEFI anymore? Yeah, that too. So...yeah. Awesome. EmuVariableUEFI is required because your UEFI doesn't provide native NVRAM access to the OS (some PC UEFI systems do). This isn't a flaw in High Sierra. Link to comment Share on other sites More sharing options...
RussianT Posted October 7, 2017 Share Posted October 7, 2017 Hello everyone. Updated to High Sierra today, now I have these nasty glitches in most apps (screenshot).At first I thought maybe it's because of previous NVIDIA web drivers I had from Sierra. So I tried to update to the latest web drivers. Installer had an error but was able to finish. Now I have latest NVIDIA web drivers and system NVIDIA drivers, and on both of them I still have these glitches. In some apps (like web browser or photo viewer) they start ~15-30 minutes after starting a system, and in some apps (like photoshop) they are shown from the very beginning. Any ideas how to fix this? Link to comment Share on other sites More sharing options...
joe75 Posted October 7, 2017 Share Posted October 7, 2017 Nope - Nvidia driver works perfectly. You must have some low standards? We can barely run a damn screen saver.. 1 Link to comment Share on other sites More sharing options...
William Parker Posted October 7, 2017 Share Posted October 7, 2017 Tried with new Nvidia divers 117 and they need to be installed with SIP 0X0 setting in Clover, this is to be done after agdpfix which needs SIP 0x67 set in clover and then after the Nvidia install boot using SIP as 0X03. Can you friends please confirm this? Thank you. Link to comment Share on other sites More sharing options...
Recommended Posts