[gentoo-user] kernel build - back in the soup.
I'll say right from the start, that building a new kernel, has always been a problem for me. I don't remember ever not having a problem, in 10+ yrs.. Many people here seem to find it completely easy... not me. So I'm back in the soup. [I hope what I try to layout below is not overly confusing] (After install of gentoo-sources-2.6.31-r4) I started with `make oldconfig' Moved from that to `make menuconfig' Trying to mimic all the needed drivers in current running kernel. But, On the first build and reboot, I got `kernel panic' So by now I've rebuilt the kernel 4 times, each time trying to get the new one to have all the needed drivers that are present in the old one, but still getting `kernel panic'. I tried closely comparing the current working kernel with newly built one. I mean side by side with `make menuconfig' running in both sources. I cannot tell what it is I'm overlooking. I copied the latest output painfully off the boot screen, and best I can make of it, a driver required to let the kernel recognize the filesystem that / is on, is not getting loaded. I think its one of PIIX items. The thing is, I cannot find the culprit. For example, examining the PIIX items in the working kernel and inserting here: zgrep PIIX /proc/config.gz CONFIG_BLK_DEV_PIIX=y CONFIG_ATA_PIIX=m CONFIG_PATA_MPIIX=y # CONFIG_PATA_OLDPIIX is not set CONFIG_I2C_PIIX4=m Try the same thing on the newbuild: grep PIIX /usr/src/linux/.config CONFIG_BLK_DEV_PIIX=y CONFIG_ATA_PIIX=m CONFIG_PATA_MPIIX=y # CONFIG_PATA_OLDPIIX is not set CONFIG_I2C_PIIX4=m So maybe it is not even related to PIIX But let me insert the kernel messages from a failed boot here: (I've numbered the lines from the bad boot output so as not confuse them with the good boot messages from kernel 2.6.30-r1 ---- ---=--- - >From Kernel 2.6.31-r4 1 hda: ST3160021A, ATA DISK drive 2 hdb: WDC SE3000JB-00KFA0, ATA DISK drive 3 hda: UDMA/100 mode selected 4 hdb: UDMA/100 mode selected 5 hdc: LITE-ON CD-ROM LTN-5291s, ATAPI CD/DVD-ROM drive 6 hdd: WDC WD16000JB-00EVA0, ATA DISK drive 7 hdc: UDMA/33 mode selected 8 hdd: UDMA/100 mode selected 9 IDE0 at 0x1f0-0X1f7,0X3f6 on irg 14 10 IDE0 at 0x170-0X177,0X376 on irg 15 ---- ---=--- - NOTE: Comparing a similar section of dmesg from working kernel 2.6.30-r1 Uniform Multi-Platform E-IDE driver piix :00:1f.1: IDE controller (0x8086:0x24db rev 0x02) PIIX_IDE :00:1f.1: enabling device (0005 -> 0007) ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered PIIX_IDE :00:1f.1: PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10 piix :00:1f.1: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xfc00-0xfc07 ide1: BM-DMA at 0xfc08-0xfc0f ** The part above, I think is where a piix driver is loaded or something (these messages from working kernel 2.6.30-r1) Probing IDE interface ide0... Switched to high resolution mode on CPU 0 hda: ST3160021A, ATA DISK drive hdb: WDC WD3000JB-00KFA0, ATA DISK drive hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hda: UDMA/100 mode selected hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hdb: UDMA/100 mode selected Probing IDE interface ide1... hdc: LITE-ON CD-ROM LTN-5291S, ATAPI CD/DVD-ROM drive hdd: WDC WD1600JB-00EVA0, ATA DISK drive hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hdc: UDMA/33 mode selected hdd: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hdd: UDMA/100 mode selected [...] snipped the rest of dmesg ouput from running kernel 2.6.30.1 ---- ---=--- - (continuation of messages from failed boot of kernel-2.6.31-r4 11 ide_generic: please use "probe_mask=0x3f" module parameters for probing all legacy IS IDE ports 12 ide-cd driver 5.00 13 ide cd:hdc: ATAPI 52X CD-ROM drive 96kB Cache 14 Uniform CD-ROM driver Revision: 3.10 15 Intel(R) PRO/1000 Network Driver version - 7.3.21-k3-NAPI 16 Copyright (c) 1999-2006 Intel Corporation 17 e1000e: Intel(R) Pro/1000 Network Driver, 1.0.2-k2 18: e1000e: Copyright(c) 1999-2008 Intel Corporation 19: e100: Intel (R) PRO/100 Network Driver 3.5.24-k-NAPI 20: e100: Copyright blah blah 21: sky2 driver version 1.23 22: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded 23: r8169 :02:03:0: PCI INT A -> GSI 19 (level,low) -> IRQ 19 24: r8169 :02:03:0: no PCI Experss capability 25: eth0 RTL8110s at 0xf8026f00, 00:40:f4:b5:29:41, XID 0400 IRQ 20 26: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded 27: r8169 :02:06:0: PCI INT A -> GSI 20 (level,low) -> IRQ 20 28: r8169 :02:06:0: no PCI Experss capability 29: eth1 RTL8110s at 0xf802ae00, 00:11:09:ee:6c:04, XID 0400 IRQ 20 30: PnP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 IRQ 1 31:
Re: [gentoo-user] kernel build - back in the soup.
your drivers for the ide disks have to be built INTO THE KERNEL! NOT MODULES. Also, you need to compile in the filesystem, not as module.
Re: [gentoo-user] kernel build - back in the soup.
091103 Harry Putnam wrote: > building a new kernel has always been a problem for me. > Many people here seem to find it completely easy... not me. I find it doable with a bit of care (smile). > After install of gentoo-sources-2.6.31-r4 > I started with `make oldconfig' > Moved from that to `make menuconfig' I just installed the same kernel with no problems. I did 'make oldconfig', looking at the '?' help for each new item & deciding whether to say Y/N as seemed appropriate. There wasn't anything dramatically new, so I went straight on to 'gvimdiff .config .config-', which allows a careful review of all the differences. There seemed to be nothing outstanding, so I went ahead with 'make', copied it by hand into /boot & updated Lilo; there was a problem, which I reported here, re Nvidia-drivers, but I moved up to a new version & then everything worked as expected. I never compile kernel items as modules if it cb avoided: it's one source of potential pain one can avoid. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] kernel build - back in the soup.
Harry Putnam wrote: > I'll say right from the start, that building a new kernel, has always > been a problem for me. I don't remember ever not having a problem, in > 10+ yrs.. > > Many people here seem to find it completely easy... not me. > > So I'm back in the soup. > [I hope what I try to layout below is not overly confusing] > > (After install of gentoo-sources-2.6.31-r4) > > I started with `make oldconfig' > Moved from that to `make menuconfig' > > Trying to mimic all the needed drivers in current running kernel. > But, On the first build and reboot, I got `kernel panic' > > So by now I've rebuilt the kernel 4 times, each time trying to get the > new one to have all the needed drivers that are present in the old > one, but still getting `kernel panic'. > > I tried closely comparing the current working kernel with newly built > one. I mean side by side with `make menuconfig' running in both sources. > I cannot tell what it is I'm overlooking. > > I copied the latest output painfully off the boot screen, and best I > can make of it, a driver required to let the kernel recognize the > filesystem that / is on, is not getting loaded. I think its one of > PIIX items. > > The thing is, I cannot find the culprit. For example, examining the > PIIX items in the working kernel and inserting here: > > zgrep PIIX /proc/config.gz > > CONFIG_BLK_DEV_PIIX=y > CONFIG_ATA_PIIX=m > CONFIG_PATA_MPIIX=y > # CONFIG_PATA_OLDPIIX is not set > CONFIG_I2C_PIIX4=m > > Try the same thing on the newbuild: > > grep PIIX /usr/src/linux/.config > > CONFIG_BLK_DEV_PIIX=y > CONFIG_ATA_PIIX=m > CONFIG_PATA_MPIIX=y > # CONFIG_PATA_OLDPIIX is not set > CONFIG_I2C_PIIX4=m > > So maybe it is not even related to PIIX > But let me insert the kernel messages from a failed boot here: > (I've numbered the lines from the bad boot output so as not confuse > them with the good boot messages from kernel 2.6.30-r1 > ---- ---=--- - > From Kernel 2.6.31-r4 > > 1 hda: ST3160021A, ATA DISK drive > 2 hdb: WDC SE3000JB-00KFA0, ATA DISK drive > 3 hda: UDMA/100 mode selected > 4 hdb: UDMA/100 mode selected > 5 hdc: LITE-ON CD-ROM LTN-5291s, ATAPI CD/DVD-ROM drive > 6 hdd: WDC WD16000JB-00EVA0, ATA DISK drive > 7 hdc: UDMA/33 mode selected > 8 hdd: UDMA/100 mode selected > 9 IDE0 at 0x1f0-0X1f7,0X3f6 on irg 14 > 10 IDE0 at 0x170-0X177,0X376 on irg 15 > ---- ---=--- - > > NOTE: Comparing a similar section of dmesg from working kernel > 2.6.30-r1 > > Uniform Multi-Platform E-IDE driver > piix :00:1f.1: IDE controller (0x8086:0x24db rev 0x02) > PIIX_IDE :00:1f.1: enabling device (0005 -> 0007) > ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 > PCI: setting IRQ 10 as level-triggered > PIIX_IDE :00:1f.1: PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ > 10 > piix :00:1f.1: not 100% native mode: will probe irqs later > ide0: BM-DMA at 0xfc00-0xfc07 > ide1: BM-DMA at 0xfc08-0xfc0f > > ** The part above, I think is where a piix driver is loaded or > something (these messages from working kernel 2.6.30-r1) > > Probing IDE interface ide0... > Switched to high resolution mode on CPU 0 > hda: ST3160021A, ATA DISK drive > hdb: WDC WD3000JB-00KFA0, ATA DISK drive > hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 > hda: UDMA/100 mode selected > hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4 > hdb: UDMA/100 mode selected > Probing IDE interface ide1... > hdc: LITE-ON CD-ROM LTN-5291S, ATAPI CD/DVD-ROM drive > hdd: WDC WD1600JB-00EVA0, ATA DISK drive > hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 > hdc: UDMA/33 mode selected > hdd: host max PIO4 wanted PIO255(auto-tune) selected PIO4 > hdd: UDMA/100 mode selected > > [...] snipped the rest of dmesg ouput from running kernel > 2.6.30.1 > > ---- ---=--- - >(continuation of messages from failed boot of kernel-2.6.31-r4 > > 11 ide_generic: please use "probe_mask=0x3f" module parameters for probing > all legacy IS IDE ports > 12 ide-cd driver 5.00 > 13 ide cd:hdc: ATAPI 52X CD-ROM drive 96kB Cache > 14 Uniform CD-ROM driver Revision: 3.10 > 15 Intel(R) PRO/1000 Network Driver version - 7.3.21-k3-NAPI > 16 Copyright (c) 1999-2006 Intel Corporation > 17 e1000e: Intel(R) Pro/1000 Network Driver, 1.0.2-k2 > 18: e1000e: Copyright(c) 1999-2008 Intel Corporation > 19: e100: Intel (R) PRO/100 Network Driver 3.5.24-k-NAPI > 20: e100: Copyright blah blah > 21: sky2 driver version 1.23 > 22: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > 23: r8169 :02:03:0: PCI INT A -> GSI 19 (level,low) -> IRQ 19 > 24: r8169 :02:03:0: no PCI Experss capability > 25: eth0 RTL8110s at 0xf8026f00, 00:40:f4:b5:29:41, XID 0400 IRQ 20 > 26: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded >
Re: [gentoo-user] kernel build - back in the soup.
Am Dienstag 03 November 2009 23:29:59 schrieb Harry Putnam:
> The thing is, I cannot find the culprit. For example, examining the
> PIIX items in the working kernel and inserting here:
Still the (IMHO) best way is to boot a LiveCD, run "lspci -vv" (two times "v")
and write down which hardware is detected and which driver is used for it.
From that you can directly determine what you need to compile into your
kernel. Everything else is guesswork.
Hint: menuconfig has a search function ("/"). You can directly search for the
driver name you got from lspci and enable the corresponding option.
If you're unsure as to what should be compiled into the kernel and what can be
a module, always say "Y". You can try "M" in later iterations. As a rule of
thumb: everything you need to access your root fs should get a "Y". That is
Chipset->(S)ATA harddisk->Filesystem.
If it still won't work, you can also post your kernel config and the output of
lspci -vv here and somebody will find out what's wrong/missing.
HTH...
Dirk
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] kernel build - back in the soup.
On Wed, Nov 4, 2009 at 12:49 PM, Dirk Heinrichs
wrote:
> Am Dienstag 03 November 2009 23:29:59 schrieb Harry Putnam:
>
>> The thing is, I cannot find the culprit. For example, examining the
>> PIIX items in the working kernel and inserting here:
>
> Still the (IMHO) best way is to boot a LiveCD, run "lspci -vv" (two times "v")
> and write down which hardware is detected and which driver is used for it.
> From that you can directly determine what you need to compile into your
> kernel. Everything else is guesswork.
>
> Hint: menuconfig has a search function ("/"). You can directly search for the
> driver name you got from lspci and enable the corresponding option.
>
> If you're unsure as to what should be compiled into the kernel and what can be
> a module, always say "Y". You can try "M" in later iterations. As a rule of
> thumb: everything you need to access your root fs should get a "Y". That is
> Chipset->(S)ATA harddisk->Filesystem.
>
> If it still won't work, you can also post your kernel config and the output of
> lspci -vv here and somebody will find out what's wrong/missing.
>
> HTH...
>
> Dirk
>
And on a reasonably new version of pciutils...
lcpci -k
lists devices and drivers, less extras to dig through.
--
Poison [BLX]
Joshua M. Murphy
Re: [gentoo-user] kernel build - back in the soup.
> And on a reasonably new version of pciutils... > lcpci -k > lists devices and drivers, less extras to dig through. > > -- > Poison [BLX] > Joshua M. Murphy > That should, of course, be lspci, not lcpci... -- Poison [BLX] Joshua M. Murphy
Re: [gentoo-user] kernel build - back in the soup.
2009/11/4 Harry Putnam : > I'll say right from the start, that building a new kernel, has always > been a problem for me. I don't remember ever not having a problem, in > 10+ yrs.. > > Many people here seem to find it completely easy... not me. > > I tried closely comparing the current working kernel with newly built > one. I mean side by side with `make menuconfig' running in both sources. > I cannot tell what it is I'm overlooking. Please do not do this. Instead emerge kccmp to compare kernel configurations! It is much easier...trust me, I tried brute-force as well! Regards, daid
