TECH_ATTACK Posted January 22, 2017 Share Posted January 22, 2017 Hi, first of all, i read and tried all Guides for this topic. Unfortunately i found only patch data for 10.11.5 and above. My Installstick owns 10.11.4. so i guess thats the reason why patching did not work. I want to use may Intel NVMe SSD. So i changed 144D,a804 to 8086,0953. But i dont know why, my SSD is not shown in Diskutility in the installer so i cant install El Capitan. In Sierra all was ok, but in many reasons, El Capitan is better for me. Can someone tell me how to get recognize my NVMe SSD that i can install 10.11.4 on it? Thanks in advance Greets Link to comment Share on other sites More sharing options...
RehabMan Posted January 22, 2017 Share Posted January 22, 2017 Hi, first of all, i read and tried all Guides for this topic. Unfortunately i found only patch data for 10.11.5 and above. My Installstick owns 10.11.4. so i guess thats the reason why patching did not work. I want to use may Intel NVMe SSD. So i changed 144D,a804 to 8086,0953. But i dont know why, my SSD is not shown in Diskutility in the installer so i cant install El Capitan. In Sierra all was ok, but in many reasons, El Capitan is better for me. Can someone tell me how to get recognize my NVMe SSD that i can install 10.11.4 on it? Thanks in advance Greets https://github.com/RehabMan/patch-nvme Link to comment Share on other sites More sharing options...
TECH_ATTACK Posted January 22, 2017 Author Share Posted January 22, 2017 I know your site. But this patches starting with 10.11.5 i have 10.11.4. So i guess patches will not work (i already test, failed because of MD5 check failure). Link to comment Share on other sites More sharing options...
RehabMan Posted January 22, 2017 Share Posted January 22, 2017 I know your site. But this patches starting with 10.11.5 i have 10.11.4. So i guess patches will not work (i already test, failed because of MD5 check failure). Current version of El Capitan is 10.11.6. I don't know why you would use something older. Link to comment Share on other sites More sharing options...
TECH_ATTACK Posted January 24, 2017 Author Share Posted January 24, 2017 I could now install 10.11.6 with generic NVMe. (could use generic nvme in 10.11.4 to download 10.11.6 and create an USB stick). Then i did use your script (with arg 10_11_6). MD5 was ok and your script creates an Hacked....kext. I did install the kext in /S/L/E and deleted the generic NVME.kext from my EFi/Clover Folder. Then i did a reboot again. But did not work. Could not boot because NVMe Drive was not found. What was wrong? Link to comment Share on other sites More sharing options...
RehabMan Posted January 24, 2017 Share Posted January 24, 2017 I could now install 10.11.6 with generic NVMe. (could use generic nvme in 10.11.4 to download 10.11.6 and create an USB stick). Then i did use your script (with arg 10_11_6). MD5 was ok and your script creates an Hacked....kext. I did install the kext in /S/L/E and deleted the generic NVME.kext from my EFi/Clover Folder. Then i did a reboot again. But did not work. Could not boot because NVMe Drive was not found. What was wrong? Did you implement the class-code spoof properly? Guide is linked from the patch-nvme README. Link to comment Share on other sites More sharing options...
TECH_ATTACK Posted January 24, 2017 Author Share Posted January 24, 2017 My english is not the best. But as far as i understood it is in the Sierra section, i use El Capitan. So i didnt spoof anything. I do not have Windows/Linux on this System, is there a possibility to find the acpi path without them (only OS X)? Must say, thats really complex and difficult. In Sierra i just had to put some Code to "Kextstopatch" but in el capitan it seems very very difficult and complex. I never thought that it is so hard to get my ssd working in El Capitan. (With my Dell 9550 i just copied 1 Kext to Efi Folder and all went fine) Link to comment Share on other sites More sharing options...
RehabMan Posted January 24, 2017 Share Posted January 24, 2017 My english is not the best. But as far as i understood it is in the Sierra section, i use El Capitan. So i didnt spoof anything. The guide is not specific to Sierra (it is clear you didn't read it). I do not have Windows/Linux on this System, is there a possibility to find the acpi path without them (only OS X)? Your question is answered in a link at the guide and from the README (in fact, to a post in this thread). Hint: you can use ioreg. Must say, thats really complex and difficult. It is not difficult. If you have reasonable hackintosh skills, should require about 10 minutes. Link to comment Share on other sites More sharing options...
TECH_ATTACK Posted January 24, 2017 Author Share Posted January 24, 2017 I will try it. But i just have a look again, this spoofing etc. is in the section "10.12 UPDATE" so i thought it is for Sierra (10.12) ACPI Path seems to be broken... IOExplorer Shows me: _SB/PCI0@0/BR1A@10000/H000@0 now installed Windows 10 (for temp) its _SB.PCI0.BR1A.H000 Is this path correct to use? (many "@" and "0") Link to comment Share on other sites More sharing options...
RehabMan Posted January 24, 2017 Share Posted January 24, 2017 I will try it. But i just have a look again, this spoofing etc. is in the section "10.12 UPDATE" so i thought it is for Sierra (10.12) ACPI Path seems to be broken... IOExplorer Shows me: _SB/PCI0@0/BR1A@10000/H000@0 Not sure why you consider that broken. Corresponds to ACPI path _SB.PCI0.BR1A.H000 now installed Windows 10 (for temp) its _SB.PCI0.BR1A.H000 Is this path correct to use? (many "@" and "0") As expected, same as above derived from ioreg. Link to comment Share on other sites More sharing options...
TECH_ATTACK Posted January 27, 2017 Author Share Posted January 27, 2017 I got it finally (with Sierra) I insert your patch data in config.plist. All is working fine.... but 2 "Hints" are just not really working: - Drives are shown as external (not so important) - Speed is slow compared to Windows (in OS X I got read/write with about 980 MB/s, in windows I got with same drive about 2500 MB/s read and 1000 MB/s write. Is there a reason why so much slower than in Windows)? Thank you a lot. Your site and your informations are really good. Link to comment Share on other sites More sharing options...
RehabMan Posted January 27, 2017 Share Posted January 27, 2017 I got it finally (with Sierra) I insert your patch data in config.plist. All is working fine.... but 2 "Hints" are just not really working: - Drives are shown as external (not so important) - Speed is slow compared to Windows (in OS X I got read/write with about 980 MB/s, in windows I got with same drive about 2500 MB/s read and 1000 MB/s write. Is there a reason why so much slower than in Windows)? Thank you a lot. Your site and your informations are really good. My technique does not use KextsToPatch content. If you follow my advice for the class-code spoof, it will also take care of external vs. internal. Intel drives tend to be slow with generic drivers (same would be the case if you used generic Microsoft drivers instead of Intel RST). It makes the Intel NVMe product a poor choice for hackintosh. Link to comment Share on other sites More sharing options...
TECH_ATTACK Posted January 27, 2017 Author Share Posted January 27, 2017 Hmm... this spoofing seems to be very complex. In Windows I have almost 2 GB/s even with the generic nvme driver. :/ Link to comment Share on other sites More sharing options...
RehabMan Posted January 27, 2017 Share Posted January 27, 2017 Hmm... this spoofing seems to be very complex. In Windows I have almost 2 GB/s even with the generic nvme driver. :/ NVMe spoof will not affect performance. There is a discussion of performance of Intel NVMe SSDs on tmx. I can't link here due to tmx ban. You can use google. Link to comment Share on other sites More sharing options...
pianoguy Posted January 31, 2017 Share Posted January 31, 2017 NVMe spoof will not affect performance. There is a discussion of performance of Intel NVMe SSDs on tmx. I can't link here due to tmx ban. You can use google. hello, my Patriot hellfire is working, but only does 170mb write speed, even though windows does 750mb write speed. I was going to do the spoof, but then I just saw you said that it doesn affect performance. What other reason could it be that my patriot has a very slow write speed (read speed is normal)? Link to comment Share on other sites More sharing options...
Recommended Posts