Modify

Opened 3 years ago

Closed 3 years ago

Last modified 22 months ago

#19121 closed defect (worksforme)

mbim (proto 'mbim', umbim) fails for Sierra Wireless AirCard 340U

Reported by: gsheremeta10 Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: mbim Cc:

Description

CHAOS CALMER (Bleeding Edge, r44622

Sierra Wireless AirCard 340U on AT&T
Fairly popular card in the US.
No pin is required, but I tried with the default pin of 1111.

The card works flawlessly on Fedora 20 under both mbimcli and ModemManager. But I cannot get it to come up on openwrt.

Notice the Segmentation Fault and the "message not long enough" errors. Perhaps some incompatibility between libmbim and umbim?

)

root@OpenWrt:~# umbim -n -d /dev/cdc-wdm0 caps
  devicetype: 0002 - removable
  cellularclass: 0001
  voiceclass: 0001 - no-voice
  simclass: 0002
  dataclass: 8000003F
  smscaps: 0003
  controlcaps: 0001
  maxsessions: 0001
  deviceid: 0xxxxxxxxxxxxxx
  firmwareinfo: SWI9X15C_01.05.11.23
  hardwareinfo: AirCard 340U


root@OpenWrt:~# umbim -n pinstate -d /dev/cdc-wdm0 
required pin: 3 - pin2
remaining attempts: 3


root@OpenWrt:~# umbim -n -d /dev/cdc-wdm0 unlock 1111
Pin Unlocked


root@OpenWrt:~# umbim -n -d /dev/cdc-wdm0 subscriber
  readystate: 0001 - initialized
  simiccid: 8xxxxxxxxxxxxxxxxx (censored)
  subscriberid: 3xxxxxxxxxxxxx (censored)
Segmentation fault


root@OpenWrt:~# umbim -n -d /dev/cdc-wdm0 registration
  nwerror: 0000 - unknown
  registerstate: 0003 - home
  registermode: 0001 - automatic
  availabledataclasses: 0020 - lte
  currentcellularclass: 0001 - gsm
  provider_id: 310410
  provider_name: AT&T
  roamingtext: (null)


root@OpenWrt:~# umbim -n -d /dev/cdc-wdm0 attach
message not long enough


root@OpenWrt:~# umbim -n -d /dev/cdc-wdm0 connect
message not long enough


root@OpenWrt:~# umbim -v -n -d /dev/cdc-wdm0 connect
sending (16): 01 00 00 00 10 00 00 00 01 00 00 00 00 04 00 00 
  header_type: 0001
  header_length: 0010
  header_transaction: 0001
reading (16): 01 00 00 80 10 00 00 00 01 00 00 00 00 00 00 00 
  header_type: 80000001
  header_length: 0010
  header_transaction: 0001
sending (108): 03 00 00 00 6c 00 00 00 02 00 00 00 01 00 00 00 00 00 00 00 a2 89 cc 33 bc bb 8b 4f b6 b0 13 3e c2 aa e6 df 0c 00 00 00 01 00 00 00 3c 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7e 5e 2a 7e 4e 6f 72 72 73 6b 65 6e 7e 5e 2a 7e 
  header_type: 0003
  header_length: 006C
  header_transaction: 0002
reading (64): 07 00 00 80 40 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 4b f3 84 76 1e 6a 41 db b1 d8 be d2 89 c2 5b db 01 00 00 00 14 00 00 00 01 00 00 00 fa 00 00 00 00 00 00 00 50 00 00 00 12 00 00 00 
  header_type: 80000007
  header_length: 0040
  header_transaction: 0000
reading (48): 03 00 00 80 30 00 00 00 02 00 00 00 01 00 00 00 00 00 00 00 a2 89 cc 33 bc bb 8b 4f b6 b0 13 3e c2 aa e6 df 0c 00 00 00 0e 00 00 00 00 00 00 00 
  header_type: 80000003
  header_length: 0030
  header_transaction: 0002
message not long enough
sending (16): 02 00 00 00 10 00 00 00 03 00 00 00 01 00 00 00 
  header_type: 0002
  header_length: 0010
  header_transaction: 0003
reading (16): 02 00 00 80 10 00 00 00 03 00 00 00 00 00 00 00 
  header_type: 80000002
  header_length: 0010
  header_transaction: 0003

Attachments (0)

Change History (4)

comment:1 Changed 3 years ago by blogic

  • Resolution set to worksforme
  • Status changed from new to closed

there is a win8 and a linux firmware. you are most likely using the win8 version. please switch the the linux one and try again.

comment:2 Changed 3 years ago by anonymous

Can you give details on what particular firmware version works with OpenWRT?

comment:3 Changed 3 years ago by arcos9000@…

bump

comment:4 Changed 22 months ago by cron410@…

You probably need QMI commands instead of MBIM.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.