Carsten, I don't know if this is what you want to know. But, you can change the name of the net_device using /sbin/ip command like the following:
$ ip link set ethX name whatever_name ethX has to be DOWN beforehand. Maybe you could add commands to reorder in early part of rc scripts? Best, Tomoe Carsten Aulbert said the following on 11/12/2008 11:28 PM: > Hi all, > > sorry to bother you such a thing, but I'm not getting anywhere right > now. I've a server with four NICs which are all powered by the e1000 > driver. Two are on the Supermicro main board and two are added via an > add-on card. It seems that I can only PXE boot from the two on-board > NICs while the install kernel sees the on-board only as eth2 and eth3. > > The kernel documentation says one should use the ether (or now better) > the netdev directive for changing the order of the built-in drivers, but > as this guy[1], I have not succeeded so far. For the ether directive not > all parameters were mandatory, if they are now for netdev, how can I > find all the values? When 'entering the firmware' via CTRL+S I can get > the IRQ, the I/O address as well as the memory start address, but I have > no idea about the memory_end address. > > Can someone give me a hint? > > Cheers > > Carsten > > [1] That's the only one I found so far: http://lkml.org/lkml/2005/3/10/213 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
