i'm now at home, and tried again to connect to my WEP encrypted AP ...
and it just worked (tm) !

i didn't try it for a few days, because i thought it wouldn't work
because of the syslog line that said it was busy, and because kismet did
not work ...

something must still be broken, because the "Device or resource busy"
error still occurs, and kismet still throws the error described, but at
least i can use WLAN now with the latest 2.6.20-12 kernel (last time i
tried was 2.6.20-8 i IIRC)

:)

-- 
[feisty] regression: prism54g driver does not work anymore, worked fine in edgy
https://launchpad.net/bugs/94389

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to