Can't boot Slackware 11 - sda/hda confusion?
in [Slackware]
|
Prev: 2nd hard drive
Next: gtk-gnutella
From: Robert Glueck on 18 Sep 2006 18:14 dfisek(a)gmail.com wrote: > Robert Glueck yazdi: > ... >> What's wrong and how can I fix it? Did I pick the wrong >> kernel, or does the 2.4.33 kernel have trouble with SATA drives? > There are two different sata modules used in 2.4.x series, one > identifies the drives as hda and the other as sda. > > If you are reluctant to use 2.4.x kernel with Slackware, you may try > installing grub, that way you wouldn't have the naming problem with the > boot manager. > > Or you could try using 2.6.x kernel with Slackware, all you have to do > is boot with huge26.s during installation, choose that kernel from > cdrom for kernel installation and then install the related > linux-modules package from extra after installation. > > - dfisek > I don't particularly care whether I use a 2.4.x or 2.6.x kernel, I just want a kernel that works. Although I have to say that this laptop is a very recent model, issued only about four months ago, and I need to rely on wireless networking with hardware that only runs with a Windows driver via ndiswrapper. My own experience has been that older kernels and older versions of ndiswrapper poorly support many recent wireless chipsets. Also, I would prefer running a kernel with SMP support. Finally, I'd also prefer to stay with the LILO installed by Xandros. If I have to opt for the huge26.s kernel, would that entail installing Slackware all over again? Or is there a way of merely replacing the present kernel with the new kernel? Also, would that new kernel support a dual-core processor (SMP)? Finally, which related linux-modules package would I have to install from extra after installing the new kernel? Robert
From: Robert Glueck on 18 Sep 2006 18:35 Grant wrote: > On Mon, 18 Sep 2006 17:34:00 -0400, Robert Glueck <rglk(a)web.de> wrote: > >> There is only one "sata" kernel in the /cdrom/kernels/ >> directory, i.e. "sata.i", and the file >> /cdrom/kernels/SATA-SUPPORT.TXT says that this kernel has >> SATA support built into it. > > $ grep SATA /boot/config-ide-2.4.33.3 > # CONFIG_BLK_DEV_IDE_SATA is not set > CONFIG_SCSI_SATA=y > CONFIG_SCSI_SATA_AHCI=y > CONFIG_SCSI_SATA_SVW=y > CONFIG_SCSI_SATA_NV=y > CONFIG_SCSI_SATA_QSTOR=y > CONFIG_SCSI_SATA_PROMISE=y > CONFIG_SCSI_SATA_SX4=y > CONFIG_SCSI_SATA_SIL=y > CONFIG_SCSI_SATA_SIS=y > CONFIG_SCSI_SATA_ULI=y > CONFIG_SCSI_SATA_VIA=y > CONFIG_SCSI_SATA_VITESSE=y > > slack-11: things have changed ;) > > Grant. Grant, what does this output say? Does it say that all these SATA support modules are built into the vmlinuz-ide-2.4.33.3 kernel that I installed? If that is so why then am I running into this problem of presumed lack of SATA support with this kernel on my system? Robert
From: Grant on 18 Sep 2006 19:21 On Mon, 18 Sep 2006 18:35:33 -0400, Robert Glueck <rglk(a)web.de> wrote: >Grant wrote: >> On Mon, 18 Sep 2006 17:34:00 -0400, Robert Glueck <rglk(a)web.de> wrote: >> >>> There is only one "sata" kernel in the /cdrom/kernels/ >>> directory, i.e. "sata.i", and the file >>> /cdrom/kernels/SATA-SUPPORT.TXT says that this kernel has >>> SATA support built into it. >> >> $ grep SATA /boot/config-ide-2.4.33.3 >> # CONFIG_BLK_DEV_IDE_SATA is not set >> CONFIG_SCSI_SATA=y >> CONFIG_SCSI_SATA_AHCI=y >> CONFIG_SCSI_SATA_SVW=y >> CONFIG_SCSI_SATA_NV=y >> CONFIG_SCSI_SATA_QSTOR=y >> CONFIG_SCSI_SATA_PROMISE=y >> CONFIG_SCSI_SATA_SX4=y >> CONFIG_SCSI_SATA_SIL=y >> CONFIG_SCSI_SATA_SIS=y >> CONFIG_SCSI_SATA_ULI=y >> CONFIG_SCSI_SATA_VIA=y >> CONFIG_SCSI_SATA_VITESSE=y >> >> slack-11: things have changed ;) >> >> Grant. > >Grant, what does this output say? Does it say that all >these SATA support modules are built into the >vmlinuz-ide-2.4.33.3 kernel that I installed? Yes > If that is so >why then am I running into this problem of presumed lack of >SATA support with this kernel on my system? If you have a very new mobo, you might need 2.6 kernel for SATA support, recent discussions on lkml concluded that there cannot be another merge of SATA code backported to 2.4 series as there's now too much divergence. Therefore the new mobos and chipsets will only be supported by 2.6 series kernel. Grant. -- http://bugsplatter.mine.nu/
From: Douglas Mayne on 18 Sep 2006 20:36 On Mon, 18 Sep 2006 17:34:00 -0400, Robert Glueck wrote: > Douglas Mayne wrote: >> On Mon, 18 Sep 2006 13:34:43 -0400, Robert Glueck wrote: >> >>> I installed Slackware v.11 (-current from 9/11/06) on a Dell >>> Inspiron 6400 laptop with Intel Core Duo processor and an >>> internal SATA hard disk drive. I picked the sata.i kernel >>> both for the installation and for running the installed >>> system; the kernel version is 2.4.33.3. >> <snip> >>> I added the following stanza for Slackware to Xandros' >>> lilo.conf: >>> >>> image=/disks/welcome_2/boot/vmlinuz-ide-2.4.33.3 >>> label=Slackware_11_on_sda8 >>> root=/dev/sda8 >>> read-only >> >> That looks like the generic kernel to me, not the sata kernel you >> mentioned earlier. Replace with the correct kernel, or build an >> appropriate initrd. For 2.6.x kernels, I think the module you need is >> ata_piix. I don't know which module for the 2.4.x kernel, but the newer >> 2.6.x kernel worked better for me with similar hardware (Dell Latitude >> D610). >> <snip> >> Note: comments inline. >> > > Well, what can I say? :-) At the beginning of the > installation I picked the "default" installation kernel > which was called "sata.i". After all the packages were > installed, I was asked to "Choose Linux Kernel", and here I > picked the highlighted choice which was > "/cdrom/kernels/sata.i/bzImage", assuming that this was the > same kernel that I picked as the installation kernel. > > There is only one "sata" kernel in the /cdrom/kernels/ > directory, i.e. "sata.i", and the file > /cdrom/kernels/SATA-SUPPORT.TXT says that this kernel has > SATA support built into it. After making the above choices, > the vmlinuz-ide-2.4.33.3 kernel is what I found installed on > my system. Obviously, this kernel is not working for me. > > Robert > I may have initially given you bad advice, due to recent changes in how the Slackware kernel is being configured by default. For older 2.6.x kernels, I think your laptop needs the ahci and ata_piix modules to work. For newer kernels, such as http://www.slackware.at/data/slackware-current/extra/linux-2.6.17.13/ The kernel might work "out of the box" (based on looking at the config file.) Sorry for my earlier mistake. -- Douglas Mayne
From: Robby Workman on 18 Sep 2006 21:08
On 2006-09-18, Robert Glueck <rglk(a)web.de> wrote: > > If I have to opt for the huge26.s kernel, would that entail > installing Slackware all over again? Or is there a way of > merely replacing the present kernel with the new kernel? Boot into your existing system (with the installer disk if need be - there's information on how to do so when the cd boots) and install the following: extra/linux-smp-2.6.17.13/kernel-generic-smp-2.6.17.13-i686-1.tgz extra/linux-smp-2.6.17.13/kernel-modules-smp-2.6.17.13-i686-1.tgz If you are using ReiserFS as your root filesystem, you will need to make an initrd, as that support is included as a module in this kernel. > Also, would that new kernel support a dual-core processor (SMP)? See above. :) > Finally, which related linux-modules package would I have to > install from extra after installing the new kernel? See above. :) In closing, I would prefer to build a custom kernel if I were in your situation, but that's entirely up to you. It doesn't have to be a complicated procedure - install the kernel-source-2.6.17.13 package, copy this file extra/source/linux-smp-2.6.17.13/config-generic-smp-2.6.17.13 to $KERNEL_SOURCE_DIR/.config and do 'make menuconfig' to add ReiserFS support statically. The rest is routine... :) RW -- http://rlworkman.net |