WWAN module randomly disappears

Weater · 2022-01-16 10:07:02

I'm running arch on X1C gen 9 with EM120R_GL WWAN module.

After the initial setup of the network I have noticed that any significant network load causes a disconnect of the module: e.g., the modem dissappears from mmcli -L and reappears with an increased index.

I use ModemManager + NetworkManager for WWAN, NetworkManager only manages WWAN, WIFI is managed by iwd

mmcli -L:

[npetric@x1c ~]$ mmcli -L
    /org/freedesktop/ModemManager1/Modem/6 [quectel] EM120R_GL

mmcli -m 6:

[npetric@x1c ~]$ mmcli -m 6
  -----------------------------------
  General  |                    path: /org/freedesktop/ModemManager1/Modem/6
           |               device id: d1903269e1764a6f2e9f40c0386b044e91a5ff95
  -----------------------------------
  Hardware |            manufacturer: quectel
           |                   model: EM120R_GL
           |       firmware revision: EM120RGLAPR02A07M4G
           |          carrier config: ROW_Commercial
           | carrier config revision: 08010809
           |            h/w revision: EM120R_GL
           |               supported: gsm-umts, lte
           |                 current: gsm-umts, lte
           |            equipment id: 015930001058958
  -----------------------------------
  System   |                  device: /sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0
           |                 drivers: mhi-pci-generic
           |                  plugin: quectel
           |            primary port: wwan0mbim0
           |                   ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim),
           |                          wwan0qcdm0 (qcdm)
  -----------------------------------
  Status   |          unlock retries: sim-pin2 (3)
           |                   state: connected
           |             power state: on
           |             access tech: lte
           |          signal quality: 19% (recent)
  -----------------------------------
  Modes    |               supported: allowed: 3g; preferred: none
           |                          allowed: 4g; preferred: none
           |                          allowed: 3g, 4g; preferred: 4g
           |                          allowed: 3g, 4g; preferred: 3g
           |                 current: allowed: 2g, 3g, 4g; preferred: 4g
  -----------------------------------
  Bands    |               supported: utran-1, utran-3, utran-4, utran-6, utran-5, utran-8,
           |                          utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7,
           |                          eutran-8, eutran-12, eutran-13, eutran-14, eutran-17, eutran-18,
           |                          eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, eutran-29,
           |                          eutran-30, eutran-32, eutran-38, eutran-39, eutran-40, eutran-41,
           |                          eutran-42, eutran-43, eutran-46, eutran-48, eutran-66, utran-19
           |                 current: utran-1, utran-3, utran-4, utran-6, utran-5, utran-8,
           |                          utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7,
           |                          eutran-8, eutran-12, eutran-13, eutran-14, eutran-18, eutran-19,
           |                          eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30,
           |                          eutran-32, eutran-38, eutran-39, eutran-40, eutran-41, eutran-42,
           |                          eutran-43, eutran-46, eutran-48, eutran-66, utran-19
  -----------------------------------
  IP       |               supported: ipv4, ipv6, ipv4v6
  -----------------------------------
  3GPP     |                    imei: 015930001058958
           |           enabled locks: fixed-dialing
           |             operator id: 25001
           |           operator name: MTS RUS
           |            registration: home
  -----------------------------------
  3GPP EPS |    ue mode of operation: csps-2
           |     initial bearer path: /org/freedesktop/ModemManager1/Bearer/12
           |  initial bearer ip type: ipv4v6
  -----------------------------------
  SIM      |        primary sim path: /org/freedesktop/ModemManager1/SIM/12
           |          sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/12 (active)
           |                          slot 2: /org/freedesktop/ModemManager1/SIM/13
  -----------------------------------
  Bearer   |                   paths: /org/freedesktop/ModemManager1/Bearer/13

ModemManager logs just before and during the failure:

Jan 16 12:43:04 x1c ModemManager[565]: <info>  [modem3] simple connect state (8/8): all done
Jan 16 12:46:09 x1c ModemManager[565]: <warn>  [modem3/bearer7] reloading stats failed: Transaction timed out
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] unexpected port hangup!
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] channel destroyed
Jan 16 12:46:20 x1c ModemManager[565]: <info>  [modem3] connection to mbim-proxy for /dev/wwan0mbim0 lost, reprobing
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] Releasing 'pdc' client with flags 'release-cid'...
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] Unregistered 'pdc' client with ID '1'
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] Releasing 'loc' client with flags 'release-cid'...
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] Unregistered 'loc' client with ID '1'
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] Releasing 'nas' client with flags 'release-cid'...
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] Unregistered 'nas' client with ID '5'
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] Releasing 'dms' client with flags 'release-cid'...
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] Unregistered 'dms' client with ID '1'
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] unexpected port hangup!
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] channel destroyed
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] MBIM error: Cannot write message: Broken pipe
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] MBIM error: Cannot write message: Broken pipe
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] MBIM error: Cannot write message: Broken pipe
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] MBIM error: Cannot write message: Broken pipe
Jan 16 12:46:20 x1c ModemManager[565]: <warn>  [modem3/wwan0mbim0/mbim] Couldn't properly close QMI device: Cannot write message: Broken pipe
Jan 16 12:46:20 x1c ModemManager[565]: <info>  [base-manager] port wwan0qcdm0 released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'
Jan 16 12:46:20 x1c ModemManager[565]: <info>  [base-manager] port wwan0mbim0 released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'
Jan 16 12:46:20 x1c ModemManager[565]: <info>  [base-manager] port wwan0at0 released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'
Jan 16 12:46:20 x1c ModemManager[565]: <info>  [base-manager] port wwan0 released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'

NetworkManager logs:

Jan 16 12:43:05 x1c NetworkManager[511]: <info>  [1642326185.0291] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 16 12:46:20 x1c NetworkManager[511]: <info>  [1642326380.6768] device (wwan0mbim0): state change: activated -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Jan 16 12:46:20 x1c NetworkManager[511]: <info>  [1642326380.7234] manager: NetworkManager state is now DISCONNECTED
Jan 16 12:46:20 x1c NetworkManager[511]: <warn>  [1642326380.7241] modem-broadband[wwan0mbim0]: failed to disconnect modem: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/freedesktop/ModemManager1>
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1311] modem["wwan0mbim0"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference)
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1315] manager: (wwan0mbim0): new Broadband device (/org/freedesktop/NetworkManager/Devices/9)
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1319] device (wwan0mbim0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1323] device (wwan0mbim0): modem state 'enabling'
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1331] device (wwan0mbim0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1335] policy: auto-activating connection 'MTS Default 1' (6282bfae-cf6c-4e6b-809b-208f5a18fd68)
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1344] device (wwan0mbim0): Activation: starting connection 'MTS Default 1' (6282bfae-cf6c-4e6b-809b-208f5a18fd68)
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1345] device (wwan0mbim0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1347] manager: NetworkManager state is now CONNECTING
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1348] device (wwan0mbim0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.1354] device (wwan0mbim0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:37 x1c NetworkManager[511]: <info>  [1642326397.3333] modem["wwan0mbim0"]: modem state changed, 'enabling' --> 'searching' (reason: user-requested)
Jan 16 12:46:38 x1c NetworkManager[511]: <info>  [1642326398.4039] modem["wwan0mbim0"]: modem state changed, 'searching' --> 'registered' (reason: unknown)
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.7337] modem["wwan0mbim0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8003] modem["wwan0mbim0"]: modem state changed, 'connecting' --> 'connected' (reason: user-requested)
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8035] device (wwan0mbim0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8039] device (wwan0mbim0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8041] modem-broadband[wwan0mbim0]: IPv4 static configuration:
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8041] modem-broadband[wwan0mbim0]:   address 10.66.2.186/30
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8041] modem-broadband[wwan0mbim0]:   gateway 10.66.2.185
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8041] modem-broadband[wwan0mbim0]:   DNS 213.87.142.84
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8042] modem-broadband[wwan0mbim0]:   DNS 195.34.32.118
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8042] modem-broadband[wwan0mbim0]:   MTU 1500
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8049] modem-broadband[wwan0mbim0]: IPv6 base configuration:
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8050] modem-broadband[wwan0mbim0]:   address 2a00:1fa0:433:97c0:c8f:ff16:59fc:e1e/64
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8051] modem-broadband[wwan0mbim0]:   gateway 2a00:1fa0:433:97c0:ad92:2fc5:42d9:fb91
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8051] modem-broadband[wwan0mbim0]:   DNS 2a00:1fa0:3e00::1
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8051] modem-broadband[wwan0mbim0]:   DNS 2a02:28:2:3::116
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8065] device (wwan0mbim0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8079] policy: set 'MTS Default 1' (wwan0) as default for IPv6 routing and DNS
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8236] device (wwan0mbim0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8240] device (wwan0mbim0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8243] manager: NetworkManager state is now CONNECTED_SITE
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8248] policy: set 'MTS Default 1' (wwan0) as default for IPv4 routing and DNS
Jan 16 12:46:40 x1c NetworkManager[511]: <info>  [1642326400.8278] device (wwan0mbim0): Activation: successful, device activated.
Jan 16 12:46:41 x1c NetworkManager[511]: <info>  [1642326401.0601] manager: NetworkManager state is now CONNECTED_GLOBAL

