On board Yukon detected as eth1 on Asus mobo
 

Hi ,

New Asus P5PE mobo fitted and then spent hours trying to get the Marvell Yukon on board NIC to talk to anything. Turned out be eth1 instead of eth0. There is no eth0 :scratch: . ifconfig -a shows only eth1 and lo. Where and when is the port assigned ? ( Slack 11 btw ).

thanks,

Interface names are assigned by the kernel pretty much arbitrarily (on some systems with eth0 and eth1, you might even notice them the two swapping upon a kernel upgrade). If you want full control over your interface names, however, you use something unique about them (most people use the MAC address).

One way to do this (which applies only to 2.6 kernels) is using udev. Another way (which also works with the 2.4 kernels that happen to be part of the default slack install) is to use a program such as ifrename or nameif in the boot sequence (before network initialization of course, but after any relevant module loading).

thanks, I'll have to do some research into udev. I didn't think there were any /dev/eth? links so not sure about that one. The confusion arose because dmesg showed it as eth0 but any attempts to set up the port failed ( because everything elses sees it as eth1 ).

There aren’t any device nodes such as /dev/eth1, but udev still controls naming, since there are entries in sysfs (remember, this is for 2.6 kernels).

See here for an example.