Bug#493420: linux-image-2.6.25-2-486: USB card reader device inaccessible
On Sat, Aug 02, 2008 at 09:36:40PM +0400, Andrey wrote:
> Package: linux-image-2.6.25-2-486
> Version: 2.6.25-7
> Severity: normal
>
> Hi Debian developers!
>
> I've just bought a cheap USB card reader device. My system seems to
> detect the device, but the sd* files in /dev are not created. The
> following is written to /var/log/messages:
>
> Aug 2 20:55:42 neo kernel: [ 1766.716747] usb 4-2: new high speed USB device using ehci_hcd and address 13
> Aug 2 20:55:42 neo kernel: [ 1766.847650] usb 4-2: configuration #1 chosen from 1 choice
> Aug 2 20:55:42 neo kernel: [ 1766.858155] scsi6 : SCSI emulation for USB Mass Storage devices
> Aug 2 20:55:42 neo kernel: [ 1766.869094] usb 4-2: New USB device found, idVendor=090c, idProduct=6000
> Aug 2 20:55:42 neo kernel: [ 1766.869109] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> Aug 2 20:55:42 neo kernel: [ 1766.869116] usb 4-2: Product: USB2.0 Card Reader
> Aug 2 20:55:42 neo kernel: [ 1766.869121] usb 4-2: Manufacturer: Generic , .
> Aug 2 20:55:42 neo kernel: [ 1766.869125] usb 4-2: SerialNumber: 0000001
> Aug 2 20:55:48 neo kernel: [ 1772.326601] scsi 6:0:0:0: Direct-Access Generic 6000 PQ: 0 ANSI: 0 CCS
> Aug 2 20:55:48 neo kernel: [ 1772.351934] sd 6:0:0:0: [sda] 4019200 512-byte hardware sectors (2058 MB)
> Aug 2 20:55:48 neo kernel: [ 1772.352701] sd 6:0:0:0: [sda] Write Protect is off
> Aug 2 20:55:48 neo kernel: [ 1772.355311] sd 6:0:0:0: [sda] 4019200 512-byte hardware sectors (2058 MB)
> Aug 2 20:55:48 neo kernel: [ 1772.355946] sd 6:0:0:0: [sda] Write Protect is off
> Aug 2 20:55:48 neo kernel: [ 1772.355971] sda:<3>end_request: I/O error, dev sda, sector 0
> Aug 2 20:55:48 neo kernel: [ 1772.485573] printk: 3 messages suppressed.
>
> The device works well on a Windows XP box (so it's not a hardware
> problem). All the other USB devices I have work on my system.
>
> Please be patient and reassign the bug accordingly if it is reported
> against wrong package.
>
> I'm ready to provide any additional info.
> Thanks for your patience.
Does this error still occur with more recent kernel versions?
Cheers,
Moritz
Reply to: