Description of problem:
NetworkManager does not connect over the Internet automatically at boot.
Moreover, being necessary to physically disconnect and reconnect the modem so I have to manually connect through it.
It reconfigured the connection and set up options to automatically connect and connection system.
Sometimes, I have to use kppp to connect, because the NM takes too long to establish the connection.
Version-Release number of selected component (if applicable):
Start the computer with the modem plugged.
I have to manually connect.
The connection is automatically established.
Modem. ZTE MF 626.
In the previous version worked correctly.
This only happens on 3G connection.
Are you using KDE's kde-plasma-networkmanagement, right?
First, try to upgrade as there's a newer version.
Also, please report NM version:
rpm -q NetworkManager
and attach /var/log/messages so that we can see logs.
(In reply to comment #2)
> Are you using KDE's kde-plasma-networkmanagement, right?
> First, try to upgrade as there's a newer version.
> Also, please report NM version:
> rpm -q NetworkManager
> and attach /var/log/messages so that we can see logs.
My system is updated.
1 - log_messages.tar.gz /var/log/messages since 11 sep
2 - log_messages2.tar.gz /var/log/messages since august with "grep Network"
Need anything else?
Created attachment 523369 [details]
/var/log/messages since 13/09/2011
Created attachment 523371 [details]
/var/log/messages with "grep Network"
Version : 0.9
Release : 0.54.20110812git.nm09.fc15
V(In reply to comment #3)
> (In reply to comment #2)
> > Are you using KDE's kde-plasma-networkmanagement, right?
> > First, try to upgrade as there's a newer version.
> > Also, please report NM version:
> > rpm -q NetworkManager
> > and attach /var/log/messages so that we can see logs.
> My system is updated.
> The attachments:
> 1 - log_messages.tar.gz /var/log/messages since 11 sep
> 2 - log_messages2.tar.gz /var/log/messages since august with "grep Network"
> Need anything else?
Thanks for the logs, there are some errors returned by Modem-Manager, but also auto-activation is interrupted several times by your manual activation (you were impatient;).
It would be useful to get more detailed logs. Would you please try this:
1) Disable NM temporarily:
# systemctl disable NetworkManager.service
2) reboot with modem plugged
3) Follow steps at http://live.gnome.org/NetworkManager/Debugging on section "Debugging NetworkManager 0.8 and 0.9 3G connections"
to run ModemManager and NetworkManager
(Copy the instructions before reboot, as you won't have network after step 1)
4) Wait will the connection is auto-activated
5) Grab the logs from terminal
6) Re-enable NM:
# systemctl enable NetworkManager.service
Not related to this bug:
Consider disabling intel_ips driver as it polutes messages with "ME failed to update for more than 1s, likely hung" and could down system performance. See e.g. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658317
Following is the log requested.
The option to enable 3G network was checked automatically (see picture attached). Not now.
When i saw the login screen (X), the connection was activated. Now, I need to check the option to enable 3G network to connect it (and sometimes can'ot connect by NM).
I stopped because was very slow.
It was faster to stop and manually connect (or use Kppp) than wait it.
Thanks for the tip of the module intel_ips!
Thanks for help me!
Created attachment 523758 [details]
Log modem-manager --debug
Created attachment 523759 [details]
Printscreen of NM Plasma plugin
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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.
The process we are following is described here: