TH3L4UGH1NGM4N, on Oct 18 2011, 02:16 AM, said:
@ cili0 I honestly always preferred using the S/L/E as opposed to E/E since Leopard days and with the release of 10.7 I was happy to notice that I didn't need to use the E/E anymore.
I don't even use a bootloader on my OS drives but rather keep the bootloaders on flash drives for the sake of plucking the drives into my MBP if I feel the urge to. Not saying that I dislike the separation that OS X had for some while, but I always wanted all my kexts to be localized in one area alone let alone two.
Just my 2 cents..
It's strange that you want to keep an extra component such as the EFI bootloader away from the the hard disk, but at the same time you place non-vanilla kext inside /S/L/E.
I appreciate the conceptual separation between what is shipped by apple (placed in /S/L/E) and what we add in order to let the system work on a generic pc (EFI bootloader + /E/E). Again, my 2 cents
Really there's no way to restore the /E/E folder? unfortunately creating the kernel cache by means of Extensions.mkext makes the system unbootable.
STLVNUB, on Oct 17 2011, 06:29 PM, said:
If you really want to keep /E/E and prefer not to touch /S/L/E then
you can use the rc.local trick, works great here, been doing it since Lion came out.
NOTE the name KextStore, you can use any name EXCEPT Extensions.
Use the UseKernelCache flag Yes in/Extra/ com.chameleon.Boot.plist.
Best way to implement this is to boot -s.
At prompt type:
mount -uw /
echo "kextload /Extra/KextStore/*" > /private/etc/rc.local
Make sure permissions are correct
ls -la /etc/rc.local
Should look like this
-rwxr-xr-x 1 root wheel 28 23 Jul 04:08 /etc/rc.local
Need to refresh the caches so then type
rm -rf System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
reboot and use -f for added measure
There may be some kexts that need to be placed into /S/L/E
This is what I have in mine
ACPIMonitor.kext IntelCPUMonitor.kext LegacyBluetooth.kext
FakeSMC.kext LegacyAGPM.kext SuperIOFamily .kext
Its all down to personal choice.
Hi STLVNUB, thanks your your suggestion. The problem with your solution is that you can't place the essence of the extra kexts, fakesmc.kext, in /E/KextStore, can you? Also i would prefer the bootloader to load the extra kexts, it would be more polished.
mindlessmissy, on Oct 17 2011, 11:29 PM, said:
Hey cili0, you might want to try this method proposed by hotKoffy here:
generate MKext in Lion 10.7.2
Seems to work pretty well in that the root device error no longer occurs ...
However, in my case, it refuses to load IONetworking family hence I am not able to load Lnx2Mac's RTL81xx during boot which I need for my Ethernet ...
EDIT: I have to add that the IONetworking kext loads FINE after booting ... Only problem is it does NOT seem to be included in the generated Extensions.mkext file (which turns out to be quite small in size compared to creating it using one of those terminal commands) ...
I can load Lnx2Mac's RTL81xx kext after login BUT IF you are someone who does NOT even use that kext, I think hotKoffy's method will be great for separating the System and Extra kext files ...
I'll try this method, but unfortunetly i do use lnx2mac kext.