Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] SATA drives

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: John T Copeland <johnc AT neto.com>
  • To: Andrej Hosna <adispam AT ibl.sk>
  • Cc: sm-discuss <sm-discuss AT lists.ibiblio.org>
  • Subject: Re: [SM-Discuss] SATA drives
  • Date: Tue, 30 Sep 2003 12:51:16 -0500

On Tuesday 30 September 2003 12:40 am, Andrej Hosna wrote:
> > I have SATA Western Digital working very well under kernel 2.4.22. I use
> > motherboard Abit NF7-S which has the Sil3112a controller. Earlier kernel
> > versions would, 2.4.21, would recognize the SIL3112A controller, but
> > leave the disk in PIO mode. 2.4.22 recognizes the controller and sets it
> > to UDMA-133. You have to rebuild the kernel and set all the Nvidia
> > configs in "make menuconfig" to get it to work right. The NF7-S mobo has
> > the nforce2 chipset for which 2.4.22 has native support.
> >
> > Only problem with the SATA is the disk busy LED will not light when disk
> > is busy! Funny thing is Win2K does light the LED when accessing the
> > SATA disk. Probably a problem in the SIL3112A driver. Don't know.
>
> I was not able to make this running although I have gigbyte motherboard
> with athlon-xp cpu -> VIA chipset. I configured sii to be built as module
> buf it i try to insmod i get:
> SiI3112 Serial ATA: IDE controller at PCI slot 00:08.0
> SiI3112 Serial ATA: chipset revision 2
> SiI3112 Serial ATA: not 100% native mode: will probe irqs later
> ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
> ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
> Nothing else about disks is present in dmesg (i have seagate 120GB disk
> connected to SATA and it's properly detected by POST BIOS routines)
> Do you have any idea what am i doing wrong ? How do you access discs
> connected to SATA ? it's not in /dev/discs/ nor in /dev/scsi.
> I forgot to tell I have linux-2.4.22 with -ac4 and -libata1 patches.
> Andrej
On my system, drives show up as /dev/{hda, hdb, hdc, hdd, hde}. The hde is
the SATA driver. All these devices show up in /proc/ide. Your SATA drive
should show up as /dev/hde. These devices SHOULD show in dmesg. In my dmesg
I get:
SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
SiI3112 Serial ATA: chipset revision 2
SiI3112 Serial ATA: not 100% native mode: will probe irqs later
ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
hda: IC35L020AVER07-0, ATA DISK drive
hdb: IC35L020AVER07-0, ATA DISK drive
blk: queue c02f2920, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c02f2a5c, I/O limit 4095Mb (mask 0xffffffff)
hdc: PLEXTOR CD-R PX-W2410A, ATAPI CD/DVD-ROM drive
hdd: IOMEGA ZIP 250 ATAPI, ATAPI FLOPPY drive
hdd: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hdd: set_drive_speed_status: error=0x04
ide1: Drive 1 didn't accept speed setting. Oh, well.
hde: WDC WD360GD-00FNA0, ATA DISK drive
blk: queue c02f31c8, I/O limit 4095Mb (mask 0xffffffff)
hdg: no response (status = 0xfe)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xe0838080-0xe0838087,0xe083808a on irq 11
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 40188960 sectors (20577 MB) w/1916KiB Cache, CHS=2501/255/63, UDMA(100)
hdb: host protected area => 1
hdb: 40188960 sectors (20577 MB) w/1916KiB Cache, CHS=2501/255/63, UDMA(100)
hde: attached ide-disk driver.
hde: host protected area => 1
hde: 72303840 sectors (37020 MB) w/8192KiB Cache, CHS=4500/255/63, UDMA(133)
hdd: attached ide-scsi driver.
hdc: attached ide-scsi driver.
Partition check:
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 >
/dev/ide/host0/bus0/target1/lun0: p1 < p5 p6 p7 p8 p9 >
/dev/ide/host2/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 >
end dmesg
First device above is hda, then hdb, then hde(SATA)

It appears you use the devfs filesystem, and if so do you run devfsd to
create
the old devices in /dev. The only other possibility I can think of is
something isn't set right in the kernel config. Offhand, I can only think of
the SIL3112A enable and the VIA chipset enable.
JohnC





Archive powered by MHonArc 2.6.24.

Top of Page