Re: NM 0.6.6 doesn't work

[Thomas Ilnseher <illth gmx de>]

Am Sonntag, den 16.11.2008, 19:41 +0100 schrieb Alexander Sack:
> On Sun, Nov 16, 2008 at 06:22:58PM +0100, Thomas Ilnseher wrote:
> > Hi!
> > 
> > I installed NM 0.6.6 from portage.
> > Sadly, It doesn't work. (wlan DOES Work, however!)
> > 
> > (I'm writing this over wlan!)
> > The connection is encrypted by WPA2.
> > 
> > This stuff is in my dmesg:
> > 
> > b43-phy3: Loading firmware version 410.2160 (2007-05-26 15:32:10)
> > Registered led device: b43-phy3::tx
> > Registered led device: b43-phy3::rx
> > ADDRCONF(NETDEV_UP): wlan0: link is not ready
> > wlan0: authenticate with AP 00:18:4d:bc:d5:f6
> > wlan0: authenticated
> > wlan0: associate with AP 00:18:4d:bc:d5:f6
> > wlan0: RX AssocResp from 00:18:4d:bc:d5:f6 (capab=0x431 status=0 aid=1)
> > wlan0: associated
> > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> > wlan0: no IPv6 routers present
> > wlan0: deauthenticating by local choice (reason=3)
> > 
> > NM doesn't provide any meaningfull error messages however!
> 
> By local choice usually means that the association was explicitly
> stopped by NM or the supplicant.
I thought that.
>  Usually this happens when that there
> is a timeout, which often indicates that you have driver issues.
The driver _does_ work flawless if I do: 

ifconfig wlan0 up
wpa_supplicant -iwlan0 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf
dhcpcd wlan0

So I can hardly imagine that this is a driver issue.
> 
> To get meaningful output, stop NM and start it from command line like:
> NetworkManager --no-daemon
Ok, Will do (as soon as I'm on my notebook)
> 
>  - Alexander
-- 
Thomas Ilnseher <illth gmx de>