Configuring HP lt4120 LTE modem in Ubuntu

I've recently bought HP Zbook 15u G3 notebook with HP lt4120 LTE modem. Most of this notebook hardware worked properly out of the box, but the modem didn't So I've started journey to configure it.

First steps for configuration I've found on Austrian ubook.at forum.

In few words:
  • This modem require some udev configuration for make existing drivers (qmi_wwan and qcserial) to see it.
  • It should be in specific configuration in order of Network Manager to see it.
  • It require firmware loaded to work properly.

What I did

  1. Installed libqmi-utils
  2. Added udev configuration for the modem (from udev.at forum):


Network Manager detected mobile broadband, but haven't connected properly to it.

Playing around with qmicli, showed that modem can work with no firmware, but network connection to it available only in ipv6 mode (but qmicli --wds-get-default-settings=3ggp states it work in ipv4-or-ipv6 PDP type) and NetworkManager doesn't work properly in this mode. If firmware was loaded by windows drivers, it can work in IPv4 mode.

So only one thing left to do before it will fully operational in Linux: firmware uploading.

Comments

  1. AnonymousApril 23, 2017 at 9:57 AM

    Ubuntu 17.04 (fresh install) and HP HP EliteBook 850 G3/8079, BIOS N75 Ver. 01.13 11/01/2016 with lt4120 almost there!


    After cold booting I get ALWAYS qmi-proxy hanging badly. Only cure is coming with "kill -9"

    top - 19:21:59 up 0 min, 2 users, load average: 1.63, 0.42, 0.14
    Tasks: 254 total, 2 running, 252 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 11.5 us, 9.7 sy, 0.0 ni, 72.5 id, 6.1 wa, 0.0 hi, 0.1 si, 0.0 st
    KiB Mem : 8018656 total, 6945564 free, 582636 used, 490456 buff/cache
    KiB Swap: 700860 total, 700860 free, 0 used. 7097980 avail Mem

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    1464 root 20 0 207076 8400 5796 R 100.0 0.1 0:15.26 qmi-proxy
    2344 root 20 0 44316 4000 3268 R 6.7 0.0 0:00.01 top

    After that dhclient gives me an IP address and connection is working !!!

    # dhclient -i wwp0s20f0u3i1

    # netstat -rn
    Kernel IP routing table
    Destination Gateway Genmask Flags MSS Window irtt Iface
    0.0.0.0 10.24.133.221 0.0.0.0 UG 0 0 0 wwp0s20f0u3i1
    10.24.133.216 0.0.0.0 255.255.255.248 U 0 0 0 wwp0s20f0u3i1


    This version of qmicli has some issues?

    # qmicli -V

    qmicli 1.16.2
    Copyright (C) 2015 Aleksander Morgado
    License GPLv2+: GNU GPL version 2 or later
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law.

    1. try
    # qmicli -d /dev/cdc-wdm0 --dms-uim-get-imsi
    [23 Apr 2017, 19:29:30] -Error ** __qmi_message_ctl_allocate_cid_response_parse: assertion 'qmi_message_get_message_id (message) == QMI_MESSAGE_CTL_ALLOCATE_CID' failed

    (qmicli:3085): GLib-GIO-CRITICAL **: g_simple_async_result_take_error: assertion 'error != NULL' failed
    [23 Apr 2017, 19:29:30] -Error ** qmi_message_ctl_allocate_cid_output_ref: assertion 'self != NULL' failed

    (qmicli:3085): GLib-GIO-CRITICAL **: g_simple_async_result_take_error: assertion 'error != NULL' failed

    (qmicli:3085): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
    Segmentation fault (core dumped)

    2. try
    # qmicli -d /dev/cdc-wdm0 --dms-uim-get-imsi
    [/dev/cdc-wdm0] UIM IMSI retrieved:
    IMSI: '244XXXXXXXX0799'


    # qmicli -d /dev/cdc-wdm0 --wds-get-packet-statistics
    [/dev/cdc-wdm0] Connection statistics:
    TX packets OK: 6651
    RX packets OK: 6872
    TX packets dropped: 0
    RX packets dropped: 0
    TX bytes OK: 615212
    RX bytes OK: 5874033

    # qmicli -d /dev/cdc-wdm0 --wds-get-current-settings
    [/dev/cdc-wdm0] Current settings retrieved:
    IP Family: IPv4
    IPv4 address: 10.24.133.220
    IPv4 subnet mask: 255.255.255.248
    IPv4 gateway address: 10.24.133.221
    IPv4 primary DNS: 192.XXX.XXX.XXX
    IPv4 secondary DNS: 192.XXX.XXX.XXX
    MTU: 1500
    Domains: none


    # qmicli -d /dev/cdc-wdm0 --nas-get-signal-strength
    [/dev/cdc-wdm0] Successfully got signal strength
    Current:
    Network 'lte': '-72 dBm'
    RSSI:
    Network 'lte': '-72 dBm'
    ECIO:
    Network 'lte': '-2.5 dBm'
    IO: '-106 dBm'
    SINR: (8) '9.0 dB'
    RSRQ:
    Network 'lte': '-11 dB'
    SNR:
    Network 'lte': '-1.0 dB'
    RSRP:
    Network 'lte': '-105 dBm'


    And so on ...

    ReplyDelete
  2. nayanajith m laxamanAugust 21, 2019 at 5:17 PM

    Worked for me with 03f0:521d by replacing 9d1d with 521d

    ReplyDelete
  3. nayanajith m laxamanAugust 21, 2019 at 5:35 PM

    I'm with HP EliteBook 840 G3. Thank you

    ReplyDelete

Post a Comment

Popular posts from this blog

Configuring HP lt4120 in Linux

Configuring HP lt4120 in Linux As I mentioned in previous post, updating firmware is not enough, modem needs configuration loaded and activated. Unfortunately there was no implementation of the calls in libqmi, so I've spend last few weeks writing code. I've submitted patches for this calls ( 96465 , 96854 , 96855 ) and this functionality should be soon in upstream. What you need to start using modem in Linux For use configuration script you need to install: Fresh libqmi version with the patches mentioned before Fastboot from android-tools.   Also you need to copy udev configuration file 99-hp-lt4120.rules to /etc/udev/rules.d. Last piece you need is firmware images. You can obtain it from Windows driver directory. In my case I've found it at C:\Program Files (x86)\HP lt4120 Snapdragon X5 LTE\Image How to use it After system startup just run script from root. After few minutes you will have you modem configured. Sometimes you need to make additional ...
Read more

Uploading new firmware to HP lt4120 modem

I've started researching how to configure the modem to work properly in Linux. First thing I checked how it's configuring in Windows drivers. Fortunately I've found drivers installer log with detailed steps to configure it. You can find relevant extract from the log here . Installer log analyzing results Reading through log I've found that it checks current firmware version (in Linux it available as 'qmicli --dms-get-revision'), then reboots device to Fastboot mode (using GobiConnect/ChangeDeviceDownLoadMode) and downloads/uploads firmware. Implementing ChangeDeviceDownLoadMode This call is present in Gobi driver, so it should use standard qmi protocol. Analyzing USB spoof results using usbpcap/Wireshark I've found that this command have id 0x5556 and have one uint8 parameter, so I've added the call to libqmi. Also I've created program to change the mode that don't require libqmi to implement new calls. You can download it here . ...
Read more