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

[normski321]

I upgraded to HS thinking that I would be headed for a better life with my 1060 6GB. Turns out not to be so. Same issues and now the 'hot corner put display to sleep' fix no longer works. Considering just getting rid of the 1060 and replacing with something that works - any recommendations?

 

[aol]

I took the plunge and updated to HS. Now I get a full on lockup when the drivers glitch out and have to hard reboot. No Kernel panic, and I cannot SSH or Remote desktop into the machine. I've disabled sleep and it is fine but I really wish it would sleep properly like it did in Sierra. I never should have updated.

I was having no issues on two 1080p monitors. I'd get the wake-from-system-sleep glitching and quickly hot-display-corner-sleep and unsleep and good to go.

Then I replaced a 1080p monitor with a 4k monitor. I had to add lilu and a couple other kexts. Now when it system sleeps it does a hard lockup on wake. FML

 

[OlliverAira]

A LOT OF TEXT

Do you have macOS High Sierra (any version) working with your GTX 1070?

Separate question: Also I wonder if you (or anyone) have any knowledge about if macOS boot up procedure can 'harm' motherboards that are somehow unsupported?

I have a Z170 and had to replace it twice (on 'insurance') after that I started using macOS kinda, the boot up of the motherboard became slower at first and then after a few boots with macOS (10-20, quite many) the mother board "every thing is fine indicator lights" stopped lighting and boot failed before it reaches BIOS



So point is? Motherboard of mine might die again if I install macOS again... Idk what to do xD (I built the PC to run macOS)

 

[pastrychef]

Do you have macOS High Sierra (any version) working with your GTX 1070?

Also I wonder if you (or anyone) have any knowledge about if macOS boot up procedure can 'harm' motherboards that are somehow unsupported?

I have a Z170 and had to replace it twice (on 'insurance') after that I started using macOS kinda, the boot up of the motherboard became slower at first and then after a few boots with macOS (10-20, quite many) the mother board "every thing is fine indicator lights" stopped lighting and boot failed before it reaches BIOS



So point is? Motherboard of mine might die again if I install macOS again... Idk what to do xD (I built the PC to run macOS)

I've never heard of trying to hackintosh a PC killing the motherboard.

 

[StudioCine]

Good evening, I had a hackintosh with the X Sierra tried to upgrade to Hight Sierra and got stuck on the black screen. I reinstalled by Tony's guide here and tried all the possibilities of this topic, but I could not. Some installation possibilities on this hardware: Asrock Extreme 4, I7 3770k, gtx 690, 16GB ram corsair, ssdhd kingston240gb. Help! It's been 7 days since I've tried the whole day and nothing .. Obs. Without the video card the system works with a perfection. Replacing the card does nothing else.

 

[Clicky]

Do you have macOS High Sierra (any version) working with your GTX 1070?

Separate question: Also I wonder if you (or anyone) have any knowledge about if macOS boot up procedure can 'harm' motherboards that are somehow unsupported?

I have a Z170 and had to replace it twice (on 'insurance') after that I started using macOS kinda, the boot up of the motherboard became slower at first and then after a few boots with macOS (10-20, quite many) the mother board "every thing is fine indicator lights" stopped lighting and boot failed before it reaches BIOS



So point is? Motherboard of mine might die again if I install macOS again... Idk what to do xD (I built the PC to run macOS)

Yes GTX 1070 worked on all High Sierras.

As far as OSX damaging your components... I guess if you had wildly inappropriate settings it could wear them out quickly.

Try a different motherboard. Now a days it'd really about the chipset. Asus, ASRock, Gigabyte, MSI... (Bio Star can be a bit wonky), but yeah, they are all the same.

 

[queenmallory]

Hello everyone,

The new version of the Nvidia Web Driver 387.10.10.10.25.158 a few light lags (much less and usable compared to 387.10.10.10.25.156 version), but solves a problem that many people have long since especially on the Pascal series (i've a GTX 1060 6GB : Gigabyte GTX 1060 Mini ITX OC 6G - GV-N1060IXOC-6GD).

With each new driver, I test the suspension of activity that creates glitching after the sleep awakening when the gpu is solicited as a benchmark for example.

The 387.10.10.10.25.158 version solves this big problem, I just tested at the moment.

Otherwise the installation procedure of the Nvidia Web Driver is still a problem and long (CsrActiveConfig to 0x0 and touch ./Library/Extension ./System/Library/Extension in recovery mode), compared to the AMD RX 560, 570 and 580 , natively supported.

It is already good that this solution for glitching.

Have a good day.

Queenmallory

 

[Gen_]

I've never heard of trying to hackintosh a PC killing the motherboard.

Confirming that Hacks do stress parts more than they are usually, and it's pretty across the board. HFS results in more data wear than NTFS. I have RMA'd a 3930k due to TSC errrors after running without PM for a year or so. That's the part of the CPU VoodooTSCSync (which hasn't been updated since Snow Leopard) takes care of and it was refusing to boot anything.

I have also RMA'd boards that I tested DSDTs on. There is a very real, but very slim possibility that a misconfigured DSDT can damage a motherboard. You are of course feeding very basic instructions to electrical circuits and there will be a few in a billion that can create harmful power states if not set up properly.

It's mostly safe because all the dangerous stuff is relegated to kexts and the like. Devs will make sure the dangerous combination of boxes cant be ticked etc etc.

 

[pastrychef]

Confirming that Hacks do stress parts more than they are usually, and it's pretty across the board. HFS results in more data wear than NTFS. I have RMA'd a 3930k due to TSC errrors after running without PM for a year or so. That's the part of the CPU VoodooTSCSync (which hasn't been updated since Snow Leopard) takes care of and it was refusing to boot anything.

I have also RMA'd boards that I tested DSDTs on. There is a very real, but very slim possibility that a misconfigured DSDT can damage a motherboard. You are of course feeding very basic instructions to electrical circuits and there will be a few in a billion that can create harmful power states if not set up properly.

It's mostly safe because all the dangerous stuff is relegated to kexts and the like. Devs will make sure the dangerous combination of boxes cant be ticked etc etc.

That makes sense. It's just more reason to get power management working right and to stick with hardware that's as close to real Macs as possible to avoid having to make such low level mods.

 

[jspalding]

Some help for anyone having issues with the new Nvidia Web Drivers in High Sierra.

1. Make sure you have some sort of backup.
2. Ensure you have the latest version of Clover installed (you should have done this before installing High Sierra)
3. If you have a separate machine - enable screen sharing/remote login in case High Sierra does boot up but with a display problem (e.g. black screen).
4. Ensure you have either a bootable USB with the High Sierra installer available or a working recover partition selectable in the Clover boot menu. This will aid in troubleshooting.
5. Check your EFI partition (subdirectories in "/EFI/CLOVER/kexts/") as well as "/Library/Extensions" and "/System/Library/Extensions" for any kext files that need updating. Ideally you should be doing this before you upgrade to High Sierra
   1. At the very least ensure you have the latest FakeSMC.kext available. Remove any duplicates/copies in the locations above and install the latest version (using KextWizard or similar) in "/System/Library/Extensions" as well copying it to "/EFI/CLOVER/kexts/Other"
   2. Temporarily remove any other kext files you rely on (e.g. Lilu.kext, Shiki.kext, NVWebDriverLibValFix.kext, FakeSMC_CPUSensors.kext, FakeSMC_GPUSensors.kext, FakeSMC_LPCSensors.kext, etc, etc). This will make troubleshooting and isolating any issues easier.
6. Reboot your system (still without the Nvidia Web Drivers installed) and check that you can successfully start High Sierra. You should expect to have no graphics acceleration at this point and a reduced resolution.
7. Reboot again - however this time select "Options" in the Clover Boot Menu and enable SIP by deselecting the "Allow unsigned kext" option. Note that the "NVRAM access" and other options should remain checked to allow a successful boot (this assumes you started off with a "CsrActiveConfig" value of "0x67" in your clover config.plist). As pointed out in other posts enabling SIP is a new requirement in High Sierra to install the Nvidia Web Drivers without errors.
8. Once High Sierra has successfully rebooted - install the Nvidia Web Drivers - either using the Nvidia Driver Manager or alternatively by directly downloading the package from the link provided in the first post of this forum.
9. The installation should proceed successfully without any error messages being shown. Don't reboot when prompted.
10. If you are using a iMac 14,2 SMBios definition you need not do anything else. If you are using a iMac 15 or iMac 17 SMBios definition - you will need the latest Lilu.kext, and NVWebDriverLibValFix installed in "/EFI/CLOVER/kexts/Other".
11. Reboot. If all goes well High Sierra should now work with full graphics acceleration as well as high resolutions.
12. Add your old kext files back to the EFI partition and "/System/Library/Extensions" one at a time - and reboot each time. It is rather laborious but it will help identifying any specific kext causing issues.
13. Disable screen sharing/remote login if you had it enabled above.

If things go wrong:

1. Check the boot and preboot logs available in "/EFI/CLOVER/misc" on the EFI partition.
2. If you cannot access the EFI partition or file system mount your EFI/file system partition after booting either the USB or recovery partition and using Terminal and diskutil to mount the partition as required.
3. If you get a "black screen", first check if you can connect via screen sharing (if you have a separate computer and assuming you have it disabled) before doing a hardware reset.
4. If all else fails remove all non-essential 3rd party kext files from "/EFI/CLOVER/kexts/" - at a minimum only FakeSMC.kext is required.
5. If you did install the Nvidia web drives and you ignored any errors - you can delete and revert to the "standard" graphics drivers by:
   1. Deleting all "NVDA*Web*.kext" and "GeForce*Web*.kext" files in "/System/Library/Extensions"
   2. Deleting all "GeForce*Web*.kext" files in /Library/Extensions

Thanks. These files are extremely useful, and here are the actual fixes for me:

1. The ignored "nvda_drv=1" boot flag. (SURPRISE!) Without it there will be "NVDAStartupWeb: Official" in verbose logs and graphics is doomed. Just setting NvidiaWeb=true in config.plist IS NOT enough to get it loading ("NVDAStartupWeb: Web"). I don't know why but it just works for me. and I've tested with this single difference to confirm this conclusion.
2. Proper EmuVariableUefi-64.efi. Maybe I have a broken EFI folder before...

And the OsxAptioFix2Drv-free2000.efi is indeed useful on my MSI B250M Mortar mobo. All other 3 equivalent EFI drivers refuse to boot with SIP enabled (though no need to enable it here).

And for those who still can not get their cards to work, pay attention to the "NVDAStartupWeb: xxxx" line in verbose boot log. If it's "Official", the web driver is not loading at all, and action is required to load the driver so it becomes "Web".

I just wanted to add physically, in the hardware, make sure your first GPU (atleast one of them) is plugged into the PCIEX16 because if it's plugged into an x8 or an x4 then it will not run correctly and you'll get the black screen! X16 is generally the one closest to the CPU! You may need an extender depending on how bulky your GPU/CPU Cooler is/are. That's what I ended up doing. Just sharing some knowledge that took me weeks to find to help out the next guy or gal.