From: Claus <cesli@ewetel.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: different h/w addresses on one eth
Date: Thu, 23 Mar 2000 20:29:44 +0100 [thread overview]
Message-ID: <20000323202943.A807@olis.north.de> (raw)
sorry, one question from another newbie
pb3400, builtin eth {not the combo card}
and de4x5:
Mar 23 19:57:53 arma kernel: eth0: DC21041 at 0x0400 (PCI bus 0, device 14), h/w address 00:05:02:26:3a:02,
Mar 23 19:57:53 arma kernel: and requires IRQ28 (provided by PCI BIOS).
Mar 23 19:57:53 arma kernel: de4x5.c:V0.544 1999/5/8 davies@maniac.ultranet.com
Mar 23 19:57:57 arma kernel: eth0: media is unconnected, link down or incompatible connection.
now tulip.o:
Mar 23 20:03:27 arma kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
Mar 23 20:03:27 arma kernel: eth0: Digital DC21041 Tulip rev 33 at 0x400, 00:A0:40:64:5C:40, IRQ 28.
Mar 23 20:03:27 arma kernel: eth0: 21041 Media table, default media ffff (Autosense).
Mar 23 20:03:27 arma kernel: eth0: 21041 media #0, 10baseT.
Mar 23 20:03:27 arma kernel: eth0: 21041 media #1, 10base2.
Mar 23 20:03:27 arma kernel: eth0: 21041 media #2, AUI.
Mar 23 20:03:30 arma kernel: eth0: No 21041 10baseT link beat, Media switched to 10base2.
hm..
/usr/doc/LDP/nag/node9.html#SECTION003320000 says:
A host is addressed by a six-byte address hard-coded into the
firmware of its Ethernet board. These addresses are usually written as a sequence of two-digit hex numbers separated by colons, as in aa:bb:cc:dd:ee:ff.
got someone of this list a solution for different h/w addresses on one eth card?
thx
Claus
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-23 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-23 19:29 Claus [this message]
2000-03-23 21:22 ` different h/w addresses on one eth Martin Costabel
2000-03-24 8:55 ` Michael Schmitz
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=20000323202943.A807@olis.north.de \
--to=cesli@ewetel.net \
--cc=cl.en@gmx.net \
--cc=linuxppc-dev@lists.linuxppc.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.