Jump to content
Mork vom Ork

Patch for using NVMe under macOS Sierra is ready.

1,380 posts in this topic

Recommended Posts

Advertisement

I am attempting to use an OWC Aura Pro X SSD NVMe (Silicon Motion pci126f,2260) on a a PCIe adapter in a MacPro1,1 running MacOS 10.11.6 (15G22010). I built the kext in patch_nvme adding the devid to the script and using the spoof; installed it disabling SIP and modifying the attributes (correctly I think): sudo chmod -R 755 and sudo chown -R root:wheel.

Unfortunately System Information/Hardware/PCI shows that the NVM Express Controller device is present but that the driver is not installed.

Can someone walk me through the troubleshooting to determine why the kext will not load? Thanks.

Edited by vicsandr

Share this post


Link to post
Share on other sites

I am running Sierra on a Mac Pro 5,1 with an NVMe boot volume.  I have been using this patch for both the 2018-005 and 2018-006 security updates.  Based on the previous comment from InsanelyMac Legend I thought I'd just try running the 2019-001 security update.  As expected, my Mac Pro 5,1 crashed on startup.  I then booted from a different volume, and deleted the newly created "IONVMeFamily.kext".  I rebooted from my NVMe volume, and it worked OK.  So it seems that it is OK to just run the 2019-001 security update, and then boot from a different volume and delete the IONVMeFamily.kext file.  Sierra 10.12.6 with the 2019-001 security update seems to work OK with the HackrNVMeFamily-10_12_6_sec2018-006.kext file once the IONVMeFamily.kext is deleted.

Share this post


Link to post
Share on other sites

Hi,


I updated my original post about the Plextor/LiteOn/Hynix patch with a new Find/Replace pattern, as the underlying code seems to be changing in the upcoming 10.14.4 (judging by the betas).

The new pattern is backwards compatible with older OSX versions, so I recommend everyone using this patch to change it with the new variant, in order not to lose booting ability when the 10.14.4 update arrives.

Share this post


Link to post
Share on other sites

Good day.

 

Can anyone please tell how to use patch_nvme.sh + config_patches.plist with 10.14.3 and PLEXTOR M9Pe? 

What parameters should be used in order to launch patch_nvme.sh and patch IONVMeFamily.kext?

 

Thank you in advance
 

Share this post


Link to post
Share on other sites

How can i made Plextor M9PeY 256Gb work with 10.14.3 OS X in my Mac Pro5.1? Can some one help please

Share this post


Link to post
Share on other sites

Thank you very much :)

I used this patch for my XPS 15 9570 with Hynix PC401 1TB  NVMe SSD, which was not recognized by Mojave 10.4.4.

Applying the patch solved the issue.

 

BUT Very important note: the SATA mode in BIOS must be set to AHCI. Dell as a standard sets SATA to RAID, which causes the NVMe drives to be not recognized by MacOS. I did not have that info and I was wondering why my hdd is not recognized even with patching... But Then I tried the setting SATA  from RAID to AHCI and that, with above patching applied, solved the problem - Mojave recognizes my Hynix SSD :) I Now I just need to transfer the OS from my USB drive to internal SSD :)

 

I just added the code below  into the config.plist under the part "<key>Patches</key>"

That's all. But it is for HACkintosh users, I do not know how MAC users should do patching.

 

On 6/8/2018 at 12:58 AM, Pene said:

 


      <dict>
        <key>Comment</key>
        <string>IONVMeFamily: Ignore FLBAS bit:4 being set - for Plextor/LiteOn/Hynix</string>
        <key>Disabled</key>
        <false/>
        <key>Name</key>
        <string>IONVMeFamily</string>
        <key>Find</key>
        <data>SBr2wRAPhQ==</data>
        <key>Replace</key>
        <data>SBr2wQAPhQ==</data>
      </dict>

 

 
Edited by gombi

Share this post


Link to post
Share on other sites

Have a question I followed this...sort of to create a patch and help my OS (EL Capitan) see my NVM e drive, I got this message in Terminal ... 

Leons-MacBook-Pro:patch-nvme.git Drex-Guru$ ./patch_nvme.sh 

Determined patch automatically from vanilla IONVMeFamily: 10_11_6_15G22010

Creating patched HackrNVMeFamily-10_11_6_15G22010.kext from /System/Library/Extensions/IONVMeFamily.kext

Vanilla MD5 matches expected MD5 entry (9b1349964b4d0d757c35189ca9f6ea9a)

Patched MD5 matches expected MD5 entry (d2d5c10907bf0d159d58e496b48d245e)

Leons-MacBook-Pro:patch-nvme.git Drex-Guru$ 

so ....well, where is the created patch to pop into Kext Utility?  please excuse my ignorance I'm spinning here my drive died the other day and I have a major hand in next week that my lap top simply will not edit. I am by no means a programmer, and this might as well be in Martian.

Kind regards,

Leon.

Share this post


Link to post
Share on other sites

Hi everyone, I have a problem with installing macOs.
I have a Matebook X Pro, 7GB of RAM and 512 of SSD.
My problem occurs when I start the macOs installer and I never read the SSD.
My SSD is a LITEON CA3-8D512.
I tried to edit the kext files but nothing.
Can someone help me?

Share this post


Link to post
Share on other sites

i'm getting same kind of issue using hynix301 on one of my alienware 15r4. here is the kernel panic:

 

<<<<<<<<<<<<<>>>>>>>>>>>>>

*** Panic Report ***
panic(cpu 2 caller 0xffffff7f97390e2b): nvme: " NVMe: Command timed-out and request found in the completion queue \n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.71.1/IONVMeController.cpp:5184
Backtrace (CPU 2), Frame : Return Address
0xffffffa3d2f7bb60 : 0xffffff8014a6d1c6 
0xffffffa3d2f7bbb0 : 0xffffff8014b95a74 
0xffffffa3d2f7bbf0 : 0xffffff8014b87d44 
0xffffffa3d2f7bc60 : 0xffffff8014a1f1e0 
0xffffffa3d2f7bc80 : 0xffffff8014a6cc3c 
0xffffffa3d2f7bdb0 : 0xffffff8014a6c9fc 
0xffffffa3d2f7be10 : 0xffffff7f97390e2b 
0xffffffa3d2f7be30 : 0xffffff801509eb7c 
0xffffffa3d2f7bea0 : 0xffffff801509eaa6 
0xffffffa3d2f7bed0 : 0xffffff8014aa6624 
0xffffffa3d2f7bf40 : 0xffffff8014aa6185 
0xffffffa3d2f7bfa0 : 0xffffff8014a1e557 
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[1170C79B-9E09-3CD3-970B-C419EBF9037F]@0xffffff7f9737c000->0xffffff7f973bbfff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[9AC0F895-00AA-35E6-A561-4FF35C9281B8]@0xffffff7f95d37000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[70EA0775-DFBE-3132-9001-F5A9C20D0CF3]@0xffffff7f95294000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[F35A52E2-CF80-3BA9-92B5-25EFE216094F]@0xffffff7f97371000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[F27A8A2A-6662-3608-83BD-415037509E01]@0xffffff7f960de000
            dependency: com.apple.iokit.IOReportFamily(31)[D2F2FBDF-4EE4-38BA-99F5-B699F886F413]@0xffffff7f97330000

BSD process name corresponding to current thread: kernel_task
Boot args: -lilubeta kext-dev-mode=1 -wegbeta -alcbeta 

Mac OS version:
17G6030

Kernel version:
Darwin Kernel Version 17.7.0: Wed Feb 27 00:43:23 PST 2019; root:xnu-4570.71.35~1/RELEASE_X86_64
Kernel UUID: E385ABD9-67BA-3CA7-9436-8F52D9C5634C
Kernel slide:     0x0000000014800000
Kernel text base: 0xffffff8014a00000
__HIB  text base: 0xffffff8014900000
System model name: MacBookPro14,3 (Mac-551B86E5744E2388)

