wpa_supplicant keeps associating.. not stable..

[Rukie]

Alright, I've got wireless, sort of working, with my Microsoft 720-ahn or n or something pcmcia card, its a broadcom chip that uses the kernels bcm43xx driver

anyways, when I look at syslog, I notice my wpa keeps associating and it doesn't grab an ip, it just associates, then reassociates, and repeats.. again and again and again..

Now 20 minutes ago it was working just fine... before I rebootred.. It works like, once every three times. any ideas what kinda things might cause this?

here's my wpa supplicant.conf file
network={
ssid="rukie"
scan_ssid=1
key_mgmt=WPA-PSK
psk=0000000000000000000000000000000000000 //you can't see this :p
priority=1
}


and here's conf.d/net
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
preferred_aps=( "rukie" "cchswireless" "Campus" "any")
dns_domain_eth1="rukie.ath.cx"
modules=( "wpa_supplicant" )
wpa_supplicant_eth1="-Dwext"
wpa_timeout_ath0=60
_________________
Gentoomania! Support the Open Source!
http://www.rukie.ath.cx

[beso_1717]

try doing a dmesg | grep bcm43xx and see if you get somwhere a bcm core failure with (-19) as tag. that means that you have to restart the system. it does nothing unloading the module and reloading it. you need to restart your system.
this happens very often with bcm4318 on wpa networks.

[PaulBredbury]

The bcm43xx driver is unstable. An alternative is ndiswrapper.

[beso_1717]

[deadfool]

wpa_supplicant wont grab an ip address for you you have to dhcpcd to get one. also i have wpa_supplicant repeatedly associating and its worked flawlessly for over a month

i use this "script"

[davidgurvich]

What chipset does lspci tell you it is?

[beso_1717]

[deadfool]