Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 downloaded 2.4 kernel sources to upgrade mandrake using 2.2. Built the custom kernel like I have many times, installed it etc. but when I booted the kernel it gives message: "VFS: Cannot open root device "305", Please append a correct "root=" boot option, Kernel panic: VFS: Unable to mount root fs on 03:05. I've never gotten this before, but I did notice that the end of the kernel complile it read "root device is (3,5). The config process is different from 2.0 and 2.2 but even though the other kernels will boot fine with the same stuff in lilo.conf, this one hangs. Interesting problem.
Hello
I assume you updated all the utilities etc as per the changes file. If not, thats the problem. If you did, then you need to tell lilo where / is.
So at lilo prompt type linux (or whatever your kernel is called) root=/dev/hda1 (or sda1 or wherever your hdd is).
Jim
I checked the Changes upgrades and everything was fine. As far as passing the "root=" directive, I tried that and when the kernel starts to boot and prints the Kernel Command Line, it still says "ro root=305" , and appended to the end of that is my command-line boot arg of "linux root=/dev/hda5". Is it possible that this has something to do with DevFS, which accorting to the Changes file is now in the kernel. I'm going to look into that a little more even though I can't remember selecting that when I did make config. Interesting.
Hello again
/dev/hda5 is the normal description for the fifth partition on your first hard disk. Are you sure thats where it is, though if the other kernels work, it must be right. I'd recheck lilo.conf, and probably redo the kernel. As I recall, dev fs support is experimental.
I had some fun with my sun machines not being able to find root today, bizarrely, putting the disk in the non booting slot of my second box (it booted!) fixed it without any fscking on my part. Maybe you could try something similar.
Jim
I really believe that something is hard-coded into the new kernel. Why, I don't know, but at the end of the kernel compile the last message is "Root device is (3,5)". It's difficult for me to believe that there isn't some link between that message and the "Kernel Command Line: BOOT_IMAGE=2.4Kernel ro root=305), and the later kernel panic saying that root isn't mounted VFS 305 or 03:05. Lots of threes and fives there : ) If there is a kernel hacker out there who can explain or dismiss this coincidence I would be grateful. A very interesting problem.
I love linux! I recompiled the kernel on another machine running red7.2 without using modules (just monolithic), copied it to the other machine running mandrake, and it loaded and ran fine. I must have been wrong about the (3,5) bit, because even though at the end of the kernel compile it still printed root=(3,5), it still ran fine on the older machine. One thing I did notice, however, was that when I did "make modules_install" on the older machine I got an error about depmod, it said that the -F option wasn't valid (the older machine has an older version of depmod), so I edited the Makefile and changed -F to -m because the newer machine's manpage said that could be used for backward compatibility. Maybe that was my problem. Regardless of that however, I think that from now on, if I am going to do a major kernel upgrade, instead of just a patch, I'll just download the isos from redhat and do a full upgrade. I tried that originally, however, and the upgrade process wouldn't locate my swap file, and only would allow me to select another partition that wasn't swap. I've used linux for about eight years, and one of the biggest problems I've had is doing distro upgrades or distro changes on dual-boot machines. I agree with lots of reviewers that before linux can be a viable desktop OS, a more reliable way to upgrade and install will have to be found-chasing RPM dependencies and moving from ipfwadm to iptables to ipchains etc-is just too time consuming and prone to failure.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.