Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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 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. I skipped installing LILO since booting on this drive is already managed by LILO installed by Xandros 4.
I added the following entry for Slackware to Xandros' lilo.conf:
When I try to boot Slackware from the Xandros LILO menu, the system quickly crashes with a kernel panic: the kernel can't find the root filesystem. The root fs is on sda8 which is a logical partition underneath an extended primary partition.
The above LILO entry is completely analogous to a LILO entry for Zenwalk 3.0 installed on the same drive (on sda6) that allows me to boot Zenwalk just fine. The Zenwalk kernel is the default sata kernel; the version is 2.6.17.11.
The Slackware installation proceeded without error, and the files are all there on sda8; I can view them from Xandros. One thing that struck me as odd though during the installation was the fact that when inquiring which partition to choose for the / (root) partition and in the section on constructing the entries for fstab, the installer referred to all partitions on the SATA drive as hdaX, never as sdaX as would have been correct.
What went 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?
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. I skipped installing LILO since booting on this drive is already managed by LILO installed by Xandros 4.
I added the following entry for Slackware to Xandros' lilo.conf:
When I try to boot Slackware from the Xandros LILO menu, the system quickly crashes with a kernel panic: the kernel can't find the root filesystem. The root fs is on sda8 which is a logical partition underneath an extended primary partition.
The above LILO entry is completely analogous to a LILO entry for Zenwalk 3.0 installed on the same drive (on sda6) that allows me to boot Zenwalk just fine. The Zenwalk kernel is the default sata kernel; the version is 2.6.17.11.
The Slackware installation proceeded without error, and the files are all there on sda8; I can view them from Xandros. One thing that struck me as odd though during the installation was the fact that when inquiring which partition to choose for the / (root) partition and in the section on constructing the entries for fstab, the installer referred to all partitions on the SATA drive as hdaX, never as sdaX as would have been correct.
What went 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?
Robert
Hi,
Why are you using the append in your stanza;
Quote:
added the following entry for Slackware to Xandros' lilo.conf:
A good stanza example;
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.31
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends
#
I use the append to pass arguements to the kernel. Your append is not correct. Your getting the panic because of the 'root=' not being defined in the stanza.
The -current changelog uses;
Code:
Sat Aug 19 23:58:27 CDT 2006
This is mostly frozen now unless bugs (or irresistible upgrades) come up, so
I'll call this update Slackware 11.0 release candidate 2. :-)
a/kernel-ide-2.4.33-i486-2.tgz:
Switched to the sata.i kernel which supports both parallel and serial ATA.
a/kernel-modules-2.4.33-i486-2.tgz: Recompiled.
Upgraded to Linux 2.4.33 kernel modules.
So both type of drives have been include in this kernel 2.4.33.
I had the same problem with it: kernel panic. Then I switched to the stanza I'd posted because it's essentially identical to the stanza that works fine for the Zenwalk (a Slackware derivative) install on the same drive.
I can't help thinking that the problem revolves around the fact that the Slackware installer identified/labelled the partitions on the internal SATA drive as hdaX rather than sdaX. The default sata kernel v.2.6.17.11 used by the Zenwalk installer (which is a slightly streamlined Slackware installer) identified/labelled the partitions correctly as sdaX.
E.g. the fstab generated by the Slackware installer looks as follows:
This looks wrong; there are no hdaX partitions (I'd entered the mount points as hdaX, simply to be consistent with this labeling scheme).
E.g. when I modify the line "root=/dev/sda8" in lilo.conf to "root=/dev/hda8", I get the error: "Fatal: Illegal 'root=' specification: /dev/hda8", when I run lilo.
I had the same problem with it: kernel panic. Then I switched to the stanza I'd posted because it's essentially identical to the stanza that works fine for the Zenwalk (a Slackware derivative) install on the same drive.
I can't help thinking that the problem revolves around the fact that the Slackware installer identified/labelled the partitions on the internal SATA drive as hdaX rather than sdaX. The default sata kernel v.2.6.17.11 used by the Zenwalk installer (which is a slightly streamlined Slackware installer) identified/labelled the partitions correctly as sdaX.
E.g. the fstab generated by the Slackware installer looks as follows:
This looks wrong; there are no hdaX partitions (I'd entered the mount points as hdaX, simply to be consistent with this labeling scheme).
E.g. when I modify the line "root=/dev/sda8" in lilo.conf to "root=/dev/hda8", I get the error: "Fatal: Illegal 'root=' specification: /dev/hda8", when I run lilo.
At the very 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 was not working for me. It was misidentifying the SATA drive partitions as hdaX, rather than sdaX.
In another thread that I initiated on this problem (a.o.l.s.), one person replied that "there are two different sata modules used in 2.4.x series, one identifies the drives as hda and the other as sda."
Another person said: "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."
In the end, I decided to boot the install CD with the huge26.s kernel and then install kernel-generic-smp-2.6.17.13-i686-1.tgz and kernel-modules-smp-2.6.17.13-i686-1.tgz, since I have a dual core processor and would like to use that capability.
In the description of this generic SMP kernel v.2.6.17.13, PV says that it has no built-in reiserfs support, hence I had to build an initrd to insert the extra reiserfs module. Finally, in /etc/fstab I changed all the device names from /dev/hdaX to /dev/sdaX.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.