Re: Possible bug in realtek 8169 ethernet driver

Francois Romieu wrote:
> Bram <[email protected]> :
> [...]
> > The device now works! But, it still comes up as eth2 instead of eth0,
> > even though it's first detected as eth0. There are no other network
> 
> Check the udev rules and/or your init scripts ?
> 
You're right, it's a udev script assigning new names to unknown cards, I
wasn't aware of that.

Thanks,
Bram
-
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/

---

• References:
  • Possible bug in realtek 8169 ethernet driver
    • From: Bram <[email protected]>
  • Re: Possible bug in realtek 8169 ethernet driver
    • From: Francois Romieu <[email protected]>
  • Re: Possible bug in realtek 8169 ethernet driver
    • From: Bram <[email protected]>
  • Re: Possible bug in realtek 8169 ethernet driver
    • From: Francois Romieu <[email protected]>

• Prev by Date: Re: [PATCH] msleep() with hrtimers
• Next by Date: Re: [PATCH] request_firmware: skip timeout if userspace was not notified
• Previous by thread: Re: Possible bug in realtek 8169 ethernet driver
• Next by thread: Page Cache Question
• 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]