[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20060827001943.c559d37d.akpm@osdl.org>
Date: Sun, 27 Aug 2006 00:19:43 -0700
From: Andrew Morton <akpm@...l.org>
To: "Miles Lane" <miles.lane@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: 2.6.18-rc4-mm[1,2,3] -- Network card not getting assigned an
"eth" device name
Please copy relevant mailing lists and maintainers on bug reports.
On Sun, 27 Aug 2006 00:07:50 -0700
"Miles Lane" <miles.lane@...il.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists