[Beowulf] Linux NIC order : (ether)boots from eth1 but Linux says it's eth0

Nelson Castillo nelsoneci at gmail.com
Tue Mar 29 17:23:47 PST 2005


I'm booting a diskless cluster. Some nodes boot from eth0, others
from eth1 or eth2. All nodes are identical.

n at mdk:~$ lspci  | grep Ethernet
0000:02:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro
100] (rev 08)
0000:02:08.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
[Cyclone] (rev 34)
0000:02:09.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
[Cyclone] (rev 34)

The etherboot image of the nodes that boot from eth0 have support
only for Ethernet Pro 100. They work fine.

The nodes that boot from eht1 have support for 3c90x and  they work
fine. I tell etherboot to boot from the first nic found. But I have an issue.

Linux kernel 2.6.8 sees eth1  (3com) as eth0! only when they boot from
the etherboot image. I don't know why they inherit the etherboot order.

Kernel log reads (Root over NFS / get ip from DHCP):

IP-Config: Complete
 device=eth0, addr=, mask=, gw=,
 host=, domain=mydomain.com, nis-domain=(none),
 bootserver=, rootserver=, rootpath=

(note! : device=eth0)

My question is: can i override this and tell Linux to call this interface eth1?

Linux names it eth0.
eth0      Link encap:Ethernet  HWaddr 00:50:DA:CE:07:7F

I also would like to know why Linux does this.


Homepage : http://geocities.com/arhuaco

The first principle is that you must not fool yourself
and you are the easiest person to fool.
     -- Richard Feynman.

More information about the Beowulf mailing list