Arjan van de Ven wrote:
and you're also sure this is not your userspace using interface
renaming...
(could be an initscripts bug for name-by-MAC ethernet device naming)
It's definitely in-kernel, since its specific to this version. And it
seems to have gone away since I turned on slab debugg
Jeremy Fitzhardinge wrote:
Arjan van de Ven wrote:
Jeremy Fitzhardinge wrote:
Andrew Morton wrote:
e1000 seems OK here. Don't know, sorry.
It's happening to all my ethernet-like devices: the Atheros wireless
comes up as a mess too. It's different each time, so it looks like
random uni
Arjan van de Ven wrote:
Jeremy Fitzhardinge wrote:
Andrew Morton wrote:
e1000 seems OK here. Don't know, sorry.
It's happening to all my ethernet-like devices: the Atheros wireless
comes up as a mess too. It's different each time, so it looks like
random uninitialized crud.
is this
Jeremy Fitzhardinge wrote:
Andrew Morton wrote:
e1000 seems OK here. Don't know, sorry.
It's happening to all my ethernet-like devices: the Atheros wireless
comes up as a mess too. It's different each time, so it looks like
random uninitialized crud.
is this the binary atheros drive
Andrew Morton wrote:
e1000 seems OK here. Don't know, sorry.
It's happening to all my ethernet-like devices: the Atheros wireless
comes up as a mess too. It's different each time, so it looks like
random uninitialized crud.
I did a clean rebuild, but it still happens. I guess I'll hav
On Mon, 07 Aug 2006 11:45:28 -0700
Jeremy Fitzhardinge <[EMAIL PROTECTED]> 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 BROAD
