Jump to content

Patch for using NVMe under macOS Sierra is ready.


  • Please log in to reply
1170 replies to this topic

#1161
RehabMan

RehabMan

    InsanelyMacaholic

  • Developers
  • 3,060 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

Can't find this one on GitHub...

 

Note commit log:

https://github.com/R...755a5b821ed9c89

 

And you could have read the README.



#1162
axel9546

axel9546

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 224 posts

Cant boot with hacknvme family kext in l e and without clover patches Attached File  Archivio.zip   1.92MB   9 downloads



#1163
Tobinejumi

Tobinejumi

    InsanelyMac Protégé

  • Members
  • Pip
  • 18 posts

Note commit log:

https://github.com/R...755a5b821ed9c89

 

And you could have read the README.

Is that patch for update, called 2017-002 security update for 11.6 at appstore?



#1164
RehabMan

RehabMan

    InsanelyMacaholic

  • Developers
  • 3,060 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

Is that patch for update, called 2017-002 security update for 11.6 at appstore?

 

No idea.  After I applied the update, it never showed in my update history... (App Store bug, I guess).

That's why I named this plist after the build#.

 

Correct use of patch_nvme.sh is with only './patch_nvme.sh --spoof'.  No need to specify the plist as it will be determined automatically (as is written in my guide).


Cant boot with hacknvme family kext in l e and without clover patches attachicon.gifArchivio.zip

 

You need to verify NVMe ACPI path: _SB.PCI0.RP09.PXSX

And you have _DSM->XDSM patch disabled.

No HackrNVMeFamily in EFI/Clover/kexts.  Make sure you generate it with --spoof.



#1165
UltraLaser

UltraLaser

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 377 posts

Hi,

 

is this compatible : MZ-V6E250BW 960 EVO ?

 

:angel:



#1166
Tobinejumi

Tobinejumi

    InsanelyMac Protégé

  • Members
  • Pip
  • 18 posts

No idea.  After I applied the update, it never showed in my update history... (App Store bug, I guess).

That's why I named this plist after the build#.

 

Correct use of patch_nvme.sh is with only './patch_nvme.sh --spoof'.  No need to specify the plist as it will be determined automatically (as is written in my guide).

 

Thank you!

Yes, they call it 2017-002 security update. Autodetection with --spoof works fine, great improvement. 



#1167
Israel Fernandes

Israel Fernandes

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Guarujá - SP - Brazil

Can someone help me ? My NVME always stays as external. I must be wrong about something.

 

 

The Board Is X99 Designare EX

Attached Files



#1168
RehabMan

RehabMan

    InsanelyMacaholic

  • Developers
  • 3,060 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

Can someone help me ? My NVME always stays as external. I must be wrong about something.

 

 

The Board Is X99 Designare EX

 

If you implement the class-code spoof with HackrNVMeFamily, you won't have that issue...



#1169
Israel Fernandes

Israel Fernandes

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Guarujá - SP - Brazil

I tried, but there was a kernel panic. I tried the coexist patch, but I must be missing the path of the pci. My pci path on windows is:

 
PCIROOT (0) #PCI (0200) #PCI (0000) #PCI (0800) # PCI (0000)
ACPI (_SB _) # ACPI (PCI0) #ACPI (BR2A) #ACPI (H000) #PCI (0800) #PCI (0000)


#1170
RehabMan

RehabMan

    InsanelyMacaholic

  • Developers
  • 3,060 posts
  • Gender:Male
  • Location:Bellingham, WA
  • Interests:skiing, software, classic cars

 

I tried, but there was a kernel panic. I tried the coexist patch, but I must be missing the path of the pci. My pci path on windows is:

 
PCIROOT (0) #PCI (0200) #PCI (0000) #PCI (0800) # PCI (0000)
ACPI (_SB _) # ACPI (PCI0) #ACPI (BR2A) #ACPI (H000) #PCI (0800) #PCI (0000)

 

 

You are doing very strange things in your SSDT for the NVMe.



#1171
Israel Fernandes

Israel Fernandes

    InsanelyMac Protégé

  • Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:Guarujá - SP - Brazil

You are doing very strange things in your SSDT for the NVMe.

Please Help-me to fix this.

 

Obs:. Sorry for my bad english.







2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy