macOS 10.13.3 Supplemental Update

[pastrychef]

I manually edited the Nvidia web drivers to work with macOS 17D102.

Then went to App Store to start the update.

Walked away to have a sandwich and the update was done before I finished the sandwich. Smooth sailing.

 

[UtterDisbelief]

I am unable to install this update. First, I had the supplemental update showing up *another time* in the Appstore update section after the *first update.* This happened to my MBP as well. The MBP did the actual update after doing the procedure for the 2nd time, however my Hack is still stuck at 17D47! There were no actual error messages I could see (like others posted). Then I tried to do a manual update using the standalone installer. Still, I am stuck at 17D47, and in addition I now see a Folder called "macOS Install Data" at the root of my boot drive. Even removing this folder and updating again has no effect. Plus I do not see the update in the Appstore anymore.

WTF? Any ideas?

Hope you have this sorted now. If not ...

My first impression when I read your problem was, yes, you did the right thing downloading the combo update instead.

Now what it *looks* like might have happened is that the installer didn't kick in. Usually, during the update Clover grows another icon. It's a High Sierra one but the text when you roll your mouse over is that it is an installer. In my experience it's usually to the left of the others. If you choose the middle one you boot straight back into your previous version and leave the temporary files unused.

Might be that. Might be something else. Check it again and see etc.

 

[UtterDisbelief]

Woah, woah. Nobody is offended here. And all I meant was that the EFI partion is always there. But you're right in that you can't access it (or any FAT/FAT32 drive) in Safe Mode. That's all. My other point was simply that the original intention of Clover on EFI and separating out third-party kexts to the /kexts/Other folder was so you have all the vanilla (and commercial vendor) items in the normal, Apple locations (LE or SLE). That way, any alterations needed can take place as early in the boot cycle as possible and you don't need to worry about duplicates causing havoc. And I'm not arguing that you CAN'T put them in either location, just the WHY it's not a good practice. Also, I couldn't agree more with your last statement. I'm not on any ego trip, either and just like to help out if I can, as well.

Yes, I agree, I put as much third-party stuff in EFI/CLOVER/kexts/Other as I can to keep it separate from the base system. A bonus is that I can just copy the EFI folder to a safe place and have an easy, restorable configuration if I ever reformat an SSD etc. (and this has been needed when Windows HFS+ drivers have corrupted a drive - or two - I learned the hard way).

Having said that some macOS kexts are patched in their original locations and need properly re-installing with cache-rebuilding too. Spotting them sometimes can be tricky...

 

[Obvious Answer Man]

Per Apple's recommendations third-party kexts go in /Library/Extensions.

The only kext recommended to go in /EFI/CLOVER/kexts/Other/ is FakeSMC.kext and it's only because kexts are not loaded from /Library/Extensions during upgrades and FakeSMC.kext is needed to boot the upgrade.

 

[Superbogey]

Yes, I agree, I put as much third-party stuff in EFI/CLOVER/kexts/Other as I can to keep it separate from the base system. A bonus is that I can just copy the EFI folder to a safe place and have an easy, restorable configuration if I ever reformat an SSD etc. (and this has been needed when Windows HFS+ drivers have corrupted a drive - or two - I learned the hard way).

Having said that some macOS kexts are patched in their original locations and need properly re-installing with cache-rebuilding too. Spotting them sometimes can be tricky...

Yeah, I'm with you there. The keeping track and updating kexts is an art all on its own. If I had any programming background, I'd try to come up with something that would mount the EFI partition, scan it and your boot drive for all kexts, check the kexts against their current versions, alert you about any version mismatch and either update them or allow you to download and install them yourself along with automatic cache rebuilding. Maybe that could somehow be added to Clover Configurator. They already have something vaguely similar in the "Drivers" section.

 

[Superbogey]

Per Apple's recommendations third-party kexts go in /Library/Extensions.

The only kext recommended to go in /EFI/CLOVER/kexts/Other/ is FakeSMC.kext and it's only because kexts are not loaded from /Library/Extensions during upgrades and FakeSMC.kext is needed to boot the upgrade.

Huh. I could swear that one of the other Mods or even TonyMac had advised - after one of the major OS releases - to put the third party ones in /kexts/Other. All I know is that doing it my way is easier to manage and I also feel less likely to unintentionally bork something when updating or troubleshooting issues that may pop up with a new release or any update to the OS. Not to mention the fact that those new releases / updates seem to go more smoothly for me while others seem to be tearing their hair out with theirs. My only issue that I haven't worked out with this system is it's unwillingness to sleep while logged in while it sleeps fine when not logged in. Other than that, I've got everything from iMessage to Handoff working fine.

 

[Duffloop]

Just used the App store update

just forgot to select boot from Mac update on the clover screen 1st time round ;-)

then updated nvidia drivers - all working good

 

[Stork]

Huh. I could swear that one of the other Mods or even TonyMac had advised - after one of the major OS releases - to put the third party ones in /kexts/Other. All I know is that doing it my way is easier to manage and I also feel less likely to unintentionally bork something when updating or troubleshooting issues that may pop up with a new release or any update to the OS. Not to mention the fact that those new releases / updates seem to go more smoothly for me while others seem to be tearing their hair out with theirs. My only issue that I haven't worked out with this system is it's unwillingness to sleep while logged in while it sleeps fine when not logged in. Other than that, I've got everything from iMessage to Handoff working fine.

That advice must have been given long time ago. Since Sierra, MultiBeast has always used /Library/Extensions/ folder which Apple started recommending with 10.12 Sierra.

 

[Superbogey]

That advice must have been given long time ago. Since Sierra, MultiBeast has always used /Library/Extensions/ folder which Apple started recommending with 10.12 Sierra.

Yeah, that could be. Maybe I'm getting old and am remembering it backwards.

 

[Superbogey]

I don't know if the following steps would work with your system but here is what I did (my motherboard is a Gigabyte GA-Z270XP-SLI, which is a 200-series board):

1. Enable Internal Graphics in the BIOS Chipset section and set Pre-Allocated to 128MB, DVMT Total Gfx Mem to 256MB

2. Modify your config.plist file using Clover Configurator:

a. Select change GFX0 to IGPU patch on the Acpi screen​

b. Set Devices > IntelGFX = <id_for_your_board>, Graphics > ig-platform-id = <id_for_your_board>, and check Graphics > Inject Intel option. Do not check Inject NVidia.​

You have to find the IntelGFX and ig-platform-id for your specific board. Mine is a Kaby Lake i7-7700K so IntelFGX = 0x59128086 and ig-platform-id = 0x59120000.

I would create a boot USB drive and put the modified config.plist on that drive. Every time you run an update, boot with that USB drive so you don't have to edit the working config.plist on your HD/SSD.

Sorry, I thinked I've missed something. Under "Devices" in CC, is <id_for_my_board> and, Graphics <id_for_my_board> the same? I've got the one in Graphics set but just wanted to make sure they're not different numbers for different reasons.

Thanks