- May 3, 2012
- Intel DH67BL
- HD 3000
- Mobile Phone
Just points to another failure to follow the guide...
HFSPlus.efi is missing from drivers64UEFI.
<key>DisableDrivers</key> <array> <string>VBoxHfs</string> </array>
For example your Clover installation link says to install "OsxAptioFixDrv-64" which will cause macOS to fail to boot for me.
I have to install "OsxAptioFix2Drv-64". Previously I tried your config.plist without modification and the macOS boot option disappeared completely.
Another failure to follow the guide. It is because you have SIP settings incorrect. My guide plist has CsrActiveConfig=0x67. Yours does not.
Already answered previously... again, it is because you forgot HFSPlus.efi in drivers64UEFI.
This is the problem with trying to pull small parts out of a guide. You will end up with mismatched parts and things will not work as expected. Must look at the big picture...
Actually it appears that installing Clover again will delete HFSPlus.efi from CLOVER/drivers64UEFI. Why is it doing that?
As much as I'd like to Gung-ho it I'm trying my best to err on the side of caution. This is my main PC right now and I can't afford to lose it. I appreciate your help and I'm sorry if I'm causing you some frustration because of it.
No idea. I haven't had that happen. May be a bug in the specific version of the Clover installer you're using.
I'm using the latest version (Clover r4049). I just tried it again to make sure I wasn't imagining things and it definitely deletes HFSPlus.efi from CLOVER/drivers64UEFI. I'm not sure when it started doing it as I had copied this file over several macOS updates ago.
If macOS fails to boot I just launch into my Windows partition and restore EFI from there. Still I'm slightly unsettled by it!
I've attached my latest files and apologise in advanced if I've done something wrong again.
You have a patch for the framebuffer that does not come from my guide...
And a few other settings LoadVBios, PatchVBios that also are not in my guide.
And you have some kexts that I don't use in kexts/10.12, but when booting your system volume, these are now ignored anyway (InjectKexts=Detect and FakeSMC.kext is installed to the system volume), so that will not affect anything.
Yeah, these settings are required to enable 4K HiDPI modes.
I just deleted everything out of kexts/10.12 and did a reboot and test... still getting the video freeze issue. So my guess is it's the same problem as HD4600/HD4400. At least IntelGraphicsFixup/Lilu/Shiki appears to solve it for now.
Thanks again for all your help RehabMan; this community benefits a great deal from your work.