Dear coreboot folks,
this question is off-topic because the board is running the vendor BIOS.
$ 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)
[…]
So I am posting this question to the coreboot list since you guys having
ported the Asus M2V-MX SE to coreboot probably know of some limitations
of the VIA chipset and how to solve this. If not a pointer to the
correct list would be nice.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
