SlackwareThis Forum is for the discussion of Slackware Linux.
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 have an A7N8X-Deluxe (nForce2) motherboard with a 160GB and an 80GB drive running off of the SIL3112 SATA ports. Slackware 10 installed and ran on this just fine (installed with bareacpi.i 2.4.26). I am trying to install Slackware 10.1 and am running into a brick wall. The installer boots just fine using bareacpi.i except my drives are nowhere to be found. If I boot with the sata.i kernel, my PATA CD-ROM drives are detected, then ATA1 and ATA2 are detected and the system hangs. The last line says :
ATA1: SATA max UDMA/100 cmd 0xF880D080 ... (missed the rest)
I do not know where to go from here, short of compiling a new kernel on another system. (I have yet to compile a kernel though.) Does anyone have a relatively simple solution?
Originally posted by CygnusX1200 Won't the upgrade install the 2.4.29 kernel? If so, will it not be just as broken with SATA as the installation kernerls for 10.1?
What is broken about SATA support in Slack-10.1?
Looking at the .config file for sata.i there is:
Code:
file:/mnt/dvd/kernels/sata.i/config
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_DEBUG_QUEUES=y
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
<snip>
CONFIG_SCSI_SATA=y
<snip>
CONFIG_SCSI_SATA_SIL=y
These three things should enable your SATA drive.
What is the problem you're having that causes you
to say SATA is broken?
Edit: See this thread
He installed Slack-10.1 to a SATA drive with no problem,
once he'd chosen the sata.i kernel...
Last edited by Bruce Hill; 02-08-2005 at 06:25 PM.
As stated in my original post, bareacpi.i = installer boots just fine, however, my disks are nowhere to be found. sata.i = hang immediately after it detects the disks.
Why is it broken? Because it isn't working!
The A7N8X has SIL3112 SATA controllers. I quote the following from the changelog (which doesn't mean much to me at this point...i.e. I don't know enough to know where to go now which is why I am here!):
Thu Sep 23 18:11:17 PDT 2004
kernels/sata.i/: Removed Silicon Image ATA support since it interferes
with the libata SATA driver. This also removes support for the PATA
CMD640 chipset, since that's part of the old Silicon Image ATA driver.
Thanks to Miha Verlic for pointing out this incompatibility.
Quote:
Originally posted by Chinaman Edit: See this thread
He installed Slack-10.1 to a SATA drive with no problem,
once he'd chosen the sata.i kernel... [/B]
As I said if you have a running 10.0 slackware system, all you need to do to have
10.1 installed, is upgrade the system (the modules and kernel won't be deleted)
After the upgrade, just cd /boot and
rm System.map vmlinuz
ln -s vmlinuz-2.4.26 vmlinuz
ln-s System.map-2.4.26 System.map
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.