[Bug 1214353] New: mhi: Enabling broadband connecting not working
https://bugzilla.suse.com/show_bug.cgi?id=1214353 Bug ID: 1214353 Summary: mhi: Enabling broadband connecting not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: holgi@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868851 --> https://bugzilla.suse.com/attachment.cgi?id=868851&action=edit 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) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c1 --- Comment #1 from Holger Sickenberg <holgi@suse.com> --- Created attachment 868852 --> https://bugzilla.suse.com/attachment.cgi?id=868852&action=edit journalctl_-u_ModemManager.txt -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |tiwai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |holgi@suse.com Flags| |needinfo?(holgi@suse.com) --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- Is it a Leap kernel problem? If you install the kernel from OBS Kernel:stable:Backport, does it start working? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c3 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(holgi@suse.com) | --- Comment #3 from Holger Sickenberg <holgi@suse.com> --- Created attachment 869786 --> https://bugzilla.suse.com/attachment.cgi?id=869786&action=edit 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c4 --- Comment #4 from Holger Sickenberg <holgi@suse.com> --- Created attachment 869787 --> https://bugzilla.suse.com/attachment.cgi?id=869787&action=edit journalctl_-u_ModemManager-6.5.5 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c5 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 15.5 |Leap 15.6 --- Comment #5 from Holger Sickenberg <holgi@suse.com> --- Same problem with Leap 15.6 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c6 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(holgi@suse.com) --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c7 --- Comment #7 from Holger Sickenberg <holgi@suse.com> --- Created attachment 876030 --> https://bugzilla.suse.com/attachment.cgi?id=876030&action=edit journalctl_-u_ModemManager-6.10.0-rc7.txt -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c8 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(holgi@suse.com) | --- Comment #8 from Holger Sickenberg <holgi@suse.com> --- Created attachment 876031 --> https://bugzilla.suse.com/attachment.cgi?id=876031&action=edit dmesg-6.10.0-rc7.txt Still no improvements with latest kernel from Kernel:HEAD:Backport -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c9 --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- 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? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c10 --- Comment #10 from Holger Sickenberg <holgi@suse.com> --- 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 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214353 https://bugzilla.suse.com/show_bug.cgi?id=1214353#c11 --- Comment #11 from Holger Sickenberg <holgi@suse.com> --- Created attachment 876068 --> https://bugzilla.suse.com/attachment.cgi?id=876068&action=edit 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) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com