Re: Why and how to blacklist soundcard or networkcard modules?
On Thu, Jan 11, 2007 at 04:04:00PM -0500, Kevin Mark wrote:
> On Thu, Jan 11, 2007 at 07:49:52AM -0800, Andrew Sackville-West wrote:
> > On Thu, Jan 11, 2007 at 04:45:16PM +0800, Richard wrote:
> >
> > If you want two sound cards then you need to look into 'writing udev
> > rules' (google that phrase, its in the top couple hits) to learn how
> > to customise the rules so that your cards are always named the same
> > thing. and read the archives of this list (probably 2 months ago) for
> > a couple threads on running multiple sound cards.
> >
> Hi Richard,
> one of the issue with the introduction of udev is hardware is not
> detected in a predictable way. This is true for network, sound, and
> other cards. Sometimes people have 2 cards that use the SAME kernel
> modules and have this problem also. So one approach is to add UDEV rules
> that look for a distinct property and create a distinct device (card
> 1=eth0, card 2=eth1).
There was a message here a while ago pointing out that this naming
scheme does not work; eth0 and eth1 are apparently assigned by some
earlier software, and to make udev give consistent names you have to com
up with new names, such as ethlan and ethworld, and then use /def/ethlan
and such in, say, the routing tables.
> If the udev rules are not working, you may try a
> crude method like renaming or removing the modules. e.g.
> if the modules is called 'ethernet.ko', name it 'ethernet.ko.bad'. This
> will make the kernel not find it and thus will not load it. But this is
> one solution. The udev rule is the best way.
> Cheers,
> Kev
> --
> | .''`. == Debian GNU/Linux == | my web site: |
> | : :' : The Universal | 'under construction' |
> | `. `' Operating System | go to counter.li.org and |
> | `- http://www.debian.org/ | be counted! #238656 |
> | my keysever: subkeys.pgp.net | my NPO: cfsg.org |
Reply to: