qmicli always getting transaction time out
EMANUEL FERNANDO MONTOYA GOMEZ
emanuel.montoya at udea.edu.co
Tue Apr 24 20:14:36 UTC 2018
*Hi all,*
*I haven't been able to get it working and getting an Ip on any of this
two, so I decided to go for Windows 10 to try.*
*I installed: GenericDriverSetup.exe*
* Skylight_Generic*
* 9999999_9904609_SWI9X30C_02.20.03.00_00_GENERIC_002.017.000*
*and it connects and gets IP address without any problem in Windows 10.*
*After that, I put the MC7455 modem into the second host devices (the one
thar has Ubuntu 16.04 and kernel version ico1 at ico1:~$ uname
-r4.17.0-041700rc1-lowlatency*
*it appers in MBIM mode:*
ico1 at ico1:~$ mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id
'6bfe7d4ea386210e64dde8fc4a0d7aa44eb7712a')
-------------------------
Hardware | manufacturer: 'Sierra'
| model: 'MBIM [1199:9071]'
| revision: 'SWI9X30C_02.20.03.00'
| supported: 'gsm-umts, lte'
| current: 'gsm-umts, lte'
| equipment id: '359072060686975'
-------------------------
System | device: '/sys/devices/pci0000:00/0000:00:15.0/usb1/1-4'
| drivers: 'cdc_mbim'
| plugin: 'Sierra'
| primary port: 'cdc-wdm0'
| ports: 'wwp0s21f0u4i12 (net), cdc-wdm0 (mbim)'
-------------------------
Numbers | own : 'unknown'
-------------------------
Status | lock: 'none'
| unlock retries: 'sim-pin2 (4)'
| state: 'registered'
| power state: 'on'
| access tech: 'umts'
| signal quality: '0' (cached)
-------------------------
Modes | supported: 'allowed: 3g, 4g; preferred: none'
| current: 'allowed: 3g, 4g; preferred: none'
-------------------------
Bands | supported: 'unknown'
| current: 'unknown'
-------------------------
IP | supported: 'ipv4, ipv6, ipv4v6'
-------------------------
3GPP | imei: '359072060686975'
| enabled locks: 'fixed-dialing'
| operator id: '732101'
| operator name: 'Claro'
| subscription: 'unknown'
| registration: 'home'
-------------------------
SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
-------------------------
Bearers | paths: 'none'
ico1 at ico1:~$ mmcli -m 0 --simple-status
/org/freedesktop/ModemManager1/Modem/0
-------------------------
Status | state: 'registered'
| signal quality: '54' (recent)
| bands: 'unknown'
| access tech: 'umts'
-------------------------
3GPP | registration: 'home'
| operator code: '732101'
| operator name: 'Claro'
| subscription: 'unknown'
ico1 at ico1:~$
*And it connects without any problem*
ico1 at ico1:~$ sudo mmcli -m 0 --simple-connect="apn=internet.comcel.com.co
,user=comcelweb,ip-type=ipv4,allowed-auth=pap,password=comcelweb" -v
[sudo] password for ico1:
[24 abr 2018, 15:00:28] [Debug] Forcing request to be run asynchronously
[24 abr 2018, 15:00:28] [Debug] Assuming '0' is the modem index
[24 abr 2018, 15:00:28] [Debug] ModemManager process found at ':1.3'
[24 abr 2018, 15:00:28] [Debug] Modem found at
'/org/freedesktop/ModemManager1/Modem/0'
[24 abr 2018, 15:00:28] [Debug] Asynchronously connecting the modem...
successfully connected the modem
ico1 at ico1:~$
ico1 at ico1:~$ mmcli -m 0 --simple-status
/org/freedesktop/ModemManager1/Modem/0
-------------------------
Status | state: 'connected'
| signal quality: '48' (recent)
| bands: 'unknown'
| access tech: 'umts'
-------------------------
3GPP | registration: 'home'
| operator code: '732101'
| operator name: 'Claro'
| subscription: 'unknown'
ico1 at ico1:~$
ico1 at ico1:~$ mmcli -b 0
Bearer '/org/freedesktop/ModemManager1/Bearer/0'
-------------------------
Status | connected: 'yes'
| suspended: 'no'
| interface: 'wwp0s21f0u4i12'
| IP timeout: '20'
-------------------------
Properties | apn: 'internet.comcel.com.co'
| roaming: 'allowed'
| IP type: 'ipv4'
| user: 'comcelweb'
| password: 'comcelweb'
| number: 'none'
| Rm protocol: 'unknown'
-------------------------
IPv4 configuration | method: 'static'
| address: '10.147.160.111'
| prefix: '27'
| gateway: '10.147.160.112'
| DNS: '190.157.8.89', '8.8.8.8'
| MTU: '1500'
-------------------------
IPv6 configuration | method: 'unknown'
-------------------------
Stats | Duration: '59'
| Bytes received: 'N/A'
| Bytes transmitted: 'N/A'
ico1 at ico1:~$
I don't know if this information would be useful to you.
I would like being able to connect using Linux only applications.
Thanks in advance
*I have installed newer kernel but still the same response from qmicli
> commands*
>
> *ico1 at ico1:~$ lsb_release -a*
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 16.04.3 LTS
> Release: 16.04
> Codename: xenial
>
> *ico1 at ico1:~$ uname -a*
> Linux ico1 4.17.0-041700rc1-lowlatency #201804152230 SMP PREEMPT Mon Apr
> 16 02:37:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
>
> *I have 3 same reference devices and modems, so I installed a fresh
> Ubuntu server 17.10 which has kernel 4.13, on one of the others and I get
> the same response from qmicli commands*ico2 at ico2:~$ uname -a
> Linux ico2 4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017
> x86_64 x86_64 x86_64 GNU/Linux
>
> ico2 at ico2:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 17.10
> Release: 17.10
> Codename: artful
>
> ico2 at ico2:~$ history
> 1 uname -r
> 2 sudo apt update
> 3 sudo apt install libqmi-utils libqmi-proxy
> 4 qmicli -d /dev/cdc-wdm0 --dms-get-manufacturer
> 5 sudo qmicli -d /dev/cdc-wdm0 --dms-get-manufacturer
> 6 sudo qmicli -d /dev/cdc-wdm0 --dms-get-manufacturer -v
> 7 uname -r
> 8 uname -a
> 9 lsb_release -a
> 10 history
>
> ico2 at ico2:~$ lsusb
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 002: ID 1199:9071 Sierra Wireless, Inc.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> ico2 at ico2:~$
>
> ico2 at ico2:~$ sudo qmicli -d /dev/cdc-wdm0 --wda-get-data-format -v
> [21 abr 2018, 00:41:05] [Debug] [/dev/cdc-wdm0] Opening device with flags
> 'auto'...
> [21 abr 2018, 00:41:05] [Debug] [/dev/cdc-wdm0] loaded driver of cdc-wdm
> port: qmi_wwan
> [21 abr 2018, 00:41:05] [Debug] [/dev/cdc-wdm0] automatically selecting
> QMI mode
> [21 abr 2018, 00:41:05] [Debug] QMI Device at '/dev/cdc-wdm0' ready
> [21 abr 2018, 00:41:05] [Debug] [/dev/cdc-wdm0] Assuming service 'wda' is
> supported...
> [21 abr 2018, 00:41:05] [Debug] [/dev/cdc-wdm0] Allocating new client ID...
> [21 abr 2018, 00:41:05] [Debug] [/dev/cdc-wdm0] sent message...
> <<<<<< RAW:
> <<<<<< length = 16
> <<<<<< data = 01:0F:00:00:00:00:00:01:22:00:04:00:01:01:00:1A
>
> [21 abr 2018, 00:41:05] [Debug] [/dev/cdc-wdm0] sent generic request
> (translated)...
> <<<<<< QMUX:
> <<<<<< length = 15
> <<<<<< flags = 0x00
> <<<<<< service = "ctl"
> <<<<<< client = 0
> <<<<<< QMI:
> <<<<<< flags = "none"
> <<<<<< transaction = 1
> <<<<<< tlv_length = 4
> <<<<<< message = "Allocate CID" (0x0022)
> <<<<<< TLV:
> <<<<<< type = "Service" (0x01)
> <<<<<< length = 1
> <<<<<< value = 1A
> <<<<<< translated = wda
>
> error: couldn't create client for the 'wda' service: CID allocation failed
> in the CTL client: Transaction timed out
> ico2 at ico2:~$
>
> ico2 at ico2:~$ lsusb -v -d 1199:9071
> Bus 001 Device 002: ID 1199:9071 Sierra Wireless, Inc.
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x1199 Sierra Wireless, Inc.
> idProduct 0x9071
> bcdDevice 0.06
> iManufacturer 1
> iProduct 2
> iSerial 3
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 160
> 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 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> 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 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 2
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 0
> bInterfaceProtocol 0
> iInterface 0
> ** UNRECOGNIZED: 05 24 00 10 01
> ** UNRECOGNIZED: 05 24 01 00 00
> ** UNRECOGNIZED: 04 24 02 02
> ** UNRECOGNIZED: 05 24 06 00 00
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x000a 1x 10 bytes
> bInterval 9
> 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
> 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 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 3
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 0
> bInterfaceProtocol 0
> iInterface 0
> ** UNRECOGNIZED: 05 24 00 10 01
> ** UNRECOGNIZED: 05 24 01 00 00
> ** UNRECOGNIZED: 04 24 02 02
> ** UNRECOGNIZED: 05 24 06 00 00
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x85 EP 5 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x000a 1x 10 bytes
> bInterval 9
> 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 0
> 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 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 8
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x87 EP 7 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0008 1x 8 bytes
> bInterval 9
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x86 EP 6 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 0x04 EP 4 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
>
> After this I installer modemmanager and it works the same as in the first
> device.
>
> Thanks in advance
>
> Ohh, so bad, sorry.
>>
>> Thanks a lot for your help and time.
>>
>> 2018-04-20 23:31 GMT-05:00 Bjørn Mork <bjorn at mork.no>:
>>
>>>
>>> > Linux ico1 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC
>>> 2017
>>> > x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> v4.4 does not support the em7455 i qmi mode. You need v4.5 or later.
>>>
>>>
>>> Bjørn
>>>
>>
>>
--
"La información aquí contenida es para uso exclusivo de la persona o
entidad de destino. Está estrictamente prohibida su utilización, copia,
descarga, distribución, modificación y/o reproducción total o parcial, sin
el permiso expreso de Universidad de Antioquia, pues su contenido puede ser
de carácter confidencial y/o contener material privilegiado. Si usted
recibió esta información por error, por favor contacte en forma inmediata a
quien la envió y borre este material de su computador. Universidad de
Antioquia no es responsable por la información contenida en esta
comunicación, el directo responsable es quien la firma o el autor de la
misma."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20180424/d66f9d46/attachment-0001.html>
More information about the libqmi-devel
mailing list