same here. WPA-PSK /TKIP doesn't work. It keeps asking for a passkey. Also, the passkey entered changes when you try to connect (form OHAKWEPA to 647168370b0c2a3f94cda08aff610611e96d7a0f8d95990df9b6b80b920fc459, or from anything to that string actually. Whatever I type in it always seems to actually use the above 64...59 string or something which looks very much like it)
dmesg tells me: [ 2164.977468] eth1: authenticate with AP 00:03:2f:28:f8:7a [ 2164.979219] eth1: authenticated [ 2164.979232] eth1: associate with AP 00:03:2f:28:f8:7a [ 2165.176052] eth1: associate with AP 00:03:2f:28:f8:7a [ 2165.376099] eth1: associate with AP 00:03:2f:28:f8:7a [ 2165.576101] eth1: association with AP 00:03:2f:28:f8:7a timed out I have a feeling the fixed release schedule (april/october) is not working out so well for intrepid, since this is only one of the many regressions I experirenced while upgrading from hardy. -- [iwl*] intel drivers take overly long to associate to WPA for some hardware https://bugs.launchpad.net/bugs/263963 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
