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 a RedHat 7.2 PC. I updated the kernel from 2.4.7-10 to 2.4.20-19.7 through the RedHat Network (RHN) service automatically. Then I got the following error messages and could not boot it with the new kernel.
kmod: failed to exec /sbin/modprobe -s -k block-major-8, errono=2
VFS: cannot open root device "802" or 08:02
Please append a correct "root=" boot option
kernel panic: VFS: Unable to mount root fs on 08:02
At the moment, I can boot it with the original kernel (when booting, I just select "Linux.bak"). The file of /boot/initrd-2.4.20-19.7(smp) was not created by the RHN updating.
I greatly appreciate your advice. Thank you very much.
---------EOF of /etc/lilo.conf ----------
-------- /boot/grub/grub.conf ---------
title Red Hat Linux (2.4.20-19.7smp)
kernel /vmlinuz-2.4.20-19.7smp ro root=/dev/sda2 hdc=ide-scsi
title Red Hat Linux (2.4.20-19.7)
kernel /vmlinuz-2.4.20-19.7 ro root=/dev/sda2 hdc=ide-scsi
title Red Hat Linux (2.4.20-18.7smp)
kernel /vmlinuz-2.4.20-18.7smp ro root=/dev/sda2 hdc=ide-scsi
title Red Hat Linux (2.4.20-18.7)
kernel /vmlinuz-2.4.20-18.7 ro root=/dev/sda2 hdc=ide-scsi
title Red Hat Linux (2.4.7-10smp)
kernel /vmlinuz-2.4.7-10smp ro root=/dev/sda2 hdc=ide-scsi
title Red Hat Linux-up (2.4.7-10)
kernel /vmlinuz-2.4.7-10 ro root=/dev/sda2 hdc=ide-scsi
--------- EOF of /boot/grub/grub.conf --------------
With lilo, (since I only use that and I assume
it would be the same with Grub) you need to
run the program so it recognises your new kernel.
Not sure how it's done with grub, but typing
/sbin/lilo at prompt is required before rebooting and
starting with a new kernel.
Thank you very much for your reply. I tried to execute /sbin/lilo and rebooting, but the situation was the same.
I may need to make /boot/initrd-2.4.20-19.7smp and add a line "initrd=/boot/initrd-2.4.20-19.7smp" to /etc/lilo.conf. However, /sbin/mkinitrd was not working as follows.
% /sbin/mkinitrd /boot/initrd-2.4.20-19.7 2.4.20-19.7
No module pti_st found for kernel 2.4.20-19.7
"pti_st" is defined in /etc/modules.conf as "alias scsi_hostadapter pti_st", but there is no definition in /boot/modules-info.2.4.20-19.7. In /var/log/messages, there is the following lines.
---------- lines from /var/log/messages -------------
Aug 13 14:34:24 RH7.2 kernel: Kernel command line: auto BOOT_IMAGE=linux.bak ro root=802 BOOT_FILE=/boot/vmlinuz-2.4.7-10smp hdc=ide-scsi
Aug 13 14:34:24 RH7.2 kernel: ide_setup: hdc=ide-scsi
Aug 13 14:34:32 RH7.2 kernel: SCSI subsystem driver Revision: 1.00
Aug 13 14:34:32 RH7.2 kernel: scsi0 : PROMISE SuperTrak SX6000 Driver
Aug 13 14:34:32 RH7.2 kernel: Type: Direct-Access ANSI SCSI revision: 02
Aug 13 14:34:32 RH7.2 kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Aug 13 14:34:32 RH7.2 kernel: SCSI device sda: 714843648 512-byte hdwr sectors (366000 MB)
Aug 13 14:34:32 RH7.2 kernel: scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Aug 13 14:34:32 RH7.2 kernel: Type: CD-ROM ANSI SCSI revision: 02
Aug 13 14:39:45 RH7.2 kernel: Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0
Aug 13 14:39:45 RH7.2 kernel: sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
If you have some idea about it, I'm happy to hear it.
Thank you again.