| Summary: | Modem is no longer recognized since update to 1.4 | ||
|---|---|---|---|
| Product: | ModemManager | Reporter: | Raphael Michel <mail> |
| Component: | plugins | Assignee: | ModemManager bug user <modemmanager> |
| Status: | RESOLVED NOTOURBUG | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | ||
| Version: | 1.4 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
systemctl status ModemManager -l -n 100
ModemManager --debug ModemManager --debug version 1.2.0 |
||
Weird, can you try to get debug logs? $ sudo systemctl disable ModemManager $ sudo systemctl stop ModemManager $ sudo /usr/sbin/ModemManager --debug (reproduce your issue) And to recover your system back to normal: $ sudo systemctl enable ModemManager $ sudo systemctl start ModemManager Created attachment 113643 [details]
ModemManager --debug
Sure, debug output is attached.
If it helps, hardware is absolutely okay, I get a working connection when using wvdial instead of ModemManager.
(In reply to Raphael Michel from comment #2) > Created attachment 113643 [details] > ModemManager --debug > > Sure, debug output is attached. > > If it helps, hardware is absolutely okay, I get a working connection when > using wvdial instead of ModemManager. ModemManager is using MBIM + the network interface, instead of AT commands, so the sequence is totally different than the one you would get with wvdial. Strange thing, we're getting NoDeviceSupport errors all the time. Any chance you can retest with MM 1.2 to see how different is the debug log? Created attachment 113644 [details]
ModemManager --debug version 1.2.0
I did downgrade to ModemManager v1.2.0 but the bug persisted.
I therefore can't say for sure that it broke with the 1.4 update, I can only say that it definitely did work two months ago and that it does not work now and that I did upgrade to 1.4 in the meantime...
(In reply to Raphael Michel from comment #4) > Created attachment 113644 [details] > ModemManager --debug version 1.2.0 > > I did downgrade to ModemManager v1.2.0 but the bug persisted. > I therefore can't say for sure that it broke with the 1.4 update, I can only > say that it definitely did work two months ago and that it does not work now > and that I did upgrade to 1.4 in the meantime... Hum, ok, so maybe it's not ModemManager related. Could you try to run the following *while* MM is in --debug? You can switch to MM 1.4 again better. $ sudo mmcli -m 0 --simple-connect="apn=sipgate,user=sipgate,password=sipgate,ip-type=ipv4" Oh, nevermind, this issue is a known one: https://bugzilla.gnome.org/show_bug.cgi?id=733696 Quoting: 2) It appears that in some cases, MM will report that modem supports PDP context types it in actuality does not. Currently, this happens with all MBIM modems that does not really support IPV4V6 (including the F5321gw): http://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-broadband-modem-mbim.c?id=0284daf87e8f0ba780a4dcbe4741713cb3c779eb#n486 Any connection attempt using such a modem will fail: <warn> (cdc-wdm1) failed to connect modem: NoDeviceSupport <warn> Activation (cdc-wdm1) failed for connection 'Default (telenor.mobil)' I can successfully establish a connection as soon as I disable IPv6 in the NetworkManager connection profile, so I think you are right that it is the problem mentioned in the gnome bugtracker. So should we change this bug's title, close it as duplicate or keep it? (In reply to Raphael Michel from comment #7) > I can successfully establish a connection as soon as I disable IPv6 in the > NetworkManager connection profile, so I think you are right that it is the > problem mentioned in the gnome bugtracker. > > So should we change this bug's title, close it as duplicate or keep it? Good, good. Let's close it here, I'm already looking at modifying the NM logic. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 113642 [details] systemctl status ModemManager -l -n 100 Hello, I'm using Arch Linux on a Thinkpad x230 with an Ericsson H5321 gw WWAN module. I recently upgraded from ModemManager 1.2.0 to 1.4.2 and my UMTS device stopped working. It still shows up in NetworkManager and shows available cellular networks but any connection attempt is immediately aborted. I attached a log file from ModemManager which includes ModemManager's startup and one unsuccessful connection attempt. $ lsusb Bus 001 Device 011: ID 0bdb:1926 Ericsson Business Mobile Networks BV Any ideas what I can do to fix it or help debug it?