prism2.5 in this case refers to the Intersil Prism 2.5 chipset which is actually very common in PCMCIA cards. This bug has nothing at all to do with prism2_* (linux-wlan-ng) and everything to do with network-manager not being able to cause a prism 2.5 chipset using the hostap drivers to associate properly even though it worked when dapper was released and doesn't work on edgy now. hostap and wpa-supplicant are also written by the same folks. hostap was the default driver for wpa-supplicant for a long long time.
I have another bug open which has a lot to do with prism2_cs (linux- wlan-ng). You also commented on that bug so I imagine the 3 bugs I'm subscribed to relating to prism2.5 chipsets and their drivers are just getting totally mixed up in everyone's heads. This is completely understandable. I have to be careful to make sure I'm commenting on the right bug myself. No biggie. I am perplexed though that you say that linux-wlan-ng doesn't support pcmcia cards. You can do a search on packages.ubuntu.com for prism2_cs.ko to see that it did exist in dapper. -- [prism2.5] doesn't associate https://launchpad.net/bugs/57146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
