Contribute
Register
Screenshot_20160524-000222

Screenshot_20160524-000222

  • Ian58
  • May 23, 2016
  • 0
  • 0
I

KP 10.11.5 with NVMeGeneric.kext

  • 1
  • Ian58
Hi,
have you found any solution? I'm facing the same issue since yesterday...
Thanks ;)
 
I
@cyrben Hi,
I've been able to boot 10.11.5 installer using the NVMeGeneric kext (placed in EFI/BOOT/CLOVER/kexts/10.11/).
The problem is causes by AppleIntelLpssI2C.kext and AppleIntelLpssI2CController.kext.
To be able to delete them from your installer drive, you must create your installer drive using BaseBinaries method in RehabMan's guide to create an install drive.
But: one problem will occur even after deleting the two kexts I named before (from /System/Librairies/Extensions/AppleIntelLpssI2C.kext and /System/Librairies/Extensions/AppleIntelLpssI2CController.kext).
You'll still have the KP because deleted kexts will still load...
This is because they've been placed in kernel cache, so you need to rebuild it (but on an installer it seems you just can't...).
Knowing that, I installed 10.11.5 on an USB drive, then deleted the two kexts causing this problem, then I rebuilt cache (boot in single user mode (space on Mac OS entry in CLOVER), then exec following command : sudo touch /System/Librairies/Extensions && sudo kextcache -u / (notice the usage of sudo, two times. Notice also the / at the end of the command).
Once you did that, it will have updated the kernel cache in /System/Librairies/Prelinkedkernels/prelinkedkernel. This file is what you need to copy from your USB installation of Mac OS to your installer drive created wirh BaseBinaries method.
Now you'll be able to : boot installer, and install to your NVMe SSD.
Amazing.
But at first reboot, same problem: you'll have the two kexts in /System/Librairies/Extensions/AppleIntelLpssI2C and I2CController...
You'll have to boot in single user mode, then type two command: the first one as follow, and the second one , the same as before to rebuild the kernel cache:
sudo rm -Rf /System/Librairies/Extensions/AppleIntelLpssI2C* (notice use of sudo, and the last char : *)
Then type the command to rebuild cache.

Once you did that, you should be able to boot your install from SSD (using Clover from USB).
What I did next: I used a Gparted USB live (use last gparted live iso, they don't support NVMe since long) to reduce my Mac OS partition about 200Mo, then created there à drive formatted in FAT32 to copy everything from USB Clover partition to this partition.
And now, you can boot from SSD without external drive at all.

Let me know if you're able to reproduce this :)
 
@Ian58 I thought I would be advised of your answer! I'll try tonight and tell you if I achieved to do it :)
Thank you very much for your help! (quite a lot of details here)
 
Okay... After a few days, I can say I failed...
Just to make sure I didn't f**k up :
1) I created the installer using BaseBinaries method
2) I deleted the two kexts from /System/Librairy/Extensions on the install_osx HFS+ partition of my installer
3) I installed Clover on the same USB drive and downloaded the appropriate config.pllist from RehabMan's GitHub
4) I added FakeSMC and VoodooPS2Controller kexts to the EFI partition (not NVMeGeneric)
5) I installed OS X 10.11.5 on a 32 GB USB drive
6) I booted on this USB drive and deleted the two AppleIntellLpssI2C kexts from /System/Library/Extensions
7) I rebooted on Single User Mode, used the second command line to mount drive, and used the command to rebuild kernel
8) I copied the file from /System/Library/Prelinkedkernels (OS X drive) into /System/Library/Prelinkedkernels (installation drive)
9) I added NVMeGeneric.kext into the EFI partition of the intallation drive
Do you see something I did wrong ?
Thank you very much for your help!
 
I
What you did seems ok.
Do you still have the same kernel panic related to nvmegeneric kext?

I can send you my config.plist or a full copy of my efi partition if you want, because I think it could be related to your config.plist.
 
@Ian58 If you think it can solve my problem, I'm okay yes ;)
I think it is the same KP yes. I haven't looked in details but NVMeGeneric is the last kext in queue when the panic occurs.
 
I had the exact same KP (NVMeGeneric.kext) and fixed it by disabling Thunderbolt support in Bios. By default, it was hidden in my BIOS so I had to mod it.
 

Album information

Album owner
Ian58
Date created
Item count
1
View count
7,535
Comment count
9
Rating
0.00 star(s) 0 ratings

Share this album

Back
Top