> Then the machine rebooted itself and it has come up > with a kernel panic. My guess is that this is related > to some problem with the bootloader or LILO. I was > just hoping that someone could refer me to a likely > fix for this since I'm not even in the city with the > machine and I have to forward this to my partner who > helps to run it so that he can work on it when he goes > to the co-locate.
I had a similar problem here - I'm running the testing disto here, and compiled a 2.6.8 kernel myself recently. Yesterday (or the day before, I don't remember) I took a deep breatht and ran an apt-get upgrade, updating lots and lots of packages (positively including kernel-sources, maybe including kernel-image). I then rebooted, and the box didn't come back online. The problem was easily determined: some script (debconf??) took the liberty of editing my /boot/grub/menu.lst, adding a few old (and unused) kernel images that I didn't remove from /boot yet. Unfortunately, these were added on top of the list, so grub defaulted to booting to a non-working image. Maybe something like that happened to you?? In that case you should be able to pick a different kernel image from the terminal when booting the machine? Good luck Dan -- "If we wanted more leisure, we'd invent machines that do things less efficiently." -Calvin's dad -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
