I confirm the bug. On dapper, dpkg -L hostap-utils gives : /. /usr /usr/sbin /usr/sbin/hostap_crypt_conf /usr/sbin/hostap_diag /usr/sbin/hostap_io_debug /usr/sbin/hostap_rid /usr/sbin/prism2_param /usr/sbin/prism2_srec /usr/sbin/split_combined_hex /usr/share /usr/share/doc /usr/share/doc/hostap-utils /usr/share/doc/hostap-utils/README.Debian /usr/share/doc/hostap-utils/copyright /usr/share/doc/hostap-utils/changelog.gz /usr/share/doc/hostap-utils/README.gz /usr/share/doc/hostap-utils/changelog.Debian.gz /etc /etc/network /etc/network/if-pre-up.d /etc/network/if-pre-up.d/hostap-utils /etc/pcmcia /etc/pcmcia/hostap_cs.conf /etc/hotplug /etc/hotplug/blacklist.d /etc/hotplug/blacklist.d/hostap-utils /etc/discover.d /etc/discover.d/hostap-utils
This means orinoco is not blacklist automatically because done in hotplug, which is not present now. The correct place for place for blacklist is /etc/modprobe.d/ After doing this manually, my prism2 based card is working succesfully with wpa_supplicant for wpa (impossible with orinoco driver). -- [dapper regression] hostap driver no longer properly blacklists orinoco https://launchpad.net/bugs/41652 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
