From: Kurt Wall <kwall@kurtwerks.com>
To: Matt Mercer <floyd@unpunk.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unknown ethernet device
Date: Sun, 3 Aug 2003 11:48:34 -0400 [thread overview]
Message-ID: <20030803154834.GF6541@kurtwerks.com> (raw)
In-Reply-To: <20030803153024.GA3602@unpunk.com>
Quoth Matt Mercer:
>
> Hi,
>
> I discovered an unknown onboard ethernet device recently. I'm
> thinking it is either an e100. Adding the ID to the
> list in the e100 driver and the nic seems to work fine.
>
> Anyone know anything about this device, should it be added
> to the e100 driver?
>
> lspci -s00:04.0 -xxx
> 00:04.0 Ethernet controller: Intel Corp.: Unknown device 0105 (rev 0d)
> 00: 86 80 05 01 17 01 90 02 0d 00 00 02 10 40 80 00
> 10: 00 d0 7f fe 01 af 00 00 00 00 7a fe 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 11 10
> 30: 00 00 7e fe dc 00 00 00 00 00 00 00 09 01 08 38
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 22 fe
> e0: 00 40 00 4b 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
This matches up pretty close with Ethernet Pro 100:
# lspci -s 00:11.0 -xxx
00:11.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
00: 86 80 29 12 17 01 90 02 08 00 00 02 08 40 00 00
10: 00 f0 bf fe 01 ef 00 00 00 00 a0 fe 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 0c 00
30: 00 00 90 fe dc 00 00 00 00 00 00 00 09 01 08 38
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 22 7e
e0: 00 40 00 3a 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Kurt
--
Stay away from hurricanes for a while.
next prev parent reply other threads:[~2003-08-03 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 15:30 unknown ethernet device Matt Mercer
2003-08-03 15:48 ` Kurt Wall [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-03 21:15 Feldman, Scott
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=20030803154834.GF6541@kurtwerks.com \
--to=kwall@kurtwerks.com \
--cc=floyd@unpunk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox