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!
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.
I have recently attempted to upgrade to 2.4.22 kernel. I configured what I needed(or so I thought) and ran all the commands to compile and install a new kernel. When I try to boot the new kernel, I get the following error while booting up:
ds: no socket drivers loaded!
VFS: Cannot open root device "LABEL=/" or 00:00
Please append a carrect "root=" boot option
Kernel panic: VFS: Unable to mount root on 00:00
Everything before that seems to work correctly. After I reach this, I go no further. My grub.conf looks like this:
# 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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/hdb2
# initrd /initrd-version.img
title Red Hat Linux (2.4.22)
kernel /vmlinuz-2.4.22 ro root=LABEL=/ hdc=ide-scsi hde=noprobe hdg=noprobe
title Red Hat Linux (2.4.20-20.9custom)
kernel /vmlinuz-2.4.20-20.9custom ro root=LABEL=/ hdc=ide-scsi hde=noprobe hdg=noprobe
#title Red Hat Linux (2.4.20-20.9)
# root (hd1,0)
# kernel /vmlinuz-2.4.20-20.9 ro root=LABEL=/ hdc=ide-scsi hde=noprobe hdg=noprobe
# initrd /initrd-2.4.20-20.9.img
#title Red Hat Linux (2.4.20-8)
# root (hd1,0)
# kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdc=ide-scsi
# initrd /initrd-2.4.20-8.img
This seems to be an easily fixed item, but maybe I'm missing something that you can spot :). Thanks
First, did you run "grub-install /dev/<your boot device>" after changing the grub.conf file? If not, you should run this command after editing the grub.conf. BUT BE CAREFUL since I do not know which one is your boot device
If you can still boot into the original kernel, try to change the "root=LABEL=/" line of your new kernel to "root=/dev/hdb1" and then run the "grub-install /dev/<your boot device>" command and restart to see whether it works.