Kernel panic : VFS : Unable to mount root fs on 00:00 on PCQLinux
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Kernel panic : VFS : Unable to mount root fs on 00:00 on PCQLinux
I am installing rtlinux on PCQLinux 2008.i have done make config,make dep,make modules,make modules_install and make install.My grub.config file is:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title PCQLinux (2.4.21-rtl3.2-pre3)
root (hd0,0)
kernel /vmlinuz-2.4.21-rtl3.2-pre3 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.4.21-rtl3.2-pre3.img
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,513
Rep:
That error usually indicates a bad or nonexistent initrd file. Check to see that the initrd file is really there, in /boot. If it is, or if it isn't, I would generate another one. What I can't figure out is why you want to use a 2.4 kernel.
initrd file exists in /boot.to make initrd image i used command
# /sbin/mkinitrd 2.4.21-rtl3.2-pre3-new.img 2.4.21-rtl3.2-pre3
but it gives error:
No module uhci-hcd found for kernel 2.4.21-rtl3.2-pre3, aborting.
rtlinux 3.2-rc1 having only patches for 2.4.xx kernels only so i used that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.