r8169 cardbus device naming weirdness

r8169 cardbus device naming weirdness

[Martin Hicks]

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]


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.

-- 
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: r8169 cardbus device naming weirdness

[Stephen Hemminger]

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.

Re: r8169 cardbus device naming weirdness

[Martin Hicks]

On Tue, May 23, 2006 at 10:51:08AM -0700, Stephen Hemminger wrote:
> 
> 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.

of course you're right.

/me fist shakes at udev

mh

-- 
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE