| To: | Alex Upton <AUpton@xxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.6.10 - "netdev=" kernel boot commands and the Intel e1000 nic |
| From: | P@xxxxxxxxxxxxxx |
| Date: | Fri, 11 Mar 2005 14:27:08 +0000 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <13A26154A563124B876A26F0EF0CE1ED032C9299@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <13A26154A563124B876A26F0EF0CE1ED032C9299@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 |
Alex Upton wrote: Hello All, For about 3.5 days now I've been trying to swap eth0 and eth1 devices through use of the netdev kernel boot switch. The scenario: We have a system with onboard NICS and a PCI Intel e1000 Fiber NIC installed. This particular system by default forces the NIC inside the PCI slot to always default to eth0. We want to have ultimate control as to which NIC is deemed worthy enough to become eth0. We are using an entirely monolithic kernel via a PXE driven build and prefer not to support use of modules. If anyone has any suggestions or insight on how to work with netdev and the e1000 properly it would be greatly appreciated!
I've found using a higher level script with heuristics
is the only way to order nics generically as I want. for e.g.
if ethtool eth0 | grep -q "Port: FIBRE"; then
ip link set dev eth0 name not_eth0
ip link set dev eth1 name eth0
fi
you get the idea...
Pádraig.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Patch] sctp: add receive buffer accounting to sctp (fwd), nhorman |
|---|---|
| Next by Date: | Re: ipv6 and ipv4 interaction weirdness, YOSHIFUJI Hideaki / 吉藤英明 |
| Previous by Thread: | Re: 2.6.10 - "netdev=" kernel boot commands and the Intel e1000 nic, jamal |
| Next by Thread: | Re: 2.6.10 - "netdev=" kernel boot commands and the Intel e1000 nic, Jean Tourrilhes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |