macOS 10.13.3 Supplemental Update

[bkendig]

HELP
not loading....
Stay in the Apple logo

After doing this step even
install FakeSMC.kext in /Volumes/EFI/EFI/CLOVER/kexts/Other

Boot into Safe Mode and Verbose (enter -v -x into the Clover boot options) and see what error it displays. If you need help, post a screenshot of the messages after it stops.

 

[ironwood]

How many displays do you have and how are you connected to them?

.156 gave me black screens on my two displays connected by HDMI. I'm curious if you're connected over HDMI as well.

I use DisplayPort and use NvidiaGraphicsFixup and Lilu. MAKE SURE ALL YOUR KEXTS AND CLOVER ARE THE LATEST VERSIONS.

EDIT: Re NVIDIA web driver and 8 or 9 Series mainboards: MUST UNINSTALL OLD WEB DRIVER AND TEMPORARILY ENGAGE SIP to properly install new web driver. I used the NVIDIA preference pane to uninstall the old web driver (25.104), downloaded the new 25.158 web driver, used Clover Configurator to set the CsrActiveConfig to 0x0 (save), and rebooted; made sure there were no Nvda* or GeForce* files in /Library/Extensions -and no GeForce*Web* files in /System/Library/Extensions (there weren't), changed CsrActiveConfig back to 0x67 (save), installed 25.158 web driver with downloaded installer; rebooted.

NOW no black screen; no lag as expected with this board; all good.

Thanks to iFrodo and previously to iLikeHackintosh, and many others here!

 

[DeviousReignz]

Updated from the AppStore and after reboot the Nvidia Manager found the new drivers and updated. No problems, everything working normal for me.

 

[frontgear]

HELP
not loading....
Stay in the Apple logo

After doing this step even
install FakeSMC.kext in /Volumes/EFI/EFI/CLOVER/kexts/Other

Any chance you have both Intel built-in graphics and NVidia GTX cards?

 

[frontgear]

Just updated from the stand-alone Supplemental Update package. After the update is finished, I had to run vulgo's webdriver.sh script to update the build number into the current (.104) Web Driver and was back in business.

I did run into a minor hiccup but figured out what had caused the issue. My system has both the Intel HD 630 and NVidia GTX 970. I had not removed the NVidia GTX 970 when trying to run the supplemental update and, of course, it got stuck at the Apple logo. I had to modify the config.plist file to include the FakeID for the Intel HD 630 (IntelGFX=0x59128086) and ig-platform-id=0x5912000 in order to proceed (without having to remove the NVidia GTX 970 card.) Once the update had finished, the config.plist file was restored to the earlier version (without the IntelGFX and ig-platform-id changes).

 

[vmiyoshi]

My machine is out of commission on the count of this update.
I'm pretty new to using Intel Graphics, I have only been using Intel since the beginning of this year.
Every time I update it's been a nightmare. The Installer crashes when trying to boot the graphics, the only thing that works is going completely back in Nvidia, which normally results in me having to download and run the installer again. Once upgraded, I try to go back to using Intel graphics, but just like when I try to run the installer, my machine crashes when MacOS tries to boot the graphics.
In the past, I would just patch the .104 drivers and keep it moving.
Once 11.13.3 came out late last month, and I learned more about "OsxAptioFix3Drv-64.efi, " I was able to get my machine back on Intel.
However now Intel isn't working, and I can't get the Nvidia Webdriver to load even after patching the .104 drivers.
I'm tempted to update to the new drivers, but I don't know. I think I will sleep on it first.
Has anyone out there see something similar to what I laid out above?

 

[sasta]

What do you changed to work?

Nothing really !
I don't know why I had problems in the first place.
This was the first time I 've had problems updating since sierra.

 

[davideantonio]

Boot into Safe Mode and Verbose (enter -v -x into the Clover boot options) and see what error it displays. If you need help, post a screenshot of the messages after it stops.

It's not working my screen after -v -x is attached

 

[UtterDisbelief]

Hi there,

@susudio made an interesting point back in post #38 on page 4.

Does anyone know if anything other than the Telugo character problem has been addressed?

I mean if you use that language/character set, great, don't mis-understand, but by Apple standards this is a small update (and worth downloading and keeping In your personal library).

Is it worth using otherwise and risking potential problems?

Just a thought.

 

[kavlos]

Works without problems.