On Wed, 20 Jul 2011 23:11:24 +0100 Josua Dietze wrote: > Am 20.07.2011 22:23, schrieb Francesco Poli (wintermute): > > I installed usb-modeswitch in order to prevent my USB HSDPA modem to be > > seen as a storage device. > > That may be a misunderstanding. After a mode switch, there may still be > storage > interfaces exposed in a modem device. The difference is that it's never the > *first* interfaces as before switching.
Ah, that was not clear to me. I thought that usb-modeswitch was some sort of replacement (implemented via udev) of the old hal-info list of storage devices to be ignored (see bug #492486). Thanks for your kind and quick reply and sorry if I raised a non-issue. Anyway, I still fail to completely understand what's the actual point of switching modes: I mean, as long as the usbserial interface is exposed by the device and is actually usable, why should I care if other exposed interfaces are the first ones or the last ones? I am puzzled. I tried to look at some documentation, but maybe I missed some important explanation that clarifies everything... > > To see the difference between the modes, use "lsusb -v -d 12d1:1001". Note > that > you may have to disable global switching in /etc/usb_modeswitch.conf to even > see > the initial (install) mode. OK, I performed the following test: * I plugged the modem * I issued the lsusb command you suggested (as root), the output is attached to this message * I unplugged the modem * I changed DisableSwitching=0 into DisableSwitching=1 in /etc/usb_modeswitch.conf * I plugged the modem again * I issued the lsusb command again, obtaining a practically identical output * I unplugged the modem * I changed DisableSwitching=1 back to DisableSwitching=0 in /etc/usb_modeswitch.conf In the two cases the outputs of the lsusb command are almost identical: the only difference is that the second time the device was identified as "Bus 007 Device 005", instead of "Bus 007 Device 003" Should I worry about the outcome of this test? > > > crw-rw---- 1 root dialout 188, 1 Jul 20 22:44 /dev/ttyUSB1 > > crw-rw---- 1 root dialout 188, 2 Jul 20 22:44 /dev/ttyUSB2 > > crw-rw---- 1 root dialout 188, 0 Jul 20 22:44 /dev/ttyUSB0 > > ttyUSB0 should be your modem port. Do you have trouble using it? No trouble at all, it seems. I tested it and I was apparently able to establish a PPP connection and access the Internet via the USB modem. But I still have to understand the usefulness of usb-modeswitch, sorry... :-p Could you please help me? Thanks for your time! -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
Bus 007 Device 003: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x12d1 Huawei Technologies Co., Ltd.
idProduct 0x1001 E620 USB Modem
bcdDevice 0.00
iManufacturer 1 ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
iProduct 2 HUAWEI Mobile
iSerial 1 ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 108
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3 Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 128
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3 Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3 Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
pgp4crsH2g6PY.pgp
Description: PGP signature