Last edited by Weater (2022-01-16 10:16:10)

Strike0 · 2022-01-16 11:08:40

Have you added the manual link to let modemmanager unlock it? re https://wiki.archlinux.org/title/Lenovo … on_(Gen_9)
Have a look at dmesg/ journal around the time a disconnect happens. I suspect:

Jan 16 12:43:04 x1c ModemManager[565]: <info>  [modem3] simple connect state (8/8): all done
Jan 16 12:46:09 x1c ModemManager[565]: <warn>  [modem3/bearer7] reloading stats failed: Transaction timed out
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] unexpected port hangup!
Jan 16 12:46:20 x1c ModemManager[565]: [/dev/wwan0mbim0] channel destroyed

implies the quectel module disappears/exits and reloads; this probably causes the noticeable load.

Weater · 2022-01-16 11:56:27

Yes, the FCC unlock link is there:

[npetric@x1c ~]$ sudo ls -l /etc/ModemManager/fcc-unlock.d/
total 0
lrwxrwxrwx 1 root root 56 Jan 15 10:45 1eac:1001 -> /usr/share/ModemManager/fcc-unlock.available.d/1eac:1001

Indeed, there are reproducible "firmware crash" messenges in dmesg:

[ 5633.415409] mhi-pci-generic 0000:08:00.0: firmware crashed (7)
[ 5633.415475] mhi-pci-generic 0000:08:00.0: firmware crashed (6)
[ 5633.884738] net_ratelimit: 3 callbacks suppressed
[ 5633.884743] wwan0: Failed to queue TX buf (-5)
[ 5634.005295] wwan0: Failed to queue TX buf (-5)
[ 5634.246333] wwan0: Failed to queue TX buf (-5)
[ 5634.726438] wwan0: Failed to queue TX buf (-5)
[ 5634.852759] wwan0: Failed to queue TX buf (-5)
[ 5635.472216] wwan0: Failed to queue TX buf (-5)
[ 5635.504548] wwan0: Failed to queue TX buf (-5)
[ 5635.505131] wwan0: Failed to queue TX buf (-5)
[ 5635.686444] wwan0: Failed to queue TX buf (-5)
[ 5635.756442] wwan0: Failed to queue TX buf (-5)

Weater · 2022-01-16 12:00:54

There is actually a whole thread on the lenovo forum devoted to "firmware crash", but for a different modem though: https://forums.lenovo.com/t5/Other-Linu … 236?page=6

The symptoms are very similar

Strike0 · 2022-01-16 15:57:14

Yes, my guess was based on similar experience also (another modem model, same brand; all those devices are fresh to the kernel tree 5.13+). In this case the stability has improved a great deal over the last year and I would expect that to happen for your model too. Good thing is I've never seen it crash to the point I had to manually interfere (rmmod/insmod). Depending on how problematic those temporary hickups are for you, perhaps check if you can contribute info to the kernel bug tracker. Sorry, that's my 2c.

Weater · 2022-01-16 20:23:39

Thank you for the information!

I will wait for kernel updates then and try to update this topic once anything changes.

progandy · 2022-01-16 20:38:51

I have noticed that any significant network load causes a disconnect of the module:

To mitigate the problem, maybe you can try to limit the bandwidth for the modem with the wondershaper script (no ipv6 support, though) or sqm-scripts or using tc directly?

Last edited by progandy (2022-01-16 20:47:06)

Weater · 2022-01-17 10:21:54

I don't like wasting time on temporary solutions, and the modem works reasonably well for web browsing, ssh, etc. Only if I try something like speedtest.net that I am able to reproduce the failure reliably.

ali_akcza · 2022-07-26 21:54:25

I have the same problem with this modem (EM120R_GL) on 5.18.14-arch1-1

ali_akcza · 2022-08-04 08:56:13

@Weater what firmware version do you have?

sudo mmcli -m 0 --firmware-status

Last edited by ali_akcza (2022-08-04 08:57:10)

GeorgF · 2022-08-04 14:47:58

I also have the same issue.
Here is the output from mmcli:

----------------------
Firmware | method: firehose
| device ids: PCI\VID_1EAC&PID_1001&REV_0000&CARRIER_ROW_COMMERCIAL
| PCI\VID_1EAC&PID_1001&REV_0000
| PCI\VID_1EAC&PID_1001
| PCI\VID_1EAC
| version: EM120RGLAPR02A07M4G_10.010.10.010

Here are some Logs, when the crash appears

Aug 04 16:25:44 georgsarch ModemManager[1432]: <warn> [modem1/bearer3] reloading stats failed: Transaction timed out
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] unexpected port hangup!
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] channel destroyed
Aug 04 16:25:49 georgsarch ModemManager[1432]: <info> [modem1] connection to mbim-proxy for /dev/wwan0mbim0 lost, reprobing
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Releasing 'pdc' client with flags 'release-cid'...
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Unregistered 'pdc' client with ID '1'
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Releasing 'loc' client with flags 'release-cid'...
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Unregistered 'loc' client with ID '1'
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Releasing 'nas' client with flags 'release-cid'...
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Unregistered 'nas' client with ID '5'
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Releasing 'dms' client with flags 'release-cid'...
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Unregistered 'dms' client with ID '1'
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] unexpected port hangup!
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] channel destroyed
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] MBIM error: Cannot write message: Broken pipe
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] MBIM error: Cannot write message: Broken pipe
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] MBIM error: Cannot write message: Broken pipe
Aug 04 16:25:49 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] MBIM error: Cannot write message: Broken pipe
Aug 04 16:25:49 georgsarch ModemManager[1432]: <warn> [modem1/wwan0mbim0/mbim] Couldn't properly close QMI device: Cannot write message: Broken pipe
Aug 04 16:25:49 georgsarch ModemManager[1432]: <info> [base-manager] port wwan0qcdm0 released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'
Aug 04 16:25:49 georgsarch ModemManager[1432]: <info> [base-manager] port wwan0mbim0 released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'
Aug 04 16:25:49 georgsarch ModemManager[1432]: <info> [base-manager] port wwan0at0 released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'
Aug 04 16:25:49 georgsarch ModemManager[1432]: <info> [base-manager] port wwan0 released by device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'
Aug 04 16:25:52 georgsarch ModemManager[1432]: transaction 0x6 aborted, but message is not abortable
Aug 04 16:25:52 georgsarch ModemManager[1432]: transaction 0x7 aborted, but message is not abortable
Aug 04 16:25:52 georgsarch ModemManager[1432]: transaction 0x8 aborted, but message is not abortable
Aug 04 16:25:52 georgsarch ModemManager[1432]: transaction 0x9 aborted, but message is not abortable
Aug 04 16:25:59 georgsarch ModemManager[1432]: opening device...
Aug 04 16:25:59 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Couldn't find descriptors file, possibly not using cdc_mbim
Aug 04 16:25:59 georgsarch ModemManager[1432]: [/dev/wwan0mbim0] Fallback to default max control message size: 4096

Kernel Version: 5.18.16-arch1-1
Notebook X1 Carbon Gen9
libqmi version:

❯ pacman -Ss libqmi
extra/libqmi 1.30.8-1 [Installiert]
QMI modem protocol helper library

Last edited by GeorgF (2022-08-04 14:51:52)

ali_akcza · 2022-08-04 20:08:46

updated today to
EM120RGLAPR02A07M4G_18.018.18.018 using windows, the problem has not yet appeared on this version

EDIT:

problem still appears

ModemManager[602]: <warn> [modem0/bearer1] reloading stats failed: Transaction timed out

Last edited by ali_akcza (2022-08-16 19:27:23)

maichelmann · 2022-08-12 15:20:23

Hi, i have exactly the same issue with an EM120R_GL in an T14s Gen2 AMD. The modem crashes as soon as I start a big download or speedtest.
Fimware: EM120RGLAPR02A07M4G_10.010.10.010

@ali_akcza: You said, that upgrading the firmware through Windows did somehow help?
What do you mean with "problem still appears, just otherwise"? Does it still disconnect each time you do a speedtest, or does it happen less often now?
What have you used to upgrade the firmware from Windows? Maybe I should also give it a try...

ali_akcza · 2022-08-16 20:48:51

@maichelmann hard to say, rather nothing helped.
I used it: https://support.lenovo.com/pl/en/downlo … -20w4-20w5

ali_akcza · 2022-09-08 16:48:40

firmware EM120RGLAPR02A07M4G_19.019.19.019 was released few days ago, is anyone able to test it? because i have changed my modem to other vendor

sikorsky · 2022-09-10 11:31:10

Hey! Good new - I managed to get the modem working by updating the firmware to version EM120RGLAPR02A07M4G_19.019.19.019 (the firmware has to be flashed from windows). So far it seems to be working reliably and I also noticed an increase in throughput.

ali_akcza · 2022-09-14 08:04:25

I confirm, but i have still problem with performance

in log seeing:

wrz 13 23:40:10 kernel: sequence number glitch prev=8 curr=0
wrz 13 23:40:23 kernel: sequence number glitch prev=19 curr=0
wrz 13 23:40:29 kernel: sequence number glitch prev=1 curr=0
wrz 14 00:07:00 kernel: sequence number glitch prev=23 curr=0
wrz 14 00:07:10 kernel: sequence number glitch prev=10 curr=0
wrz 14 00:07:16 kernel: sequence number glitch prev=1 curr=0
wrz 14 00:07:19 kernel: sequence number glitch prev=3 curr=0
wrz 14 00:07:23 kernel: sequence number glitch prev=5 curr=0

Firestar · 2022-11-08 06:39:25

This is your wwan device

WWAN: Quectel EM120R-GL 4G LTE CAT12 No eSIM

I use thinkpad X13 Gen2 Intel (Quectel EM120R-GL, 4G LTE CAT12, M.2 card)

which use the same wwan device as you. I do not appear to see that.

Last edited by Firestar (2022-11-08 15:49:21)

ansemjo · 2022-11-16 10:38:58

sikorsky wrote:

Hey! Good new - I managed to get the modem working by updating the firmware to version EM120RGLAPR02A07M4G_19.019.19.019 (the firmware has to be flashed from windows). So far it seems to be working reliably and I also noticed an increase in throughput.

Thank you! I too had a constantly disappearing modem as mentioned in this thread running firmware version 10.010.10.010. I've used a virtual machine with PCI passthrough and the update file from your link. Another reboot of the Windows machine and I had a pop-up saying I should not shut down as "Windows is preparing my mobile broadband modem" ... or something like that.

Now my modem's firmware reports as EM120RGLAPR02A07M4G_19.019.19.019 and everything seems to work fine under Linux as well.

Arch Linux

#1 2022-01-16 10:07:02

WWAN module randomly disappears

#2 2022-01-16 11:08:40

Re: WWAN module randomly disappears

#3 2022-01-16 11:56:27

Re: WWAN module randomly disappears

#4 2022-01-16 12:00:54

Re: WWAN module randomly disappears

#5 2022-01-16 15:57:14

Re: WWAN module randomly disappears

#6 2022-01-16 20:23:39

Re: WWAN module randomly disappears

#7 2022-01-16 20:38:51

Re: WWAN module randomly disappears

#8 2022-01-17 10:21:54

Re: WWAN module randomly disappears

#9 2022-07-26 21:54:25

Re: WWAN module randomly disappears

#10 2022-08-04 08:56:13

Re: WWAN module randomly disappears

#11 2022-08-04 14:47:58

Re: WWAN module randomly disappears

#12 2022-08-04 20:08:46

Re: WWAN module randomly disappears

#13 2022-08-12 15:20:23

Re: WWAN module randomly disappears

#14 2022-08-16 20:48:51

Re: WWAN module randomly disappears

#15 2022-09-08 16:48:40

Re: WWAN module randomly disappears

#16 2022-09-10 11:31:10

Re: WWAN module randomly disappears

#17 2022-09-14 08:04:25

Re: WWAN module randomly disappears

#18 2022-11-08 06:39:25

Re: WWAN module randomly disappears

#19 2022-11-16 10:38:58

Re: WWAN module randomly disappears

Board footer