Arch Linux

1311219

Member

From: Sweden

Registered: 2007-01-09

Posts: 121

Kernel doesn't detect USB storage correctly [SOLVED!]

> After upgrading to the new official arch kernel things are back to normal...

I haven't found any other post describing this problem, but I'm sure someone else must have experienced it to?

When running the "2.6.26-ARCH" kernel (pacman version 2.6.26.2-1) my mp3 player isn't correctly identified (an Iriver T60), only the first 512B-sector is available.

I do not have this problem with other USB storage units (everything else still works fine), and my T60 works perfectly fine in any other kernel (custom or older official Arch kernel),
and in other distros, so it's clear that the problem is withing some change of configuration of the official Arch kernel.

Here is some quite self-explaining dmesg output (the interesting stuff begins with the "scsi scan: INQUIRY result too short (5), using 36" line...):

usb 2-7: new high speed USB device using ehci_hcd and address 3
usb 2-7: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi4 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi scan: INQUIRY result too short (5), using 36
scsi 4:0:0:0: Direct-Access                                    PQ: 0 ANSI: 0
sd 4:0:0:0: [sdb] Sector size 0 reported, assuming 512.
sd 4:0:0:0: [sdb] 1 512-byte hardware sectors (0 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] Sector size 0 reported, assuming 512.
sd 4:0:0:0: [sdb] 1 512-byte hardware sectors (0 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
 sdb:
sd 4:0:0:0: [sdb] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete

So... is this something anyone else have experienced, is it likely that it will be fixed in future kernel versions?
Any reply is appreciated.:P

UPDATE: Assuming this to be an Arch related issue was wrong of me, after searching a bit I found a lot of other people with similar problems... Still seems to be a kernel configuration issue though...:(

Last edited by 1311219 (2008-08-29 17:22:58)