You are not logged in.
UPDATE: I installed netcfg, but it wouldn't work from the commandline, so I didn't think that was the problem. However, replacing networkmanager with netcfg in rc.conf, fixes my problem. So this is either a configuration issue with networkmanager or a bug. In any case, if networkmanager starts as a daemon, nothing can bring up the wireless.
When I start up networkmanager, wlan0 associates and then it instantly disassociates. It worked prior to today. It looks like I updated networkmanager as well as the kernel yesterday. I'm not sure what information would be useful to others, but here's the output from dmesg:
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
iwlagn 0000:02:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn: Tunable channels: 13 802.11bg, 19 802.11a channels
phy0: Selected rate control algorithm 'iwl-agn-rs'
iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
iwlagn 0000:02:00.0: irq 760 for MSI/MSI-X
iwlagn 0000:02:00.0: firmware: requesting iwlwifi-4965-2.ucode
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with AP 00:0b:86:ce:a6:e0
wlan0: authenticated
wlan0: associate with AP 00:0b:86:ce:a6:e0
wlan0: RX AssocResp from 00:0b:86:ce:a6:e0 (capab=0x421 status=0 aid=1)
wlan0: associated
wlan0: disassociating by local choice (reason=3)And pacman.conf:
[2009-02-08 13:29] synchronizing package lists
[2009-02-08 13:29] starting full system upgrade
[2009-02-08 13:36] starting full system upgrade
[2009-02-08 13:38] upgraded binutils (2.19-1 -> 2.19.1-1)
[2009-02-08 13:38] upgraded ed (1.1-2 -> 1.2-1)
[2009-02-08 13:38] upgraded file (4.26-1 -> 5.00-1)
[2009-02-08 13:38] upgraded git (1.6.1.2-1 -> 1.6.1.3-1)
[2009-02-08 13:38] upgraded hal (0.5.11-4 -> 0.5.11-7)
[2009-02-08 13:39] upgraded kernel26 (2.6.28.2-1 -> 2.6.28.3-1)
[2009-02-08 13:39] upgraded libnetworkmanager (0.6.6-1 -> 0.7.0-1)
[2009-02-08 13:39] installed libpcap (1.0.0-1)
[2009-02-08 13:39] installed ppp (2.4.4-7)
[2009-02-08 13:39] upgraded networkmanager (0.6.6-1 -> 0.7.0-1)
[2009-02-08 13:39] upgraded patch (2.5.9-1 -> 2.5.9-2)
[2009-02-08 13:39] upgraded tzdata (2008i-1 -> 2009a-1)Thanks in advance.
edit: That's what happens at the work (university). At home it just times out while trying to associate. I just use WEP encryption there, and like I've said, it worked before the update. I tried downgrading the kernel, but I have the same problems. I may try downgrading networkmanager too, but I haven't been able to get it to work using iwconfig, so it doesn't really feel like that's the issue. Also, wireless works in Windows, so I know it's a software thing. Oh, and this is what gets logged to /var/log/messages.log (eth0 entries removed):
Feb 10 00:12:26 eve NetworkManager: <info> wlan0: driver is 'iwlagn'.
Feb 10 00:12:26 eve NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01).
Feb 10 00:12:26 eve NetworkManager: <info> Found new 802.11 WiFi device 'wlan0'.
Feb 10 00:12:26 eve NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_xx_xx_xx_xx_xx_xx
Feb 10 00:12:30 eve NetworkManager: <info> (wlan0): device state change: 1 -> 2
Feb 10 00:12:30 eve NetworkManager: <info> (wlan0): bringing up device.
Feb 10 00:12:31 eve NetworkManager: <info> (wlan0): preparing device.
Feb 10 00:12:31 eve NetworkManager: <info> (wlan0): deactivating device (reason: 2).
Feb 10 00:12:31 eve NetworkManager: <info> (wlan0): device state change: 2 -> 3
Feb 10 00:12:31 eve NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready
Feb 10 00:14:15 eve NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally.
Feb 10 00:14:15 eve NetworkManager: <info> (wlan0): now unmanaged
Feb 10 00:14:15 eve NetworkManager: <info> (wlan0): device state change: 3 -> 1
Feb 10 00:14:15 eve NetworkManager: <info> (wlan0): cleaning up...
Feb 10 00:14:15 eve NetworkManager: <info> (wlan0): taking down device.
Feb 10 00:14:17 eve NetworkManager: <info> disconnected by the system bus.
Feb 10 00:14:23 eve NetworkManager: <info> starting...
Feb 10 00:14:23 eve NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():Last edited by shimage (2009-02-11 00:17:29)
Offline
I can report the same problem. I logging in with net-profiles.
I've mandriva installed on an other partition and there I have this problem too.
Offline
Ok, this is an old post, however I had the same issue. The reason for this was that I previously tried to connect to the AP via command line, though this is fun I use a laptop so it's quite troublesome to use command line every time. When I decided to switch to wicd I've noticed this problem too...
What I had to do was, getting back to previous /etc/wpa_supplicant.conf which I saved before as wpa_supplicant.conf.backup
After doing this I can use wicd with no problems at all! Hope that helps someone...
Offline