Jump to content



Member Since 25 Jun 2012
Online Last Active 13 minutes ago

Posts I've Made

In Topic: Patch for using NVMe under macOS Sierra is ready.

29 November 2016 - 01:53 PM

seems contention only happened when more then one.. never happened when it was the single NVMe, which makes sense.. never a problem with one kid waiting for their icecream..

Actually, typical result is panic with only one NVMe should both HackrNVMeFamily and IONVMeFamily load.
But the actual panic is random/system dependent, which means it is a timing/memory trash issue, which means there could be cases that the timing is not bad, or the memory trashed is somewhere not important.

In Topic: Patch for using NVMe under macOS Sierra is ready.

29 November 2016 - 05:59 AM

@ Racer 
hello ,
it did step by step what you have written to the post 569, created the SSDT and edited info.plist in kext hack, but unfortunately it does not work, I also eliminated the kext vanilla, but I always know kp ..not where I'm wrong, very honest, do you want to see my SSDT and ioreg? looks very patiently, thanks

You will need to provide complete details.

Update: Samsung 960 PRO works! I checked all my settings today and it seems I never deleted/renamed vanilla IONVMeFamily.kext. I renamed and it booted with the 960's installed and working. All three M.2 are bound to HackrNVMe. AJA benchmark was at 2100/3100 MB/s..
So It seems that its the same as the 950's! Dumb mistake to make,

Good to know... (details matter!)

but the single 950 didn't have any problems with the vanilla kext.. maybe Rehabman has an idea why?

Panic is due to possible hardware contention/timing... and it appears to be a random memory trashing (perhaps writing to memory through an uninitialized pointer), so the panic varies, and even no panic is possible (and in fact, reported here).

In Topic: Patch for using NVMe under macOS Sierra is ready.

25 November 2016 - 03:48 PM

ok..here it is..
I managed to boot into a virgin 10.12.1 installation pre-nvme kext install. so I have all 3 installed M2_1(960PRO-512GB), M2_2(950PRO-256GB) and M2_3 (960PRO-1TB). In Sytem Info, it even shows 3X Apple SSD controller started but nothing else. IOREG too.. 
Clover install is from the original boot disk with hackrnvme installed...
if it is possible to use vanilla, can you walk me through it to get the 960's going? would seem easier to use vanilla kext over long term..the 950 I can sell..

It is going to involve looking at the debug traces from IONVMeFamily to determine what kind of patches will be required.
From what you show, it seems the 960 not working with unmodified IONVMeFamily.
And what you said earlier, not working with Pike's patches either.

In Topic: Patch for using NVMe under macOS Sierra is ready.

25 November 2016 - 06:57 AM

yes.. unfortunately, from Tom's Hardware:
"The 960 EVO delivers more random performance than the 950 Pro, Samsung's only shipping retail consumer SSD. Peak performance for the 960 EVO comes in the largest capacity size, and users get up to 380,000 read IOPS and 360,000 write IOPS (4KB block sizes). That makes the 960 EVO second only to the 960 Pro in performance for (announced) consumer SSDs."
..maybe I sell the 950 and get another 960 to make everything simpler to maintain (I originally wanted that but the 960's were backordered several times..)

If it is true (960 == 4k block size), it would mean it could work with vanilla IONVMeFamily.kext.

In Topic: Patch for using NVMe under macOS Sierra is ready.

24 November 2016 - 10:42 PM

here's what I have from today: 2 kinds of KP's https://www.dropbox....G_9827.jpg?dl=0
and here's the 960 Specs: no mention of blocksize but it does have a new controller(internal) https://www.dropbox....tionen.jpg?dl=0
can't seem to upload images.. so I'll just link them for now..

Need all data requested. Please provide in single post.

It is possible the 960 does not use 512 byte block size. In which case, you would need to inject a different class code (or match on PCI ID) for each, with appropriately patched (or un-patched) kext for each 950/960 with respective block sizes.
Vanilla IONVMeFamily.kext assumes 4096 byte block size.
Patched HackrNMVmeFamily.kext assumes 512 (Pike's patches).
A system with both installed, would need two patched kexts (all class names would need to be renamed, such that they are independent) with separate matching criteria, so the correct driver is selected.
Probably best to test each independently first, so you know what is required for each.
© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy