2006-12-05 22:07:55

by Kok, Auke

[permalink] [raw]
Subject: 2.6.19-rc6-mm2: Network device naming starts at 1 instead of 0

[resend]

Quick note: I loaded up 2.6.19-rc6-mm2 on a platform here and noticed that the onboard
e1000 NIC was enumerated to eth1 instead of eth0. on 2.6.18.5 and any other kernel I
used before, it was properly named eth0 after startup. eth0 itself is completely missing
(-ENODEV).

I'll try to see if I can point out the culprit, but perhaps this rings a bell to anyone.

Cheers,

Auke


2006-12-05 22:14:14

by Rafael J. Wysocki

[permalink] [raw]
Subject: Re: 2.6.19-rc6-mm2: Network device naming starts at 1 instead of 0

On Tuesday, 5 December 2006 23:07, Auke Kok wrote:
> [resend]
>
> Quick note: I loaded up 2.6.19-rc6-mm2 on a platform here and noticed that the onboard
> e1000 NIC was enumerated to eth1 instead of eth0. on 2.6.18.5 and any other kernel I
> used before, it was properly named eth0 after startup. eth0 itself is completely missing
> (-ENODEV).
>
> I'll try to see if I can point out the culprit, but perhaps this rings a bell to anyone.

Please try to revert

gregkh-driver-driver-core-fixes-sysfs_create_link-retval-checks-in-core.c.patch

I had some similar problems that went away after I had reverted it.

Greetings,
Rafael


--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King