Contribute
Register

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

Status
Not open for further replies.
Rulebreaker01 said:
thank you for your quick reply. I know what you are talking about. If I run the script using version 10_12_3 witch I am using, it generates HackrNVMeFamily 10_12_3.kext. I copy this kext in Efi/Clover/Kext/Other and it does not work. The drive does not appear in disk utility. If I delete this kext and use the one I created when I was on 10_12_0, (HackrNVMeFamily 10_12_0) in the same place, it works.
When I generate HackrNVMeFamily 10_12_3, the script tells me that the MD5 sums in correct.
Click to expand...

I would have to see all data as requested in post #1, "Problem Reporting".

Perhaps you did not generate with the --spoof option when you created the 10_12_3 kext?
 
Last edited by a moderator:
I have attached two zips, the one that does work (with 10_12_0.kext) and the one that does not work.
I surely did generate with --spoof. Had I not use --spoof, the kext generated wouldn't have been named HackrNVMeFamily 10_12_3.
 

Attachments

  • 0 bytes · Views: 34
  • 0 bytes · Views: 46
Rulebreaker01 said:
I have attached two zips, the one that does work (with 10_12_0.kext) and the one that does not work.
I surely did generate with --spoof.
Click to expand...

The HackrNVMeFamily_10_12_3.kext in "not workingCLOVER.zip" WAS NOT generated with --spoof.
The HackrNVMeFamily_10_12_0.kext in "workingCLOVER.zip" was generated with --spoof.

Had I not use --spoof, the kext generated wouldn't have been named HackrNVMeFamily 10_12_3.
Click to expand...

The --spoof option DOES NOT affect the name of the kext.
 
Last edited by a moderator:
Is every guide this esoteric and complicated? I'm not a programmer.
 
rdjg22 said:
Is every guide this esoteric and complicated? I'm not a programmer.
Click to expand...

No need to be a programmer. For novices, this topic may seem relatively advanced. But really it is quite a simple case of property injection via ACPI _DSM.

Read the guide carefully.
 
OK. I did it. Now it works. What I did differently was, when I execute in terminal ./patch_nvme.sh --spoof 10_12_3 command, first I dragged and dropped the folder downloaded from github to enter the paht to the file and after that path I wrote the name of the file with the spoof argument.
 
Rulebreaker01 said:
OK. I did it. Now it works. What I did differently was, when I execute in terminal ./patch_nvme.sh --spoof 10_12_3 command, first I dragged and dropped the folder downloaded from github to enter the paht to the file and after that path I wrote the name of the file with the spoof argument.
Click to expand...

Please note that the guide in post #1 does not use any kind of Finder drag/drop... because none is necessary.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top