Description of problem: in fedora 24 are no mobile Broadband (UMTS / Surf Stick) working. you can´ t see the mobile connection in the networkmanager Version-Release number of selected component (if applicable):actual version ogf f24 beta relase How reproducible:everytime Steps to Reproduce: 1.Boot fedora 2.go on a place without WLAN 3.put your surfstick in any USB port on your Notebook Actual results: Surfstick did not detect and ist not working Expected results: Surfstick works Additional info:
For exaple: I using the Huwai E3051 and the Huwai E303
Did the modem worked before in previous Fedoras? $ rpm -q NetworkManger $ rpm -q ModemManager $ mmcli -L $ sudo journalctl -b 0 -u NetworkManager Any errors in dmesg output?
I see any errors... rpm -q NetworkManger Das Paket NetworkManger ist nicht installiert [root@localhost dfiedler]# dnf install NetworkManager Letzte Prüfung auf abgelaufene Metadaten: vor 4:36:13 am Wed Jul 27 16:02:07 2016. Paket NetworkManager-1:1.2.2-2.fc24.x86_64 ist bereits installiert, wird übersprungen. Abhängigkeiten sind aufgelöst. Nichts zu tun. Komplett! rpm -q ModemManager Das Paket ModemManager ist nicht installiert [root@localhost dfiedler]# dnf install ModemManager Letzte Prüfung auf abgelaufene Metadaten: vor 4:37:14 am Wed Jul 27 16:02:07 2016. Fehler: package ModemManager-1.6-0.3.rc3.fc24.i686 requires libmbim-utils, but none of the providers can be installed (Fügen Sie »--allowerasing« zur Befehlszeile hinzu, um die problematischen Pakete zu ersetzen) mmcli -L bash: mmcli: Befehl nicht gefunden... Soll das Paket »ModemManager« installiert werden, welches den Befehl »mmcli« bereitstellt? [N/y] y * Warten in Warteschlange... * Paketliste wird geladen.... Die folgenden Pakete müssen heruntergestuft werden: libmbim-1.12.4-2.fc24.x86_64 Support library for the Mobile Broadband Interface Model protocol libqmi-1.14.2-1.fc24.x86_64 Support library to use the Qualcomm MSM Interface (QMI) protocol Die folgenden Pakete müssen installiert werden: ModemManager-1.6-0.3.rc3.fc24.x86_64 Mobile broadband modem management service libmbim-utils-1.12.4-2.fc24.x86_64 Utilities to use the MBIM protocol from the command line libqmi-utils-1.14.2-1.fc24.x86_64 Utilities to use the QMI protocol from the command line Mit Änderungen fortfahren? [N/y] y * Warten in Warteschlange... * Warten auf Legitimation... * Warten in Warteschlange... * Pakete werden heruntergeladen... * Daten werden abgefragt... * Änderungen werden getestet... * Signaturen werden überprüft... * Aktualisierungen werden installiert... * Signaturen werden überprüft... * Aktualisierungen werden installiert... * Pakete werden installiert... * Pakete werden bereinigt... error: couldn't find the ModemManager process in the bus sudo journalctl -b 0 -u NetworkManager -- Logs begin at Mi 2016-06-22 18:23:32 CEST, end at Mi 2016-07-27 20:42:26 CEST Jul 27 20:31:42 localhost.localdomain systemd[1]: Starting Network Manager... Jul 27 20:31:45 localhost.localdomain NetworkManager[1016]: <info> [1469644305. Jul 27 20:31:45 localhost.localdomain NetworkManager[1016]: <info> [1469644305. Jul 27 20:31:45 localhost.localdomain NetworkManager[1016]: <info> [1469644305. Jul 27 20:31:45 localhost.localdomain NetworkManager[1016]: <info> [1469644305. Jul 27 20:31:45 localhost.localdomain NetworkManager[1016]: <info> [1469644305. Jul 27 20:31:45 localhost.localdomain NetworkManager[1016]: <info> [1469644305. Jul 27 20:31:45 localhost.localdomain NetworkManager[1016]: <info> [1469644305. Jul 27 20:31:45 localhost.localdomain NetworkManager[1016]: <info> [1469644305. Jul 27 20:31:45 localhost.localdomain systemd[1]: Started Network Manager. Jul 27 20:31:46 localhost.localdomain NetworkManager[1016]: <info> [1469644306. Jul 27 20:31:46 localhost.localdomain NetworkManager[1016]: <info> [1469644306. Jul 27 20:31:46 localhost.localdomain NetworkManager[1016]: <info> [1469644306. Jul 27 20:31:46 localhost.localdomain NetworkManager[1016]: <info> [1469644306. Jul 27 20:31:46 localhost.localdomain NetworkManager[1016]: <info> [1469644306. Jul 27 20:31:47 localhost.localdomain NetworkManager[1016]: <info> [1469644307. Jul 27 20:31:47 localhost.localdomain NetworkManager[1016]: <info> [1469644307. Jul 27 20:31:47 localhost.localdomain NetworkManager[1016]: <info> [1469644307. Jul 27 20:31:47 localhost.localdomain NetworkManager[1016]: <info> [1469644307. Jul 27 20:31:47 localhost.localdomain NetworkManager[1016]: <info> [1469644307. Jul 27 20:31:47 localhost.localdomain NetworkManager[1016]: <info> [1469644307. Jul 27 20:31:47 localhost.localdomain NetworkManager[1016]: <info> [1469644307. lines 1-23 more see next post
for dmseg see http://paste.fedoraproject.org/396532/14696453/
Please install ModemManager package. And make sure you have the latest one, there was a problem with modem modeswitching (bug 1354142).
I do have the same problem here. Web'n Walk Surfstick... The Option 225 one... On Fedora 20 ... works (The machine I am writing from) On Fedora 22 ... works On Fedora 24 ... fail! When I plug in the UMTS Stick in Fedora 20 / 22, then the ttyHS* devices are created, the hso.ko module is being loaded and you can put the connection up with nmcli d up <uuid> uuid = the connection for the UMTS stick as created with the mobile network editor wizard. With Fedora 22 / 22, this works... With Fedora 24 this fails and returns that no suitable device is being found. With Fedora 24 not even the ttyHS* devices are created nor will the hso.ko Kernel module being load. Not even the correct chmod/chown is set for the ttyHS* devices (660 root.dialout). This drives me nuts today, because my ISP has a total failout today and I relied on using the UMTS stick to get at least some stuff done. NetworkManager 1.2.4 ModemManager 1.6.0 usb_modeswitching 2.4.0 I even downgraded / upgraded a bunch of these, to see if something changed. Same issues. systemctl start NetworkManager systemctl start ModemManager systemctl enable NetworkManager systemctl enable ModemManager ...all done... No changes!
After some more digging (downgrading Kernel etc) I also downgraded usb_modeswitchback to 2.3.0-1 and the issues I got with *my* UMTS Stick are gone. I then re-updated the kernel again and made sure that everything else is updated as well.. (this also updated modeswitch back to 2.4.0-4) and the issues are back again... downgrading explicitly usb_modeswitch to 2.3.0-1 solved the issues. So the problem must be in usb_modeswitch 2.4.0-4
(In reply to Ali Akcaagac from comment #7) > After some more digging (downgrading Kernel etc) I also downgraded > usb_modeswitchback to 2.3.0-1 and the issues I got with *my* UMTS Stick are > gone. I then re-updated the kernel again and made sure that everything else > is updated as well.. (this also updated modeswitch back to 2.4.0-4) and the > issues are back again... > > downgrading explicitly usb_modeswitch to 2.3.0-1 solved the issues. So the > problem must be in usb_modeswitch 2.4.0-4 A udev rule probably changed. You might look in (compare) the /usr/lib/udev/rules.d/40-usb_modeswitch.rules file. Would use run 'lsusb' to identify the modem. And also dmesg output would be helpful (when you plug in the stick).
(In reply to Blueowl from comment #8) > A udev rule probably changed. You might look in (compare) the > /usr/lib/udev/rules.d/40-usb_modeswitch.rules file. > > Would use run 'lsusb' to identify the modem. And also dmesg output would be > helpful (when you plug in the stick). Thanks for the feedback. Short: dnf remove usb_modeswitch* Was the solution! Long: I tried the steps that you suggested already. Compared the rules, compared the device list, compared the systemd.service file, compared the usb_modeswitch udev script and so on. At the end I figured out, that the usb_modeswitch_dispatcher caused the issue. When removing the udev usb_modeswitch file, my HSDPA stick works normally. Leaving the file there will render the HSDPA stick useless - because (what I assume) the hso.ko driver seem (I am not sure) to put the Option iCON 225 (web'n walk stick from t-mobile) already in the right "modem" state. So a switch wasn't necessary. Calling the dispatcher looks the HSDPA stick up (and it's also listed in the devices list) but renders it unusable. Why and how I don't know. The usb_modeswitch-2.3.0 udev dispatcher script (not the rules list) called up the "if else" clause differently and ended up triggering nothing, while the new usb_modeswitch-2.4.0 udev dispatcher script calls up systemd directly and this renders the HSDPA stick useless *for me*. Rather than leaving the state as is and simply exiting, it seem to have changed something. I first thought that this might have something to do with the order how systemd loads up the script... I played around with some After and Before keywords to make sure that all kernel drivers are loaded etc... But this didn't help... At the end I concluded as follows. If the udev_modeswitch dispatcher script isn't needed, then the entire udev_modeswitch* is not needed *for me*... Though figuring this out costs 2 days of work (also to understand it). Maybe something in the hso.ko has changed ? On my older Fedora 20/22 installations the usb_modeswitch was always part of the Workspace installation. Same for Fedora 24... but on 24 this rendered the stick useless... until modeswitch was uninstalled. I also filled a different bug-report on bugzilla... Explaining my steps in more detail... https://bugzilla.redhat.com/show_bug.cgi?id=1373274
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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.