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/wp
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 He
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_p
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 conf
On 12/06/06 17:10 -0700, Jesse Brandeburg wrote:
> On 6/12/06, John W. Linville <[EMAIL PROTECTED]> 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 hotplu
