Blacklistiing modules

Blacklistiing modules

[Jar]

Hello

When using FC4 2.6.12, I have to put the following lines to the end of 
the /etc/hotplug/blacklist to get rid of loading orinoco_pci.

# a) Do NOT load orinoco_pci when we are using hostap driver
# b) Do NOT load hostap_pci or it's alias wlan0 defined in
#    /etc/modprobe.conf, let network service run it instead.
orinoco_pci
hostap_pci
wlan0

Now when I updated to FC4 2.6.14 this doesn't work any more. I have to 
delete orinoco_pci. Otherwise both hostap_pci and orinoco_pci are loaded 
at boot.

Intresiting thing is (according to dmesg) that the orinoco_pci is loaded 
first and then hostap_pci. Anyhow, finally lsmod shows that no orinoco* 
modules has been loaded. Who unloads them, does loading another module 
(hostap_pci) for same device cause that?

orinoco 0.15rc2 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel 
Roskin <proski@gnu.org>, et al)
orinoco_pci 0.15rc2 (Pavel Roskin <proski@gnu.org>, David Gibson 
<hermes@gibson.dropbear.id.au> & Jean Tour
eth2: WEP supported, 104-bit key
eth2: MAC address 00:0E:6A:6A:6A:6A
eth2: Station name "Prism  I"
eth2: ready
ACPI: PCI interrupt for device 0000:02:0a.0 disabled
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
ip_tables: (C) 2000-2002 Netfilter core team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.3 (4095 buckets, 32760 max) - 236 bytes per conntrack
u32 classifier
     Perfomance counters on
     OLD policer on
     input device check on
Ingress scheduler: Classifier actions prefered over netfilter
ieee80211_crypt: registered algorithm 'NULL'
hostap_pci: 0.4.4-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)
ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKG] -> GSI 11 (level, 
low) -> IRQ 11
hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x50
prism2_hw_init: initialized in 192 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: Intersil Prism2.5 PCI: mem=0xdfbff000, irq\x11
wifi0: registered netdevice wlan0

Finally I have to delete orinoco_pci to get rid of it. That is not 
elegant way to handle this. Is there some other method than the delete 
method to handle this? Why the blacklisting doesn't work any more?

Is some feture missing from udev/hotplug that should handle this kind of 
  "many drivers to same hardware" dilemma?

o kernel-2.6.14-1.1644_FC4
o hotplug-2004_09_23-7
o udev-058-1.0.FC4.1

I am not suscribed to the list, so please cc.

-- 
Best Regards, Jar


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Blacklistiing modules

[Kay Sievers]

On Sat, Dec 03, 2005 at 08:58:30AM +0200, Jar wrote:
> Finally I have to delete orinoco_pci to get rid of it. That is not 
> elegant way to handle this. Is there some other method than the delete 
> method to handle this? Why the blacklisting doesn't work any more?
> 
> Is some feture missing from udev/hotplug that should handle this kind of 
>  "many drivers to same hardware" dilemma?

My box has this:
  $ grep "blacklist orinoco" /etc/modprobe.d/*
  /etc/modprobe.d/prism2:blacklist orinoco_cs
  /etc/modprobe.d/prism2:blacklist orinoco_pci
  /etc/modprobe.d/prism2:blacklist orinoco_plx

The blacklist is a native feature of module-init-tools now.

Kay


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Blacklistiing modules

[Jar]

>
> My box has this:
>   $ grep "blacklist orinoco" /etc/modprobe.d/*
>   /etc/modprobe.d/prism2:blacklist orinoco_cs
>   /etc/modprobe.d/prism2:blacklist orinoco_pci
>   /etc/modprobe.d/prism2:blacklist orinoco_plx
>
> The blacklist is a native feature of module-init-tools now.

Oh thanks. I can't find modprobe.d directory enywhere. It sems that my Ferora 4 has
only /etc/hotplug/blacklist and that doesn't work any more with 2.6.14 kernel.

Does anybody know how to do this in Fedora4?

My module init tools version is: module-init-tools-3.1-4

-- 
Best Regards, Jar


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&opÌk
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Blacklistiing modules

[Kay Sievers]

On Sun, Dec 04, 2005 at 12:38:10PM +0200, Jar wrote:
> >
> > My box has this:
> >   $ grep "blacklist orinoco" /etc/modprobe.d/*
> >   /etc/modprobe.d/prism2:blacklist orinoco_cs
> >   /etc/modprobe.d/prism2:blacklist orinoco_pci
> >   /etc/modprobe.d/prism2:blacklist orinoco_plx
> >
> > The blacklist is a native feature of module-init-tools now.
> 
> Oh thanks. I can't find modprobe.d directory enywhere. It sems that my Ferora 4 has
> only /etc/hotplug/blacklist and that doesn't work any more with 2.6.14 kernel.
> 
> Does anybody know how to do this in Fedora4?
> 
> My module init tools version is: module-init-tools-3.1-4

  $ cat /etc/fedora-release
  Fedora Core release 4 (Rawhide)

  $ rpm -qf /etc/modprobe.d
  module-init-tools-3.2-0.pre9.1

  $ rpm -qf /etc/modprobe.d/blacklist
  hwdata-0.172-1

Kay


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel