Burbruee Posted April 20, 2008 Share Posted April 20, 2008 I was just going to update QuickTime and iTunes really, but forgot to uncheck the "Security Update" checkbox which has now broken my install. Now when I try to boot Leopard it will endlessly reboot itself. Is there _any_ way to fix this or do I have to reinstall the system? Also, how can I access the files on the partition so I can save important documents and stuff, is there any software available for windows xp which lets me read the partition? The real pain-in-the-ass if I need to do a clean install will be all hacked kexts that I have installed, and I have no idea which ones I've installed to get sound working etc or where I got them from. >_> Thanks. Link to comment https://www.insanelymac.com/forum/topic/100527-oops/ Share on other sites More sharing options...
MrRoper Posted April 21, 2008 Share Posted April 21, 2008 I was just going to update QuickTime and iTunes really, but forgot to uncheck the "Security Update" checkbox which has now broken my install. Now when I try to boot Leopard it will endlessly reboot itself. Is there _any_ way to fix this or do I have to reinstall the system? Also, how can I access the files on the partition so I can save important documents and stuff, is there any software available for windows xp which lets me read the partition? The real pain-in-the-ass if I need to do a clean install will be all hacked kexts that I have installed, and I have no idea which ones I've installed to get sound working etc or where I got them from. >_> Thanks. odd. i think i remember 2 security updates since leopard 10.5.1 and neither did anything to kill my install. you should try booting with -v if you can even get to the F8 prompt and video it if you have to, try and see what the last lines of text are before it reboots on you. As far as accessing your important files, install macdrive on your windows installation, and reach into the macintosh partition/drive and grab what you need. hope that helps one thing's for sure, once u manage to get things going again, i bet you never forget again to back up your kexts/ files/links etc etc Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-718462 Share on other sites More sharing options...
dajavax Posted April 21, 2008 Share Posted April 21, 2008 yeah use macdrive... it works great... i've tried it Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-718631 Share on other sites More sharing options...
Burbruee Posted April 22, 2008 Author Share Posted April 22, 2008 Right, I did try with -v it's just that, it didn't give me much information. In fact, I t only prints out about four lines before it reboots. I made a video: http://www.sendspace.com/file/u5xxst [1.7MB/QT] Reboots right after the line "Starting Darwin/x86...", I had to put a slow-mo effect on the video for you to be able to read it. And well, I did make backups of all the kexts I downloaded from here, however I had to download a lot of them before everything worked perfectly. Problem is that I don't know which ones made sound input work etc.. But I'll probably sort it out. Thanks for the tip about macdrive, I haden't heard of it so I'll give it a try. Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-719556 Share on other sites More sharing options...
Gujal Posted April 23, 2008 Share Posted April 23, 2008 I think you got the dreaded "Time machine and Airport update" which installs a new System.kext and 9.2.2 kernel. Look at this topic to get patched System.kext and 9.2.2 kernel and replace them on your machine which will fix the problem Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-720555 Share on other sites More sharing options...
MrRoper Posted April 23, 2008 Share Posted April 23, 2008 I think you got the dreaded "Time machine and Airport update" which installs a new System.kext and 9.2.2 kernel.Look at this topic to get patched System.kext and 9.2.2 kernel and replace them on your machine which will fix the problem i installed time machine update directly from apple, no issues to speak of after, but of course it can be different for different hardware. . . but if that is the case it should be easy enough to replace the system.kext and kernelfrom -s if you can boot to it, or from the terminal when booting from dvd . if you backed up your kernel using the renaming method in your root folder then you can boot with mach_kernel_backup at the f8 prompt or whatever you named the backup kernel to Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-721443 Share on other sites More sharing options...
Gujal Posted April 23, 2008 Share Posted April 23, 2008 @MrRoper, you have a Intel Core2 CPU so you had no issues with update, same with me, no issues. Unfortunately Burbruee is running AMD CPU so cant run vanilla kernel and hence the reason for the problem Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-721557 Share on other sites More sharing options...
PlayingKarrde Posted April 23, 2008 Share Posted April 23, 2008 Isn't it down to the chipset of the motherboard rather than the CPU? Because I have a C2D as well but i can't run vanilla kernel (same reboot problem) so I have to run the patched one. Basically you need an intel chipset on your mobo to use vanilla kernel. Burbruee try booting with old_kernel and see if that helps, because the constant reboot is down to your kernel becoming vanillarised. Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-721586 Share on other sites More sharing options...
JustinTD Posted April 24, 2008 Share Posted April 24, 2008 Its both the chipset and the CPU. you need to be running an "Apple Compatible" hardware set for Vanilla. IE, Intel CPU and RECOGNIZED Intel chipset. I am using a Q6600 C2Q and a P35 chipset mobo with Vanilla now. Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-721757 Share on other sites More sharing options...
Burbruee Posted April 25, 2008 Author Share Posted April 25, 2008 Thanks for all the help, yeah that's probably the update that broke it. But well, I just reinstalled the system instead, needed a quick & easy fix. I'll keep this in mind if this were to happen again in the future though, thanks. Link to comment https://www.insanelymac.com/forum/topic/100527-oops/#findComment-724386 Share on other sites More sharing options...
Recommended Posts