Contribute
Register

[SOLVED] Samsung EVO with NVMe results in 'Prohibition screen' after the multibeast...

Status
Not open for further replies.
jnm2 said:
1) With that IORegiteryExplorer I already could see that ACPI path as shown on page 7 in your guide, and will probably be able todo it again. But, will the result of that path be reprensative as my installation is not complete and 100% ?
Click to expand...

I would need to see ioreg to make any comment.

2) Ubuntu install was easy, so it would be nice to get that ACPI path from out that (I don't know how to do that) ?
Click to expand...

There may be a way, but I'm not aware of it.
 
RehabMan said:
I would need to see ioreg to make any comment.
Click to expand...
I think you need this, then ? (based on the picture-info shown at page 7 of your guide).

IOReg ACPI.jpg
 
Last edited:
RehabMan said:
The path is _SB.PCI0.RP09.PXSX
Click to expand...
What does that mean ?
Is it good, is it bad or what ?

[EDIT]Ooops I see the picture above is different from the one I have now ??? I don't know how it changed but I'll post it again :[/EDIT]
IOReg ACPI 2.jpeg
 
Last edited:
jnm2 said:
Yeah, helpfull comment.
Click to expand...

If you follow the guide, you can make NVMe work with the class-code spoof.
You have everything you need, as I have already provided the ACPI path for you...

If you give up before trying, no chance of success.
 
RehabMan said:
If you follow the guide, you can make NVMe work with the class-code spoof.
You have everything you need, as I have already provided the ACPI path for you...

If you give up before trying, no chance of success.
Click to expand...
I don't give up, I might take a pause after all those installations.
My NVMe works already, but I just don't have certainty about where or what causes (the other) problems still existing.
Now I'm also unsure about my NVMe installation process. If you would have said that NVMe installation process in the video is wrong (and explained a bit why), that would have helped me more then only promoting your way of doing it.
I hope you'll understand that opinion.

Stiil I'll go on.
 
jnm2 said:
I don't give up, I might take a pause after all those installations.
My NVMe works already, but I just don't have certainty about where or what causes (the other) problems still existing.
Now I'm also unsure about my NVMe installation process. If you would have said that NVMe installation process in the video is wrong (and explained a bit why), that would have helped me more then only promoting your way of doing it.
I hope you'll understand that opinion.

Stiil I'll go on.
Click to expand...

Your ioreg shows you're using HackrNVMeFamily without the class-code spoof (I have no need to review any video). That is fine (assuming you got valid md5 sums from the patch_nvme.sh script), but complicates system updates due to the need to remove IONVMeFamily.kext. Hence the suggestion to use the class-code spoof.
 
Last edited:
Well ok. Now that 'my' path is known _SB.PCI0.RP09.PXSX I can scip the windows install, which makes it less mess to restart doing it the class-code spoof way. One of these ... I'll post the result.

Thanks.
 
Last edited:
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top