Re: Order of loading wired/wireless driver modules in unstable
Pasi Kärkkäinen wrote:
[Please CC to me, I'm not on list]
Please don't do this.
*I* feel bad when I join a list for the sole purpose of asking a
question, knowing that I'm going to unsubscribe as soon as I get my
answer. But you won't even bother to join and sample the list traffic
for a few days? I consider that very disrespectful... as though you
consider us to be your personal tech support staff.
Nevertheless, I'll answer your question *and* CC you.
The order that they're loaded in used to only matter because the names
we assigned sequentially (eth0, eth1, etc.). Now, with udev, it appears
that you can name your interfaces anything you want. You could name your
wireless interface "my_favorite_eth", I suppose.
For a long time, my debian unstable laptop loaded wlan driver before wired
lan driver.. couple of weeks ago the order was reversed, wired lan drivers
were loaded before wlan.
With this flexibility in naming the interfaces, the load order shouldn't
The best section I've found regarding renaming interfaces is at:
but I haven't had a chance to try it to see if it works.
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
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
alias hostap_pci off
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
Is there tutorial/documents somewhere how loading of drivers is handled in
So, udev handles finding the actual hardware and deciding which drivers
need loading *AND* deciding what names they are assigned in /dev (read
Modprobe handles actually loading the module and any other modules that
it depends upon.