Jason Harley wrote:
To get around this issue I usually create /etc/modules.d/network to
ensure that each network device gets loaded as the device I expect.
Yepp, that's the usual way to do that...
Assuming (for the sake of example) that you have an Intel-based card, a
Realtek-based card and the IEEE1394-device, the file might look
something like this:
# /etc/modules.d/network - ensure expected init. of network devices
alias eth0 e100
alias eth1 8139too
alias eth2 eth1394
correct... done that with my modules..
After you've made the file, run 'modules-update' and you should begin to
see the behaviour you expect without having to pull any "hotplug
voodoo".
ack, "modules-update" merged those entries into /etc/modules.conf and
/etc/modprobe.conf..
Alas, this aliasing only works for (e.g. scripts) doing things like:
# modprobe eth0
But hotplug does something like "let me look into lspci and grep for
ids; look them up in my "module-for-pci-id-map" and modprobe the module
*by name*.
Now in my case the module "eth1394" gets modprobed prior to any regular
network module and thus occupies the eth0 slot...
Any module loaded afterwards can't get the first eth (i.e. eth0) as it's
already occupied by the firewire module...
So the only chance I see right now is to blacklist the module in
/etc/hotplug/blacklist so it does not get autoprobed.
As soon as some application however would try to access eth3 later on,
the kernel would modprobe it via the alias definition in
/etc/modprobe.conf.. and this works (actually it *should* work - haven't
tried)
Christian
Cheers,
./JRH
--
Jason Harley < jharley at oanda dot com >
Systems Administrator
OANDA Corporation
On Wed, 2006-02-15 at 13:09 +0100, Christian Bricart wrote:
Hi,
is there a possible solution to delay hot-/cold-/whatever-plugging after
loading autoload-modules (/etc/modules.autoload.d/kernel-2.6) or at least
after some network probing..?
right now I have to add "eth1394" to /etc/hotplug/blacklist, as it load
before my Ethernet cards ;-)
So Firewire becomes eth0, moving old eth0 to eth1 and eth1 to eth2...
(Fortunately, i've got a serial console for that server which I'm able to
connect to via SSH after the network has been all messed up...)
Christian
--
[email protected] mailing list
