hellspawn Posted September 6, 2008 Share Posted September 6, 2008 Hi! I have a fresh iATKOS v4.0i installation. I installed some programs I needed and suddenly, between two reboots, I can only boot when I use the -f switch. I remember that everything worked fine before I installed Little Snitch (which requires a restart to complete its installation) - but that might be a coincidence. LS however runs fine, so I don't think that there was a problem with the installation. When I don't use the -f switch, my system almost instantly reboots. Using -v doesn't help, since everything is too fast to read. It takes less than a second from hitting return at the boot loader prompt before the reboot occurs. How can I nail the error down? Is there a way to prevent the reboot so that I could at least read the output? Link to comment Share on other sites More sharing options...
Donw35 Posted September 7, 2008 Share Posted September 7, 2008 I added the -f switch to my boot so it happens everytime, my OSX is stable with it but don't know why it only boots with it. Link to comment Share on other sites More sharing options...
hellspawn Posted September 7, 2008 Author Share Posted September 7, 2008 Ok, that would be my last resort. I'd still prefer a "clean" solution :-/ Link to comment Share on other sites More sharing options...
hellspawn Posted September 7, 2008 Author Share Posted September 7, 2008 Update: I used my cell phone's camera to capture a video of the boot process. The output is as follows: Loading Darwin/x96Loading kernel mach_kernel Loading HFS+ file [mach_kernel] from $SOME_ADDRESS Loading HFS+ file [mach_kernel] from $SOME_ADDRESS LoadDrivers: Loading from [/system/Library/Extensions.mkext] ... Loading HFS+ file [...Extenstions.mkext]... Loading HFS+ file [...Extenstions.mkext]... EFI enhanced bootloader build: ToH Using SMBIOS table found at $SOME_ADDRESS Using ACPI revision 0 found at $SOME_ADDRESS Starting Darwin/x86 -> BAM! Reboot... Does this ring a bell for anybody? Link to comment Share on other sites More sharing options...
hellspawn Posted September 8, 2008 Author Share Posted September 8, 2008 Could it be a problem that I'm using netkas' pc_efi v8 to boot? Maybe it conflicts with "EFI enhanced bootloader build: ToH"? Link to comment Share on other sites More sharing options...
jclaude_nantes Posted September 8, 2008 Share Posted September 8, 2008 Bonjour, I had the same problem. kernel caches was corrupted (Extensions.mkext and caches directory). You have to delete then. And force the system to rebuilt the kext cache. Some terminal command. sudo -s [enter password] rm -rf /System/Library/Extensions/caches rm -rf /System/Library/Extensions.mkext reboot The system built the cache at statup. Works for me!! Sorry for my poor English Link to comment Share on other sites More sharing options...
hellspawn Posted September 8, 2008 Author Share Posted September 8, 2008 Thanks for your help! Sadly, it didn't solve my problem. I already deleted Extensions.mkext several times, but not the Caches directory though. I now also deleted the Caches directory but it didn't change anything. Link to comment Share on other sites More sharing options...
Recommended Posts