Re: Can't mount pen drive (SOVED -- Sort of)
Florian Kulzer wrote:
On Wed, Apr 25, 2007 at 13:11:44 -0700, Marc Shapiro wrote:
Florian Kulzer wrote:
On Wed, Apr 25, 2007 at 08:01:02 -0700, Marc Shapiro wrote:
I am having trouble getting a USB pen drive to mount. I am running an
up-to-date Etch box.
[...]
The output from dmesg shows:
------------------------------------------------------------------------------------
usb 4-4.4: new high speed USB device using ehci_hcd and address 6
usb 4-4.4: no configuration chosen from 1 choice
[...]
What do you get with "lsusb" when the pen drive is plugged in? Maybe you
need to "update-usbids" to have the device identified correctly.
[...]
I do not have the 'lsusb' command on my box and can not find it with 'dpkg
-S lsusb'. What package is it in? I also do not have an 'update-usbids'
command.
Both are from package "usbutils".
If this does not bring any new clues then it would probably be best to
upgrade your kernel as Greg has suggested.
When I ran lsusb -v I got a lot of output, most of which I either didn't
understand, or didn't see any use for at the moment. However, at the
end of each section was a line about not being able to get the device
qualifier (see following output):
Bus 004 Device 010: ID 0781:5406 SanDisk Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0781 SanDisk Corp.
idProduct 0x5406
bcdDevice 0.10
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
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 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
--------------------------------------------------------------------
Additionally, the hub that the pen drive was inserted into was also
giving a similar message saying:
can't get hub descriptor: Operation not permitted
I disconnected the hub and plugged the pen drive directly into the cable
from the USB port and now /dev/sda and /dev/sda1 are created on plugging
in the drive and it mounts just fine.
I know that I used the hub with a USB pen connected to it when I was
running Sarge. Also this pen drive is one of those that lights up when
it is plugged in and it *does* light up when plugged into the hub. The
hub is a Belkin Hi-Speed USB 2.0 Mini Hub (model FSU215-MOB). Does
anyone have any ideas how I can get the pen drive to work when using the
hub? If not, then at least my wife can get to the data, but it would be
nice to know why the hub/pendrive combination is not working.
--
Marc Shapiro
mshapiro_42@yahoo.com
Reply to: