NVIDIA Releases Alternate Graphics Drivers for macOS High Sierra 10.13.0 (378.10.10.10.15)

[Raouws]

#2

I did try exactly that and it failed.

 

[Raouws]

Remove the files the web driver installs then -

Supposedly that error is irrelevant. But I also installed fresh, then before installing the drivers, I booted with SIP enabled. (CSRActive Config 0x0). When I installed the web drivers, I got a popup for gatekeeper security and allowed the Nvidia Extension. Then rebooted with SIP disabled (CSRActive Config 0x67) All good. But I do not require Lilu, NVidiaGraphicsFixup , and or the AGDP patch because I use SMBIOS iMac 18,3. I also have EMUVariable64UEFI.efi because my motherboard does not support NVRAM. My iGPU is disabled in the BIOS and Primary graphics is set to PEG.


P.S. If I try to install the Web drivers with SIP disabled, I get the same error as you. So as a precaution, I enabled SIP before installing them.

So if you are using SMBIOS iMac 15,1 17,1 or Mac Pro 6,1 you are going to need Lilu, NVidiaGraphicsFixup , or the AGDP patch. And EMUVariable64UEFI.efi just to be safe. If you already borked the library you may need to add NVWebDriverLibValFix.kext

Im using SMBIOS 17,1.
and I've heard that NVWebDriverLibValFix should not be used with NVidiaGraphicsFixup.& Lilu
Im not quite sure what any of them do either way, so maybe if you know could you quickly describe what exactly these kexts do?

How do I know if I have NVRAM?
Also what I want to understand is what is this EMUVariable64UEFI.efi extension? where do I put it and what does it do?
I did try some thing similar to storks post #2 with SIP but it failed, but you describe a slightly different way
and I haven't tried it out yet with the inclusion of those extensions NVidiaGraphicsFixup.& Lilu & EMUVariable64UEFI.

I will try your way but I need one final thing, I'm not very familiar with all the terminal commands and stuff and it seems to be very hard to find all the right ones in google which seems very odd.
In the scenario where I try your way and still fail I won't be able to boot, how do I go to recovery mode and delete all the installed WevDriver files.

 

[vulgo]

I get an error message
saying the drivers where installed improperly and might not function correctly.

That popup is generated in the pre-install script if unsigned kexts are allowed, BEFORE the installation begins. Ignore it.

I got a popup for gatekeeper security and allowed the Nvidia Extension.

On a fresh install, this is the expected behaviour with SIP 0x0, 0x3, 0x67, as none of these turn off 'User-approved kernel extension loading'. Use 0x2EF or just put 0x3FF in the config.plist to disable SIP completely including this security prompt and to allow third-party kexts automatically.

I've heard that NVWebDriverLibValFix should not be used with NVidiaGraphicsFixup

The latest version of NvidiaGraphicsFixup includes the LibVal fix so you should remove NVWebDriverLibValFix.

 

[Raouws]

That popup is generated in the pre-install script if unsigned kexts are allowed, BEFORE the installation begins. Ignore it.

Ive also noticed that the first time I tired installing the WebDriver with SIP being 0x3, it installed its kexts into /L/E
as far as I can remember in my previous install of MacOS 10.12.6 they were all in S/L/E
is that normal? for them to appear in /L/E now? or is that because of SIP?

 

[vulgo]

Ive also noticed that the first time I tired installing the WebDriver with SIP being 0x3, it installed its kexts into /L/E
as far as I can remember in my previous install of MacOS 10.12.6 they were all in S/L/E
is that normal? for them to appear in /L/E now? or is that because of SIP?

/L/E is the correct location for third-party kexts, for whatever reason, with this driver update the kexts are where they should be.

 

[Raouws]

/L/E is the correct location for third-party kexts, for whatever reason, with this driver update the kexts are where they should be.

Ok thank god, you've calmed me down with this one.
At least now I know they are being installed to the correct place.

 

[Clicky]

That popup is generated in the pre-install script if unsigned kexts are allowed, BEFORE the installation begins. Ignore it.
On a fresh install, this is the expected behaviour with SIP 0x0, 0x3, 0x67, as none of these turn off 'User-approved kernel extension loading'. Use 0x2EF or just put 0x3FF in the config.plist to disable SIP completely including this security prompt and to allow third-party kexts automatically.
The latest version of NvidiaGraphicsFixup includes the LibVal fix so you should remove NVWebDriverLibValFix.

0x67 doesn't trigger the gatekeeper message. And on a previous fresh install when testing after borking the library by installing without SIP enabled, NVWebDriverLibValFix was the only thing that got me past the boot loop. The latest version of NvidiaGraphicsFixup and Lilu didn't.

 

[vulgo]

0x67 doesn't trigger the gatekeeper message.

When?

 

[Clicky]

When?

When you install the web drivers. If CSRActive config is set to 0x67 and you booted that way, you will not get the gatekeeper pop up but the error message instead. If you are CSRActive config 0x0, it will trigger the gatekeeper message. I didn't bother to try the other ones.

It seems that most people on here just have wacked out beast configs - are not using Emuvariable or AGDP or Lilu/NvidiaGraphicsfix up when needed. It's like the way their system was set up it wouldn't have worked on Sierra either.

I sent a couple an EFI that was set up correctly and removed kexts and all the other trash they were told to place in S/L/E L/E and magically everything worked. Imagine that.

 

[vulgo]

When you install the web drivers. If CSRActive config is set to 0x67 and you booted that way, you will not get the gatekeeper pop up but the error message instead. If you are CSRActive config 0x0, it will trigger the gatekeeper message. It didn't bother to try the other ones.

The error/warning message's sole purpose is to pop up if unsigned kexts are being allowed, it doesn't do anything else, look at the pre-install Perl script if you don't believe me. 0x67 doesn't set the 'user approved kernel extensions' CSR bit, unless you've already installed any version of the web drivers previously you should get the prompt to allow them to load. Either way, they load with that bit set, with or without a security prompt.

It seems that most people on here just have wacked out beast configs - are not using Emuvariable or AGDP or Lilu/NvidiaGraphicsfix up when needed. It's like the way their system was set up it wouldn't have worked on Sierra either.

That sounds about right.