Version: unspecified (using KDE 4.6.2) OS: Linux Since upgrading to networkmanager 0.8.998-2 my 3g modem is not found. Using nm-applet at the moment, works perfectly, but the plasma widget does not show the connection and if I press 'Manage connections' and try to add a new, it does not find any modems. Reproducible: Always Steps to Reproduce: Upgrade networkmanager. Actual Results: 3g modem not found. Expected Results: 3g modem found and working Distro: Arch Linux, fully updated, testing repository enabled.
Created attachment 58859 [details] Script to get information about the modem Can you execute the attached script and send me the file /tmp/modem.txt? To execute the script you must save it somewhere and change its permissions (chmod 755 modem.sh).
Created attachment 58886 [details] output from modem.sh script
Also, got this error message when I ran the script, don't know if it's useful: oscar@arch-laptop: [~] >>> ./modem.sh Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
You need to use Plasma NM for NetworkManager 0.9 when using NetworkManager 0.9. Networkmanager 0.8.998-2 is a beta version of NM-0.9. Plasma NM for NM-0.9 is not stable yet but works with my 3G connection. The biggest problem is that it saves secrets (passwords, encryption keys, etc) unencrypted for now and VPN does not work yet. I do not recommend using it until we fix those two problems.
This is working in nm09 branch now.
It still doesn't work here. I just built kdeplasma-applets-networkmanagement from nm09 git, using fully updated kde 4.7 beta1. Modem is now recognized but when trying to connect it immediately says 'connection failed'. I now have a little box in the applet to enable/disable mobile broadband, just as for wireless, but it's impossible to check it. Networkmanager 0.8.9997-1, applet from git.
Never mind my last post, it works as it should. Made a stupid error when testing.
Hm. I don't know if I do anything wrong, but it's still not working for me. I'm quite sure I'm using the right version of the plasmoid. I found this in /var/log/everything.log: Jun 25 23:48:03 arch-laptop NetworkManager[1692]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Jun 25 23:48:03 arch-laptop NetworkManager[1692]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Jun 25 23:48:03 arch-laptop NetworkManager[1692]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Jun 25 23:48:24 arch-laptop NetworkManager[1692]: <warn> GSM connection failed: (32) Serial command timed out Jun 25 23:48:24 arch-laptop NetworkManager[1692]: <info> (ttyUSB0): device state change: prepare -> failed (reason 'unknown') [40 120 1] Jun 25 23:48:24 arch-laptop NetworkManager[1692]: <info> Marking connection 'Tre 3G' invalid. Jun 25 23:48:24 arch-laptop NetworkManager[1692]: <warn> Activation (ttyUSB0) failed. Jun 25 23:48:24 arch-laptop NetworkManager[1692]: <info> (ttyUSB0): device state change: failed -> disconnected (reason 'none') [120 30 0] Jun 25 23:48:24 arch-laptop NetworkManager[1692]: <info> (ttyUSB0): deactivating device (reason: 0). Modem is Huawei E180.
If you use Fedora then y(In reply to comment #9) > Hm. I don't know if I do anything wrong, but it's still not working for me. I'm > quite sure I'm using the right version of the plasmoid. I found this in > /var/log/everything.log: If you use Fedora 15 you probably hit this bug: https://bugzilla.redhat.com/show_bug.cgi?id=698975
(In reply to comment #10) > If you use Fedora then y(In reply to comment #9) > > Hm. I don't know if I do anything wrong, but it's still not working for me. I'm > > quite sure I'm using the right version of the plasmoid. I found this in > > /var/log/everything.log: > > If you use Fedora 15 you probably hit this bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=698975 I am using Arch Linux. The problem in the bug you link to seems to be to create a connection profile. I can do that without problems. The problem now is that it tries to dial but fails.
Well, my Sony MD300 modem works with NM-0.8.9997. Do you have PIN enabled? Did you enabled the "Mobile Broadband" checkbox in main window before trying to connect?
(In reply to comment #12) > Well, my Sony MD300 modem works with NM-0.8.9997. Do you have PIN enabled? No pin. >Did you enabled the "Mobile Broadband" checkbox in main window before trying to > connect? Yes.
Which ModemManager version do you use? Well, the message "Serial command timed out" suggests the modem is not responding. Can you send me the log when connecting with nm-applet?
It does not work with nm-applet either. The log is identical except for one line. Before the serial command time out message there is this line: Dbus[854]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out Does this mean the problem is elsewhere? When rebooting to windows 7 it works, so it's not a problem with signal strength or modem. Modemmanager version is 0.4.997-1.
I use ModemManager 0.4 here, maybe the new MM does not work with your modem. Anyway, if it does not work with nm-applet then the problem is elsewhere. Maybe you do not have usb_modeswitch installed. Several modems, including yours and mine, need to be switched to modem state to be used as modem, usb_modeswitch does that for your modem.