leafofsummer Posted December 23, 2008 Share Posted December 23, 2008 voodoo 9.5.0 kernel panic after updating to 10.5.6.....help anyone? Link to comment https://www.insanelymac.com/forum/topic/142568-invalid-kernel-ip-wont-attempt-to-handle-trap-after-updating-to-1056/ Share on other sites More sharing options...
cybercow Posted January 6, 2009 Share Posted January 6, 2009 LOL, i was an smart ass and done an automatic iDeneb 10.5.5 update to 10.5.6 ... after the system rebooted i can`t start the system anymore, now i downloaded vodoo kernel, replaced the original one and i get the same message as you i`m on AMD lol Link to comment https://www.insanelymac.com/forum/topic/142568-invalid-kernel-ip-wont-attempt-to-handle-trap-after-updating-to-1056/#findComment-1029692 Share on other sites More sharing options...
richrard Posted January 26, 2009 Share Posted January 26, 2009 i had the same problem, on my computer that i just had to redo. it worked on my girlfriends, and hers is almost the same build as mine, so i thought about what was different, and the only difference was that i had put the beta 2c on there first, since its an older installation. so i installed it, it boot, then the latest release worked for me. i guess the only real difference was the cpuid.kext that was not included in this latest release. perhaps some of us need this? either way im happy with it best kernel ever Link to comment https://www.insanelymac.com/forum/topic/142568-invalid-kernel-ip-wont-attempt-to-handle-trap-after-updating-to-1056/#findComment-1056281 Share on other sites More sharing options...
boba899 Posted February 11, 2009 Share Posted February 11, 2009 Sorry to bump, but I'm having this exact issue and I'm not sure as to a solution. It sounds like using CPUID.kext might help, but the package for the beta 2c kernel says this should only be for diagnostics. Any body had any luck? Link to comment https://www.insanelymac.com/forum/topic/142568-invalid-kernel-ip-wont-attempt-to-handle-trap-after-updating-to-1056/#findComment-1077259 Share on other sites More sharing options...
boba899 Posted February 13, 2009 Share Posted February 13, 2009 I'm not sure how related to everyone elses problem this is, but after specifying the root device in the boot options (in my case rd=disk1s2) a different kernel panic occured, one with something about Firewire. I unplugged my firewire sound card but the panic still happened, so I took out my firewire PCI card and it booted with the rd= option. Trying to get both the kernel and firewire working now. Link to comment https://www.insanelymac.com/forum/topic/142568-invalid-kernel-ip-wont-attempt-to-handle-trap-after-updating-to-1056/#findComment-1079483 Share on other sites More sharing options...
Recommended Posts