Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 588882 - Cannot connect to wireless network
Cannot connect to wireless network
Status: CLOSED DUPLICATE of bug 588814
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
13
All Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-04 14:42 EDT by Ulrich Hobelmann
Modified: 2010-05-04 23:28 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-04 23:28:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ulrich Hobelmann 2010-05-04 14:42:45 EDT
Description of problem:
After the latest push on F13-updates-testing, I cannot connect to wireless anymore. NetworkManager tries to login, but seems to fail. Booting the previous kernel failed, too, as did downgrading all NetworkManager packages. So I really have no idea what the problem is.

Machine is a Samsung NC10 with ath5k wireless.

Connecting to wired LAN still works.

Version-Release number of selected component (if applicable):
kernel 2.6.33.3-72.fc13.i686 (or 2.6.33.2)
NetworkManager.i686                1:0.8.0-7.git20100422.fc13  @fedora          
NetworkManager-glib.i686           1:0.8.0-7.git20100422.fc13  @fedora          
NetworkManager-gnome.i686          1:0.8.0-7.git20100422.fc13  @fedora          
NetworkManager-openconnect.i686    0.8.0-1.git20100411.fc13    @updates-testing 
NetworkManager-openvpn.i686        1:0.8-2.git20100411.fc13    @updates-testing 
NetworkManager-pptp.i686           1:0.8.0-1.git20100411.fc13  @updates-testing 
NetworkManager-vpnc.i686           1:0.8.0-1.git20100411.fc13  @updates-testing
(NM 1:0.8.0-8 also failed).

How reproducible:
Try to login to a wireless network. Give password if asked.
Comment 1 Holger Wesser 2010-05-04 15:31:19 EDT
Same here on a Sony Vaio VGN-Z51XG. Establishing a connection to a 3G-network is also not possible.

Output of /var/log/messages:

May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) starting connection 'Auto my_accesspoint'
May  4 18:38:06 howe-notebook NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0)
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May  4 18:38:06 howe-notebook NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto my_accesspoint' has security, but secrets are required.
May  4 18:38:06 howe-notebook NetworkManager: <info> (wlan0): device state change: 5 -> 6 (reason 0)
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May  4 18:38:06 howe-notebook NetworkManager: <info> (wlan0): device state change: 6 -> 4 (reason 0)
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May  4 18:38:06 howe-notebook NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto my_accesspoint' has security, and secrets exist.  No new secrets needed.
May  4 18:38:06 howe-notebook NetworkManager: <info> Config: added 'ssid' value 'my_accesspoint'
May  4 18:38:06 howe-notebook NetworkManager: <info> Config: added 'scan_ssid' value '1'
May  4 18:38:06 howe-notebook NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May  4 18:38:06 howe-notebook NetworkManager: <info> Config: added 'psk' value '<omitted>'
May  4 18:38:06 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May  4 18:38:06 howe-notebook NetworkManager: <info> Config: set interface ap_scan to 1
May  4 18:38:06 howe-notebook NetworkManager: <info> (wlan0): supplicant connection state:  inactive -> scanning
May  4 18:38:08 howe-notebook NetworkManager: <info> (wlan0): supplicant connection state:  scanning -> associating
May  4 18:38:08 howe-notebook kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May  4 18:38:08 howe-notebook kernel: cfg80211: Calling CRDA for country: DE
May  4 18:38:08 howe-notebook NetworkManager: <info> (wlan0): supplicant connection state:  associating -> associated
May  4 18:38:08 howe-notebook kernel: cfg80211: Current regulatory domain updated by AP to: DE
May  4 18:38:08 howe-notebook kernel:    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May  4 18:38:08 howe-notebook kernel:    (2402000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
May  4 18:38:08 howe-notebook NetworkManager: <info> (wlan0): supplicant connection state:  associated -> 4-way handshake
May  4 18:38:09 howe-notebook kernel: Intel AES-NI instructions are not detected.
May  4 18:38:09 howe-notebook kernel: padlock: VIA PadLock not detected.
May  4 18:38:09 howe-notebook NetworkManager: <info> (wlan0): supplicant connection state:  4-way handshake -> group handshake
May  4 18:38:09 howe-notebook NetworkManager: <info> (wlan0): supplicant connection state:  group handshake -> completed
May  4 18:38:09 howe-notebook NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'my_accesspoint'.
May  4 18:38:09 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
May  4 18:38:09 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
May  4 18:38:09 howe-notebook NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0)
May  4 18:38:09 howe-notebook NetworkManager: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May  4 18:38:10 howe-notebook NetworkManager: <info> dhclient started with pid 3335
May  4 18:38:10 howe-notebook NetworkManager: <info> (wlan0): device state change: 7 -> 9 (reason 0)
May  4 18:38:10 howe-notebook NetworkManager: <warn> Activation (wlan0) failed for access point (my_accesspoint)
May  4 18:38:10 howe-notebook NetworkManager: <info> Marking connection 'Auto my_accesspoint' invalid.
May  4 18:38:10 howe-notebook NetworkManager: <warn> Activation (wlan0) failed.
May  4 18:38:10 howe-notebook NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
May  4 18:38:10 howe-notebook NetworkManager: <info> (wlan0): device state change: 9 -> 3 (reason 0)
May  4 18:38:10 howe-notebook NetworkManager: <info> (wlan0): deactivating device (reason: 0).
May  4 18:38:10 howe-notebook NetworkManager: <info> (wlan0): canceled DHCP transaction, DHCP client pid 3335
Comment 2 Holger Wesser 2010-05-04 15:38:44 EDT
Btw: Possible duplicate #588814
Comment 3 Ulrich Hobelmann 2010-05-04 15:54:45 EDT
Bug #588814 is right in that downgrading NetworkManager DOES in fact solve the problem.  I just had to reboot for it to be effective.
Comment 4 Dan Williams 2010-05-04 23:28:59 EDT

*** This bug has been marked as a duplicate of bug 588814 ***

Note You need to log in before you can comment on or make changes to this bug.