Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Hardware
User Name
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?


  Search this Thread
Old 02-18-2007, 11:52 PM   #1
Registered: Jul 2006
Location: Hamburg, Germany
Distribution: Debian, CentOS
Posts: 297

Rep: Reputation: 31
Unhappy Problems viewing sata HD at Slackware11.0

I'm having problems with my new Seagate 120gb SATA harddisk.
I'm using Slackware 11.0 on Kernel 2.6.18. P4S800D-X motherboard.

I wanna use this SATA as slave, it seems it's booting, however I cannot see any /dev/sda*

As I said, seems it is booting:

bash-3.1# dmesg | grep ata
BIOS-e820: 000000001ffb0000 - 000000001ffc0000 (ACPI data)
Memory: 515940k/523968k available (1852k kernel code, 7480k reserved, 717k data, 168k init, 0k highmem)
ReiserFS: hda5: using ordered data mode
libata version 2.00 loaded.
sata_sis 0000:00:05.0: version 0.6
sata_sis 0000:00:05.0: Detected SiS 180/181 chipset in SATA mode
ata1: SATA max UDMA/133 cmd 0xEFF0 ctl 0xEFE6 bmdma 0xEF90 irq 20
ata2: SATA max UDMA/133 cmd 0xEFA8 ctl 0xEFE2 bmdma 0xEF98 irq 20
scsi0 : sata_sis
ata1: SATA link down (SStatus 0 SControl 300)
scsi1 : sata_sis
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-6, max UDMA/133, 234441648 sectors: LBA48 NCQ (depth 0/32)
ata2.00: ata2: dev 0 multi count 16
ata2.00: configured for UDMA/133

bash-3.1# lspci | grep SATA
00:05.0 RAID bus controller: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] (rev 01)

bash-3.1# lsmod | grep sata
sata_sis 5508 0
libata 76692 1 sata_sis

as I said, everything seems fine, however I cannot see any /dev/sda*
even when I do "fdisk -l" I see no sda*.

Someone has any idea about what is happening here?
Old 02-19-2007, 02:38 AM   #2
Registered: Jan 2006
Location: India
Distribution: Fedora 7, Linuxfromscratch 6.2
Posts: 66

Rep: Reputation: 15
Have you configured the drive as slave?

The extreme end of your data cable should go into your primary drive and the middle connecter into the slave drive if you are using a colour coded cable. The jumper should be left in the 'cable select' position. (this is for a non-SATA drive, i'm not sure if it's the same for a SATA drive)
Old 02-22-2007, 11:08 AM   #3
Registered: Jul 2006
Location: Hamburg, Germany
Distribution: Debian, CentOS
Posts: 297

Original Poster
Rep: Reputation: 31
I've found the problem by myself and I would like to share it with the community.

A kernel recompilation would be necessarry:

# cd /usr/src/linux-2.6.*.*/
# make menuconfig

SCSI device support ---->[*] Raid transport Class

SCSI Low-Level Drivers --->[*] Serial ATA (SATA) support[*] SIS 964/180 SATA support (NEW)

Now my SATA harddisk finally works.


sata, sda

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrading Glibc for Slackware11 easuter Slackware 3 01-07-2007 02:44 PM
Why can't I find /etc/inetd.conf in Slackware11.0? naihe2010 Linux - Server 4 11-19-2006 05:44 PM
amsn not working on slackware11.0 arubin Slackware 6 10-30-2006 09:47 PM
dual monitor problem in slackware11 pkalakota Slackware 1 10-30-2006 01:14 PM
slackware11 alsaconfig yakoub Slackware - Installation 1 10-05-2006 06:27 AM > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 09:34 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration