From: Stephen Hemminger <shemminger@osdl.org>
To: Martin Hicks <mort@bork.org>
Cc: romieu@fr.zoreil.com, netdev@vger.kernel.org
Subject: Re: r8169 cardbus device naming weirdness
Date: Tue, 23 May 2006 10:51:08 -0700 [thread overview]
Message-ID: <20060523105108.7c0e2367@localhost.localdomain> (raw)
In-Reply-To: <20060523174402.GG29687@bork.org>
On Tue, 23 May 2006 13:44:02 -0400
Martin Hicks <mort@bork.org> wrote:
>
> Hi,
>
> I've got a D-Link DGE-660TD that the driver claims to register as eth1,
> but it actually ends up being eth2. (eth0 is the on-board NIC).
>
> mort@socrates:~$ dmesg
>
> [...]
>
> r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
> ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
> eth1: Identified chip type is 'RTL8169s/8110s'.
> eth1: RTL8169 at 0xe8a36000, 00:13:46:29:65:62, IRQ 5
> mort@socrates:~$ sudo /sbin/ifconfig eth1 192.168.1.102 netmask 255.255.255.0
> SIOCSIFADDR: No such device
> eth1: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> mort@socrates:~$ sudo /sbin/ifconfig eth2 192.168.1.102 netmask 255.255.255.0
> mort@socrates:~$ sudo /usr/sbin/ethtool -i eth2
> driver: r8169
> version: 2.2LK-NAPI
> firmware-version:
> bus-info: 0000:07:00.0
> mort@socrates:~$ sudo /usr/sbin/ethtool -i eth1
> Cannot get driver information: No such device
> mort@socrates:~$
>
>
> On a IBM T23 laptop running 2.6.16.14.
Most likely some user space script is renaming it.
Each distro seems to have it's own way of doing configuration, and most
do something in response to the hotplug event from device registration.
So it was eth1 until what ever ran in response to the hotplug event
decide to change it.
next prev parent reply other threads:[~2006-05-23 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 17:44 r8169 cardbus device naming weirdness Martin Hicks
2006-05-23 17:51 ` Stephen Hemminger [this message]
2006-05-24 19:13 ` Martin Hicks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060523105108.7c0e2367@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=mort@bork.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).