From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Quad ethernet card getting assigned different channels every install
Date: 3 Dec 2002 20:26:58 GMT [thread overview]
Message-ID: <asj42i$6vi$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 3DECC289.2050500@vgertech.com
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.
prev parent reply other threads:[~2002-12-03 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 14:16 Quad ethernet card getting assigned different channels every install Ian S. Nelson
2002-12-03 14:41 ` Nuno Silva
2002-12-03 15:34 ` device driver modules Salman
[not found] ` <01cd01c29afc$1dab5900$61a1ba40@Henrique>
2002-12-03 21:58 ` Salman
2002-12-03 20:26 ` bill davidsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='asj42i$6vi$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.