Update: I just realized I may have been on the wrong track here. I saw the same DHCP failure yesterday even using prism54 drivers, and I think it was due to a misconfigured firewall. At some point I had configured firestarter on my laptop, but of course it is simple minded and does not work correctly if you have multiple internet-connected interfaces, as my laptop does (one wired, one wireless). So I may have been confused above -- the connection failure might not have been due to the driver but rather to a misconfigured firewall, and maybe updating the kernel frobbed the firewall into working (e.g. by changing the naming of the network interfaces).
-- regression: prism2 fails to connect to some access points, prism54 works https://bugs.launchpad.net/bugs/112919 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
