From: Andrew Morton <akpm@osdl.org>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: 2.6.18-rc4-mm[1,2,3] -- Network card not getting assigned an "eth" device name
Date: Sun, 27 Aug 2006 00:19:43 -0700 [thread overview]
Message-ID: <20060827001943.c559d37d.akpm@osdl.org> (raw)
In-Reply-To: <a44ae5cd0608270007gc6a919fx9e36562d8023635d@mail.gmail.com>
Please copy relevant mailing lists and maintainers on bug reports.
On Sun, 27 Aug 2006 00:07:50 -0700
"Miles Lane" <miles.lane@gmail.com> wrote:
> I have a:
>
> eth0: RealTek RTL8139 at 0xf8fa2800, 00:c0:9f:95:18:1b, IRQ 10
> eth0: Identified 8139 chip type 'RTL-8100B/8139D'
>
> and a:
>
> ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kd
> ipw2200: Copyright(c) 2003-2006 Intel Corporation
> ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
> ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
>
> My dmesg output includes:
> w<8E>^U<C1>: link down
> NET: Registered protocol family 10
> lo: Disabled Privacy Extensions
> ADDRCONF(NETDEV_UP): w<8E>^U<C1>: link is not ready
>
> As you can see, one of my network cards is getting "w<8E>^U<C1>" as a
> device name. This isn't the actual string. Here's what I get by
> cutting and pasting from iwconfig: "w�"
>
> ifconfig shows:
> HWaddr 00:C0:9F:95:18:1B
> 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)
> Interrupt:10 Base address:0x2800
>
> In most of my builds it has been the ipw2200 which gets busted by this
> problem. This time, ifconfig sees eth1 and not eth0. Oddly, dmesg
> output includes:
> eth0: RealTek RTL8139 at 0xf8fa2800, 00:c0:9f:95:18:1b, IRQ 10
> eth0: Identified 8139 chip type 'RTL-8100B/8139D'
> so I am puzzled at the disappearance of eth0 from the ifconfig output.
Jeremy reported that a while back too. I do not know what is causing it
and as far as I know no net developers have yet looked into it.
next parent reply other threads:[~2006-08-27 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a44ae5cd0608270007gc6a919fx9e36562d8023635d@mail.gmail.com>
2006-08-27 7:19 ` Andrew Morton [this message]
2006-08-27 7:38 ` David Miller
2006-08-28 15:52 ` Miles Lane
2006-08-28 19:03 ` Andrew Morton
2006-08-28 20:27 ` David Miller
[not found] ` <a44ae5cd0608290143m3ad300eej5b325270c9d57b66@mail.gmail.com>
2006-08-29 9:26 ` David Miller
2006-08-27 16:30 ` Jeremy Fitzhardinge
2006-08-28 14:32 ` Benoit Boissinot
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=20060827001943.c559d37d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--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
all inboxes | Powered by JetHome®