Skip to contentSkip to conversation

2.6.19-rc6-mm2: Network device naming starts at 1 instead of 0

DISCUSSION Auke Kok 2 participants 2 messages Dec 5, 2006

Subsystems (2)
lore
Share & tools
lore

Auke Kok

author
#0 lore raw

[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

#1 lore raw
Quoted 8 lines · Auke Kok

[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

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