Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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][/U][/B]I'll start off by stating that I'm pretty new to linux so this could likely be a stupid newbie mistake. Here's the problem:
The kernel I have working is version 2.4.22 and I can still boot up to that. I compiled a 2.6 version and installed it in exactly the same way that the old version is, just appending 2-6 to the end of the file. I did this also with /etc/lilo.conf and ran lilo afterwards so when I reboot I get a menu that shows linux and linux-2.6
linux still boots up fine but when I try and boot up linux-2.6 I get some ouput and then a kernel panic with this message:
<snip>
VFS: Cannot open root device "888" or unknown-block(8,8)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(8,8)
I am running debian testing on a dell poweredge 1750. It has 2 Xeon processors and 1 scsi HD. The whole reason behind my compiling a kernel is trying to get support for high memory (this machine has 2 gigs of ram) and multi-processor support.
I doubt this has anything to do with lilo and suspect that I've somehow configured the kernel wrong. I am using reiserFS and I'm pretty sure I selected all scsi and driver support. Everything is compiled in and not as modules.
Solution This is the solution
could u check on IDE support, whether is turned on or not.
Check your .config and look for CONFIG_BLK_DEV_IDE and CONFIG_BLK_DEV_IDEDISK entries.
did you installed from a rpm? if you compiled your own kernel from a kernel source your .config is in the top directory of your kernel directory tree along with your system.map file. i suggest you read the kernel howto's first. i am sorry for the other post in the other thread but with all honest means i suggest you read the kernel howto's and procedures that you have to follow in order to compile and run your new kernel. you will be delighted by the output instead of frustrated which you are right now.
Wherever you built your kernel will have the .config file.
Perhaps it's /usr/src/linux/.config or /usr/src/linux-2.6.whichever.version.you.compiled/.config ?
Your error
Quote:
VFS: Cannot open root device "888" or unknown-block(8,8)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(8,8)
means the kernel cannot find the root file system. Make sure that LiLO is parsing the correct root=/dev/???? parameter, make sure that the device exists, and that the kernel has driver support for the device compiled in.
In other words, either (a) your / (root) filesystem is not in that location or (b) you don't have the block device for that filesystem compiled in your kernel, or compiled as a module (M) rather than built-in (Y).
In my experience, that error is usually caused by forgetting to compile the appropriate filesystem support into the kernel (Chinaman's option "b" above). I suggest you start there.
In my experience, that error is usually caused by forgetting to compile the appropriate filesystem support into the kernel (Chinaman's option "b" above). I suggest you start there.
I also just ran across while compiling my first 2.6 kernel in Slackware. Checked my config and I had left out ext3. Thanks Charred!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.