qmicli always getting transaction time out

Bjørn Mork bjorn at mork.no
Tue Apr 24 21:14:49 UTC 2018


EMANUEL FERNANDO MONTOYA GOMEZ <emanuel.montoya at udea.edu.co> writes:

> *Hi all,*
>
> *I haven't been able to get it working and getting an Ip on any of this
> two,

Really weird.  I have no idea what could be wrong.

> 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:*

Yes, the Windows drivers will do that by default.

>
> 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

Great!  If you are happy with the modem in MBIM mode, then there is no
reason not to use that.  You'll still have access to all the powers of
QMI through the QMI-in-MBIM wrapper service.  See the qmicli
"--device-open-mbim" parameter.

Too bad you have to use Windows to switch modes though.  Or do you have
a working AT command port in QMI mode?  If so, then you can switch to
MBIM using the AT!USBCOMP command.  You'll need AT!ENTERCND="A710"
first. Then run "AT!USBCOMP?" and "AT!USBCOMP=?" to see your current
setting and options.




Bjørn


More information about the libqmi-devel mailing list