Red Hat Bugzilla – Bug 220980
NetworkManager fails on initial boot with ipw3945
Last modified: 2008-05-06 13:15:39 EDT
Description of problem:
NetworkManager is not able to initiate a wifi connection (ipw3945d) to a
WEP-protected access point on initial boot. A supplemental restart of ipw3945d
and NetworkManager is required.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enable services on boot: ipw3945d, NetworkManger
2. Disable wifi interface on boot (ONBOOT=no in ifcfg-XXX)
3. Disable kudzu so that it doesn't regenerate ifcfg-XXX files
4. Boot system
5. Log in using KDE
6. Start knetworkmanager (possibly automatically as per a saved session)
To work around the problem, alter the steps as follows:
5. Log in using KDE, without running knetworkmanager during session startup
6. Open a root shell, and type 'service ipw3945d restart'
7. Start knetworkmanager
WiFi authentication times out, and knetworkmanager prompts for a new WEP key.
WiFI should authenticate automatically.
The system is a Thinkpad T60 with Intel ipw3945d wireless. Wired LAN is not
My own dumb analysis of the problem would be that somehow ipw3945d is "stuck",
and NetworkManager is not able to get it to associate with the access point.
Using NetworkManager and knetworkmanager, this behavior is easily reproducible.
My previous network setup used vanilla RedHat startup scripts (ifcfg-XXX) plus
some wpa_supplicant tricks as per BUG154348. This worked consistently; the
initial bringup would fail, leaving dhclient running in the background, and
wpa_supplicant would retry as long as necessary. On the other hand I can
definitely say that this method started up quicker than the 40s or so timeout
that NetworkManager/knetworkmanager enforces, though.
I suspect this behavior is being triggered by
What's happening on my system is that
1. NetworkManager starts at boot-time and tries to associate with my wireless NIC
2. The wpa_supplicant.conf file is invalid, so the boot-time interface bringup
3. NetworkManager leaves wpa_supplicant running.
4. When I log in to KDE, knetworkmanager starts a *second* instance of
5. The userland AP configuration is correct, but it's fighting with the first
instance of wpa_supplicant, and loses.
My observation about having to restart NetworkManager and/or ipw3945d was
clearing up the problem by forcing the boot-time NetworkManager instance to shut
down its *first* wpa_supplicant instance, thereby allowing the userland instance
to associate properly.
I confirm this bug, same problem and same workaround. FYI, setting up the wifi
connection with iwconfig/ifconfig works fine.
This behavior appears to be similar in F7 test 1.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.