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.
I ran into exactly the same problem. Apparently the 2.6.8 kernel regards my hard drives as /dev/sda, whereas the 2.4.27 kernel is happy with /dev/hda. So what happens is that grub finds the kernel image, but the kernel image can't find the root partition and so can't find /dev (or anything, for that matter).
So if you replace /dev/hde3 with /dev/sde3 for the two 2.6.8 entries, it should work. Leave it as /dev/hde3 for the 2.4.27 entries.
Boot the 2.4 kernel, install debfoster, launch it, when it shows the 2.6 kernel-image purge it (press p) or # dpkg -P kernel-image-2.6.8-2-386, apt-get clean, reboot, come back, and install
# apt-get -y install kernel-image-2.6.8-2-686 (unless your box is older than a PII)
Got nothing to lose? Seems like a lot of trouble when just editing a few lines of menu.lst will do the trick.
Anyways, I just upgraded the recently bugfixed 2.6.8 kernel-image using aptitude, and it re-built the menu.lst file using /dev/hdxx instead of /dev/sdxx for the 2.6.8 kernel. So I had to edit the file again by hand. Explain, please, how purging the kernel-image and re-installing it will solve this problem.
halsum wrote:
"Got nothing to lose? Seems like a lot of trouble when just editing a few lines of menu.lst will do the trick."
IF you know what you're doing, it SHOULD work, and if it doesn't?
"Anyways, I just upgraded the recently bugfixed 2.6.8 kernel-image using aptitude, and it re-built the menu.lst file using /dev/hdxx instead of /dev/sdxx for the 2.6.8 kernel. So I had to edit the file again by hand. Explain, please, how purging the kernel-image and re-installing it will solve this problem."
It doesn't take long to purge/reinstall from a safe 2.4 kernel, and if indeed the bug is fixed, all will go fine.
If he messes up the grub menu, it will be longer, and another can of worms will open, won't you say?
Debian/Linux is just an operative system, no life and death here. I gave my opinion because after 3 pages he is still nowhere. It's just common sense.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.