+1 "Me too"
"update-manager -d" from Jaunty. Same chip, same results.
I'd like to point out that the chip is detected, but something is definitely not working properly.
Consider this output:
$ iwconfig lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11abg ESSID:"" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=off Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
AND:
$ sudo ifconfig wlan0 up SIOCSIFFLAGS: Unknown error 132
+1 "Me too"
"update-manager -d" from Jaunty. Same chip, same results.
I'd like to point out that the chip is detected, but something is definitely not working properly.
Consider this output:
$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11abg ESSID:""
Mode: Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power= off
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
AND:
$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Unknown error 132