Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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 had the same error in my build BUT I am building on usb drive I dont think that it will help, Besides drunna and roken have far more experiance than me. I dont want to add things to make them worse you have tried enough
Can we see your fstab from the LFS filesystem, too? I'm going to be out for a good couple of hours in five minutes, so don't panic if no reply (unless drunna turns up, of course)
Edit: Just read that and it sounds like I meant you CAN panic if drunna turns up - I didn't of course. I just meant that you won't be waiting for a reply
If I look at the png you posted it looks like the kernel didn't see/load your hd's. This would point to a kernel option that isn't set (or i wrongly set).
I already asked you to post the LFS kernel .config file in post #55. Any reason you haven't done so?
You should disable the following (not needed, at least for the moment):
Code:
Device Drivers --> ATA/ATAPI/MFM/RLL support (DEPRECATED)
Device Drivers --> Multiple devices driver support (RAID and LVM)
Device Drivers --> Macintosh device driver
You need to have a good look at this section:
Code:
Device Drivers --> Serial ATA and Parallel ATA drivers
If I Look at your entries I only see a few activated drivers (a mix of intel, amd and generic). I do wonder if you have selected the correct one (or more). Most, if not all, of this information can be found on your host when you issue the dmesg command (I would suggest you re-route the output to file for easier access/searching (dmesg > dmesg.output).
You need to search for PATA, SATA and ATA to determine which hardware you have and set the options accordingly. The output of lspci will also help in determining what you have.
Looking at the rest of the .config file I don't see any major mistakes as far as I can tell. There are a lot of options that can probably be disabled (and a few enabled) but without knowing your hardware I cannot advise you on which. Focus on the PATA, SATA and ATA entries and let the rest as-is for now.
Leave the rest as it is, and rebuild your kernel. See how you get on. SATA_AHCI_PLATFORM is reported to cause problems on some systems, and the others you simply don't need.
For info, your vendor specific driver (which you will leave enabled) is CONFIG_ATA_PIIX=y.
Don't think I've missed anything there, but perhaps a second opinion would save time later.
Device Drivers --> Serial ATA and Parallel ATA drivers:
- Initio 162x SATA support
- ACard AHCI variant (ATP 8620)
- Silicon Image 3124/3132 SATA support
- Pacific Digital SATA QStor support
- Promise SATA SX4 support (Experimental)
- NVIDIA SATA support
- Promise SATA TX2/TX4 support
- AMD/NVidia PATA support
Enable the following:
Code:
Device Drivers --> SCSI device support --> SCSI low-level drivers:
- LSI Logic Legacy MegaRAID Driver (*, not M)
- VMware PVSCSI driver support (*, not M) Not sure if this one is needed, but you do have a vmware layer that "feeds" certain hardware info
This is based on only the output of the lspci command, a lot more might be found in the dmesg output.
BTW: DO NOT edit these out using an editor and the .config file (this might have nasty side effects). Use the make menuconfig command!!
BTW2: Have a look at post #13 to make sure you do all the correct steps to rebuild and place the kernel.
I'm pretty sure that on an LFS kernel teh vmware driver will not be required right now (provided you aren't planning on sharing the kernel with your host).
Just a Q for druuna. Your list of removed is much in accordance with mine, and I checked for possible dependant entries and didn't see any (though I'll accept I may have missed something, but for the sake of argument), can you envisage any problems either way (if I'm right) as long as make menuconfig is done just for the purpose of saving the config file. @ devilboy09 - ignore this bit, just for my own info.
If you're ever unsure what to enter for a driver, try pasting the results of 'lspci -n' into the box at http://kmuto.jp/debian/hcl/. Also, very time that you rebuild your kernel, it is a good idea to copy your .config into another directory, run 'make mrproper', then copy .config back into the kernel directory.
Last edited by liquidkaleidoscopes; 11-15-2011 at 07:27 PM.
Just a Q for druuna. Your list of removed is much in accordance with mine, and I checked for possible dependant entries and didn't see any (though I'll accept I may have missed something, but for the sake of argument), can you envisage any problems either way (if I'm right) as long as make menuconfig is done just for the purpose of saving the config file.
You already answered you own question
Dependencies are the biggest possible problem (typo's, especially when editing out commands is another).
I've always seen the manually editing of the .config file as a bad habit (especially for newbies, but also for experienced kernel builders). Using make menuconfig isn't that much extra work (especially if you know which entries you want to change) and this command does do al the checks necessary and makes changes accordingly. Why take the chance to overlook something when all this is in place.
I never tried, but I do wonder if you can just edit out (# OPTION=X) an entry or that one needs to change the entry to # OPTION is not set
You should disable the following:
Code:
Device Drivers --> Serial ATA and Parallel ATA drivers:
- Initio 162x SATA support
- ACard AHCI variant (ATP 8620)
- Silicon Image 3124/3132 SATA support
- Pacific Digital SATA QStor support
- Promise SATA SX4 support (Experimental)
- NVIDIA SATA support
- Promise SATA TX2/TX4 support
- AMD/NVidia PATA support
Enable the following:
Code:
Device Drivers --> SCSI device support --> SCSI low-level drivers:
- LSI Logic Legacy MegaRAID Driver (*, not M)
- VMware PVSCSI driver support (*, not M) Not sure if this one is needed, but you do have a vmware layer that "feeds" certain hardware info
This is based on only the output of the lspci command, a lot more might be found in the dmesg output.
BTW: DO NOT edit these out using an editor and the .config file (this might have nasty side effects). Use the make menuconfig command!!
BTW2: Have a look at post #13 to make sure you do all the correct steps to rebuild and place the kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.