- Jul 17, 2018
- Gigabyte Z370P D3
- GTX 1060 + GTX 650 Ti
Clover will also set/unset that variable if NvidiaWeb setting is present in config.plist. The NvidiaWeb setting is not required when nvram is working aka natively.
OK that's interesting, thanks. I've been booting both with and without ticking NvidiaWeb -- with it, my computer hangs at the login page; removing it lets me boot up (with a flickery screen) and try things. So this may be what is un-setting it.
Do you know whether the boot argument also changes the nvram setting, or is that an independent mechanism?
Edit: Booting with "nv_disable=1" and without anything else (no nv* boot arg, no NvidiaWeb tickbox) the nvram setting seems to be preserved now. The only weirdness is that it gets altered from 1 to 1%00 but I am assuming that means nothing:
$ nvram -p | grep nv nvda_drv 1%00 $ nvram -p | grep test test_oct 13
Maybe at last I conclude that nvram is working fine. And my driver problem must be something else.