USB Stick wird nicht eingebunden

17/03/2009 - 11:44 von Oliver ojo Bedford | Report spam
Hi!

Ich habe ein Problem mit einem bestimmten Typ von USB-Sticks.
Der Riegel wird nicht eingebunden.

Andere USB Geràte machen keine Probleme.

Dieser spezielle Typ von USB-Stick macht auch unter Windows Probleme,
da dort das Security Device erkannt wird und dann unbedingt
Software installieren will.

Weiß jemand Rat?

Oliver

ojo@hermes:~$ uname -a
Linux hermes 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux

Bus 007 Device 005: ID 13e0:2516
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13e0
idProduct 0x2516
bcdDevice 1.00
iManufacturer 1 TSE Inc.
iProduct 5 USB Security Device
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 18
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

Bus 007 Device 004: ID 13e0:2517
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13e0
idProduct 0x2517
bcdDevice 1.00
iManufacturer 1 TSE Inc.
iProduct 4 USB Mass Storage Device
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
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 0x01 EP 1 OUT
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 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Bus 007 Device 003: ID 13e0:2515
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x13e0
idProduct 0x2515
bcdDevice 1.00
iManufacturer 1 TSE Inc.
iProduct 3 USB Embedded Hub
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
** UNRECOGNIZED: 09 29 02 0d 00 32 64 06 ff
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000d
Per-port power switching
Compound device
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 50 * 2 milli seconds
bHubContrCurrent 100 milli Ampere
DeviceRemovable 0x06
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0503 highspeed power enable connect
Port 2: 0000.0503 highspeed power enable connect
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered

Log:

Mar 17 11:33:42 hermes kernel: [ 8574.196194] usb 7-2: new high speed USB device using ehci_hcd and address 3
Mar 17 11:33:42 hermes kernel: [ 8574.344275] usb 7-2: configuration #1 chosen from 1 choice
Mar 17 11:33:42 hermes kernel: [ 8574.345646] hub 7-2:1.0: USB hub found
Mar 17 11:33:42 hermes kernel: [ 8574.345853] hub 7-2:1.0: 2 ports detected
Mar 17 11:33:43 hermes kernel: [ 8574.632221] usb 7-2.1: new high speed USB device using ehci_hcd and address 4
Mar 17 11:33:43 hermes kernel: [ 8574.739580] usb 7-2.1: configuration #1 chosen from 1 choice
Mar 17 11:33:43 hermes kernel: [ 8574.742443] scsi7 : SCSI emulation for USB Mass Storage devices
Mar 17 11:33:43 hermes kernel: [ 8574.824634] usb 7-2.2: new high speed USB device using ehci_hcd and address 5
Mar 17 11:33:43 hermes kernel: [ 8574.930733] usb 7-2.2: configuration #1 chosen from 1 choice
Mar 17 11:33:48 hermes kernel: [ 8579.751049] scsi scan: INQUIRY result too short (5), using 36
Mar 17 11:33:48 hermes kernel: [ 8579.751065] scsi 7:0:0:0: Direct-Access USB 2.0 Flash Drive 1.00 PQ: 0 ANSI: 0
Mar 17 11:33:48 hermes kernel: [ 8579.753551] sd 7:0:0:0: [sdb] Attached SCSI disk
Mar 17 11:33:48 hermes kernel: [ 8579.753990] sd 7:0:0:0: Attached scsi generic sg2 type 0
 

Lesen sie die antworten

#1 Henning Paul
17/03/2009 - 11:57 | Warnen spam
Oliver 'ojo' Bedford wrote:

Ich habe ein Problem mit einem bestimmten Typ von USB-Sticks.
Der Riegel wird nicht eingebunden.

Andere USB Geràte machen keine Probleme.

Dieser spezielle Typ von USB-Stick macht auch unter Windows
Probleme,
da dort das Security Device erkannt wird und dann unbedingt
Software installieren will.



Aber man kommt an den Speicher heran? Könnte nàmlich Absicht sein, dass
der Zugriff auf den Speicher erst gestattet wird, wenn das Passwort
korrekt eingegeben/der Fingerabdruck erkannt worden ist.

Denn laut dmesg-Ausgabe meldet sich das Mass Storage Device an, verràt
aber nicht, wie gross es ist, so dass nicht darauf zugegriffen werden
kann.

Gruß
Henning

Ähnliche fragen