Contribute
Register

OS X Driver for NVMe M.2 Solid State Drives Released

Status
Not open for further replies.
This is ENORMOUSLY unclear. Many of you say you can boot in 10.12.1 using the USB installer with KextToPatch.

You can, but you will need updated patches.
 
OK I am in the following situation now: I updated to 10.12.1 and I thought I could remove IONVMEFamily.kext from Windows, which I could, thanks to my HFS driver, but it seems that it's still loading the kext through some extensions.mkext or something like that. How do I delete the cache from Windows?
 
Any updated patch I can try? I feel like I've hosed my system. I dont even have a USB installer, I thought I had it. :(
 
Any updated patch I can try? I feel like I've hosed my system. I dont even have a USB installer, I thought I had it. :(

Updated patches for IONVMeFamily 10.12.1 are available if you search for them. I have not tested them and will not have a chance to add them to my repo for a while (busy with other things).
 
did you try to boot without cache option from the bootloader screen?

When you see clover screen press the space bar and then select option without caches then boot with these options
 
Last edited by a moderator:
Hi, thank you for the reply. I dont have such option if I press spacebar at boot. I also tried to add NoCaches=1 in the options but the result is always the same.

I have a USB drive with a CCC copy of my system before the upgrade, but clover won't boot into it.

Ideas?
 
Hi, thank you for the reply. I dont have such option if I press spacebar at boot. I also tried to add NoCaches=1 in the options but the result is always the same.

I have a USB drive with a CCC copy of my system before the upgrade, but clover won't boot into it.

Ideas?

You might try an older version of Clover that does have the "without caches" option.
 
Thanks for the props. In the end I managed to never the footer to the older version and boot the recovery partition. With that, I managed to delete IONVFamily.kext from my main partition, and that did the trick.

Is there any "IONVFamilyDisabler.kext" that prevents the vanilla one from loading? This would make future updates so easy...
 
Is there any "IONVFamilyDisabler.kext" that prevents the vanilla one from loading? This would make future updates so easy...

I worked on it for a little while, but the problem here is the memory trash/bug upon a failed probe. It is not difficult to keep a kext from starting (by having another probe with a higher IOProbeScore), but there doesn't seem to be a way to keep a kext from running probe.

One idea I would like to try is injecting a bogus class-code via ACPI (_DSM method), and then changing the HackrNMVeFamily to match against this bogus code.
 
One idea I would like to try is injecting a bogus class-code via ACPI (_DSM method), and then changing the HackrNMVeFamily to match against this bogus code.

This sounds like a stable solution. Consider me one f your guinea pigs as soon as you got something to throw at us. :)
 
Status
Not open for further replies.
Back
Top