DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.