On Mon, Nov 14, 2005 at 02:54:15PM -0800, Joe Emenaker wrote: > Pasi Kärkkäinen wrote: > > >And in fact my system now loads 2 different wlan drivers for the same > >card, orinoco_pci and hostap_pci.. how can I disable the other? I tried to > >add it to skip list of discover, but it didn't help.. > > > > > Hmmm. This same question was asked on this very list earlier today. But > then, you're not on the list, so you wouldn't know that. > > One of the changes listed with the new udev packages reads: > + /etc/hotplug/blacklist*: must be replaced by modprobe > configuration directives. > > Supposedly, you can prevent modprobe from loading a module by adding a > file to /etc/modprobe.d which contains: > > alias drivername off > > So, you could create a file like "/etc/modprobe.d/blockhostap" which > contains: > > alias hostap_pci off >
In fact the above does not work. The correct file is /etc/modprobe.d/blacklist and you need to add lines like this: blacklist drivername Now only one wlan driver is loaded. Thanks. > >Is there tutorial/documents somewhere how loading of drivers is handled in > >Debian nowadays? > > > > > I haven't seen one. However, it appears that udev handles all > hot/cold-plugging now, and that it uses modprobe to actually do the > loading. > > So, udev handles finding the actual hardware and deciding which drivers > need loading *AND* deciding what names they are assigned in /dev (read > http://www.reactivated.net/writing_udev_rules.html). > Modprobe handles actually loading the module and any other modules that > it depends upon. > > - Joe -- Pasi Kärkkäinen ^ . . Linux / - \ Choice.of.the .Next.Generation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
