In article <3DECC289.2050500@vgertech.com>,
Nuno Silva <nuno.silva@vgertech.com> wrote:
| Hi!
|
| You can load the module and specify the I/O address of each mii. This
| way you'll allways get the same eth for a given I/O. Read the module's
| fine manual :)
| Ian S. Nelson wrote:
| > The kernel is 2.4.18, from Redhat. I've looked at some of the code and I
| > think this might actually be a hardware bug. I'm helping setup a 3 port
| > firewall, I'm remote so I haven't been hands on, the guy has a quad
| > ethernet card in it. Between kernel installs eth0, eth1, eth2, and eth3
| > seem to change which socket on the card they are.
It's not clear if the association of the name (ethN) to the io address
changes or the association of the io address to the connector. If Ian
will clarify, and perhaps check the ifconfig after a few boots...
If it's the name to io address mapping, and I assume it is, then Nuno
has the right idea, an options statement in modules.conf or on a command
line. If it's the latter the the BIOS is NOT doing deterministic
assignment. That would show in lspci with -vv, I believe. You could
still fix this, but it would be ugly, parsing lspci output and building
a command line for insmod.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 07 2002 - 22:00:17 EST