Linux - Software This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
04-08-2004, 05:05 AM
|
#1
|
LQ Newbie
Registered: Aug 2003
Location: Brussels, Belgium
Distribution: Debian Sid
Posts: 9
Rep:
|
VFS: Cannot open root device (kernel panic)
Okay, here's the deal.
I'm trying to get Debian Woody to work on my comp. Unfortunately, the native 2.4.18 kernel shipped with it doesn't support my network card.
On the other hand, compiling a newer 2.4 kernel resolves the problem. BUT, I'm trying to compile a 2.6 kernel (which I've heard many good things about). In fact I've been trying to compile 2.6.4 and 2.6.4-ck2.
The compilation itself doesn't encounter any problems, so that's clear.
The problem comes at boot time, where I can the following message:
Code:
VFS: Cannot open root device "341" or hdb1
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on hdb1
Any ideas how to fix this? I've read around a bit, some people claim that it's due to missing IDE drivers, so I activated them all just in case and... nothing happens.
Last edited by Mamour; 04-08-2004 at 05:17 AM.
|
|
|
04-08-2004, 05:18 AM
|
#2
|
Member
Registered: Jul 2003
Location: netherlands
Distribution: debian
Posts: 403
Rep:
|
well, is your root dir (/) on hdb1? it could be the bootloader setup is corrupted somehow when you added the 2.6 kernel to it...
greetz
-= iluvatar =-
|
|
|
04-08-2004, 05:21 AM
|
#3
|
LQ Newbie
Registered: Aug 2003
Location: Brussels, Belgium
Distribution: Debian Sid
Posts: 9
Original Poster
Rep:
|
I wish it were that easy.
No, my lilo.conf is configured correctly, so I don't believe LILO causes the trouble (the default vmlinuz image has the exact same configuration, and it works without a hinch).
|
|
|
04-08-2004, 07:26 AM
|
#4
|
Member
Registered: Feb 2003
Distribution: Gentoo
Posts: 381
Rep:
|
Have you compiled the filesystem of the partition directly into the kernel?
Or maybe the ide driver?
|
|
|
04-08-2004, 09:13 AM
|
#5
|
LQ Newbie
Registered: Aug 2003
Location: Brussels, Belgium
Distribution: Debian Sid
Posts: 9
Original Poster
Rep:
|
Yes I have, I even tried to compile the kernel without module support at all (i.e. everything got compiled directly into the kernel), and it hasn't fixed the problem either.
|
|
|
04-15-2004, 06:43 PM
|
#6
|
LQ Newbie
Registered: Apr 2004
Posts: 3
Rep:
|
I have a belife here,
It seems that it has to do with the linking to the system.map, the original kernel has a monoply on the link. If this is what is causing it how do you either make a multi link or tell grub to use a specific System.map?
Paul
|
|
|
04-20-2004, 01:30 AM
|
#7
|
Member
Registered: Mar 2004
Location: Melton Mowbray England
Distribution: Ubuntu
Posts: 37
Rep:
|
same problem here, did you get a fix?
I'm having exactly the same problem... as it appears are many other people.
I'm a relative newbie as well, have played around with it for years and honestly have spent more time wrestling with Lilo than any other part of Linux....!
I'm running Mandrake 10, which is originally 2.6.3 kernel, compiled the new 2.6.5 kernel and now neither will boot. When I try to login using Knoppix and change lilo.conf, then run lilo I get an error from Lilo "Fatal: creat /boot/map :read only file system", whic I suspect is perhaps due to the fact that it is attempting to write the new bootstrap file back to the Knoppix CD? Can anyone tell me how to get around this and get it put on my hda mbr?
In the past I've tried GRUB but not had any luck so stick with Lilo.
I've included my lilo.conf, although have not been able to rerun lilo yet because of above. /dev/hda and /dev/hda3 have worked fine until this compile/install. If anyone can give me a set of steps to diagnose the cause of the problem I would be most greatful. I might even put the results together in a howto file because many of us are having the same problem. We never know if it is something we did incorrrectly in our ambitious kernel configure/compile or a bug!!
Thanks a bunch, all suggestions most helpful.
Jim
|
|
|
04-20-2004, 04:02 AM
|
#8
|
Senior Member
Registered: Mar 2004
Location: Munich
Distribution: Ubuntu
Posts: 3,517
Rep:
|
Do you use a S-ATA controller? In that case, your HDD is maybe recognized as scsi-device by the 2.6 kernel (eg. sdb1 instead of hdb1). This was the case (and the solution) when I upgraded from 2.4 to 2.6.
|
|
|
04-20-2004, 01:21 PM
|
#9
|
LQ Newbie
Registered: Apr 2004
Posts: 3
Rep:
|
No SATA drives here just IDE
|
|
|
All times are GMT -5. The time now is 03:55 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|