[SOLVED] Compiling the kernel

spiky0011 · 11-15-2011, 11:23 AM

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

Roken · 11-15-2011, 11:27 AM

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

druuna · 11-15-2011, 11:28 AM

Hi,

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?

devilboy09 · 11-15-2011, 11:39 AM

here's the kernel config file that i copied from source into /boot
http://hotfile.com/dl/135115708/9db2be8/config.txt.html

druuna · 11-15-2011, 11:51 AM

Hi,

hotfile is limited to 1 download per 30 minutes.......

spiky0011 · 11-15-2011, 11:52 AM

try pastebin.com

devilboy09 · 11-15-2011, 12:06 PM

http://pastebin.com/HsKgKAcC

druuna · 11-15-2011, 12:41 PM

Hi,

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.

Hope this helps.

devilboy09 · 11-15-2011, 01:13 PM

this is the output of lspic:
http://pastebin.com/3x57z6vF

can u help?
im' not familiar with this command

Roken · 11-15-2011, 01:35 PM

I would say disable:

CONFIG_SATA_AHCI_PLATFORM=y
CONFIG_SATA_INIC162X=y
CONFIG_SATA_ACARD_AHCI=y
CONFIG_SATA_SIL24=y
CONFIG_SATA_NV=y
CONFIG_SATA_PROMISE=y
CONFIG_PATA_AMD=y
CONFIG_SATA_QSTOR=y
CONFIG_SATA_SX4=y
CONFIG_ATA_BMDMA=y

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.

druuna · 11-15-2011, 02:06 PM

Hi,

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.

Hope this helps.

Roken · 11-15-2011, 06:38 PM

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.

liquidkaleidoscopes · 11-15-2011, 07:25 PM

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.

druuna · 11-16-2011, 12:04 AM

Hi Roken,

Quote:

Originally Posted by Roken

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

Hope this helps.

devilboy09 · 11-16-2011, 01:09 AM

Code:

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.

it didn't work