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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: 2.6.19-rc6-mm2: Network device naming starts at 1 instead of 0
    • From: "Rafael J. Wysocki" <[email protected]>

• Prev by Date: Re: [PATCH] Export current_is_keventd() for libphy
• Next by Date: Re: [PATCH -rt 2/3] Make trace_freerunning work
• Previous by thread: Scheduling a higher priority thread returning from clock_nanosleep()
• Next by thread: Re: 2.6.19-rc6-mm2: Network device naming starts at 1 instead of 0
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]