Skip to contentSkip to conversation

sata-via : bug?

SATA Jay Roplekar 2 participants 4 messages Mar 21, 2005 – Mar 24, 2005

lore
Share & tools
lore
#0 lore raw

I have a brand new Western Digital sata drive, VIA KT600 based ECS motherboard on which I am trying to install various distros (with installers based on 2.4.26, 2.6.7, 2.6.8, 2.6.11 etc) all of them fail to detect the HD (and bomb out) because sata-via is ignoring it . I have only one disk, I am not interested in raid.

lspci which tells me it is VIA 6420 and should be supported based on
sata-via.c. Following are syslog snippets that show more.
I would appreciate your help in resolving this. Thanks,

Jay
##
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000a000-0000afff
Memory behind bridge: e0000000-e1ffffff
Prefetchable memory behind bridge: d8000000-dfffffff
Capabilities: [80] Power Management version 2

00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)

        Subsystem: Elitegroup Computer Systems: Unknown device 1884
        Flags: bus master, medium devsel, latency 32, IRQ 11
        I/O ports at b000 [size=8]
        I/O ports at b400 [size=4]
        I/O ports at b800 [size=8]
        I/O ports at bc00 [size=4]
        I/O ports at c000 [size=16]
        I/O ports at c400 [size=256]
        Capabilities: [c0] Power Management version 2

##Dmesg when I connect the disk on channel 1
libata version 1.10 loaded.
sata_via version 1.1
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 11 (level, low) -> IRQ 11 sata_via(0000:00:0f.0): routed to hard irq line 11
ata1: SATA max UDMA/133 cmd 0xB000 ctl 0xB402 bmdma 0xC000 irq 11
ata2: SATA max UDMA/133 cmd 0xB800 ctl 0xBC02 bmdma 0xC008 irq 11
ata1: dev 0 cfg 49:3030 82:0078 83:0078 84:0000 85:0000 86:3fff 87:0010 88:000f
ata1: no dma/lba
ata1: dev 0 not supported, ignoring
scsi0 : sata_via
ata2: no device found (phy stat 00000000)
scsi1 : sata_via
##with disk on second channel following
ata1: no device found (phy stat 00000000)
scsi0 : sata_via
ata2: dev 0 cfg 49:3030 82:0078 83:0078 84:0078 85:0000 86:0000 87:0000 88:0000
ata2: no dma/lba
ata2: dev 0 not supported, ignoring
scsi1 : sata_via
## I took this disk and sata cable on a different (ICH5 based) motherboard and ## knoppix detected the disk ok and associated sda with it.

#1 lore raw
Quoted 49 lines · Jay Roplekar

I have a brand new Western Digital sata drive, VIA KT600 based ECS motherboard on which I am trying to install various distros (with installers based on 2.4.26, 2.6.7, 2.6.8, 2.6.11 etc) all of them fail to detect the HD (and bomb out) because sata-via is ignoring it . I have only one disk, I am not interested in raid.

lspci which tells me it is VIA 6420 and should be supported based on
sata-via.c. Following are syslog snippets that show more.
I would appreciate your help in resolving this. Thanks,

Jay
##
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000a000-0000afff
Memory behind bridge: e0000000-e1ffffff
Prefetchable memory behind bridge: d8000000-dfffffff
Capabilities: [80] Power Management version 2

00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)

        Subsystem: Elitegroup Computer Systems: Unknown device 1884
        Flags: bus master, medium devsel, latency 32, IRQ 11
        I/O ports at b000 [size=8]
        I/O ports at b400 [size=4]
        I/O ports at b800 [size=8]
        I/O ports at bc00 [size=4]
        I/O ports at c000 [size=16]
        I/O ports at c400 [size=256]
        Capabilities: [c0] Power Management version 2

##Dmesg when I connect the disk on channel 1
libata version 1.10 loaded.
sata_via version 1.1
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 11 (level, low) -> IRQ 11 sata_via(0000:00:0f.0): routed to hard irq line 11
ata1: SATA max UDMA/133 cmd 0xB000 ctl 0xB402 bmdma 0xC000 irq 11
ata2: SATA max UDMA/133 cmd 0xB800 ctl 0xBC02 bmdma 0xC008 irq 11
ata1: dev 0 cfg 49:3030 82:0078 83:0078 84:0000 85:0000 86:3fff 87:0010 88:000f
ata1: no dma/lba
ata1: dev 0 not supported, ignoring
scsi0 : sata_via
ata2: no device found (phy stat 00000000)
scsi1 : sata_via
##with disk on second channel following
ata1: no device found (phy stat 00000000)

Quoted 8 lines

scsi0 : sata_via
ata2: dev 0 cfg 49:3030 82:0078 83:0078 84:0078 85:0000 86:0000 87:0000 88:0000
ata2: no dma/lba
ata2: dev 0 not supported, ignoring
scsi1 : sata_via
## I took this disk and sata cable on a different (ICH5 based) motherboard and ## knoppix detected the disk ok and associated sda with it.

Any modes in the bios for the SATA ports? Maybe it is in a mode not supported by linux. I know the ICH5 only wanted to work for me in native (enhanced?) mode, not compatible (emulating PATA) mode. Maybe via does something similar. I am puzzles by the UDMA/133 message which makes no sense for SATA which should be 150 or 300 not 133.

Len Sorensen

#2 lore raw
Quoted 9 lines

Any modes in the bios for the SATA ports? Maybe it is in a mode not supported by linux. I know the ICH5 only wanted to work for me in native (enhanced?) mode, not compatible (emulating PATA) mode. Maybe via does something similar. I am puzzles by the UDMA/133 message which makes no sense for SATA which should be 150 or 300 not 133.

Len Sorensen

Len,

Thanks for the suggestion but I do not have any option of turning any modes on in the BIOS.
At this point I am thinking/hoping that this is quirk introduced by mobo that is triggering this behavior in the driver that can be fixed by somebody easily. Although I do not have the skill set to device a solution.

Jay

#3 lore raw

Re: [SATA] sata-via : bug?(Closed No Bug)

In reply to Lennart Sorensen

This turns out to be a motheboard/bios issue + my lack of careful thinking.
And the driver seems to work ok so far. Sorry for the false alarm..

Jay Roplekar