Jump to content
Mork vom Ork

Patch for using NVMe under macOS Sierra is ready.

1,362 posts in this topic

Recommended Posts

Pike R. Alpha's patch for using NVMe under SIERRA (and right now only under Sierra) is ready. Give it a go here.

Also works for NVMe as a bootdrive. Running SIERRA right now on my SAMSUNG 950PRO NVMe 256GB drive.

 

EDIT I: maybe someone of the "Pro"s here could provide with a much more simplier method to patch the bin, cause right now,

i just made 17 KernelAndKextPatches for CLOVER config.plist just to make the patch work. The BIN-file has to be modified in

17 (!) different Offsets, so i made 17 different NVMEFamily.kext patch entries.

 

Pike provided me with its own patched IONVMeFamily BIN, but i prefered to patch the original BIN via CLOVER, so i won't get lost the

kextsignature. If some of you will find a better way to patch the original BIN w/o getting the kextsignature lost, drop me

a line.

 

Source: NVMeFamily.kext bin patch data

Share this post


Link to post
Share on other sites
Advertisement

There is one thing i forgot to mention:

 

if u are going to use SIERRA installer to install SIERRA on your NVMe drive, you have to boot into the installer, open terminal and load the IONVMeFamily.kext manually. After the kext got loaded, you could open Disc Utility and than you should be able to see and format your NVMe device. I havent tried it this way - i installed SIERRA on AHCI device and after installation i Carbon Copy cloned this Installation to my NVMe device, than restarted - et voila: successfull boot from my SAMSUNG 950 Pro NVMe drive..

Share this post


Link to post
Share on other sites

The big question is does it prevent the data corruption the genericnvme.kext causes in (rare?) cases?

Before on 10.11.4 (did work correct on .2 and .3) I got data corruption with the genericnvme kext and since no source was released or maintained I decided to keep windows on my hack for now.

The weird thing is the SSD partition became unaccessible so I never got to look at the logs anymore.

Still I like it a lot and can't wait for the golden build so I can test around (yes I got a dev account but no spare NVME SSD).

Share this post


Link to post
Share on other sites

There is one thing i forgot to mention:

 

if u are going to use SIERRA installer to install SIERRA on your NVMe drive, you have to boot into the installer, open terminal and load the IONVMeFamily.kext manually. After the kext got loaded, you could open Disc Utility and than you should be able to see and format your NVMe device. I havent tried it this way - i installed SIERRA on AHCI device and after installation i Carbon Copy cloned this Installation to my NVMe device, than restarted - et voila: successfull boot from my SAMSUNG 950 Pro NVMe drive..

I've tried several times to load the kext using terminal on the installer setup (using the patched kext in SLE) but sadly, the kext isn't being loaded.

 

Would you mind to write a step by step guide? 
I mean, by explaining both methods (patched kext and clover kext to patch), thank you in advance.

Share this post


Link to post
Share on other sites

Put the IONVMeFamily.kext from SIERRA to your CLOVER  EFI-CLOVER-Kexts-Other Kexts folder. Be sure to have the KernelAndKextPatches in your config.plist and boot into SIERRA installer.

From the selection screen select DISC UTILITY. Now you should be able to see your NVMe-device, format it and select it as installdrive for SIERRA. Works for me - just tested.

Share this post


Link to post
Share on other sites
Would you mind to write a step by step guide? thank you in advance.

Well ok, let's go:

 

1) grab your copy of macOS 10.12 SIERRA. download it to a disc of your choice. If u grabed it on a legal way, it should be named like "Install 10.12 Developer Preview"

 

2) boot into any previous OS X (10.10.x or 10.11.x) and put the downloaded file to your APPLICATIONS folder.

 

3) have a 16GB USB-stick handy and connected to any USBport

 

4) open terminal window and type in the following to make a bootable SIERRA usb-stick:

sudo /Applications/Install\ 10.12\ Developer\ Preview.app/Contents/Resources/createinstallmedia --volume /Volumes/your_USBstick_here --applicationpath /Applications/Install\ 10.12\ Developer\ Preview.app

just to make sure: "your_USBstick_here" should be replaced with the name of YOUR USBstick. Please don't use "your_USBstick_here", cause it won't work.

 

