* Asus M2V-MX SE (VIA K8T890): SATA-II disk only detected as UDMA/100
[not found] <1308508217.4141.20.camel@mattotaupa>
@ 2011-06-22 13:56 ` Paul Menzel
2011-06-23 0:22 ` Jeff Garzik
2011-06-24 5:08 ` Robert Hancock
0 siblings, 2 replies; 3+ messages in thread
From: Paul Menzel @ 2011-06-22 13:56 UTC (permalink / raw)
To: linux-ide
[-- Attachment #1: Type: text/plain, Size: 6307 bytes --]
Dear SATA subsystem folks,
please keep my address in CC list since I am not subscribed.
This is a reply to my message to the coreboot list [1] and I am adding
more current information to it.
Am Sonntag, den 19.06.2011, 20:30 +0200 schrieb Paul Menzel:
the ASUS M2V-MX SE HAS A VIA K8T890 chipset and the following BIOS
version is used.
> $ sudo dmidecode
> […]
> # dmidecode 2.9
> SMBIOS 2.4 present.
> 49 structures occupying 1801 bytes.
> Table at 0x000F0740.
>
> Handle 0x0000, DMI type 0, 24 bytes
> BIOS Information
> Vendor: American Megatrends Inc.
> Version: 0304
> Release Date: 10/30/2007
> Address: 0xF0000
> Runtime Size: 64 kB
> ROM Size: 512 kB
> […]
>
> I had to replace my hard drive and bought a new SATA-II disk.
> Unfortunately the full speed is not detected. Instead of UDMA/133 – as
> was used with the old SATA-I disk – it is reporting UDMA/100.
>
> $ uname -a
> Linux joe 2.6.32-5-amd64 #1 SMP Tue Mar 8 22:49:26 UTC 2011 x86_64 GNU/Linux
> $ dmesg # new SATA-II disk
> […]
> [ 0.792878] ata3: SATA max UDMA/133 cmd 0xec00 ctl 0xe880 bmdma 0xe400 irq 21
> [ 0.792881] ata4: SATA max UDMA/133 cmd 0xe800 ctl 0xe480 bmdma 0xe408 irq 21
> […]
> [ 1.384015] ata4: SATA link up 1.5 Gbps (SStatus 123 SControl 300)
> [ 1.392019] usb 2-1: new low speed USB device using uhci_hcd and address 2
> [ 1.548219] ata4.00: ATA-8: WDC WD20EARS-60MVWB0, 51.0AB51, max UDMA/100
>
> Here seems to be the problematic line, that somehow the drive is
> reporting the wrong maximum speed or the chipset does not detect it
> correctly.
>
> [ 1.548223] ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32)
> [ 1.556240] ata4.00: configured for UDMA/100
> [ 1.556343] scsi 3:0:0:0: Direct-Access ATA WDC WD20EARS-60M 51.0 PQ: 0 ANSI: 5
> […]
> $ dmesg # old SATA-I disk
> [ 0.779300] ata1: SATA max UDMA/133 cmd 0xec00 ctl 0xe880 bmdma 0xe400 irq 21
> [ 0.779303] ata2: SATA max UDMA/133 cmd 0xe800 ctl 0xe480 bmdma 0xe408 irq 21
> […]
> [ 0.980024] ata1: SATA link up 1.5 Gbps (SStatus 123 SControl 300)
> [ 0.980427] ata3.00: configured for UDMA/33
> [ 1.144418] ata1.00: ATA-8: Hitachi HDP725050GLA360, GM4OA52A, max UDMA/133
> [ 1.144421] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
> [ 1.160414] ata1.00: configured for UDMA/133
> [ 1.160566] scsi 0:0:0:0: Direct-Access ATA Hitachi HDP72505 GM4O PQ: 0 ANSI: 5
> [ 1.364012] ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
> […]
[…]
The guy at the computer shop said that under MS Windows you have to set
a jumper to get this working and I also found that in the FAQ of Western
Digital Web site [2]. But setting the jumper did not change anything.
The `dmesg` output is the same.
Also looking at the VIA controllers on their site [2] it does not match
the one I am using, so this problem might not be related to this at all.
$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
00:00.5 PIC: VIA Technologies, Inc. K8M890CE I/O APIC Interrupt Controller
00:00.7 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:02.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller
00:03.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller
00:0f.0 IDE interface: VIA Technologies, Inc. Device 5372
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev b0)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev b0)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev b0)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev b0)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237S PCI to ISA Bridge
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
00:13.0 Host bridge: VIA Technologies, Inc. VT8237A Host Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] (rev 11)
20:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
This problem is reproducible with Linux kernel 2.6.32 and 2.6.39 on a
Debian Sid/unstable system.
Any insight or help is much appreciated. Searching for
linux-ide sata II via chipset udma 100
did not find anything useful.
Thanks,
Paul
[1] http://www.coreboot.org/pipermail/coreboot/2011-June/065622.html
[2] http://wdc.custhelp.com/app/answers/detail/search/1/a_id/1337/c/130/p/227,294
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread