| 1 |
To get around this issue I usually create /etc/modules.d/network to |
| 2 |
ensure that each network device gets loaded as the device I expect. |
| 3 |
|
| 4 |
Assuming (for the sake of example) that you have an Intel-based card, a |
| 5 |
Realtek-based card and the IEEE1394-device, the file might look |
| 6 |
something like this: |
| 7 |
|
| 8 |
# /etc/modules.d/network - ensure expected init. of network devices |
| 9 |
alias eth0 e100 |
| 10 |
alias eth1 8139too |
| 11 |
alias eth2 eth1394 |
| 12 |
|
| 13 |
After you've made the file, run 'modules-update' and you should begin to |
| 14 |
see the behaviour you expect without having to pull any "hotplug |
| 15 |
voodoo". |
| 16 |
|
| 17 |
Cheers, |
| 18 |
./JRH |
| 19 |
-- |
| 20 |
Jason Harley < jharley at oanda dot com > |
| 21 |
Systems Administrator |
| 22 |
OANDA Corporation |
| 23 |
|
| 24 |
On Wed, 2006-02-15 at 13:09 +0100, Christian Bricart wrote: |
| 25 |
> Hi, |
| 26 |
> |
| 27 |
> is there a possible solution to delay hot-/cold-/whatever-plugging after |
| 28 |
> loading autoload-modules (/etc/modules.autoload.d/kernel-2.6) or at least |
| 29 |
> after some network probing..? |
| 30 |
> |
| 31 |
> right now I have to add "eth1394" to /etc/hotplug/blacklist, as it load |
| 32 |
> before my Ethernet cards ;-) |
| 33 |
> So Firewire becomes eth0, moving old eth0 to eth1 and eth1 to eth2... |
| 34 |
> |
| 35 |
> (Fortunately, i've got a serial console for that server which I'm able to |
| 36 |
> connect to via SSH after the network has been all messed up...) |
| 37 |
> |
| 38 |
> Christian |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-server@g.o mailing list |
Archives