Hi folks,
i have an issue here..

My server was working fine, but since i set up a new NIC, i got this problem:
my 3rd interface got dev$RANDOM name when eth2 was expected.


i'm trying to rename a interface label from dev$RANDOM to eth2, but i got this message:

# nameif eth2 00:50:BF:38:xx:xx
cannot change name of dev28022 to eth2: Device or resource busy
#

The problem is:
# ifconfig |grep HWaddr |cut -f 1 -d ' '
dev28022
eth0
eth1

I have NO eth2.

Checking boot logs i found this suspect information:
kernel: eth0: RealTek RTL8139 at 0xd000, 00:50:bf:38:99:23, IRQ 10
kernel: eth1: RealTek RTL8139 at 0xd400, 00:08:54:17:82:c6, IRQ 11
kernel: eth2: VIA Rhine II at 0xef003000, 00:0f:ea:a1:9c:85, IRQ 11.

but this order is wrong!

# cat /etc/sysconfig/hwconf
------------------------------
class: NETWORK
bus: PCI
detached: 0
device: eth0
driver: via-rhine
desc: "VIA Technologies, Inc. VT6102 [Rhine-II]"
network.hwaddr: 00:0F:EA:A1:xx:yy
...
-
class: NETWORK
bus: PCI
detached: 0
device: eth1
driver: 8139too
desc: "Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+"
network.hwaddr: 00:08:54:17:xx:xy
...
-
class: NETWORK
device: eth3
driver: 8139too
desc: "Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+"
network.hwaddr: 00:50:BF:38:xx:xx
....
-----------------------------------

my ifcfg-eth* is configured like hwconf, and my modprobe.conf too.



Why my eth2 is BUSY?
I will organize these interfaces like boot sugest, but i'm curious WHY its busy when it doesn't.

thankz.

This is getting right on the edge of my knowledge so what I say may or may not be good info. I once experienced something sort of like this
and had to mess around with the udev configuration. Udev caches stuff that it sees for later use and retains that setting, if untouched,
forever. Did you *EVER* have an interface that registered as "eth2"? If so, that may be the reason why it's refusing to allow it. I can't
remember which file contains the udev cache, you'll have to look at the documents, but I'm willing to bet from past experience and what you're
saying that your problem lies there.

Let me know if this works!

Mike

Hi storkus,
yes, it aways "hold" the name 'eth2'.
I've been searching about 'udev cache', but without lucky.
I fix the problem using the correct name detected at boot time, configuring hwconf,modprobe and ifcfg files.

Its a way to solve another problem my internet NIC hang, causing lost of connection to internet.
Investigating the problem I found this problem yesterday, now i'm looking the new scenario to know if this is the solution.

thankz for you support, i really apreciated.