CDROM Resolved. Re: SUCCESS: Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Resolved the CDROM recognition problem. create a file named libata into /etc/modprobe.d/ with the content: options libata atapi_enabled=1 Then: # dpkg-reconfigure linux-image-`uname -r` This regenerate the initrd image with the special parameter. It tried to pass libata.atapi_enabled=1 at boot params but didn't worked. I now have /dev/sr0 and can mount a read the CDROM. -Steve Lennart Sorensen wrote: On Sun, Jan 08, 2006 at 10:42:20AM -0500, Stephen Woodbridge wrote: Hi Len, Thank You! Thank you! Thank you! Using the kernel from sid did the trick! I guess I was too focused on having to build a kernel to step back from the problem and see that. Also the kernel-image to linux-image tripped me up so I didn't see them in apt-cache search. I now can see the 3ware device as /dev/sdb but I seem to have lost the CDROM drive again. I suppose the 2.6.15 wants the BIOS settings changed again or I have run up against the problem that the CDROM seems to only run as a slave device on the PATA IDE bus. Any idea what causes the: ata1(1): WARNING: ATAPI is disabled, device ignored. There is an option I think might have to be enabled. There is also a bug in 2.6.15 that I just read on lkml about 30 minutes ago, that on intel ICH controllers, PATA secondary slave is currently broken. primary master, primary slave, and secondary master all work, but no atapi on secondary slave. If your cdrom is secondary slave, change it. Otherwise look for the libata.atapi_enabled=1 or something option and add that to the module options, or the kernel boot command. Might have to add it to the initrd configuration and generate a new initrd with that option enabled. yaird has a config file where you can list modules to load, and modules options and such. Adding it to the kernel boot options might work too. SCSI subsystem initialized libata version 1.20 loaded. ata_piix :00:1f.2: version 1.05 ata_piix :00:1f.2: combined mode detected (p=0, s=1) GSI 17 sharing vector 0xB1 and IRQ 17 ACPI: PCI Interrupt :00:1f.2[A] -> GSI 18 (level, low) -> IRQ 17 PCI: Setting latency timer of device :00:1f.2 to 64 ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x1470 irq 14 ata1: dev 1 cfg 49:0f00 82:4210 83:4000 84:4000 85: 86: 87:4000 88:0407 ata1: dev 1 ATAPI, max UDMA/33 ata1: dev 1 configured for UDMA/33 scsi0 : ata_piix ata1(1): WARNING: ATAPI is disabled, device ignored. ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1478 irq 15 ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:207f ata2: dev 0 ATA-7, max UDMA/133, 488397168 sectors: LBA48 ata2: dev 0 configured for UDMA/133 scsi1 : ata_piix Vendor: ATA Model: WDC WD2500JS-00N Rev: 10.0 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) SCSI device sda: drive cache: write back SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 > sd 1:0:0:0: Attached scsi disk sda Yeah I think the libata.atapi_enabled option would help. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SUCCESS: Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Sun, Jan 08, 2006 at 10:42:20AM -0500, Stephen Woodbridge wrote: > Hi Len, > > Thank You! Thank you! Thank you! Using the kernel from sid did the > trick! I guess I was too focused on having to build a kernel to step > back from the problem and see that. Also the kernel-image to linux-image > tripped me up so I didn't see them in apt-cache search. > > I now can see the 3ware device as /dev/sdb but I seem to have lost the > CDROM drive again. I suppose the 2.6.15 wants the BIOS settings changed > again or I have run up against the problem that the CDROM seems to only > run as a slave device on the PATA IDE bus. > > Any idea what causes the: > > ata1(1): WARNING: ATAPI is disabled, device ignored. There is an option I think might have to be enabled. There is also a bug in 2.6.15 that I just read on lkml about 30 minutes ago, that on intel ICH controllers, PATA secondary slave is currently broken. primary master, primary slave, and secondary master all work, but no atapi on secondary slave. If your cdrom is secondary slave, change it. Otherwise look for the libata.atapi_enabled=1 or something option and add that to the module options, or the kernel boot command. Might have to add it to the initrd configuration and generate a new initrd with that option enabled. yaird has a config file where you can list modules to load, and modules options and such. Adding it to the kernel boot options might work too. > SCSI subsystem initialized > libata version 1.20 loaded. > ata_piix :00:1f.2: version 1.05 > ata_piix :00:1f.2: combined mode detected (p=0, s=1) > GSI 17 sharing vector 0xB1 and IRQ 17 > ACPI: PCI Interrupt :00:1f.2[A] -> GSI 18 (level, low) -> IRQ 17 > PCI: Setting latency timer of device :00:1f.2 to 64 > ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x1470 irq 14 > ata1: dev 1 cfg 49:0f00 82:4210 83:4000 84:4000 85: 86: 87:4000 > 88:0407 > ata1: dev 1 ATAPI, max UDMA/33 > ata1: dev 1 configured for UDMA/33 > scsi0 : ata_piix > ata1(1): WARNING: ATAPI is disabled, device ignored. > ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1478 irq 15 > ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 > 88:207f > ata2: dev 0 ATA-7, max UDMA/133, 488397168 sectors: LBA48 > ata2: dev 0 configured for UDMA/133 > scsi1 : ata_piix > Vendor: ATA Model: WDC WD2500JS-00N Rev: 10.0 > Type: Direct-Access ANSI SCSI revision: 05 > SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) > SCSI device sda: drive cache: write back > SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) > SCSI device sda: drive cache: write back > sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 > > sd 1:0:0:0: Attached scsi disk sda Yeah I think the libata.atapi_enabled option would help. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SUCCESS: Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Hi Len, Thank You! Thank you! Thank you! Using the kernel from sid did the trick! I guess I was too focused on having to build a kernel to step back from the problem and see that. Also the kernel-image to linux-image tripped me up so I didn't see them in apt-cache search. I now can see the 3ware device as /dev/sdb but I seem to have lost the CDROM drive again. I suppose the 2.6.15 wants the BIOS settings changed again or I have run up against the problem that the CDROM seems to only run as a slave device on the PATA IDE bus. Any idea what causes the: ata1(1): WARNING: ATAPI is disabled, device ignored. below: SCSI subsystem initialized libata version 1.20 loaded. ata_piix :00:1f.2: version 1.05 ata_piix :00:1f.2: combined mode detected (p=0, s=1) GSI 17 sharing vector 0xB1 and IRQ 17 ACPI: PCI Interrupt :00:1f.2[A] -> GSI 18 (level, low) -> IRQ 17 PCI: Setting latency timer of device :00:1f.2 to 64 ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x1470 irq 14 ata1: dev 1 cfg 49:0f00 82:4210 83:4000 84:4000 85: 86: 87:4000 88:0407 ata1: dev 1 ATAPI, max UDMA/33 ata1: dev 1 configured for UDMA/33 scsi0 : ata_piix ata1(1): WARNING: ATAPI is disabled, device ignored. ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1478 irq 15 ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:207f ata2: dev 0 ATA-7, max UDMA/133, 488397168 sectors: LBA48 ata2: dev 0 configured for UDMA/133 scsi1 : ata_piix Vendor: ATA Model: WDC WD2500JS-00N Rev: 10.0 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) SCSI device sda: drive cache: write back SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 > sd 1:0:0:0: Attached scsi disk sda Lennart Sorensen wrote: On Sat, Jan 07, 2006 at 05:07:10PM -0500, Stephen Woodbridge wrote: OK, I am making some progress ... I found this link and it seems pretty clean and straight forward. http://www.dominik-epple.de/Sarge-Linux_2.6.14-yaird/ and I have followed these steps except I'm using 2.6.15, ie: Backporting yaird, texi2html, make, kernel-package I spent all day going through menuconfig and follow an example config file the Andrew sent me. You can just skip building a new kernel and use the one from sid. You only need to get yaird and such rebuilt and installed, then you can use the prebuilt package for the kernel from sid. But when I try to compile the kernel it looks like it thinks it should be trying to cross compile. I'm wonder if it is somehow confused by the packages I backported? You are running amd64 right? Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Sat, Jan 07, 2006 at 09:26:21PM -0500, Stephen Woodbridge wrote: > Fixed the cross-compile problem by adding --arch=amd64 to the make-kpkg > command and the kernel compiles but of the package is strange and it > will not install. > > fakeroot make-kpkg --arch=amd64 --initrd --append-to-version=.20060107 > kernel-image Don't use a . at the start of your append to version. Use a - That way the kernel version will look sane (2.6.15, not 2.6.15.20060107) Apparently yaird does things based on the version of the kernel, and with your append, it has no clue what to make of it. I still suggest starting with just the prebuilt debian kernel instead. > The package name is: > > linux-image-2.6.15.20060107_2.6.15.20060107-10.00.Custom_amd64.deb > > which is strange because I gave the target as kernel-image not > linux-image and 2.6.15.20060107 is added to the name twice. > > and yaird failed on the install see below. New kernels are named linux-image nor kernel-image on debian. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Sat, Jan 07, 2006 at 05:07:10PM -0500, Stephen Woodbridge wrote: > OK, I am making some progress ... I found this link and it seems pretty > clean and straight forward. > > http://www.dominik-epple.de/Sarge-Linux_2.6.14-yaird/ > > and I have followed these steps except I'm using 2.6.15, ie: > > Backporting yaird, texi2html, make, kernel-package > > I spent all day going through menuconfig and follow an example config > file the Andrew sent me. You can just skip building a new kernel and use the one from sid. You only need to get yaird and such rebuilt and installed, then you can use the prebuilt package for the kernel from sid. > But when I try to compile the kernel it looks like it thinks it should > be trying to cross compile. I'm wonder if it is somehow confused by the > packages I backported? You are running amd64 right? Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Fixed the cross-compile problem by adding --arch=amd64 to the make-kpkg command and the kernel compiles but of the package is strange and it will not install. fakeroot make-kpkg --arch=amd64 --initrd --append-to-version=.20060107 kernel-image The package name is: linux-image-2.6.15.20060107_2.6.15.20060107-10.00.Custom_amd64.deb which is strange because I gave the target as kernel-image not linux-image and 2.6.15.20060107 is added to the name twice. and yaird failed on the install see below. -Steve [EMAIL PROTECTED]:/usr/src$ sudo dpkg -i linux-image-2.6.15.20060107_2.6.15.20060107-10.00.Custom_amd64.deb Password: Selecting previously deselected package linux-image-2.6.15.20060107. (Reading database ... 41199 files and directories currently installed.) Unpacking linux-image-2.6.15.20060107 (from linux-image-2.6.15.20060107_2.6.15.20060107-10.00.Custom_amd64.deb) ... Done. Setting up linux-image-2.6.15.20060107 (2.6.15.20060107-10.00.Custom) ... Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: unknown kernel version: 2.6.15.20060107 (fatal) mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.15.20060107 (--install): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.15.20060107 [EMAIL PROTECTED]:/usr/src$ sudo dpkg -P linux-image-2.6.15.20060107 (Reading database ... 41349 files and directories currently installed.) Removing linux-image-2.6.15.20060107 ... Running postrm hook /sbin/update-grub . Searching for GRUB installation directory ... found: /boot/grub . Purging configuration files for linux-image-2.6.15.20060107 ... Running postrm hook /sbin/update-grub . Searching for GRUB installation directory ... found: /boot/grub . dpkg: error processing linux-image-2.6.15.20060107 (--purge): subprocess post-removal script returned error exit status 128 Errors were encountered while processing: linux-image-2.6.15.20060107 Stephen Woodbridge wrote: OK, I am making some progress ... I found this link and it seems pretty clean and straight forward. http://www.dominik-epple.de/Sarge-Linux_2.6.14-yaird/ and I have followed these steps except I'm using 2.6.15, ie: Backporting yaird, texi2html, make, kernel-package I spent all day going through menuconfig and follow an example config file the Andrew sent me. But when I try to compile the kernel it looks like it thinks it should be trying to cross compile. I'm wonder if it is somehow confused by the packages I backported? $ fakeroot make-kpkg --initrd --append-to-version=.20060107 kernel-image [snip] /usr/bin/make EXTRAVERSION=.20060107 ARCH=x86_64 \ CROSS_COMPILE=x86_64-linux- bzImage make[1]: Entering directory `/usr/src/linux-2.6.15' CHK include/linux/version.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost HOSTCC scripts/kallsyms HOSTCC scripts/conmakehash CC init/main.o CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o CC init/do_mounts.o CC init/do_mounts_rd.o CC init/do_mounts_initrd.o LD init/mounts.o /bin/sh: line 1: x86_64-linux-ld: command not found make[2]: *** [init/mounts.o] Error 127 make[1]: *** [init] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.15' make: *** [debian/stamp-build-kernel] Error 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
OK, I am making some progress ... I found this link and it seems pretty clean and straight forward. http://www.dominik-epple.de/Sarge-Linux_2.6.14-yaird/ and I have followed these steps except I'm using 2.6.15, ie: Backporting yaird, texi2html, make, kernel-package I spent all day going through menuconfig and follow an example config file the Andrew sent me. But when I try to compile the kernel it looks like it thinks it should be trying to cross compile. I'm wonder if it is somehow confused by the packages I backported? $ fakeroot make-kpkg --initrd --append-to-version=.20060107 kernel-image [snip] /usr/bin/make EXTRAVERSION=.20060107 ARCH=x86_64 \ CROSS_COMPILE=x86_64-linux- bzImage make[1]: Entering directory `/usr/src/linux-2.6.15' CHK include/linux/version.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost HOSTCC scripts/kallsyms HOSTCC scripts/conmakehash CC init/main.o CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o CC init/do_mounts.o CC init/do_mounts_rd.o CC init/do_mounts_initrd.o LD init/mounts.o /bin/sh: line 1: x86_64-linux-ld: command not found make[2]: *** [init/mounts.o] Error 127 make[1]: *** [init] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.15' make: *** [debian/stamp-build-kernel] Error 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Fri, Jan 06, 2006 at 06:37:43PM -0500, Stephen Woodbridge wrote: > Lennart Sorensen wrote: > >On Fri, Jan 06, 2006 at 01:11:04AM -0500, Stephen Woodbridge wrote: > > > >>Tried to build my first kernel, but no joy. This is what I did ... > >> > >>cd /usr/src > >>wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2 > > > > > >Try getting the linux-source package from unstable instead. It has > >debian's patches and such. You can also get the config file from one of > >the newer kernels for your cpu as a start for oldconfig. It's a big > >jump from 2.6.8 to 2.6.15. A lot has changed. > > > >For that matter, you could probably see if there is a new linux-image > >package already for your cpu in unstable. Would be even simpler. > > > >Len Sorensen > > > > I tried to install it: > > sudo apt-get install linux-image-2.6.15-1-em64t-p4-smp > > The following packages have unmet dependencies: > linux-image-2.6.15-1-em64t-p4-smp: Depends: yaird but it is not going > to be installed or > initramfs-tools but it is > not going to be installed or > linux-initramfs-tool > > I tried to install yaird: > > sudo apt-get install yaird > > The following packages have unmet dependencies: > yaird: Depends: libc6 (>= 2.3.5-1) but 2.3.2.ds1-22 is to be installed > > yaird is at backports.org but there are no amd64 arch packages at > backports.org. > > Someone mentioned back porting yaird, how would I go about doing that if > that is the right thing to do? apt-get source -b yaird If it has any build dependancies, do those too. It only depends on libc6 2.3.5-1 because it was build on sid not sarge. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Lennart Sorensen wrote: On Fri, Jan 06, 2006 at 01:11:04AM -0500, Stephen Woodbridge wrote: Tried to build my first kernel, but no joy. This is what I did ... cd /usr/src wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2 Try getting the linux-source package from unstable instead. It has debian's patches and such. You can also get the config file from one of the newer kernels for your cpu as a start for oldconfig. It's a big jump from 2.6.8 to 2.6.15. A lot has changed. For that matter, you could probably see if there is a new linux-image package already for your cpu in unstable. Would be even simpler. Len Sorensen I tried to install it: sudo apt-get install linux-image-2.6.15-1-em64t-p4-smp The following packages have unmet dependencies: linux-image-2.6.15-1-em64t-p4-smp: Depends: yaird but it is not going to be installed or initramfs-tools but it is not going to be installed or linux-initramfs-tool I tried to install yaird: sudo apt-get install yaird The following packages have unmet dependencies: yaird: Depends: libc6 (>= 2.3.5-1) but 2.3.2.ds1-22 is to be installed yaird is at backports.org but there are no amd64 arch packages at backports.org. Someone mentioned back porting yaird, how would I go about doing that if that is the right thing to do? -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Fri, Jan 06, 2006 at 01:11:04AM -0500, Stephen Woodbridge wrote: > Tried to build my first kernel, but no joy. This is what I did ... > > cd /usr/src > wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2 Try getting the linux-source package from unstable instead. It has debian's patches and such. You can also get the config file from one of the newer kernels for your cpu as a start for oldconfig. It's a big jump from 2.6.8 to 2.6.15. A lot has changed. For that matter, you could probably see if there is a new linux-image package already for your cpu in unstable. Would be even simpler. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
