From: Andrew Morton <akpm@osdl.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>
Subject: Re: 2.6.18-rc3-mm2: bad e1000 device name
Date: Tue, 8 Aug 2006 00:40:11 -0700 [thread overview]
Message-ID: <20060808004011.ab3cd65f.akpm@osdl.org> (raw)
In-Reply-To: <44D78A48.7050707@goop.org>
On Mon, 07 Aug 2006 11:45:28 -0700
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> With 2.6.18-rc3-mm2, I get a bogus device name for my e1000 device,
> which I would expect to be eth0:
>
> : ezr:pts/0; ifconfig -a
> �6f� Link encap:Ethernet HWaddr 00:16:D3:20:D2:0B
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Base address:0x2000 Memory:ee000000-ee020000
> [...]
e1000 seems OK here. Don't know, sorry.
next prev parent reply other threads:[~2006-08-08 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 18:45 2.6.18-rc3-mm2: bad e1000 device name Jeremy Fitzhardinge
2006-08-08 7:40 ` Andrew Morton [this message]
2006-08-08 8:16 ` Jeremy Fitzhardinge
2006-08-08 15:17 ` Arjan van de Ven
2006-08-08 15:25 ` Jeremy Fitzhardinge
2006-08-08 15:26 ` Arjan van de Ven
2006-08-08 16:17 ` Jeremy Fitzhardinge
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=20060808004011.ab3cd65f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).