Author Message

<  Setup Discussion  ~  Huawei E3231 - new model

PostPosted: Wed Jan 02, 2013 7:05 pm Reply with quote
Posts: 7 Joined: Wed Jan 02, 2013 6:23 pm
The Huawei E3231 is a new device, launched in the UK August 2012, promising much improved speed of operation, but not much search information on the product currently available.

I'm trying to configure the modem on Puppy Linux Prestige 5.4.3, Puppy has no record
of the device and I can't find mention of it on this board :

>_usb_modeswitch -v 0x12d1 -p 0x14db -W

.
.
>_ OK, got current device configuration (1)
>_ Error: message endpoint not given or found. Aborting

Where can I find the vendor specific control message?
The device tries to attach to ttyS0, is this significant in any way?

I'm begining to regret purchasing something so new, I should have chosen a more established model as my experience is limited, but no choice now, need to give it a go, can anyone help?

Thanx


Offline
PostPosted: Thu Jan 03, 2013 2:48 am Reply with quote
Posts: 1236 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
12d1:14db is the target id for the modeswitch and not the install(default) id.

The cmd lsusb will show you the id of all found usb devices, and lsusb -v -d xxxx:yyyy will show verbose info for a particular device.
Paste the latter here.


Offline
PostPosted: Fri Jan 04, 2013 7:36 pm Reply with quote
Posts: 7 Joined: Wed Jan 02, 2013 6:23 pm
Thanks for the input.

I'm not sure where to find 'default' ID's

>_ lsusb -v -d 12d1:14db
Code:
Bus 001 Device 042: ID 12d1:14db Huawei Technologies Co., Ltd.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x12d1 Huawei Technologies Co., Ltd.
  idProduct          0x14db
  bcdDevice            1.02
  iManufacturer           2 HUAWEI Technology
  iProduct                1 HUAWEI Mobile
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           71
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          3 Huawei Configuration
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      6 Ethernet Networking
      bInterfaceProtocol      0
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC Ethernet:
        iMacAddress                      4 xxxxxxxxxxx3
        bmEthernetStatistics    0x00000005
        wMaxSegmentSize               1514
        wNumberMCFilters            0x0003
        bNumberPowerFilters              1
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      6
      bInterfaceProtocol      0
      iInterface              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              32
      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              32
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)


Last edited by lightspeed on Tue Jan 15, 2013 3:40 pm, edited 1 time in total.

Offline
PostPosted: Sat Jan 05, 2013 8:58 am Reply with quote
Posts: 1236 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
The install id for the stick is 12d1:1f01 and you may see that in dmesg before usb_modeswitch switches it over to 12d1:14db.
Your lsusb shows a typical HiLink device in ethernet mode where it needs ethernet drivers which creates an additional eth device in your OS.

You can try and edit the /etc/usb_modeswitch.d config file for 12d1:1f01 and change the message contents to:
55534243123456780000000000000011062000000100000000000000000000

replug the stick and check with lsusb if it gets a different modem id this time.
If so, then paste the lsusb -v -d for 12d1:new id

With some luck it may become 12d1:1c05 with serial modem interfaces.


Offline
PostPosted: Tue Jan 08, 2013 6:37 pm Reply with quote
Posts: 7 Joined: Wed Jan 02, 2013 6:23 pm
No luck yet but i'm learning a lot. :)

I see now the install id with dmesg.

cdc_ether registers an interface on port4 and an ethernet address
for eth1.

/etc/usb_modeswitch.d.conf is an empty folder on my system.


/usr/share/usb_modeswitch/12d1:1f01 contains the control message, target
vendor 12d1, target_product 14db, NoDriverloading=1. This was
originaly intended for the E353 (3.se) device. I swapped the file
messgage for your message but no joy.


I don't understand how the 1c05 manifests itself.
12d1:1c0b is the install for E173 with 1c05 the target product. :?


Last edited by lightspeed on Tue Jan 15, 2013 6:45 pm, edited 1 time in total.

Offline
PostPosted: Tue Jan 08, 2013 7:08 pm Reply with quote
Site Admin Posts: 6496 Joined: Sat Nov 03, 2007 12:30 am
You can try one more "command":

Code:
MessageContent="55534243123456780000000000000011060000000000000000000000000000"

To experiment with variations of the original configuration, just copy the respective file from
"/usr/share/usb_modeswitch" to "/etc/usb_modeswitch.d". From there, it will be preferred over the original file, so you can make all edits to it and just plug your device in.


Offline
PostPosted: Tue Jan 15, 2013 6:38 pm Reply with quote
Posts: 7 Joined: Wed Jan 02, 2013 6:23 pm
I've tried Josh's message:

Code:
MessageContent="55534243123456780000000000000011060000000000000000000000000000"

lsusb now gives a new modem id 0x1442


lsusb-v -d 12d1:1442

Code:
Bus 001 Device 011: ID 12d1:1442 Huawei Technologies Co., Ltd.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x12d1 Huawei Technologies Co., Ltd.
  idProduct          0x1442
  bcdDevice            1.02
  iManufacturer           2 HUAWEI Technology
  iProduct                1 HUAWEI Mobile
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           95
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol    255 Vendor Specific (MSFT RNDIS?)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          0
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         0 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              32
      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              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol    255 Vendor Specific (MSFT RNDIS?)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          1
      CDC Union:
        bMasterInterface        1
        bSlaveInterface         1 1
      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              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
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:     0x0001
  Self Powered


What should I do next, create a new config file somewhere?


Offline
PostPosted: Tue Jan 15, 2013 6:59 pm Reply with quote
Posts: 167 Joined: Thu Mar 15, 2012 10:47 pm Location: Oslo, Norway
lightspeed wrote:
I've tried Josh's message:

Code:
MessageContent="55534243123456780000000000000011060000000000000000000000000000"

lsusb now gives a new modem id 0x1442


lsusb-v -d 12d1:1442


Ouch. Very difficult to read that without the "code" wrappers... I've added them in the quote below

Quote:
Code:
Bus 001 Device 011: ID 12d1:1442 Huawei Technologies Co., Ltd.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x12d1 Huawei Technologies Co., Ltd.
  idProduct          0x1442
  bcdDevice            1.02
  iManufacturer           2 HUAWEI Technology
  iProduct                1 HUAWEI Mobile
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           95
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol    255 Vendor Specific (MSFT RNDIS?)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          0
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         0 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              32
      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              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol    255 Vendor Specific (MSFT RNDIS?)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          1
      CDC Union:
        bMasterInterface        1
        bSlaveInterface         1 1
      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              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
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:     0x0001
  Self Powered



OK, that does not look good at all. Only two interfaces and both look like possible RNDIS interfaces, but without any interrupt endpoint. I have no idea how to use that. AFAIK it is required for RNDIS. We certainly require it in Linux at least.


Bjørn


Offline
PostPosted: Wed Jan 16, 2013 6:08 pm Reply with quote
Posts: 7 Joined: Wed Jan 02, 2013 6:23 pm
My device now appears to be permanently switched over to 0x1442, I was expecting
it to revert back to its default id 0x1f01 when unplugged. Is this usually the case with
these modems?

The switched modem is not recognised when I plug it in and does not attach to a driver,
for now it's almost dead, the LED flashes but that's about it.

How to switch it back?


Offline
PostPosted: Wed Jan 16, 2013 6:56 pm Reply with quote
Posts: 167 Joined: Thu Mar 15, 2012 10:47 pm Location: Oslo, Norway
lightspeed wrote:
My device now appears to be permanently switched over to 0x1442, I was expecting
it to revert back to its default id 0x1f01 when unplugged. Is this usually the case with
these modems?


No, definitely not. That's the first report I've heard of something like that. It seems that we have to be more careful wrt trying different switching commands.

Quote:
The switched modem is not recognised when I plug it in and does not attach to a driver,
for now it's almost dead, the LED flashes but that's about it.

How to switch it back?


I am very sorry, but I do not know.

Could you please record as many details as possible about exactly what you did and what that resulted in while it is fresh in your memory and logs? That increases the chances of finding out what went wrong, and will help preventing others from doing the same.

And I guess we should find out what these 02/02/ff with only 2 bulk endpoints are so you can attach a driver. I see no quick fix for the rndis_host driver. It will need an interrupt enpoint to do it's RNDIS specific setup. But maybe one or both of these really are serial ports? You could try doing
Code:
modprobe option
echo 12d1 1442 >/sys/bus/usb-serial/drivers/option1/new_id


That will make the option driver bind to these interfaces and create two ttyUSBx devices. This is no proof of any success, but it will let you try to send AT commands to the ports. Try that and see what happens.


Offline
PostPosted: Wed Jan 16, 2013 8:17 pm Reply with quote
Posts: 1236 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
The usb_modeswitch msg switching the device to 12d1:14db is
"55534243123456780000000000000a11062000000000000100000000000000"

here is what happens if one changes the "lonely 1"

usb_modeswitch -v 0x12d1 -p 0x1f01 -M
"55534243123456780000000000000011062000000000000200000000000000"

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1441 Rev= 1.02
S: Manufacturer=HUAWEI
S: Product=HUAWEI HiLink
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=500mA

I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=06 Prot=00 Driver=(none)
E: Ad=8f(I) Atr=03(Int.) MxPS= 64 Ivl=2ms

I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=06 Prot=00 Driver=(none)
E: Ad=8e(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=0f(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms

I:* If#= 2 Alt= 0 #EPs= 2 Cls=02(comm.) Sub=02 Prot=ff Driver=(none)
E: Ad=8d(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=0e(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms

I:* If#= 3 Alt= 0 #EPs= 2 Cls=02(comm.) Sub=02 Prot=ff Driver=(none)
E: Ad=8c(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=0d(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms

I:* If#= 4 Alt= 0 #EPs= 2 Cls=02(comm.) Sub=02 Prot=ff Driver=(none)
E: Ad=8b(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=0c(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms


ie a cdc_ether device but now with those extra interfaces.
Not tested afaik is an 11062 type msg followed by all zeros.


Offline
PostPosted: Fri Jan 18, 2013 5:55 pm Reply with quote
Posts: 7 Joined: Wed Jan 02, 2013 6:23 pm
It's not a big problem for me, and there is nothing for anyone to apologize about, I appreciate
what you guys are trying to do with the forum and the help you a providing, quite honestly
without your assistance I would be unable to make any progress at all.

As for providing a detailed log of the commands I sent to the modem that's
a little difficult, I was experimenting with quite a few different messages and not always
taking the time to note what I was doing. My approach was trial and error n see how
it goes. I need to be more careful in future.

I will try the modprobe fix and report back here.


Thanx


Offline
PostPosted: Sat Jan 19, 2013 6:19 pm Reply with quote
Posts: 7 Joined: Wed Jan 02, 2013 6:23 pm
I've not yet been able to switch the 3231 back to its default id but my efforts continue.

As it is now locked into product id 1442 can it now be considered a special case
not needing further usb_modeswitch switching? Maybe it's meant to happen that way. lol


Here's my most recent log:

Code:
# from boot:
#
# Hotplug Huawei 3231 3G USB modem
#
>_dmesg
.
.
[  172.283338] usb 1-4: new high-speed USB device number 5 using ehci_hcd
[  172.408144] usb 1-4: New USB device found, idVendor=12d1, idProduct=1442
[  172.408152] usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[  172.408158] usb 1-4: Product: HUAWEI Mobile
[  172.408162] usb 1-4: Manufacturer: HUAWEI Technology
[  172.790617] usbcore: registered new interface driver cdc_ether
[  172.794788] usb 1-4: bad CDC descriptors
[  172.794820] usb 1-4: bad CDC descriptors
[  172.795352] usbcore: registered new interface driver rndis_host
[  172.881132] cfg80211: Calling CRDA to update world regulatory domain
[  172.899459] usb 1-4: bad CDC descriptors
[  172.904100] usb 1-4: bad CDC descriptors
[  172.904997] usbcore: registered new interface driver rndis_wlan
.
.
# manualy attach driver to Huawei 3231 3g modem
#
>_modprobe ubserial vendor=0x12d1 product=0x1442
.
.
>_dmesg
.
[  289.750955] usbcore: registered new interface driver usbserial
[  289.750998] USB Serial support registered for generic
[  289.751165] usbserial_generic 1-4:1.0: generic converter detected
[  289.751696] usb 1-4: generic converter now attached to ttyUSB0
[  289.751721] usbserial_generic 1-4:1.1: generic converter detected
[  289.752300] usb 1-4: generic converter now attached to ttyUSB1
[  289.752640] usbcore: registered new interface driver usbserial_generic
[  289.752647] usbserial: USB Serial Driver core
.
.
.
# Send AT command to 3231
#
>_modem-stats -c "AT" /dev/ttyUSB0




.
^C Abort
.
#
#  waiting for OK, modem hangs, no response, try again with "ATZ", again modem fails.
# dialer n chatt script fails
.
.
.
# Unplug Huawei3231 3G modem from USB
.
>_dmesg
.
.
.
[  360.595581] usb 1-4: USB disconnect, device number 5
[  360.595863] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[  360.595883] usbserial_generic 1-4:1.0: device disconnected
[  360.596002] generic ttyUSB1: generic converter now disconnected from ttyUSB1
[  360.596019] usbserial_generic 1-4:1.1: device disconnected
.




'bad CDC descriptors'?

edit: I found this but way too technical for me. http://www.usb.org/developers/devclass_ ... bcdc11.pdf
Most of the fixes I've seen for CDC problems involve recompiling the the kernal or some other major adjustment.
Maybe it's time to buy another modem.


E=mc2


Offline
PostPosted: Mon Jan 21, 2013 10:45 am Reply with quote
Posts: 167 Joined: Thu Mar 15, 2012 10:47 pm Location: Oslo, Norway
lightspeed wrote:
'bad CDC descriptors'?


That's expected. The 02/02/ff codes are normally used by RNDIS functions and the rndis_host driver will therefore attempt to use this interface. But it cannot work without an interrupt endpoint. It therefore consider the descriptors "bad".

But it is important to realize that this is in the context that this is really RNDIS. We do not know that, so the descriptors may be perfectly OK. The device may just implement som other vendor specific CDC protocol.



Bjørn


Offline
PostPosted: Tue Feb 12, 2013 4:35 pm Reply with quote
Posts: 6 Joined: Tue Feb 12, 2013 4:31 pm
Hi,

First post here, so trying to get things right!

I have an E353 from 3 UK. I tried various commands back in the autumn, and have ended up with the id: 12d1:1c05.

Dmesg shows:

[28129.716081] usb 2-4: new high-speed USB device number 5 using ehci_hcd
[28129.849993] usb 2-4: bad CDC descriptors
[28129.850312] usb 2-4: bad CDC descriptors
[28129.850571] usb 2-4: bad CDC descriptors
[28129.850783] usb 2-4: bad CDC descriptors
[28129.850974] usb 2-4: bad CDC descriptors
[28129.851187] usb 2-4: bad CDC descriptors


I think I'm in a similar situation to the chap above.

Code:
$ lsusb -v -d 12d1:1c05

Bus 002 Device 005: ID 12d1:1c05 Huawei Technologies Co., Ltd.
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x12d1 Huawei Technologies Co., Ltd.
  idProduct          0x1c05
  bcdDevice            1.02
  iManufacturer           2
  iProduct                1
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          142
    bNumInterfaces          3
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol    255 Vendor Specific (MSFT RNDIS?)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x03
          line coding and serial state
          get/set/clear comm features
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          0
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
      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              32
      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              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol    255 Vendor Specific (MSFT RNDIS?)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x00
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          1
      CDC Union:
        bMasterInterface        1
        bSlaveInterface         1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol    255 Vendor Specific (MSFT RNDIS?)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x00
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          2
      CDC Union:
        bMasterInterface        2
        bSlaveInterface         2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32


Does this add anything to the above problem, and is there any hope of fixing my mistake?

Thanks for your help!
Chris


Offline

Display posts from previous:  Sort by:

All times are UTC+02:00
Page 1 of 3
40 posts
Go to page 1 2 3 Next
Users browsing this forum: No registered users and 1 guest
Search for:
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum