Comment 47 for bug 207446

Thanks guys, that worked for me as well!
I canged the file /etc/network/interfaces
............
pre-up nice -n 19 wpa_supplicant ...
............

and restarted the network: sudo /etc/init.d/networking restart

On Tue, Aug 12, 2008 at 1:27 PM, Chri <email address hidden> wrote:
> This WorkAround also works for me :
> - from the gnome network manager, launch the connection
> - find the wpa PID by a 'ps -ef | grep wpa_supplicant'
> - do a 'sudo renice 19 wpa_pid' , replace wpa_pid by the wpa_supplicant PID
>
> Now i understand why sometimes, it can connect without this workaround,
> it's when i launch the connection when the PC is very busy.
>
> --
> Chri
>
> --
> [ndiswrapper] [wg511] fails to associate
> https://bugs.launchpad.net/bugs/207446
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: New
> Status in "wpasupplicant" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: wpasupplicant
>
> After upgrading from gutsy to hardy, wpa_supplicant can no longer authenticate. It seems to try repeatedly until I kill it.
>
> The results of sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd are in the attachment.
>
> I can get a wireless connection if I disable WPA; wpa_supplicant still works fine if I boot with kernel 2.6.22.
>
> wpasupplicant version is 0.6.0+0.5.8-0ubuntu2.
>
> Wireless is netgear wg511v2/ndiswrapper.
>
> /etc/wpa_supplicant.conf is
>
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> ap_scan=2
>
> network={
> ssid="MySSID"
> scan_ssid=1
> proto=WPA
> key_mgmt=WPA-PSK
> pairwise=TKIP
> group=TKIP
> psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> }
>