Failure accessing 2GB SD card using Neodio 7-in-1 card reader

Bug #129597 reported by Rocko on 2007-08-01
14
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Feisty reads my 2 GB SD card fine through my camera, but not through my Neodio Technologies Corp. 7-in-1 Card Reader. Note: I have tried with the card formatted both by gparted in Feisty with the card mounted through the camera, and by Windows, with the same result.

1. Syslog when mounting through the Neodio 7-in-1:

[163538.908000] SCSI device sdf: 1960448 512-byte hdwr sectors (1004 MB)
[163538.908000] sdf: Write Protect is off
[163538.908000] sdf: Mode Sense: 03 00 00 00
[163538.908000] sdf: assuming drive cache: write through
[163538.912000] SCSI device sdf: 1960448 512-byte hdwr sectors (1004 MB)
[163538.912000] sdf: Write Protect is off
[163538.912000] sdf: Mode Sense: 03 00 00 00
[163538.912000] sdf: assuming drive cache: write through
[163538.912000] sdf: sdf1
[163538.916000] sdf: p1 exceeds device capacity
[163538.932000] attempt to access beyond end of device
[163538.932000] sdf: rw=0, want=3920768, limit=1960448
[163538.932000] printk: 114 messages suppressed.
[163538.932000] Buffer I/O error on device sdf1, logical block 3920512
[163538.936000] attempt to access beyond end of device
[163538.936000] sdf: rw=0, want=3920769, limit=1960448

and fdisk -l shows:

Disk /dev/sdf: 1003 MB, 1003749376 bytes
29 heads, 28 sectors/track, 2414 cylinders
Units = cylinders of 812 * 512 = 415744 bytes

   Device Boot Start End Blocks Id System
/dev/sdf1 * 1 4829 1960320+ b W95 FAT32

The number of cylinders and size are wrong (should be 4828 and 2007 MB), but the other details are correct.

Nautilus will read and write to the card, but some files get truncated *without* any warning that this happened.

2. Mounting through the camera works fine:

syslog:

[164487.828000] scsi 15:0:0:0: Direct-Access PENTAX DIGITAL_CAMERA 1.00 PQ: 0 ANSI: 0 CCS
[164487.832000] SCSI device sdh: 3920896 512-byte hdwr sectors (2007 MB)
[164487.832000] sdh: Write Protect is off
[164487.832000] sdh: Mode Sense: 00 06 00 00
[164487.832000] sdh: assuming drive cache: write through
[164487.836000] SCSI device sdh: 3920896 512-byte hdwr sectors (2007 MB)
[164487.840000] sdh: Write Protect is off
[164487.840000] sdh: Mode Sense: 00 06 00 00
[164487.840000] sdh: assuming drive cache: write through
[164487.840000] sdh: sdh1
[164487.844000] sd 15:0:0:0: Attached scsi removable disk sdh
[164487.844000] sd 15:0:0:0: Attached scsi generic sg8 type 0

fdisk -l:

Disk /dev/sdh: 2007 MB, 2007498752 bytes
29 heads, 28 sectors/track, 4828 cylinders
Units = cylinders of 812 * 512 = 415744 bytes

   Device Boot Start End Blocks Id System
/dev/sdh1 * 1 4829 1960320+ b W95 FAT32

3. A 4GB CF flash card mounted via the Neodio works fine. fdisk -l shows:

Disk /dev/sdc: 4110 MB, 4110188544 bytes
255 heads, 63 sectors/track, 499 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sdc1 * 1 500 4013824+ 6 W95 FAT32

This looks like a duplicate of 89138, but that bug is flagged as invalid and I'm not sure what that means.

Rocko (rockorequin) wrote :

This bug occurs also in Gutsy tribe 5 and in Edgy.

Ryan Maki (ryan.maki) wrote :

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/89138 was closed as invalid because it was assumed that the card was not formatted correctly.

That bug report and this one both have problems with 2GB cards in a 'Neodio Technologies Corp. 7-in-1 Card Reader' which may indicate a problem in the devices which only occur with the 2GB cards. (?)

Do you have other you can test with this device? Especially 2GB or larger cards? If the same formatting procedures work correctly with those cards, as in the other bug, but fail with your 2GB card, please post the details of your test cards. Please also post a comment with the relevant line for your card reader from 'lsusb'.

Rocko (rockorequin) wrote :

I've tried a 256 MB SD card and the 4 GB compact flash card, both of which work fine, so I was assuming it was a problem with SD cards above a certain capacity, possibly 1 GB since this is what fdisk tells me my 2 GB card is.

I'll see if I can get hold of some other cards to test.

Here's the output of lsusb:

$ sudo lsusb -s 9 -v

Bus 001 Device 009: ID 0aec:3260 Neodio Technologies Corp. 7-in-1 Card Reader
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x0aec Neodio Technologies Corp.
  idProduct 0x3260 7-in-1 Card Reader
  bcdDevice 1.8a
  iManufacturer 1 GENERIC
  iProduct 2 USB Storage Device
  iSerial 3 200501041423444LD
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk (Zip)
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
Device Qualifier (for other device speed):
  bLength 10
  bDescriptorType 6
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  bNumConfigurations 1
can't get debug descriptor: Connection timed out
Device Status: 0x0000
  (Bus Powered)

Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Rocko (rockorequin) wrote :

It was still happening with the 8.04 release in April. Unfortunately I can't test with the 8.04.1 release because the hardware has since become faulty and can't read anything.

Jean-Baptiste Lallement (jibel) wrote :

Thanks for your reply. I'm closing this report due to your last comment regarding this can't be reproduced anymore due to a hardware failure. Don't hesitate to reopen if you're able to access this hardware again.

Thanks for your time.

AMSlider (dan-deeog) wrote :
Download full text (4.4 KiB)

Hi Jean-Baptiste,

Sorry to open up this can of worms again, but I am having the same issue on Intrepid and am hoping you can help. I figured I'd post it here (rather than the general forum) since it is exactly the same issue. Please let me know if this is wrong as it is my first post. I've had this system installed since Fiesty and the card reader always seemed to recognize a card, but it has never worked. I've left it in the case and used it as an extra USB port in the front of my computer, to get a little use out of it. Anyways, I've tested it with a 2GB Kingston 120x Ultimate SD card, a 1GB PNY card, and a 4 GB Lexar MicroSD card wrapped in an SD holder/adapter. None of them work in the Neodio, but they work great when tethered to the Casio Exilim camera. For grins, I plugged the camera into the Neodio's USB port, and Gnome wanted to launch FSpot within seconds.

I just reseated the Neodio and plugged it into a different USB hub port on my mobo to see if it would make a difference, and it did not.

In the attached dmesg.log, the Kingston 2GB card was plugged in around 151 seconds (it listed it as 1GB, then failed), the 1GB PNY was around 265 seconds. The Casio Camera was around 851 seconds. The plugin of Gparted formatted (fat16 and fat32) 2GB card seems to be around 1044 seconds.

I've tried to format the cards as listed in Ryan Maki's comment (bug 89138), when plugged in through the camera, but came up with the same result.

In researching this, it looks like all of the modules are loaded, and the SCSI emulation appears to be correct in the dmesg log.

Here's the link to where I got this POS - http://www.newegg.com/Product/Product.aspx?Item=N82E16820300901

Here's my computer's info:

$ uname -a
Linux deeog 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

$ lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 046d:0992 Logitech, Inc. QuickCam Communicate Deluxe
Bus 004 Device 002: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 045e:00f9 Microsoft Corp.
Bus 003 Device 003: ID 03f0:2811 Hewlett-Packard PSC-2100
Bus 003 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 0aec:3260 Neodio Technologies Corp. 7-in-1 Card Reader
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

$ lspci
00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI...

Read more...

AMSlider (dan-deeog) wrote :
AMSlider (dan-deeog) wrote :

@AMSlider:

Please include the following additional information, (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Changed in linux:
status: Invalid → Incomplete
AMSlider (dan-deeog) wrote :

Hi Jean-Baptiste,

In my post from 2008-12-02, there is a dmesg.log attached to my first post. It is after a reboot.

There is also a "uname -a" in the post, though here it is again:
$ uname -a
Linux deeog 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

I have attached the lscpi-vvnn.log file per your request. Thank you for your time.

~Slider

Thank you. I'm setting status to "confirmed" because required information is attached.

Changed in linux:
status: Incomplete → Confirmed
davidr (davaweb) wrote :

I've just found this bug report and Hardy AMD64 8.04.1 cannot read 2GB cards.

Haven't tried 8GB until it is fixed.

David

Alistair Buxton (a-j-buxton) wrote :

I have the same reader and can't get it to work with a 1GB SD card. 512MB works fine.

StoatWblr (stoatwblr) wrote :

I believe this device can't read SDHC cards. It definitely can't handle my 8Gb SDHC ones.

Rocko, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue in a supported release, 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 <replace-with-bug-number>

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.

tags: added: edgy feisty gutsy hardy needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Rocko (rockorequin) wrote :

The hardware in question failed years ago, so I can't re-test. So it's no longer an issue for me!

Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers