Bug 1214353 - mhi: Enabling broadband connecting not working
Summary: mhi: Enabling broadband connecting not working
Status: NEW
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Network (show other bugs)
Version: Leap 15.6
Hardware: x86-64 openSUSE Leap 15.5
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Takashi Iwai
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-17 08:45 UTC by Holger Sickenberg
Modified: 2024-07-16 11:27 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
hwinfo.txt (724.92 KB, text/plain)
2023-08-17 08:45 UTC, Holger Sickenberg
Details
journalctl_-u_ModemManager.txt (9.11 KB, text/plain)
2023-08-17 08:48 UTC, Holger Sickenberg
Details
dmesg-6.5.5-lp154.3.g6cf5261-default (94.31 KB, text/plain)
2023-09-27 09:13 UTC, Holger Sickenberg
Details
journalctl_-u_ModemManager-6.5.5 (10.61 KB, text/plain)
2023-09-27 09:14 UTC, Holger Sickenberg
Details
journalctl_-u_ModemManager-6.10.0-rc7.txt (9.22 KB, text/plain)
2024-07-12 15:11 UTC, Holger Sickenberg
Details
dmesg-6.10.0-rc7.txt (99.19 KB, text/plain)
2024-07-12 15:12 UTC, Holger Sickenberg
Details
journalctl_-u_ModemManager_-u_NetworkManager.txt (9.24 KB, text/plain)
2024-07-16 11:27 UTC, Holger Sickenberg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Sickenberg 2023-08-17 08:45:40 UTC
Created attachment 868851 [details]
hwinfo.txt

When trying to use broadband connecting with network manager, I can not get beyond entering SIM code - starting connection does not work

  System Slot: #36
    Designation: "M.2 WWAN Connector (J3702)"
    Type: 0xa6 (Other)
    Bus Width: 0x08 (Other)
    Status: 0x03 (Available)
    Length: 0x04 (Long)
    Slot ID: 4
    Characteristics: 0x0704 (3.3 V, PME#, Hot-Plug)
Comment 1 Holger Sickenberg 2023-08-17 08:48:32 UTC
Created attachment 868852 [details]
journalctl_-u_ModemManager.txt
Comment 2 Takashi Iwai 2023-08-19 07:31:25 UTC
Is it a Leap kernel problem?  If you install the kernel from OBS Kernel:stable:Backport, does it start working?
Comment 3 Holger Sickenberg 2023-09-27 09:13:34 UTC
Created attachment 869786 [details]
dmesg-6.5.5-lp154.3.g6cf5261-default

I don't think the 6.5.5 kernel is improving the situation in any sense. See new logs attached.
Comment 4 Holger Sickenberg 2023-09-27 09:14:08 UTC
Created attachment 869787 [details]
journalctl_-u_ModemManager-6.5.5
Comment 5 Holger Sickenberg 2024-06-12 09:08:13 UTC
Same problem with Leap 15.6
Comment 6 Takashi Iwai 2024-06-17 16:11:45 UTC
You can try the latest kernel from OBS Kernel:stable:Backport or Kernel:HEAD:Backport repo.  If it doesn't work with those, it means that the problem is in the upstream kernel, and it should be handled in the upstream tracker.
Comment 7 Holger Sickenberg 2024-07-12 15:11:31 UTC
Created attachment 876030 [details]
journalctl_-u_ModemManager-6.10.0-rc7.txt
Comment 8 Holger Sickenberg 2024-07-12 15:12:15 UTC
Created attachment 876031 [details]
dmesg-6.10.0-rc7.txt

Still no improvements with latest kernel from Kernel:HEAD:Backport
Comment 9 Takashi Iwai 2024-07-15 14:44:24 UTC
Then at best please report to the upstream devs.

But, looking through the modem log, I noticed the following line:
  [modem0] error initializing: Modem is currently locked, cannot fully initialize

Is the SIM card really usable for this device?
Comment 10 Holger Sickenberg 2024-07-16 08:32:35 UTC
I found https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg6051059.html

And after the command

# mbimcli -p -d /dev/wwan0mbim0 --quectel-set-radio-state=on

The connection could be started:

Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] simple connect started...
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] simple connect state (3/10): enable
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] state changed (disabled -> enabling)
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] power state updated: on
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] simple connect state (4/10): wait to get fully enabled
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] state changed (enabling -> enabled)
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] 3GPP registration state changed (unknown -> registering)
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] simple connect state (5/10): wait after enabled
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] 3GPP registration state changed (registering -> home)
Jul 16 10:27:19 t14s ModemManager[19631]: <info>  [modem0] state changed (enabled -> registered)
Jul 16 10:27:20 t14s ModemManager[19631]: <info>  [modem0] simple connect state (6/10): register
Jul 16 10:27:20 t14s ModemManager[19631]: <info>  [modem0] simple connect state (7/10): wait to get packet service state attached
Jul 16 10:27:20 t14s ModemManager[19631]: <info>  [modem0] simple connect state (8/10): bearer
Jul 16 10:27:20 t14s ModemManager[19631]: <info>  [modem0] simple connect state (9/10): connect
Jul 16 10:27:20 t14s ModemManager[19631]: <info>  [modem0] state changed (registered -> connecting)
Jul 16 10:27:20 t14s ModemManager[19631]: <info>  [modem0/bearer1] reloading stats is supported by the device
Jul 16 10:27:20 t14s ModemManager[19631]: <info>  [modem0] state changed (connecting -> connected)
Jul 16 10:27:20 t14s ModemManager[19631]: <info>  [modem0] simple connect state (10/10): all done
Jul 16 10:29:27 t14s ModemManager[19631]: <info>  [modem0] state changed (connected -> disconnecting)
Jul 16 10:29:27 t14s ModemManager[19631]: <info>  [modem0] state changed (disconnecting -> registered)
Jul 16 10:29:27 t14s ModemManager[19631]: <info>  [modem0/bearer1] connection #1 finished: duration 127s, tx: 106835 bytes, rx: 140370 bytes
Comment 11 Holger Sickenberg 2024-07-16 11:27:28 UTC
Created attachment 876068 [details]
journalctl_-u_ModemManager_-u_NetworkManager.txt

Log for running command:
mbimcli -p -d /dev/wwan0mbim0 --quectel-set-radio-state=on

first as user (failed with "couldn't enable interface: 'Invalid transition'"), then via sudo (passed)