System uptime in nanoseconds: 96990501825
last loaded kext at 10228475039: com.nvidia.CUDA    1.1.0 (addr 0xffffff7f95f18000, size 12288)
loaded kexts:
com.nvidia.CUDA    1.1.0
com.nvidia.web.GeForceWeb    10.3.3
com.nvidia.web.NVDAGP100HalWeb    10.3.3
com.nvidia.web.NVDAResmanWeb    10.3.3
org.tw.CodecCommander    2.7.1
com.nvidia.NVDAStartupWeb    10.3.3
de.brumbaer.UnSolid    1
com.realtek.driver.RtWlanU    1830.20.b14
com.insanelymac.AtherosE2200Ethernet    2.2.2
org.emlydinesh.driver.ApplePS2SmartTouchPad    4.6.8
org.hwsensors.driver.LPCSensors    1800
org.emlydinesh.driver.ApplePS2Keyboard    4.6.8
org.hwsensors.driver.GPUSensors    1800
org.hwsensors.driver.ACPISensors    1800
org.darkvoid.driver.IOElectrify    1.0.0
org.emlydinesh.driver.ApplePS2Controller    4.6.8
org.rehabman.driver.AppleSmartBatteryManager    1.90.1
org.hwsensors.driver.SMMSensors    1800
org.rehabman.driver.VoodooTSCSync    1.5.0
org.hwsensors.driver.CPUSensors    1800
org.netkas.driver.FakeSMC    1800
as.vit9696.WhateverGreen    1.2.8
xyz.racermaster.NoTouchID    1.0.1
as.vit9696.Lilu    1.3.5
com.rehabman.driver.USBInjectAll    0.7.1
com.apple.filesystems.ntfs    3.13
com.apple.filesystems.autofs    3.0
com.apple.driver.AudioAUUC    1.70
com.apple.driver.AppleTyMCEDriver    1.0.3d2
com.apple.driver.AppleHDAHardwareConfigDriver    282.10
com.apple.driver.AppleHDA    282.10
com.apple.driver.AppleGraphicsDevicePolicy    3.20.15
com.apple.AGDCPluginDisplayMetrics    3.20.0
com.apple.driver.pmtelemetry    1
com.apple.iokit.IOUserEthernet    1.0.1
com.apple.iokit.IOBluetoothSerialManager    6.0.7f12
com.apple.driver.AppleUpstreamUserClient    3.6.5
com.apple.driver.AppleMCCSControl    1.5.5
com.apple.driver.AppleIntelKBLGraphics    10.3.6
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleHV    1
com.apple.nvidia.NVDAStartup    10.3.2
com.apple.driver.AppleIntelCFLGraphicsFramebuffer    10.3.6
com.apple.driver.AppleOSXWatchdog    1
com.apple.driver.ACPI_SMC_PlatformPlugin    1.0.0
com.apple.driver.AppleIntelSlowAdaptiveClocking    4.0.0
com.apple.driver.AppleFIVRDriver    4.1.0
com.apple.driver.AppleFileSystemDriver    3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0
com.apple.AppleSystemPolicy    1.0
com.apple.BootCache    40
com.apple.filesystems.hfs.kext    407.50.6
com.apple.filesystems.apfs    748.51.0
com.apple.driver.AppleAHCIPort    329.50.2
com.apple.driver.AppleACPIButtons    6.1
com.apple.driver.AppleACPIEC    6.1
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleAPIC    1.7
com.apple.nke.applicationfirewall    183
com.apple.security.quarantine    3
com.apple.security.TMSafetyNet    8
com.apple.kext.triggers    1.0
com.apple.iokit.IOBluetoothHostControllerUSBTransport    6.0.7f12
com.apple.iokit.IOBluetoothHostControllerTransport    6.0.7f12
com.apple.driver.DspFuncLib    282.10
com.apple.kext.OSvKernDSPLib    526
com.apple.driver.AppleGraphicsControl    3.20.15
com.apple.iokit.IOSerialFamily    11
com.apple.driver.AppleSMBusController    1.0.18d1
com.apple.iokit.IOBluetoothFamily    6.0.7f12
com.apple.iokit.IOAVBFamily    683.1
com.apple.plugin.IOgPTPPlugin    680.15
com.apple.iokit.IOEthernetAVBController    1.1.0
com.apple.driver.AppleSSE    1.0
com.apple.iokit.IONDRVSupport    519.21
com.apple.AppleGPUWrangler    3.20.0
com.apple.driver.AppleHDAController    282.10
com.apple.iokit.IOHDAFamily    282.10
com.apple.iokit.IOAudioFamily    206.5
com.apple.vecLib.kext    1.2.0
com.apple.driver.AppleSMBusPCI    1.0.14d1
com.apple.AppleGraphicsDeviceControl    3.20.15
com.apple.iokit.IOAcceleratorFamily2    378.26
com.apple.iokit.IOGraphicsFamily    519.21
com.apple.iokit.IOSurface    211.15
com.apple.driver.IOPlatformPluginLegacy    1.0.0
com.apple.driver.IOPlatformPluginFamily    6.0.0d8
com.apple.iokit.IOSlowAdaptiveClockingFamily    1.0.0
com.apple.driver.usb.IOUSBHostHIDDevice    1.2
com.apple.driver.usb.cdc    5.0.0
com.apple.driver.usb.networking    5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice    1.2
com.apple.filesystems.hfs.encodings.kext    1
com.apple.driver.usb.AppleUSBHostPacketFilter    1.0
com.apple.iokit.IOUSBFamily    900.4.1
com.apple.driver.AppleXsanScheme    3
com.apple.iokit.IOAHCIBlockStorage    301.40.2
com.apple.iokit.IONVMeFamily    2.1.0
com.apple.iokit.IOAHCIFamily    288
com.apple.driver.usb.AppleUSBXHCIPCI    1.2
com.apple.driver.usb.AppleUSBXHCI    1.2
com.apple.driver.AppleEFINVRAM    2.1
com.apple.driver.AppleEFIRuntime    2.1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.security.sandbox    300.0
com.apple.kext.AppleMatch    1.0.0d1
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleEffaceableStorage    1.0
com.apple.driver.AppleKeyStore    2
com.apple.driver.AppleUSBTDM    439.70.3
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.iokit.IOUSBMassStorageDriver    140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice    404.30.3
com.apple.iokit.IOSCSIArchitectureModelFamily    404.30.3
com.apple.driver.AppleCredentialManager    1.0
com.apple.driver.KernelRelayHost    1
com.apple.iokit.IOUSBHostFamily    1.2
com.apple.driver.usb.AppleUSBCommon    1.0
com.apple.driver.AppleBusPowerController    1.0
com.apple.driver.AppleSEPManager    1.0.1
com.apple.driver.IOSlaveProcessor    1
com.apple.driver.DiskImages    480.60.2
com.apple.iokit.IOStorageFamily    2.1
com.apple.iokit.IOReportFamily    31
com.apple.iokit.IOTimeSyncFamily    680.15
com.apple.iokit.IONetworkingFamily    3.4
com.apple.driver.AppleACPIPlatform    6.1
com.apple.driver.AppleSMC    3.1.9
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.Libm    1
com.apple.kec.pthread    1
com.apple.kec.corecrypto    1.0

