what USB-2 CF reader is alleged to work?

[Harry Hoffman]

Hurrah! Not that I don't want you to use your device Pete but it's nice 
on occasion when "taking the car to the mechanic" it actually produces 
the symptoms.

--Harry

Pete Zaitcev wrote:
> Guess what, I have received a new USB key today, and it shows the problem
> right off the bat. But what's more, my old and trusty SDDR-31 now misbehaved,
> too (only one time though)! Here's an unedited dmesg:
> 
>  <----- plugging new 1GB stick
> usb 1-3: new high speed USB device using ehci_hcd and address 3
> usb 3-1: new full speed USB device using uhci_hcd and address 2
> usb 3-1: device descriptor read/64, error -71
> usb 3-1: device descriptor read/64, error -71
> usb 3-1: new full speed USB device using uhci_hcd and address 3
> usb 3-1: device descriptor read/64, error -71
> usb 3-1: device descriptor read/64, error -71
>  <----- device not recognized, not drivers are attached
>  <----- plugging SDDR-31
> usb 3-1: new full speed USB device using uhci_hcd and address 4
> ub: sizeof ub_scsi_cmd 64 ub_dev 2576
> uba: device 4 capacity nsec 15681 bsize 512
> uba: device 4 capacity nsec 15681 bsize 512
>  uba: uba1
> usbcore: registered new driver ub	<---- You'd think you are safe....
> ub: cmd #175 cmd status (-71)		<---- ... but no. Yay!
> ub: cmd #176 cmd status (-71)
> uba: device 4 capacity nsec 0 bsize 512
> ub: cmd #177 cmd status (-71)
> ub: cmd #178 cmd status (-71)
> uba: device 4 capacity nsec 0 bsize 512
> ub: cmd #179 cmd status (-71)
> uba: device 4 capacity nsec 0 bsize 512
> ub: cmd #180 cmd status (-71)
> uba: device 4 capacity nsec 0 bsize 512
> usb 3-1: USB disconnect, address 4
>  <----- Pulling SDDR-31 and inserting different CF card
> usb 3-1: new full speed USB device using uhci_hcd and address 5
> uba: device 5 capacity nsec 2041201 bsize 512
> uba: device 5 capacity nsec 2041201 bsize 512
>  uba: uba1
> usb 3-1: USB disconnect, address 5
>  <----- From this point on I was unable to make SDDR-31 to throw a -71,
>         but the Imation key does it every time.
> 
> Insanity! I guess I'm too cheap to buy good stuff which breaks, Jamie :-)
> The 1GB key was sent to me by Red Hat (the laptop, too). Hurray for corporate
> support.
> 
> I'll let you know if I find and fix this, but it's likely the same problem.
> 
> -- Pete
>