5) wait to get the bootable SIERRA USB-stick ready

 

6) get a copy of any CLOVER installer (4 myself i prefere this one. Thx to chris1111 for his great work)

 

7) install CLOVER to the just created SIERRA USBstick (within the installer choose the desired options you need for your setup)

 

8) copy your YOSEMITE or EL CAPITAN config.plist to your CLOVER installation you just made.

 

9) open the just copied config.plist with any texteditor (how about TEXTEDIT?) application and go to <key>KernelAndKextPatches</key> section

 

10) paste the following code somewhere between the two <array> </array> commands of <key>KextsToPatch</key> section:

<dict>
    <key>Comment</key>
    <string>IONVMeFamily IONameMatch</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>InfoPlistPatch</key>
    <true/>
    <key>Find</key>
    <data>PHN0cmluZz5wY2kxNDRkLGE4MDQ8L3N0cmluZz4=</data>
    <key>Replace</key>
    <data>PHN0cmluZz5wY2kxNDRkLGE4MDI8L3N0cmluZz4=</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#1</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>ibPoAgAAweAMBQAQAACJgw==</data>
    <key>Replace</key>
    <data>ibPoAgAAweAJBQAQAACJgw==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#2</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>D7aMiIIAAACD+QwPhTIBAA==</data>
    <key>Replace</key>
    <data>D7aMiIIAAACD+QkPhTIBAA==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#3</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>AMeDpAAAAAAQAABIi0gISA==</data>
    <key>Replace</key>
    <data>AMeDpAAAAAACAABIi0gISA==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#4</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>SYnGTYX2dGFBwecMSWP/vg==</data>
    <key>Replace</key>
    <data>SYnGTYX2dGFBwecJSWP/vg==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#5</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>hv8PAABIwegMD7cPgeH/Dw==</data>
    <key>Replace</key>
    <data>hv8PAABIwegJD7cPgeH/Dw==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#6_7</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>icGB4f8PAABIAdFIgfn/DwAAdzs=</data>
    <key>Replace</key>
    <data>icGB4f8BAABIAdFIgfn/AQAAdzs=</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#8</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>SYHF/w8AAEnB7QxJiwQkSA==</data>
    <key>Replace</key>
    <data>SYHF/w8AAEnB7QlJiwQkSA==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#9_10</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>BgIAAEyNuAAQAABMiflIgeEA8P//SYmGGgEAAEmJjiIBAABBvAAQAABJKfQ=</data>
    <key>Replace</key>
    <data>BgIAAEyNuAACAABMiflIgeEA8P//SYmGGgEAAEmJjiIBAABBvAACAABJKfQ=</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#11</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>AABJiY4iAQAAugAQAABIKQ==</data>
    <key>Replace</key>
    <data>AABJiY4iAQAAugACAABIKQ==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#12</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>yAAAAEkp17gAEAAATYskJA==</data>
    <key>Replace</key>
    <data>yAAAAEkp17gAAgAATYskJA==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#13</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>4b+AQBUGTYnWugAQAABFMQ==</data>
    <key>Replace</key>
    <data>4b+AQBUGTYnWugACAABFMQ==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#14</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>iWTY+EmBxAAQAABJgccA8A==</data>
    <key>Replace</key>
    <data>iWTY+EmBxAACAABJgccA8A==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#15</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>Bf8PAABIwegMZvfB/w8PlQ==</data>
    <key>Replace</key>
    <data>Bf8PAABIwegJZvfB/w8PlQ==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#16</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>weIIQQ+2wcHgDEQJ0EQJwA==</data>
    <key>Replace</key>
    <data>weIIQQ+2wcHgCUQJ0EQJwA==</data>
</dict>
<dict>
    <key>Comment</key>
    <string>IONVMeFamily Pike R. Alpha Patch#17</string>
    <key>Disabled</key>
    <false/>
    <key>Name</key>
    <string>IONVMeFamily</string>
    <key>Find</key>
    <data>RYTJD5XAD7bAweAMRAnYRA==</data>
    <key>Replace</key>
    <data>RYTJD5XAD7bAweAJRAnYRA==</data>
</dict>

11) save your config.plist file

 

12) grab the IONVMeFamily.kext from SIERRA (attached to this post) and paste it to your CLOVER EFI partition in the following place: EFI -> CLOVER -> kexts -> Other

      ! this step is neccesary, cause SIERRA Installer doesn't contain this kext in its own startup and you won't be able to select NVMe-device, cause it wasn't detected during startup !

 

13) install your NVMe device to your hardware. Either on an M.2 PCIe card for PCIe slot or directly into an M.2 slot on your motherboard. Have both tested here myself, both configs work perfectly 4 me

 

14) reboot your system, enter your BIOS and select SIERRA USBstick as your bootdevice

 

15) when CLOVER gets booted, select your SIERRA USBstick, press ENTER and wait for SIERRA booting into macOS 10.12 Installer.

 

16) when arrived into the installer, choose Use Disc Utility to get your NVMe-Device formatted. Format the device with desired partition or just delete partitions data

 

17) Quit DISC UTILITY to get back to SIERRA installer

 

18) select INSTALL SIERRA, choose your just formated NVMe-device and start Installation

 

19) when finished with the install process, copy your CLOVER EFI folder from SIERRA USBstick to EFI partition of your just installed SIERRA NVMe-device.

      After doing so, you could delete IONVMeFamily.kext from EFI -> CLOVER -> kexts -> Other from your just installed SIERRA EFI partition, cause kext is now installed in S/L/E

 

20) if you have any questions: ask your local dealer or post the question here

 

Regards... Mork vom Ork

 

PS: don't forget to drop Pike R. Alpha a line for his great work on this patch.

IONVMeFamily.kext.zip

Share this post


Link to post
Share on other sites

Hello friend how are you?

 

I did everything that you say, but here does not work 

Please post your config.plist. Did you copy IONVMeFamily.kext to USB EFI partition CLOVER kexts/Other folder?

Which of the three M.2 slots are you using? Remember: each M.2 slot shares its connection with normal SATA-port (read about it in Extreme7+ manual).

Share this post


Link to post
Share on other sites

Got it working. Thnx for the guide and Pike for your work.

Disc shows as external. But that might be related to other issues.

Would be great to have this working on current Os versions.

 

t2m

post-1317959-0-80300100-1467145644_thumb.png

post-1317959-0-99444400-1467145649_thumb.png

Share this post


Link to post
Share on other sites

Please post your config.plist. Did you copy IONVMeFamily.kext to USB EFI partition CLOVER kexts/Other folder?

Which of the three M.2 slots are you using? Remember: each M.2 slot shares its connection with normal SATA-port (read about it in Extreme7+ manual).

of course friend have followed with great precision, I am using the slot m2 of asrock Z97 Extreme6 ... I think this does not matter

Share this post


Link to post
Share on other sites

Oooops, he did it again!

 

People get ready for the Pike R. Alpha IONVMeFamily.kext patch for EL CAPITAN 10.11.6 beta4: (CLOVER patch for EL CAPITAN 10.11.5 will be found here)

 

once again you have to patch your CLOVER config.plist file - this time with the following entries:

        <key>KextsToPatch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>NVMe SSD IONameMatch</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>InfoPlistPatch</key>
                <true/>
                <key>Find</key>
                <data>PHN0cmluZz5wY2kxNDRkLGE4MDQ8L3N0cmluZz4=</data>
                <key>Replace</key>
                <data>PHN0cmluZz5wY2kxNDRkLGE4MDI8L3N0cmluZz4=</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#01</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>hfZ0YUHB5wxJY/++IAAAAA==</data>
                <key>Replace</key>
                <data>hfZ0YUHB5wlJY/++IAAAAA==</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#02&03</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>AAAAg/kMdVhBx4akAAAAABAAAEg=</data>
                <key>Replace</key>
                <data>AAAAg/kJdVhBx4akAAAAAAIAAEg=</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#04</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>SI2G/w8AAEjB6AwPtw+B4Q==</data>
                <key>Replace</key>
                <data>SI2G/w8AAEjB6AkPtw+B4Q==</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#05&06</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>SIHm/w8AAEgB1kiB/v8PAAB3PEg=</data>
                <key>Replace</key>
                <data>SIHm/wEAAEgB1kiB/v8BAAB3PEg=</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#07&08&09</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>DwAAScHuDEmLTQBIictIgeP/DwAAD5XAD7bARAHwg/gCD4W4AAAATI2hABAAAEyJ4EglAPD//0mJjyIBAABJiYcqAQAAQb4AEAAASSneSI0=</data>
                <key>Replace</key>
                <data>DwAAScHuCUmLTQBIictIgeP/DwAAD5XAD7bARAHwg/gCD4W4AAAATI2hAAIAAEyJ4EglAPD//0mJjyIBAABJiYcqAQAAQb4AAgAASSneSI0=</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#10</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>hyoBAAC6ABAAAEgp</data>
                <key>Replace</key>
                <data>hyoBAAC6AAIAAEgp</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#11</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>AABJKdS4ABAAAE2L</data>
                <key>Replace</key>
                <data>AABJKdS4AAIAAE2L</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#12&13</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>TYnXugAQAABFMclIid7oAAAAAE2J+kyLfdBJi4dgAQAATIls2PhJgcUAEAAASYHE</data>
                <key>Replace</key>
                <data>TYnXugACAABFMclIid7oAAAAAE2J+kyLfdBJi4dgAQAATIls2PhJgcUAAgAASYHE</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#14</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>DwAASMHpDGap/w8P</data>
                <key>Replace</key>
                <data>DwAASMHpCWap/w8P</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#15&16&17&18&19</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>QYP4B3dtRIpVEEQPt5+wAAAAQcHjEA+2h7YAAACD4AjB4ApECdiDyAKJhwoBAACJtw4BAABIiZcyAQAAioe2AAAAJAIPtsDB4B0JyImHOgEAAEHB4AhBD7bBRAnAicGByQAQAABFhNIPRMiJjz4BAA==</data>
                <key>Replace</key>
                <data>QYP4B3dtRA+2VRBED7efsAAAAEHB4xAPtoe2AAAAg+AIweAKRAnYg8gCiYcKAQAAibcOAQAASImXMgEAAIqHtgAAACQCD7bAweAdCciJhzoBAABBweAIQQ+2wcHgCZCQkJCQkJBECcBECdCJhz4BAA==</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#20&21&22&23</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>AEE5TMnr5HVOB+mmeHIKS8+CkpFCxsGSjVQ55RGF7HPyMLRAEenCdlw9ABkXy+TC79wzkECAIfgaReSm28x6CQ==</data>
                <key>Replace</key>
                <data>AMJYAvbk8/5BhFjxfdTbqbQ3/1ltxsGSjVQ55RGF7HPyMLRAEenCdlwmCld+AkentTJyBbhSN24VAkP5CMx6CQ==</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IONVMeFamily Pike R. Alpha Patch#24 - 51</string>
                <key>Disabled</key>
                <false/>
                <key>Name</key>
                <string>IONVMeFamily</string>
                <key>Find</key>
                <data>BIIBAEnKT7RtSMZmBUXJYiljxJJFkczm2pfZ5IPg1G+cQK7aL5iJtDi/MS7xRfQh4/Cs1uRhuguFiFsVa7a/sXvhr5/UrH6i3DeDuzcrF2X81s+YC/0IEX26bgq/WJnS69bVcqu0JAIr0Gzx4RQ8M4k4WpsrPKhSQlqe2bJnkpbmYV/DpcBTrXJTrq9GtTe4565lM8Nn60z90dTC7lJr3M5AWT4ZL1N0yj/fdzcr1F2oLSkjs3Fs95hGsJlRJ8k6R1i41gNm8YmAjVaUqpRqPI4dCtIuu60VT9WOeyRNla7HlfgurT0vWeAVbGI1rlNGXJ4fPe+wHrxjs1bG0ZOusIF8d5IAAAAA</data>
                <key>Replace</key>
                <data>BIIBAFjhf2OXh9C5pDLqAaMZOl8QQ8KDZNVIa9drFKiwvp8Zb1rrYOwRVgvIxJyL5wFhpAKV9CIY9usXBrgiYGahXiaBmWcaDnMAlLu2THdDzI4h3XN/02Dk9uL8RupUJJjhq4dJcZncs8Kd07co2Nml5nvrGUXV9jHJ2EgBMIm2OxjRuuApt0AWauSZ/dgXT1rlc4YcyYXCBRPCUqpm7C7Pcz202/io08M99B4aZvAcUzUv5e54pjCrZrtMFrz2Oh8hQZbFM0vXVKBXLEGAN9hmHe3o51sapwyyHikUZ827nlT+y4zHnWAMc0v7r6R4uQ1+8iaMwaf3gBjIlY8K2tFHkjMAAAAA</data>
            </dict>
        </array>

Please remember, that you have to paste the whole block to your CLOVER KernelAndKextPatches section as it is! Keep the order of those entries, otherwise it may not work properly. You can insert all your other patches BEFORE or AFTER all the entries above between the two <array></array> commands.

 

You do NOT have to copy IONVMeFamily.kext to your CLOVER - EFI -> CLOVER -> kexts -> Other folder this time, cause i think EL CAPITAN installer loads this kext also when booted from EL CAPITAN installer.

 

If everything goes well, your NVMe device should be selectable as Bootdrive this time. Tested it here and it works great. NVMEGeneric.kext here no longer needed.

And this is my speed result from a booted NVMe EL CAPITAN SSD M.2 device:

EL_CAPITAN_NVMe.jpg

systeminformation_nvme.jpg

Shown Speeds are the results from an SAMSUNG SM951 NVMe 256GB SSD connected directly to M.2 slot of ASRock Z170 Extreme7+ motherboard. Please ignore, that it is running as a MacBook - thats cause of my ASUS Thunderbolt EX II card works best with SMBIOS settings for MacBookPro10,1. Screenshots are seriously taken from running EL CAPITAN 10.11.6 beta 4.

 

And as 4 the SIERRA IONVMeFamily.kext patch all credits for this patch belongs to Pike R. Alpha. I've just created the CLOVER Kext patch entries. So once again feel free to drop him a line.

Regards...

 

Mork vom Ork

 

! ATTENTION !: I may had an error (different length for seach and replace to each other) in the above patch, which i corrected right now.

                          Please erase the old patch block completely and paste the whole new block into your config.plist.

                          (The entry for patch#15 and #16&17&18&19 have been combined now to patch#15&16&17&18&19 in just one line - so your NVMe patch should have 13 items instead of 14 and now all

                          SEARCH and REPLACE entries have the same length to each other)

 

EDIT 2: NOW everything works correct. I just forget to ENABLE Patch#15 again by setting <key>Disabled</key><true/> to <key>Disabled</key><false/>. Now the patch is FULLY applied:

Bildschirmfoto_2016_07_01_um_00_08_56.pn

 

 

PS: please keep in mind, that with an update to IONVMeFamily.kext, this patch may get obsolete. But i haven't recognised an update between 10.11.0 and 10.11..6 so far to this kext. But: you have been warned  ;-)

Share this post


Link to post
Share on other sites

 
The first method didn't worked for you.
 
I mean what (modifications in the patch) you did to show your M.2 SSD.  :P

Share this post


Link to post
Share on other sites

 

We have a new version of Piker's patch, thanks to RehabMan.

 

Sorry, but that's not correct. The code within the spoiler is my second attempt to correct my mistake - but it still gets ignored by CLOVER while booting. So please: DON'T USE. - as i described above under ATTENTION 2

Share this post


Link to post
Share on other sites

Patch has been corrected: i just forgot to ENABLE patch#15,16,17,18,19 by setting the following keys from

<key>Disabled</key><true/>

 

to

 

<key>Disabled</key><false/>.

 

Thats why patch#15 wasn't applied by CLOVER during boot. It has been corrected in Post#16 , so now the patch could be used fully working (as you can see here):

 

Bildschirmfoto_2016_07_01_um_00_08_56.pn

Thanx to ALL, who post bug report on Pike's blog - so i was able to fix the CLOVER patch immediatly.

Share this post


Link to post
Share on other sites

Yes, patch posted in main post#16 is still the same you can find on Pike's blog. It is the corrected (and hopefully final) one. If you applied it already to config.plist, booted with it and take a look into CLOVER bootlog, you should see all patches applied like in the screenshot above.

Share this post


Link to post
Share on other sites

 

 
The first method didn't worked for you.
 
I mean what (modifications in the patch) you did to show your M.2 SSD.  :P

 

:P  :P  My mistake of typing on the keyboard  :P  :P

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.

×