EOF
Model: MacBookPro14,3, BootROM 185.0.0.0.0, 6 processors, Intel Core i7, 2.21 GHz, 32 GB, SMC 2.45f0
Graphics: NVIDIA GeForce GTX 1070, NVIDIA GeForce GTX 1070, PCIe
Memory Module: BANK 0/DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, HMA82GS6CJR8N-VK
Memory Module: BANK 1/DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, HMA82GS6CJR8N-VK
Bluetooth: Version 6.0.7f12, 3 services, 26 devices, 1 incoming serial ports
PCI Card: NVIDIA GeForce GTX 1070, Display Controller, Slot-1
Serial ATA Device: HGST HTS721010A9E630, 1 TB
USB Device: USB 3.1 Bus
USB Device: Bluetooth HCI
USB Device: Integrated_Webcam_HD
USB Device: AW-ELC
USB Device: Razer Atheris - Mobile Gaming Mouse
USB Device: 802.11n NIC
Thunderbolt Bus: 
 

<<<<<<<<<<<<<,EOM>>>>>>>>>>>>>

 

I have been trying to patch stuff from like 4 months now and nothing works. Whenever i try to copy files from ssd over to the mac ssd it just crashes. I have got 2 ssds, one is samsung and the other one is hynix.

 

I have also attached my debug files just in case. Any help will be very much appreciated.

debug_28235.zip

Edited by Razz
Attaching debug files.

Share this post


Link to post
Share on other sites

I'm new to this, perhaps someone can point me to some of the existing 55 pages here if it helps with the below, which is basically how to replace internal SSD on a laptop running 10.11?

 

My end goal, is to replace the factory internal SSD in my MBP with a larger after-market NVMe. I imagine this goal is similar to many of you... Therefore I wish to have the new NVMe be basically a disc clone of the original internal SSD before it's disconnected.

 

Preconditions: latest 10.11, using RehabMan's patch process, I have applied patch to my factory SSD, and disabled SIP. I will perform a Time Machine backup of the factory SSD to an external USB drive immediately before disassembly.

 

Here's where I need help, the hard part seems to be, how do I get the replacement drive to be mountable and bootable? I I have kind of broken down 3 possible paths,

 

A ) remove factory SSD and install the new SSD first, then by magic, make it mountable (I assume that booting from the internet recovery, the new SSD will not be mountable), then easily recover from the Time Machine backup drive

B ) put the new SSD in an enclosure, connect it and perform a disk clone (possible with Disk Utility?) or transfer the Time Machine backup to it (not sure if that's possible), then install new SSD, at this point, since it contains the mod kext, it should mount

C) upgrade to 10.13 then no tricks for the kext are needed (putting this for reference, would prefer not to do this)

 

Is A possible at all? If it's tricky, then I guess the cost of an enclosure is worth it. Then what enclosure & other parts would I have to get exactly?

Edited by Sharkle

Share this post


Link to post
Share on other sites

Hi All,

 

Im totally lost. There's so much info and I can't figure out what is related to a real Mac vs Hackintosh.

I have a Mac Pro cheesegrater 4.1 flashed to a 5.1 and I've installed an NVMe (Corsair Mp510) onto a PCIe adapter card.

Initially I installed High Sierra 10.13. Then had to go through the steps to install a metal capable gpu (temporarily borrowed), to upgrade the Mac bootrom to 144. At this point I realised certain applications wouldn't run! So went to re-install Sierra 10.12 only to find it wouldn't see the NVMe! 

 

So basically, Im fine with Sierra, but have the latest updates installed on 10.12.6 (Security update 2019-003). Could someone give me a step by step for getting the NVMe to be recognised by Sierra? Really hoping that would be the last step to booting from the NVMe too!

 

Thanks,

Tom.

Share this post


Link to post
Share on other sites
20 minutes ago, Tommer said:

Im totally lost. There's so much info and I can't figure out what is related to a real Mac vs Hackintosh.

I have a Mac Pro cheesegrater 4.1 flashed to a 5.1 and I've installed an NVMe (Corsair Mp510) onto a PCIe adapter card.

Initially I installed High Sierra 10.13. Then had to go through the steps to install a metal capable gpu (temporarily borrowed), to upgrade the Mac bootrom to 144. At this point I realised certain applications wouldn't run! So went to re-install Sierra 10.12 only to find it wouldn't see the NVMe! 

 

So basically, Im fine with Sierra, but have the latest updates installed on 10.12.6 (Security update 2019-003). Could someone give me a step by step for getting the NVMe to be recognised by Sierra? Really hoping that would be the last step to booting from the NVMe too!

 

Upgrading Mac bootroom means you tried Mojave? You say applications wouldn't run, do you mean they won't run on Mojave? If so, then why downgrade to 10.12? Did you try the applications in 10.13? Did you try the NVMe drive in 10.13?

 

If you really need to try 10.12, then follow the 10.12 steps at https://github.com/RehabMan/patch-nvme

1) create HackrNVMeFamily.kext using the appropriate script

2) move IONVMeFamily.kext from /System/Library/Extensions to a backup location

Don't use the --spoof option because there's no easy way to change the class code of a device on a real Mac. Don't use NVMe devices that require the original IONVMeFamily.kext.

 

There doesn't seem to be a script for 10.12.6 (Security update 2019-003) but the patches from Security update 2019-001 might work (they are the same as the patches for security update 2018-006.

 

Share this post


Link to post
Share on other sites
On 7/12/2019 at 1:23 PM, joevt said:

Upgrading Mac bootroom means you tried Mojave? You say applications wouldn't run, do you mean they won't run on Mojave? If so, then why downgrade to 10.12? Did you try the applications in 10.13? Did you try the NVMe drive in 10.13?

 

If you really need to try 10.12, then follow the 10.12 steps at https://github.com/RehabMan/patch-nvme

1) create HackrNVMeFamily.kext using the appropriate script

2) move IONVMeFamily.kext from /System/Library/Extensions to a backup location

Don't use the --spoof option because there's no easy way to change the class code of a device on a real Mac. Don't use NVMe devices that require the original IONVMeFamily.kext.

 

There doesn't seem to be a script for 10.12.6 (Security update 2019-003) but the patches from Security update 2019-001 might work (they are the same as the patches for security update 2018-006.

 

Thanks for the reply Joevt!
I did plan to install Mojave, but then found that the apps I need to use dont even run on 10.13, so no hope with 10.14 I assume!

I mainly did the bootrom upgrade to get the NVMe recognised as a boot device.

Ill have another go with the RehabMan patches, but got a little lost along the way with it before. When I tried to create the HackrNVMeFamily.kext, I got a 'ERROR: Vanilla MD5 does not match and --override not specified.'

 

Share this post


Link to post
Share on other sites
7 hours ago, Tommer said:

Ill have another go with the RehabMan patches, but got a little lost along the way with it before. When I tried to create the HackrNVMeFamily.kext, I got a 'ERROR: Vanilla MD5 does not match and --override not specified.'

MD5 won't match because you're running update 003 and the patch is only update 001 which has a different MD5. So you should try the --override option.

Share this post


Link to post
Share on other sites
11 hours ago, joevt said:

MD5 won't match because you're running update 003 and the patch is only update 001 which has a different MD5. So you should try the --override option.

Could you advise me on what the --override options are?

Im trying this, but the error now always says '--override not specified. No kext generated.'

Share this post


Link to post
Share on other sites
7 hours ago, Tommer said:

Could you advise me on what the --override options are?

Im trying this, but the error now always says '--override not specified. No kext generated.'

Actually... Ive made some progress today! I've managed to get the new kext generated (from a new system install of 10.12.6 2019-003 & using the --override option) and have installed the new kext, set it's permissions etc and removed the IONVMeFamily.kext somewhere else! ... but still no NVMe!! Im on the cusp of giving up!

Here's what I did:

cd ~/Downloads/patch-nvme-master
./patch_nvme.sh --override 10_12_6_sec2019-001

Was that correct? It gave me the 'HackrNVMeFamily-10_12_6_sec2019-001.kext' that I have used!

Thanks for your help!

Share this post


Link to post
Share on other sites
10 hours ago, Tommer said:

Actually... Ive made some progress today! I've managed to get the new kext generated (from a new system install of 10.12.6 2019-003 & using the --override option) and have installed the new kext, set it's permissions etc and removed the IONVMeFamily.kext somewhere else! ... but still no NVMe!! Im on the cusp of giving up!

Here's what I did:


cd ~/Downloads/patch-nvme-master

./patch_nvme.sh --override 10_12_6_sec2019-001

Was that correct? It gave me the 'HackrNVMeFamily-10_12_6_sec2019-001.kext' that I have used!

 Thanks for your help!

Did you rebuild the kext cache? Using Kext Utility.app does this for you.

 

Compare info.plist of IONVMeFamily.kext with HackrNVMeFamily-10_12_6_sec2019-001.kext

 

Check if an NVMe driver was loaded.

kextstat | grep NVMe

 

Find the NVMe device in the IORegistry. Compare the match properties in the info.plist with the properties of your NVMe device.

ioreg -flw0 > ioreg.txt

 

Check Console.app for errors?

 

Maybe try verbose options with kextutil to diagnose the problem. First, if HackrNVMeFamily-10_12_6_sec2019-001.kext exists in kextstat, then unload it with kextunload. Then load it again with kextutil. Check the logs in Console.app for messages that occurred at the time you tried to load. 

 

You can get information for commands by using the man command, like this

man kextutil

, or right click the name of a command in Terminal.app and selecting "Open man Page".

 

Share this post


Link to post
Share on other sites
On 7/12/2019 at 7:46 PM, Tommer said:

So basically, Im fine with Sierra, but have the latest updates installed on 10.12.6 (Security update 2019-003). Could someone give me a step by step for getting the NVMe to be recognised by Sierra? Really hoping that would be the last step to booting from the NVMe too!

 

Thanks,

Tom.

 

NVMe_patches_10_12_6_sec2019-003.zip

Share this post


Link to post
Share on other sites

Thanks so much for your help @joevt and @ellaosx!

I obvs hadn't installed the kext correctly (tried doing it manually and refreshing the cache in terminal, but I must have gone wrong). Anyway, tried using Easy Kext to install the 'HackrNVMeFamily-10_12_6_sec2019-001.kext' i generated from the 2019-001 patches (with --override set) and bingo, the NVMe drive popped up straight away!

So all good now it seems! Thanks again!

Share this post


Link to post
Share on other sites
On 7/16/2019 at 9:48 AM, ellaosx said:

He

Hello! I am trying to do it with the NVMe_patches_10_12_6_sec2019-005 version but it is very recent and I cannot find the patch for this version.
Can someone tell me how I can do to get the 10_12_6_sec2019-005.plist

I'm sorry if it's something simple, but I'm new to this hackintosh world and I'm a little lost.
Thanks greetings.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×