Re: Remove Prism II support from Orinoco

Re: Remove Prism II support from Orinoco

[Stephen Hemminger]

On 12/06/06 17:10 -0700, Jesse Brandeburg wrote:
> On 6/12/06, John W. Linville <linville@tuxdriver.com> wrote:
> >On Mon, Jun 12, 2006 at 01:49:54AM +0300, Faidon Liambotis wrote:
> >
> >> Having two drivers supporting the same set of hardware seems pretty
> >> pointless to me. Plus, it confuses hotplugging/automatic detection.
> >
> >This subject comes-up from time to time.  In fact, I'm pretty sure
> >it came-up very recently w.r.t. orinoco and hostap.
> >
> >The consensus seems to be that drivers should have IDs for all devices
> >they support, even if that means that some devices are supported by
> >multiple drivers.  This leaves the choice of which driver to use in
> >the hands of the user and/or distro.
> 
> my problem is that for my prism 2 adapter both drivers are loaded at
> which point neither of them works.  I'm running FC5, and i have to
> keep removing the orinoco*.ko files to keep them from loading, so I'm
> all for this patch.
> 

use blacklist in module config to block one.
Just put in /etc/modprobe.conf

blacklist orinoco

Re: Remove Prism II support from Orinoco

[Faidon Liambotis]

Stephen Hemminger wrote:
>> my problem is that for my prism 2 adapter both drivers are loaded at
>> which point neither of them works.  I'm running FC5, and i have to
>> keep removing the orinoco*.ko files to keep them from loading, so I'm
>> all for this patch.
>>
> 
> use blacklist in module config to block one.
> Just put in /etc/modprobe.conf
> 
> blacklist orinoco
Unfortunately, that workaround doesn't work so well when you want to
have the ability to plug real orinoco (hermes) cards to your computer...
In other words and unless I'm missing something, there isn't currently a
way to have a Hermes card and a Prism II card both plugged in and working.

Regards,
Faidon

Re: Remove Prism II support from Orinoco

[Jar]

Stephen Hemminger wrote:

 >use blacklist in module config to block one.
 >Just put in /etc/modprobe.conf

 >blacklist orinoco

Unfortunately this is not work at least it is not work with FC4. I can 
blacklist eepro100 and 8139cp.

blacklist eepro100
blacklist 8139cp

but I can't blacklist orinoco_pci
blacklist orinoco_pci

It always loads itself with or without blacklist. That's why I have to 
do 'rm -f orinoco*.* && depmod -a' when the new kernel arrives. Seems 
that users are directed to use unsecure orinoco (wep) driver rather than 
secure hostap (wpa/wpa2,tkip,aes) driver for their prism2 hardware.

-- 
Best Regards, Jar

Re: Remove Prism II support from Orinoco

[Jiri Benc]

On Tue, 13 Jun 2006 07:30:56 +0300, Faidon Liambotis wrote:
> Unfortunately, that workaround doesn't work so well when you want to
> have the ability to plug real orinoco (hermes) cards to your computer...
> In other words and unless I'm missing something, there isn't currently a
> way to have a Hermes card and a Prism II card both plugged in and working.

Do you know about /sys/bus/pci/drivers/*/bind and unbind?

http://lwn.net/Articles/143397/

-- 
Jiri Benc
SUSE Labs

Re: Remove Prism II support from Orinoco

[Mike Kershaw]

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

On Tue, Jun 13, 2006 at 09:24:49PM +0300, Jar wrote:
> It always loads itself with or without blacklist. That's why I have to 
> do 'rm -f orinoco*.* && depmod -a' when the new kernel arrives. Seems 
> that users are directed to use unsecure orinoco (wep) driver rather than 
> secure hostap (wpa/wpa2,tkip,aes) driver for their prism2 hardware.

The hostap drivers are also much better behaved for rfmon than the
orinoco drivers for prism2.

-m

-- 
Mike Kershaw/Dragorn <dragorn@kismetwireless.net>
GPG Fingerprint: 3546 89DF 3C9D ED80 3381  A661 D7B2 8822 738B BDB1

Bus Error at 008BE426 while reading byte from DEADBEEF in User data space


[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]