[dapper regression] hostap driver no longer properly blacklists orinoco

Bug #41652 reported by Michael R. Head
18
Affects Status Importance Assigned to Milestone
hostap-utils (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I just upgraded to dapper. I've been using hostapd to use my netgear plx adapter in master mode. It was working fine in breezy, and I note that /etc/hotplug/blacklist.d/hostap-utils, but if I'm not mistaken, hotplug is gone in dapper, and there should be a file named /etc/modprobe.d/blacklist-hostap-utils containing lines like these:

blacklist orinoco_plx
blacklist orinoco_cs
blacklist orinoco_pci
blacklist hermes

Revision history for this message
Chuck Short (zulcss) wrote :

You should be installing hostap-utils.

Changed in hostapd:
status: Unconfirmed → Rejected
Revision history for this message
Michael R. Head (burner) wrote :

I have hostap-utils. The problem remains.

Changed in hostapd:
status: Rejected → Unconfirmed
Revision history for this message
Michael R. Head (burner) wrote :

I think this should be a quickly closable bug.
Just add the the blacklist file in /etc/modprobe.d and toss the file in /etc/hotplug/blacklist.d.

Revision history for this message
JasonVenkiteswaran (jjvenky) wrote :

i've had a similar problem with an upgrade from 5.10 to 6.06 (breezy to dapper).

the orinoco module is getting loaded before the hostap modules. this, in turn, loads the orinoco_pci and hermes modules. as a result when hostap comes around and tries to load the firmware into my DLinkDWL520E1 pci card, it can't.

to fix this i have added orinoco to the list in /etc/hotplug/blacklist.d/hostap-utils file.

this file already had four modules in it, but did not have the plainly named orinoco:
orinoco_plx
orinoco_cs
orinoco_pci
hermes

Revision history for this message
Pascal Vincent (pvincent00) wrote :

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).

Revision history for this message
JasonVenkiteswaran (jjvenky) wrote :

Re: Pascal Vincent at 2006-09-24 19:25:36 UTC

this work for my DLink DWL520E1 pci card and this also works well for my Linksys WPC11 ver.3 pcmcia card too.

Revision history for this message
sam tygier (samtygier) wrote :

i added

blacklist orinoco_plx
blacklist orinoco_cs
blacklist orinoco_pci
blacklist hermes
blacklist orinoco
blacklist airport

to my /etc/modprobe.d/blacklist

but the orinoco driver still loads.

Changed in hostap-utils:
status: Unconfirmed → Confirmed
Revision history for this message
Michael R. Head (burner) wrote :

If you're using a PCMCIA-based device, you'll have to fiddle with the contents of /etc/pcmcia/config, too.

Revision history for this message
Michael R. Head (burner) wrote :

On gutsy, it appears that hostap is the only prism driver, so this is not really a problem anymore.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this issue still relevant in 8.10 alpha?

Changed in hostap-utils:
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in hostap-utils:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.