LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (https://www.linuxquestions.org/questions/debian-26/)
-   -   Dist-Upgrade = Kernel Panic (https://www.linuxquestions.org/questions/debian-26/dist-upgrade-%3D-kernel-panic-493575/)

carlosinfl 10-18-2006 12:44 PM

Dist-Upgrade = Kernel Panic
 
So I did a new install of Etch and I did the usual "apt-get update" and "apt-get dist-upgrade". I noticed in the list of upgrades it installed the 2.6.17-2-686 kernel over the default 2.6.16-2-686 kernel. When I rebooted after the "apt-get dist-upgrade", I received a "Kernel Panic".

Is there a way to verify why and how to fix this? I was able to boot back into the 2.6.16-2-686 kernel now and everything is fine but I don't understand.

Thanks!

pljvaldez 10-18-2006 01:56 PM

I would enable the boot log (modify /etc/default/bootlogd and the log will be at /var/log/boot). Also, if you can post your menu.lst, and the output of ls /boot, maybe there will be something clear there.

carlosinfl 10-18-2006 02:13 PM

I enabled logging.

Code:

cwilliams:/etc/default# ls /boot/
config-2.6.16-2-686  initrd.img-2.6.16-2-686      System.map-2.6.17-2-686
config-2.6.17-2-686  initrd.img-2.6.16-2-686.bak  vmlinuz-2.6.16-2-686
grub                System.map-2.6.16-2-686      vmlinuz-2.6.17-2-686

Code:

title          Debian GNU/Linux, kernel 2.6.17-2-686
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.17-2-686 root=/dev/sda1 ro
savedefault

title          Debian GNU/Linux, kernel 2.6.17-2-686 (single-user mode)
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.17-2-686 root=/dev/sda1 ro single
savedefault

title          Debian GNU/Linux, kernel 2.6.16-2-686
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.16-2-686 root=/dev/sda1 ro
initrd          /boot/initrd.img-2.6.16-2-686
savedefault

title          Debian GNU/Linux, kernel 2.6.16-2-686 (single-user mode)
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.16-2-686 root=/dev/sda1 ro single
initrd          /boot/initrd.img-2.6.16-2-686
savedefault


antidrugue 10-18-2006 02:38 PM

It seems you are missing the obvious : a "initrd" file for your new 2.6.17-2-686 kernel.

Perhaps you can build a new one. Boot with your working kernel (2.6.16-2-686) and use one of these commands :
Code:

mkinitramfs -o /boot/initrd.img-2.6.17-2-686
if you use "initramfs".

Or
Code:

mkinitrd -o /boot/initrd.img-2.6.17-2-686
if you use "initrd".

Then update grub so it boots from the 2.6.17-2-686 initrd file. And boot into your new kernel.

carlosinfl 10-18-2006 02:39 PM

Awesome - I will try that and post back my results!


All times are GMT -5. The time now is 10:22 AM.