Linux - SoftwareThis 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.
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.
Boots Fine, MBR prompt comes ups, Select Gentoo, Lilo comes up. Hit Enter. Starts Boot Process:
Then things start getting weird, when it loads my two HD's they come up as:
/hda = Windows
Obviously, i then get the error:
!!Block device /dev/sdb3 is not a valid root device
!!The root block device is unspecified or not detected
Loadup busybox shell:
Dev list confirms the above information.
I can chroot into the Gentoo installation and everything works great.
Tried 9 different manual kernel configs, tooling around with the SATA configuration because everyone on the internet instructed me that it was a SATA related error. Finally after extreme frustration i broke down and at the advice of someone i used genkernel (I KNOW! I was desperate) with --menuconfig option and selected EVERY SATA option on, just to cover all bases.
from Gentoo Forums Team:
NeddySeagoons' Rough Guide to Intel ICH7 Chip Set
You have an Intel ICH7 Family chip set. genkernel will net set this one up correctly, so you have to help it if you want to use genkernel.
In make menuconfig choose the following options:-
Device Drivers --->
< > ATA/ATAPI/MFM/RLL support --->
turn off the ATA/ATAPI/MFM/RLL support menu item entirely.
You may think this will prevent your CDROM working - it won't. I'll explain later.
<*> Serial ATA (prod) and Parallel ATA (experimental) drivers --->
<*> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
notice how it says PATA/SATA in the name. This driver is a combined driver for both SATA and IDE modes - its peculiar to Intel. All other options on this menu must be off, including the two Intel PATA options close to the bottom. If you get that wrong your hard drive will appear as an IDE drive and be very slow as you will not get DMA modes.
Thats the low level drivers set.
Now the high level driver
go back up to
SCSI device support --->
Inside that menu choose
│ │ < > RAID Transport Class
│ │ -*- SCSI device support
│ │ < > SCSI target support
│ │[*] legacy /proc/scsi/ support
│ │ *** SCSI support type (disk, tape, CD-ROM) ***
│ │ <*> SCSI disk support
│ │ < > SCSI tape support
│ │ < > SCSI OnStream SC-x0 tape support
│ │ <*> SCSI CDROM support
SCSI CDROM support may be either <M> or <*> but your CDROM is going to be treated as a SCSI device now. It will have two entries in /dev, /dev/sr0 which is the block device you use in the normal way and /dev/sg0 which is its controlling charater device. Normally, you don't need to know that as udev takes care of creating the symlinks properly. However, if your CDROm is listed in /etc/fstab as /dev/hd... that will need to change.
I had the same problem but with a ATI chipset sata device
and thanks to this info I found I've been able to fix this... It took me 2 install's and numerous kernel builds to get this system to boot from the SATA HD into gentoo.
And thanks to this tip relating to the intel chipset that I've managed to get Linux booted. This should go into the gentoo X64 installation manual or in a faq on the gentoo web site. Then poeple with newer systems would not have to be stuck like I was.