CF card in PC Card adapter very slow

[Morgan]

I'm trying to use a Compact Flash card in a PC card adapter, but it's incredibly slow under Ubuntu 8.10.

Laptop is a Thinkpad X40
CF card is 32GB 233x (35MB/s) made by Ridata
Adapter is made by "Viking Interworks," says "32 Bit" on it.

When I do:
# hdparm -t /dev/sdc

/dev/sdc:
 Timing buffered disk reads: 6 MB in 3.32 seconds = 1.80 MB/sec

So I tried:
# hdparm -d1 /dev/sdc

/dev/sdc:
 setting using_dma to 1 (on)
 HDIO_SET_DMA failed: Inappropriate ioctl for device
 HDIO_GET_DMA failed: Inappropriate ioctl for device

Here are what I think are the relevant bits of the system log:

kernel: [25690.572156] pccard: CardBus card inserted into slot 0
kernel: [25690.795820] pata_ninja32 0000:03:00.0: enabling device (0000 -> 0003)
kernel: [25690.795850] pata_ninja32 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
kernel: [25690.799684] scsi3 : pata_ninja32
kernel: [25690.801309] ata3: PATA max PIO4 irq 16
kernel: [25691.020519] ata3.00: ATA-4: SMI Model, 20080308, max UDMA/66
kernel: [25691.020535] ata3.00: 62652416 sectors, multi 0: LBA
kernel: [25691.036561] ata3.00: configured for PIO4
kernel: [25691.037215] scsi 3:0:0:0: Direct-Access ATASMI Model 2008 PQ: 0 ANSI: 5
kernel: [25691.038994] sd 3:0:0:0: [sdc] 62652416 512-byte hardware sectors (32078 MB)
kernel: [25691.039580] sd 3:0:0:0: [sdc] Write Protect is off
kernel: [25691.040483] sd 3:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
kernel: [25691.041305] sd 3:0:0:0: [sdc] 62652416 512-byte hardware sectors (32078 MB)
kernel: [25691.043666] sd 3:0:0:0: [sdc] Write Protect is off
kernel: [25691.047576] sd 3:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
kernel: [25691.050580] sdc: sdc1
kernel: [25691.054717] sd 3:0:0:0: [sdc] Attached SCSI disk
kernel: [25691.056667] sd 3:0:0:0: Attached scsi generic sg2 type 0

Thanks for any help,
-M

[kernel-janitor (kernel-janitor)]

Hi Morgan,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 290554

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[ole.tange (n-launchpad-net-tange-dk)]

I have experienced the same problem. I have tested Karmic today and saw no improvements. However, 2.6.31-rc5 may solve it according to http://osdir.com/ml/linux-kernel/2009-08/msg00222.html

I will not get around to try 2.6.31-rc5 any time soon, so please try that and see if it helps.

[Skippy le Grand Gourou (lecotegougdelaforce)]

Probably related to bug #228302.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]