Hide Forgot
Created attachment 1201735 [details] output of mmcli -m 0 Description of problem: I can't connect my Huawei ME906s-158 modem (inside a ThinkPad T460p) anymore under Fedora 24. It used to work back when installing Fedora 24 (albeit with suspend/resume problems), but around the time of the ModemManager 1.6 update it completely stopped working. Using a fedora live usb stick (Workstation 24-1-2, ModemManager 1.4) it works, also connecting under win 10 works fine (so a modem/network problem can be ruled out) Version-Release number of selected component (if applicable): ModemManager 1.6.0-1.fc24 Linux froqpad 4.7.3-200.fc24.x86_64 #1 SMP Wed Sep 7 17:31:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux How reproducible: Try to connect to a cellular network using an up to date Fedora 24 installation and a Huawei ME906s-158. Steps to Reproduce: 1. mmcli -m 0 --enable successfully enabled the modem 2. mmcli -m 0 --simple-connect="apn=internet" error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.NetworkTimeout: Network timeout' Actual results: The modem is unable to connect, whether using mmcli or the gnome network settings UI. Gnome Network Settings UI still reports the modem as disabled and doesn't offer the created modem configurations to selected (dropdown is empty). mmcli reports the modem as enabled though. (output attached) Expected results: The modem connects to the network; Gnome network settings UI shows the correct state and my created modem configurations Additional info: output of mmcli -m 0 after trying to connect is attached.
Created attachment 1201737 [details] output of mmcli -m 0 (cleaned)
same problem here, Or, if network manager has the modem enabled. # mmcli -m 0 --simple-connect="apn=internet" error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.Unknown: No cause information available'
tested on a Fedora 25 live USB stick. still does not work
Tested on antergos live cd, does not work as well. Tested on Ubuntu 16.10, and it works perfectly. What debugging information can I provide from the working Ubuntu version? Kernel version: 4.8.0-22-generic
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Please update bug to Fedora 26, still occurs after upgrading to version 26.
Are you able to: mmcli -G DEBUG then try connecting. When it fails, grab logs with: journalctl -b -u ModemManager > mm-huawei-906s.log and look through the logs and replace any sensitive information (phone numbers, IMSI, IMEI) with XXXX and then attach to this bug.
Created attachment 1308079 [details] mm-huawei-906s.log - log file from Fedora 26 Output from: mmcli -G DEBUG then try connecting. When it fails, grab logs with: journalctl -b -u ModemManager > mm-huawei-906s.log I tried connecting twice. Also going to attach the same log, from Ubuntu 1610, as it modem works in Ubuntu. The code difference appears to be that Ubuntu has <debug> This device (enp0s20f0u2c2) can support ndisdup feature <debug> ^NDISDUP supported, creating huawei bearer... <debug> New huawei bearer created at DBus path '/org/freedesktop/ModemManager1/Bearer/0 Where the Fedora modem manager log does not have any NDISDUP ATA commands, and ends up with an error about the bearer.
Created attachment 1308080 [details] mm-huawei-906s-ubuntu.log - log file from Ubuntu 1610 - works! Output from: mmcli -G DEBUG journalctl -b -u ModemManager > mm-huawei-906s-ubuntu.log This is useful for comparison. Same hardware, but booted into Ubuntu. Same network manager configuration as far as I can tell. Here, it detects the modem is huawei and creates a New huawei bearer. It then uses AT^NDISDUP=1,1,"internet"<CR>
Any ideas how I can debug why the huawei plugin is not leaping into life on Fedora and creating a bearer? Glen
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.