Moderators Jake Lo Posted December 17, 2014 Moderators Share Posted December 17, 2014 Try booting with this: /System/Library/Kernels/kernel -v -f if that works, you might want to check your o.c.b.p to make sure it's pointing to the same directory. By the way are you dual booting? Link to comment Share on other sites More sharing options...
TMNTony Posted December 17, 2014 Author Share Posted December 17, 2014 I am dual booting, but I tried taking out the other drive and nothing changed. Still saying that it cant find /System/Library/Kernels/kernel. I booted my old Mavericks installation and confirmed that that particular file is indeed where it's supposed to be. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted December 17, 2014 Moderators Share Posted December 17, 2014 add /system/library/kernels/kernel to o.c.b.p of the yosemite drive Link to comment Share on other sites More sharing options...
Administrators Hervé Posted December 17, 2014 Administrators Share Posted December 17, 2014 Watch the casing, it's critical -> /System/Library/Kernels/kernel. If you're booting with Chameleon, you may also copy the kernel file to the root of your HDD as "mach_kernel" and try to boot with option: /mach_kernel. Link to comment Share on other sites More sharing options...
TMNTony Posted December 17, 2014 Author Share Posted December 17, 2014 I was having some problems with the drive. It was showing as a raid drive in chameleon, and after reverting it to the old format, it would boot as normal. My issue now it that I get an error to the effect of unsupported chip found at which point the screen goes black Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted December 17, 2014 Administrators Share Posted December 17, 2014 it can be a fakeSMC kext issue. remove the lpc.kext plugin and rebuild your caches. if not replace fakesmc kext and it's plugins. Link to comment Share on other sites More sharing options...
TMNTony Posted December 18, 2014 Author Share Posted December 18, 2014 I tried replacing the fakesmc kext but no dice Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted December 18, 2014 Administrators Share Posted December 18, 2014 you sure you do not have more then one fakesmc installed? one in extra one in sle? Link to comment Share on other sites More sharing options...
TMNTony Posted December 19, 2014 Author Share Posted December 19, 2014 I got everything up and running now. My one question now is that I still need to use the -f bootflag for it to start up now that the installation has completely finished. is that supposed to be the case? Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted December 19, 2014 Administrators Share Posted December 19, 2014 that usually happens when you have a kernel that is not named mach_kernel and or not in the location that it usually resides in. Link to comment Share on other sites More sharing options...
Recommended Posts