Contribute
Register

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

Status
Not open for further replies.
RehabMan said:
You forgot to use --spoof. Read post #1 carefully.
Click to expand...

Ok. i ran the script again with the --spoof option. I also deleted the SSDT_NVMe-Pcc.dsl from the kext/other folder. I did not get the KP this time and was able to see the drive in diskutil and format. but after the first self reboot from the installation, and i go into the newly made "boot macos install from...". it just keeps rebooting at the apple logo.

thanks for the help!

EDIT: Nevermind. I realized I should keep the SSDT_NVME-pcc.aml (not .dsl) in the patched folder. (thats the whole point in getting my NVMe drive to work) So now my disk appear in diskutil. Great. And when I install it does seem to work as the light on my usb flashes (whereas it didn't before during this process) and it goes by much faster.

the problem now is i get this error at this stage of install. IMG_0972.JPG

attached new clover files too. thanks!
 

Attachments

  • CLOVER.zip
    1.9 MB · Views: 73
Last edited:
jacknick said:
Ok. i ran the script again with the --spoof option. I also deleted the SSDT_NVMe-Pcc.dsl from the kext/other folder. I did not get the KP this time and was able to see the drive in diskutil and format. but after the first self reboot from the installation, and i go into the newly made "boot macos install from...". it just keeps rebooting at the apple logo.

thanks for the help!

EDIT: Nevermind. I realized I should keep the SSDT_NVME-pcc.aml (not .dsl) in the patched folder. (thats the whole point in getting my NVMe drive to work) So now my disk appear in diskutil. Great. And when I install it does seem to work as the light on my usb flashes (whereas it didn't before during this process) and it goes by much faster.

the problem now is i get this error at this stage of install. View attachment 312932

attached new clover files too. thanks!
Click to expand...

Off-topic.
Your issue is something else (not NVMe related).
 
hi RehabMan

not sure what to do here cause im new but i have sabertooth x79 with moded bios to enable booting m.2 drive and asus mini pci-e adapter with 960 evo 256gig and os x 10.11.6 :)

i made new install disk with 10.13 and booted and could see my new 960 m.2 drive as external though but did format it and created 1 partition and started to installation of 10.13. so the copy install part finished well but when the system reboot there is nothing showing up in clover.. i cant find the new installation partition and maybe its problem related to creating the install disk in the first place... maybe not.. not sure.

anyway i would like to patch 10.11.6 IONVMeFamily but this guide looks so complicated for me.. is there a patched kext that could work with my 960 evo that i can use maybe? or clover patch that i can add to the config.pls instead of all these complicated steps?

or simply a better way to install 10.13 to my 960 evo since i already can boot the drive but clover is not showing up the new installed partition.
i have the latest clover v2.4k_r4411 installed but when i boot the clover booting screen show 4392 not sure what i did wrong there as well.

what should i do man...
 
daviddx said:
i made new install disk with 10.13 and booted and could see my new 960 m.2 drive as external though but did format it and created 1 partition and started to installation of 10.13. so the copy install part finished well but when the system reboot there is nothing showing up in clover.. i cant find the new installation partition and maybe its problem related to creating the install disk in the first place... maybe not.. not sure.
Click to expand...

Off-topic (as your NVMe is working)...
But you probably forgot apfs.efi in drivers64UEFI.
 
ok sounds good, i guess i forgot to add apfs.efi thanks for that rehabman :)
I would like to know how to patch or use colover patch for 10.11.6 as well... what should i do ?
 
I just made a new Clover v r4411 USB and downloaded the latest 10.13.3 apfs.efi (https://www.tonymacx86.com/threads/...apfs-efi-downloads.236103/page-4#post-1681873) and put it in drivers64UEFI although I didn't make APFS partition but the normal HFS+, I still cant see the new installed 10.13.3 when I boot with Clover...

What did I miss RehabMan ?
BTW, do I need so many drivers in both folders, and is that why the new installation partition is not showing up?

Screenshot https://imgur.com/a/Rwl1b
 
daviddx said:
I just made a new Clover v r4411 USB and downloaded the latest 10.13.3 apfs.efi (https://www.tonymacx86.com/threads/...apfs-efi-downloads.236103/page-4#post-1681873) and put it in drivers64UEFI although I didn't make APFS partition but the normal HFS+, I still cant see the new installed 10.13.3 when I boot with Clover...

What did I miss RehabMan ?
BTW, do I need so many drivers in both folders, and is that why the new installation partition is not showing up?

Screenshot https://imgur.com/a/Rwl1b
Click to expand...

Off-topic. This topic is for NVMe on Sierra and El Capitan. Nothing to do with Clover detection.
 
daviddx said:
sry for going Off-topic again but im trying to explain my situation here...
anyway right now im trying to read your guide section by section but wanted to ask is the clover inject okej to use or could that generate read error as piker mentioned with you in his blog here
https://pikeralpha.wordpress.com/2016/06/29/nvmefamily-kext-bin-patch-data-for-el-capitan/

if the clover inject its easier to use where can i find it ?
Click to expand...

For 10.13, this guide does not apply.
10.13 has better native support for 512 byte LBA NVMe SSDs.

If you're actually installing Sierra or El Capitan, then follow the guide as written in post #1.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top