From: Stephen Clark <sclark46@earthlink.net>
To: linux-ide@vger.kernel.org
Subject: Kernel 2.6.37 erroneously limiting to UDMA/33
Date: Wed, 05 Jan 2011 15:39:30 -0500 [thread overview]
Message-ID: <4D24D702.9090908@earthlink.net> (raw)
Hello,
Why is the kernel limiting me to udma/33 when the device says it can do
ata2.01: CFA: TRANSCEND, 20070831, max UDMA/66
There is no cable the compact flash is a socket on the motherboard!
Loading sd_mod.ko module
Loading libata.ko module
Loading ata_generic.ko module
Loading pata_acpi.ko module
pata_acpi 0000:00:0f.0: PCI INT B -> GSI 21 (level, low) -> IRQ 21
pata_acpi 0000:00:0f.0: PCI INT B disabled
Loading pata_via.ko module
scsi0 : pata_via
scsi1 : pata_via
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15
ata2.01: CFA: TRANSCEND, 20070831, max UDMA/66
ata2.01: 7962192 sectors, multi 0: LBA
ata2.01: limited to UDMA/33 due to 40-wire cable
ata2.01: configured for UDMA/33
scsi 1:0:1:0: Direct-Access ATA TRANSCEND 2007 PQ: 0 ANSI: 5
sd 1:0:1:0: [sda] 7962192 512-byte logical blocks: (4.07 GB/3.79 GiB)
sd 1:0:1:0: [sda] Write Protect is off
sd 1:0:1:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DA
sda: sda1 sda2 sda3
sd 1:0:1:0: [sda] Attached SCSI disk
Loading ata_piix.ko module
Thanks,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next reply other threads:[~2011-01-05 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 20:39 Stephen Clark [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-05 18:33 Kernel 2.6.37 erroneously limiting to UDMA/33 Stephen Clark
2011-01-05 23:50 ` Robert Hancock
2011-01-06 10:30 ` Andreas Mohr
2011-01-06 15:29 ` Stephen Clark
2011-01-06 15:26 ` Stephen Clark
2011-01-06 18:29 ` Stephen Clark
2011-01-07 20:58 ` Tejun Heo
2011-01-07 12:31 ` Stan Hoeppner
2011-01-06 13:47 ` Alan Cox
2011-01-06 18:20 ` Stephen Clark
2011-01-06 18:22 ` Stephen Clark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D24D702.9090908@earthlink.net \
--to=sclark46@earthlink.net \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.