Both kernels 2.4 & 2.6 failed loading after compiling 2.6
SlackwareThis Forum is for the discussion of Slackware 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.
Both kernels 2.4 & 2.6 failed loading after compiling 2.6
I'm back with more problems.
I moved to Slack 10. Try an upgrade with swaret and since then my GNOME stoped working, ..., no problem, I moved to KDE and started reading on how to solve the problem. Finally I read on some forum that if I install Dropline, my actual GNOME problems will be fixed, so I try installing Dropline. Too bad, my kernel s too old. No problem, lets move from Kernel 2.4.2 to kernel 2.6.9 (big upgrade for my system).
I followed the steps from:
and I could swear I followed every single step (I've been reading a lot of forums where shilo ends up saving the game, so I really like the way he works, no complains, just trying to solve my problem). Actually we were doing the same procedure in 2 machines at the same time, and in the first one it worked perfectly, that's why I tryed on my computer.
After finishing with all the steps now I received this message on both kernels when trying to load my system:
Code:
UDF - fs: No partition found (1)
Code:
kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (3,6)
So there is no way for me to run anything here.
Now, here comes the worst part. My computer is my computer from my work, and unfortunately I don't have a floppy, CD-Rom or any device to run a backup disk (security reasons, that's what my boss said).
I actually need help...
Last edited by ernesto_lelo; 10-21-2004 at 08:05 PM.
Send us the contents of /etc/lilo.conf and your partitioning scheme (e.g.: /dev/hda1 - /boot, /dev/hda2 - /, etc.). Please specify which file systems you're using, too. Something's probably wrong with your configuration of Lilo, because the kernel can't find the root partition with the arguments you're passing.
By default kernel 2.6.x does not have the reiserfs support enabled. When you compile your kernel you have to enable reiserfs support otherwise you're system won't boot.
Recompile your kernel and make sure that you have the reiserfs enabled [marked with '*'<built in>]; it's in the 'File System' submenu.
thanks for the answer.
My problem is that can't do anything, there is no way for me to get access to the files, once I get to the error (while loading the system) my computer gets stuck and there is nothing for me to do.
Is there a way for me to access the linux partitions in a different way (I know I could use the CD 1 to try to recover the system, but I don't have a CD-ROM nor floppy)
Did you mess around with the Lilo entry for the old kernel? If you can't boot at all, as far as I know, you're completely screwed. Unless you can boot another kernel, you need to be able to boot from something other than the hard drive and mount the hard drive so you can view/edit /etc/lilo.conf. I guess you'll just have to beg your boss to let you temporarily install a floppy drive or a CD drive, or let you take out the hard drive and mount it on another computer.
Or if your BIOS supports it and your boss isn't too much worried about security, use a usb card to boot, mount the harddisk, chroot to it, edit lilo.conf and run lilo
Btw, it seems you didn't compile your filesystem support built-in so also check kernel options to see if it's right.
you can just compile it into the kernel.
or, if you really want it to be a module, use an initrd.
but compiling it in is the most simple, you only need a new bzImage and you can skip the "make modules" as they are already 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.