Contribute
Register

[Guide] HackrNVMeFamily co-existence with IONVMeFamily using class-code spoof

Status
Not open for further replies.
Hi Rehabman,

Ahhhhh bugger ... i forgot all about the --spoof option requirement (brain-fade) for the kext gen , this system has been running a long time without spoofing, i set it up before you came up with the spoof method, so the HackrNVMeFamily kext was from that time ...

Have just generated new kext (with --spoof) and all working now ... good spot bro.

Just a suggestion but maybe you could mod your sketch so that the kext generated by it has "spoof" in the file name if run with the --spoof option .... otherwise hard to tell them apart ...

Thanks buddy
Jay
 
Gosh that was quick ... Nice Job ReHabMan

Jay
 
Hi, could this guide work on a mac with High sierra 10.13.3? I'm trying to create the kext and ssdt for my xps 15 that has a samsung pm981 nvme. (keeps rebooting during install)

so i upgrade to high sierra from el capitan on my main hackintosh. but when running the script I'm getting this error.

Code:
ERROR: no patch name specified, and unable to determine a suitable patch automatically
 
Hi, could this guide work on a mac with High sierra 10.13.3? I'm trying to create the kext and ssdt for my xps 15 that has a samsung pm981 nvme. (keeps rebooting during install)

so i upgrade to high sierra from el capitan on my main hackintosh. but when running the script I'm getting this error.

Code:
ERROR: no patch name specified, and unable to determine a suitable patch automatically

The set of patches applied to create HackrNVMeFamily*.kext are for 512 byte LBA, as the IONVMeFamily.kext in 10.11 and 10.12 is coded only for 4k LBA. 10.13 is reported to have better support for 512 byte LBA, so this set of patches is neither required nor applicable to 10.13.

You could still implement the class-code spoof and use a HackrNVMeFamily*.kext on 10.13 generated from 10.11 or 10.12 IONVMeFamily.kext. But you would need IONVMeFamily.kext from one of the supported 10.11 or 10.12 builds. Assuming you have such a copy of IONVMeFamily.kext, as per patch-nvme README, you can specify the path of IONVMeFamily.kext with the --unpatched option.
 
You could still implement the class-code spoof and use a HackrNVMeFamily*.kext on 10.13 generated from 10.11 or 10.12 IONVMeFamily.kext. But you would need IONVMeFamily.kext from one of the supported 10.11 or 10.12 builds. Assuming you have such a copy of IONVMeFamily.kext, as per patch-nvme README, you can specify the path of IONVMeFamily.kext with the --unpatched option.

How could I get IONVMeFamily.kext from 10.11? I have my El Capitan backed up on time machine. I guess I could revert to that and grab it. Then would I have to update again to 10.13 and run the script to specify the path of the old IONVMeFamiky.kext? Thanks

The set of patches applied to create HackrNVMeFamily*.kext are for 512 byte LBA, as the IONVMeFamily.kext in 10.11 and 10.12 is coded only for 4k LBA. 10.13 is reported to have better support for 512 byte LBA, so this set of patches is neither required nor applicable to 10.13.

Is it possible that the Samsung pm981 ssd could be one drive that doesn't work well with 10.13.3 as was said in this thread by @f23258

https://www.tonymacx86.com/threads/guide-dell-xps-15-9560-high-sierra-10-13-2.243384/page-3
 
Last edited:
How could I get IONVMeFamily.kext from 10.11?

Download 10.11 from the App Store.

I have my El Capitan backed up on time machine. I guess I could revert to that and grab it.

Assuming it is not patched, that would work too.

Then would I have to update again to 10.13 and run the script to specify the path of the old IONVMeFamiky.kext? Thanks

You can create the HackrNVMeFamily any time you like.
If you plan on using it with 10.13,... well, then you'd have to create it before you attempt the update.

Is it possible that the Samsung pm981 ssd could be one drive that doesn't work well with 10.13.3

I don't have the device, so no personal experience with it.
 
You could still implement the class-code spoof and use a HackrNVMeFamily*.kext on 10.13 generated from 10.11 or 10.12 IONVMeFamily.kext. But you would need IONVMeFamily.kext from one of the supported 10.11 or 10.12 builds. Assuming you have such a copy of IONVMeFamily.kext, as per patch-nvme README, you can specify the path of IONVMeFamily.kext with the --unpatched option.
hi. so i downloaded El Capitan and have the unpatched IONVMeFamily.kext from it on my desktop. What would be the command for the script that will allow me to specify the path to it? I'm also still on 10.13.3 .

thanks!

EDIT. NM. I saw it the README. sorry
Code:
./patch_nvme.sh --unpatched /path/to/kext
 
Last edited:
You could still implement the class-code spoof and use a HackrNVMeFamily*.kext on 10.13 generated from 10.11 or 10.12 IONVMeFamily.kext. But you would need IONVMeFamily.kext from one of the supported 10.11 or 10.12 builds. Assuming you have such a copy of IONVMeFamily.kext, as per patch-nvme README, you can specify the path of IONVMeFamily.kext with the --unpatched option.

Gave this a shot but now my nvme drive is not showing under diskutil. I thought from the README that i did not have to include the SSDT_NVMe-Pcc.aml; but excluding that just got me the fast scrolling KP after 3 min of trying to boot up. Should I include the HackrNVMeFamilyInjector.kext since I am dual boot (windows 10) or is that only for dual booting with older 10.11 or 10.12?

attaching problem rep files. thanks
 

Attachments

  • CLOVER.zip
    1.9 MB · Views: 101
hi. so i downloaded El Capitan and have the unpatched IONVMeFamily.kext from it on my desktop. What would be the command for the script that will allow me to specify the path to it? I'm also still on 10.13.3 .

thanks!

EDIT. NM. I saw it the README. sorry
Code:
./patch_nvme.sh --unpatched /path/to/kext
Gave this a shot but now my nvme drive is not showing under diskutil. I thought from the README that i did not have to include the SSDT_NVMe-Pcc.aml; but excluding that just got me the fast scrolling KP after 3 min of trying to boot up. Should I include the HackrNVMeFamilyInjector.kext since I am dual boot (windows 10) or is that only for dual booting with older 10.11 or 10.12?

attaching problem rep files. thanks

You forgot to use --spoof. Read post #1 carefully.
 
Status
Not open for further replies.
Back
Top