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

[RehabMan]

Hello
RehabMan

I'm having problem tried to follow all 88 pages still can't get my NMVE to show in disk util

I have a X99 Asrock NVMe 960 evo

I'm on 10.12.4

I attached my EFI folder

My id BIOS name is _SB_.PCI0.BR1B.H000

I put the generated .aml file in the ACPI patched, and I generated HackrNVMeFamily-10_12_4.kext. use kext wizard to install in /system/lib/ext


Also, when I tried to create another patched HackrNVMeFamily-10_12_4.kext, it doesn't create one even though it says its creating



Thank in advance for your time.

Since it is clear you already can boot (because you said you installed to /S/L/E)... Assuming you're booting to a different device (not an NVMe SSD).

Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

Note: Your use of the _OSI->XOSI patch is invalid (SSDT-XOSI.aml is missing).

 

[brucelee888]

Since it is clear you already can boot (because you said you installed to /S/L/E)... Assuming you're booting to a different device (not an NVMe SSD).

Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

Note: Your use of the _OSI->XOSI patch is invalid (SSDT-XOSI.aml is missing).

Sorry I did not give all info at first.

yes, I'm booting from a regular SSD, and I cannot see the NVMe Samsung pro 960 internal drive. This is a desktop, and that patch I entered last the OSI was just me trying new things to see if I can get it to be seen in disk utility .....

And, yes, I can boot no kernel panic.

So, your saying to use that patch on this desktop I need to create a ssdr-XOSI.aml ? or is that patch not even needed?

 

[RehabMan]

Sorry I did not give all info at first.

yes, I'm booting from a regular SSD, and I cannot see the NVMe Samsung pro 960 internal drive. This is a desktop, and that patch I entered last the OSI was just me trying new things to see if I can get it to be seen in disk utility .....

And, yes, I can boot no kernel panic.

So, your saying to use that patch on this desktop I need to create a ssdr-XOSI.aml ? or is that patch not even needed?

_OSI->XOSI patch only valid with SSDT-XOSI.aml.
Either disable the patch or add SSDT-XOSI.aml to ACPI/patched.

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

Hint: Problem Reporting files not specific to desktop vs. laptop. Please attach the requested files.

 

[brucelee888]

ok

 

[brucelee888]

_OSI->XOSI patch only valid with SSDT-XOSI.aml.
Either disable the patch or add SSDT-XOSI.aml to ACPI/patched.

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

Hint: Problem Reporting files not specific to desktop vs. laptop. Please attach the requested files.

_OSI->XOSI patch only valid with SSDT-XOSI.aml.
Either disable the patch or add SSDT-XOSI.aml to ACPI/patched.

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

Hint: Problem Reporting files not specific to desktop vs. laptop. Please attach the requested files.

ok thanks here you go

 

[RehabMan]

ok thanks here you go

Your SSDT_NVMe-Pcc.aml is wrong.
This:

   Method (_SB.PCI0.BR1B.H000, 4, NotSerialized)

Should be:

   Method (_SB.PCI0.BR1B.H000._DSM, 4, NotSerialized)

 

[brucelee888]

Your SSDT_NVMe-Pcc.aml is wrong.
This:

   Method (_SB.PCI0.BR1B.H000, 4, NotSerialized)

Should be:

   Method (_SB.PCI0.BR1B.H000._DSM, 4, NotSerialized)

Don't know how I can thank you enough. This my first time doing this type of thing.

I appreciate what you do, your effort and your quick response.

Thank you again and yes that worked.

 

[jugglehard]

Yesterday everything was ok. Today i got this error


Only thing i did other than usual was booting inside the Yosemite recover partition, but went back to Sierra and nothing like this was shown. Only today.

 

[RehabMan]

Yesterday everything was ok. Today i got this error
View attachment 266053

Only thing i did other than usual was booting inside the Yosemite recover partition, but went back to Sierra and nothing like this was shown. Only today.

Repair the disk in Disk Utility.
As for the cause, you would need to provide more information on your system configuration.
Most corruption is caused by incorrectly implemented PM (eg. forgetting to disable hibernation), or use of software such as Paragon HFS+ for Windows.

 

[xxcesarioxx]

Hi @RehabMan here is your update

i have remount the EFI hidden parition from windows and extracted it via xcopy to another directory and removed "theme folder" attached below.

for your reference, below is also the screenshot of the ACPI path.

just for your reference,

i am using

Motherboard: Asus Maximus IX Formula
M.2 NVMe SSD 960 EVO 1TB
M.2 Plextor M8Pe 1TB PX-1TBM8PeG
GTX 1080 STRIX ROG 8GB OC
FENVI T919 wireless card

Overview

Problem Reporting

Provide a detailed and concise description of the problem.

If your drive is not recognized by the macOS/OS X installer or you are getting a panic...

Provide image from Windows Device Manager showing the ACPI namespace path of your SSD.

Attach EFI/Clover folder as ZIP (press F4 at main Clover screen before collecting). Please eliminate 'themes' directory. Provide only EFI/Clover, not the entire EFI folder.

UPDATE:

I managed to use diskpart and mount the hackintosh drive's EFI assigning to a letter as a drive.

i copied out the files and here is a screenshot of it, i opened it with mac's MaciASL.

i double checked it with the PATH on windows , its correct but it still can't boot.

@RehabMan

*ACPI NAME"

Error upon booting with above patch that reference with windows device path correctly.

error messages:-