[Solved] 1080ti boot loop with 10.13 nvidia web drivers

[strategy]

(title should be 378.10 not 10.13)

Finally got my high sierra hackintosh installed via clover UEFI. Went to install the latest 378.10 nvidia web drivers and ran into a boot loop. Nuked the drive and reinstalled high sierra. I went to reinstall the nvidia web drivers again thinking maybe something went wrong on my original install but same issue once again.

Web drivers from here:
http://www.nvidia.com/download/driverResults.aspx/125379/en-us

I've set the NvidiaWeb boot option in clover. Is there something else I need to do to make them work?

 

[adar]

Boot with -v flag and post the results/errors

 

[jrii]

Does the system work without nvidia driver?
You can disable the webdriver with nv_disable=1 boot option (no need to nuke drive)

 

[strategy]

Does the system work without nvidia driver?
You can disable the webdriver with nv_disable=1 boot option (no need to nuke drive)

I tried that but I thought that command doesn’t work with clover. Regardless it still won’t boot.

Boot with -v flag and post the results/errors

I’ll have to take a video and pause it. It seems to happen right after DSMOS has arrived but I don’t see any error messages but it instantly reboots.

 

[Amitkumar80752]

Before installing nvidia web driver mount your partition using efi mounter go to config.plist anf open it it will be opened in clover configurator then go to rt variables and change csr config active 0x0 and restart your pc then after restarting install nvidia web driver it will ask for permission in midway just give it and install it will say to restart to finish installation don't restart right now go to efi mounter mount your partition open config.plist and in rt variables change csr config active to 0x67 then close clover configurator and then restart now it should not give you bootloop mine gtx970 working great after that i hope this solves your problem do tell if it works for you.

 

[strategy]

Here is a picture of a video I took and the last thing I see before reboot. Sorry for the potato quality.
https://i.imgur.com/6aQ0YYe.jpg

Before installing nvidia web driver mount your partition using efi mounter go to config.plist anf open it it will be opened in clover configurator then go to rt variables and change csr config active 0x0 and restart your pc then after restarting install nvidia web driver it will ask for permission in midway just give it and install it will say to restart to finish installation don't restart right now go to efi mounter mount your partition open config.plist and in rt variables change csr config active to 0x67 then close clover configurator and then restart now it should not give you bootloop mine gtx970 working great after that i hope this solves your problem do tell if it works for you.

Ill try this later today, hopefully that works.

If I do nv_disable=1 I get this new screen:

https://i.imgur.com/4CBcSy6.jpg?1

I used this guide to configure my config.plist, I know its for high sierra beta but im wondering if I missed an option and that is what is causing this.

https://www.macobserver.com/tips/deep-dive/macos-high-sierra-public-beta-hackintosh/

 

[Amitkumar80752]

Here is a picture of a video I took and the last thing I see before reboot. Sorry for the potato quality.
https://i.imgur.com/6aQ0YYe.jpg




Ill try this later today, hopefully that works.

If I do nv_disable=1 I get this new screen:

https://i.imgur.com/4CBcSy6.jpg?1

I used this guide to configure my config.plist, I know its for high sierra beta but im wondering if I missed an option and that is what is causing this.

https://www.macobserver.com/tips/deep-dive/macos-high-sierra-public-beta-hackintosh/

You need to remove nvidia drivers first if you are getting black screen at startup and then follow method

 

[aol]

Yeah you are probably having the issue where the unsigned kexts are not being loaded because of a SIP issue, and it's causing you a boot loop. If SIP is enabled (the default), the kextcache won't be built using unsigned kexts and a Hackintosh won't boot without unsigned kexts like FakeSMC.kext. Folks doing the Nvidia web drivers have tied themselves in knots enabling then disabling SIP. Personally my SIP was always disabled and folks advocate for leaving it enabled and disabled. But be aware that if it's enabled you'll need to manually rebuild the kextcache whenever you make kext changes in order to cache the unsigned kexts.

Ideally you'll delete your GeForce*.kext and NVDA*.kext from /System/Library/Extensions and /Library/Extensions (wherever they are) and boot with SIP DISABLED so the kextcache gets rebuilt and you can get to the desktop. Then just reinstall the web drivers (SIP DISABLED, nvidiaweb true, nv_disable false, nvda-drv false, inject Nvidia false), possibly force a kextcache rebuild, reboot to a working system. If you're going to mess around with enabling SIP be aware that you need to follow a different path and it's very precise, you have to manually rebuild after you install the web drivers and before you reboot. I THINK. Just reporting my synthesis of other posts, I didn't have this problem.

 

[strategy]

Before installing nvidia web driver mount your partition using efi mounter go to config.plist anf open it it will be opened in clover configurator then go to rt variables and change csr config active 0x0 and restart your pc then after restarting install nvidia web driver it will ask for permission in midway just give it and install it will say to restart to finish installation don't restart right now go to efi mounter mount your partition open config.plist and in rt variables change csr config active to 0x67 then close clover configurator and then restart now it should not give you bootloop mine gtx970 working great after that i hope this solves your problem do tell if it works for you.

Just tried this and no go - still the same boot loop. Even did a complete new fresh install.

 

[strategy]

Yeah you are probably having the issue where the unsigned kexts are not being loaded because of a SIP issue, and it's causing you a boot loop.

Im using kext-dev-mode=1, doesnt that allow unsigned kexts?