Blacklisting does not work...

[Ewan Mac Mahon]

On Thu, May 18, 2006 at 06:33:52PM +1000, Fawad Nazir wrote:
> After doing a little bit of more research on it. I found out few
> interesting things.
> 
> /etc/modprobe.d/blacklist file is only to blacklist modules to be
> loaded when the linux boots up, and this also works for me.
>
The modprobe blacklists apply invocations of modprobe after boot for
hotplugged hardware too.
 
> This list had no control over the modules loaded through hotplug (like
> plugging in a PCMCIA card after booting).
> 
> For this i tried to add modules names in /etc/hotplug/blacklist. But
> this actually does not work. Still the orinoco modules gets loaded
> when i plug in my PCMCIA card.
> 
> Any clues about this?
> 
The interface between the kernel and userspace portions of the
hotplugging system have been changing quite a bit recently; I'm guessing
that you have 'upgraded' to a kernel version that is expecting to use
the kernel/udev approach not involving /sbin/hotplug, while not
upgrading the userspace components. The simplest solution is to ditch the
custom kernel and use the distribution one; 2.6.12-10 for a Breezy
system, 2.6.15-21 for a Dapper one. If you desperately need a custom
kernel try building it from the Ubuntu sources rather than kernel.org
ones, and with the minimum deviation from the Ubuntu config.

Ewan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20060518/d063ce54/attachment.sig>