Re: Gembird usb card reader

Alan Stern <[email protected]>
Newsgroups gmane.linux.usb.devel
Message-ID <[email protected]>
On Sun, 26 Aug 2007, Ernestas [utf-8] Vaiciukevičius wrote:

> Hello,
> 
> I'm having problems trying to make Gembird card reader work with 128 mb SD 
> card. My kernel version is 2.1.18.
> When I connect the reader, it is detected, entries show up in 
> /proc/partitions:
>    8    32     122752 sdc
>    8    33     122608 sdc1
> Device nodes are created by udev, but i'm unable to mount and use the 
> partition:
> # mount /dev/sdc1 /mnt/misc/
> mount: special device /dev/sdc1 does not exist

That sounds like a problem with udev.  Make sure that /dev/sdc1 is 
getting created with the correct major and minor numbers.

> Perhaps it is fixable by including some entry in unusual_devices.h ?
> 
> Here is the contents of /proc/bus/devices:
> T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 22 Spd=480 MxCh= 0
> D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> P:  Vendor=058f ProdID=6362 Rev= 1.29
> S:  Manufacturer=Generic
> S:  Product=Mass Storage Device
> S:  SerialNumber=058F312D81B
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
> I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
> E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> 
> Here is the debug output of usb-storage:

Here's where the first error occurs:

> Aug 26 04:04:17 gw vmunix: usb-storage: queuecommand called
> Aug 26 04:04:17 gw vmunix: usb-storage: *** thread awakened.
> Aug 26 04:04:17 gw vmunix: usb-storage: Command READ_10 (10 bytes)
> Aug 26 04:04:17 gw vmunix: usb-storage:  28 00 00 03 bd 20 00 00 08 00
> Aug 26 04:04:17 gw vmunix: usb-storage: Bulk Command S 0x43425355 T 0x36 L 
> 4096 F 128 Trg 0 LUN 0 CL 10
> Aug 26 04:04:17 gw vmunix: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 
> bytes
> Aug 26 04:04:17 gw vmunix: usb-storage: Status code 0; transferred 31/31
> Aug 26 04:04:17 gw vmunix: usb-storage: -- transfer complete
> Aug 26 04:04:17 gw vmunix: usb-storage: Bulk command transfer result=0
> Aug 26 04:04:17 gw vmunix: usb-storage: usb_stor_bulk_transfer_sglist: xfer 
> 4096 bytes, 1 entries
> Aug 26 04:04:17 gw vmunix: usb-storage: Status code -71; transferred 0/4096
> Aug 26 04:04:17 gw vmunix: usb-storage: -- unknown error
> Aug 26 04:04:17 gw vmunix: usb-storage: Bulk data transfer result 0x4
> Aug 26 04:04:17 gw vmunix: usb-storage: -- transport indicates error, 
> resetting
> Aug 26 04:04:17 gw vmunix: usb-storage: storage_pre_reset
> Aug 26 04:04:17 gw vmunix: usb 1-2: reset high speed USB device using ehci_hcd 
> and address 23
> Aug 26 04:04:17 gw vmunix: usb-storage: storage_post_reset
> Aug 26 04:04:17 gw vmunix: usb-storage: usb_reset_composite_device returns 0
> Aug 26 04:04:17 gw vmunix: usb-storage: scsi cmd done, result=0x70000
> Aug 26 04:04:17 gw vmunix: usb-storage: *** thread sleeping.

The computer tried to read sectors 245024 - 245031, which are close to 
the end but not right at the end (the device reported that it contains 
245504 sectors), and the device did not send a valid reply.  The error 
occurred again each time the computer tried to read those sectors.

I don't think any sort of entry in unusual_devs.h will fix this.  Maybe 
you just have a bad SD card.

Maybe you can edit the card's partition table and change it so that the
first partition doesn't contain any sectors near the end.  For example,
you might try shrinking it down to 122000 blocks (each block is 2
sectors).

Alan Stern


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.