Description of problem: ----------------------- The kernel detects the controller and the drive correctly as UDMA/100 capable, but it limits the connection to UDMA/33 because it detects a 40-wire cable instead of a 80-wire cable. Version-Release number of selected component (if applicable): ------------------------------------------------------------- Linux noname 2.6.29-0.258.2.3.rc8.git2.fc11.i586 #1 SMP Tue Mar 24 18:37:23 EDT 2009 i686 i686 i386 GNU/Linux Actual results: --------------- From dmesg: scsi5 : ata_piix ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14 ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15 ata5.00: ATA-5: ST320011A, 3.75, max UDMA/100 ata5.00: 39102336 sectors, multi 1: LBA ata5.00: limited to UDMA/33 due to 40-wire cable ata5.00: configured for UDMA/33 Expected results: ----------------- ata5.00: configured for UDMA/100 Additional info: ---------------- * The cable is definitely a 80-wire cable. I've tried two different 80-wire cables, but both get detected as 40-wire cable. * I have the same problem on Fedora 10, so this is not a rawhide regression.
Created attachment 337651 [details] dmesg
Created attachment 337653 [details] dmidecode
Created attachment 337654 [details] lspci -vv
Created attachment 337655 [details] dsdt
Created attachment 337657 [details] inteltool -a
Adding "libata.force=5.00:80c" to the kernel boot parameters works as a workaround.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The problem is gone in Fedora 12.