[E1000-devel] Changing the ethX names
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 -- Dr. Carsten Aulbert - Max Planck Institute for Gravitational Physics Callinstrasse 38, 30167 Hannover, Germany Phone/Fax: +49 511 762-17185 / -17193 http://www.top500.org/system/9234 | http://www.top500.org/connfam/6/list/31 - 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
Re: [E1000-devel] Changing the ethX names
if you have udev installed and running you can just edit: /etc/udev/rules.d/70-persistent-net.rules to rename the devices persistently. No ugly firmware hacks needed. Auke Carsten Aulbert wrote: > 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 > -- > Dr. Carsten Aulbert - Max Planck Institute for Gravitational Physics > Callinstrasse 38, 30167 Hannover, Germany > Phone/Fax: +49 511 762-17185 / -17193 > http://www.top500.org/system/9234 | http://www.top500.org/connfam/6/list/31 > > - > 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 - 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
Re: [E1000-devel] Changing the ethX names
Hi Auke, Kok, Auke wrote: > > if you have udev installed and running you can just edit: > > /etc/udev/rules.d/70-persistent-net.rules > > to rename the devices persistently. No ugly firmware hacks needed. That's too far down the road as the kernel needs to make the inquieries already and udev is not installed at that point (we are doing a 'FAI' installation and the kernel gets fed something which looks like: kernel kernel/vmlinuz-2.6.23.1-faiinstall append root=/dev/nfs nfsroot=/srv/fai/nfsroot,v3,tcp,rsize=32768,wsize=32768 ip=:eth0:dhcp FAI_FLAGS=verbose,sshd,createvt,reboot FAI_ACTION=install console=tty0 as you can see there is nfsroot involved which in turn needs dhcp and this needs... a correct interface to work with :( Any other ideas? Cheers Carsten - 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
Re: [E1000-devel] Changing the ethX names
Carsten Aulbert wrote: > Hi Auke, > > Kok, Auke wrote: >> if you have udev installed and running you can just edit: >> >> /etc/udev/rules.d/70-persistent-net.rules >> >> to rename the devices persistently. No ugly firmware hacks needed. > > That's too far down the road as the kernel needs to make the inquieries > already and udev is not installed at that point (we are doing a 'FAI' > installation and the kernel gets fed something which looks like: > > kernel kernel/vmlinuz-2.6.23.1-faiinstall > append root=/dev/nfs > nfsroot=/srv/fai/nfsroot,v3,tcp,rsize=32768,wsize=32768 > ip=:eth0:dhcp FAI_FLAGS=verbose,sshd,createvt,reboot > FAI_ACTION=install console=tty0 > > > as you can see there is nfsroot involved which in turn needs dhcp and > this needs... a correct interface to work with :( > > Any other ideas? what's in a name? is it really that bad that your device has a name that is less-than logical? *shrug* with an initrd you can have udev run from a minimal initrd doing the renaming and mount the filesystem, or just use `ifrename` from said initrd. maybe that works? if you really have to resolve to reordering the probing, you're solving the wrong problem IMHO, and creating a non-portable solution. Auke - 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
Re: [E1000-devel] Changing the ethX names
Bummer. I guess I was too focused to get the 'ordering' right, i.e. to have eth0 and eth1 on the motherboard and then eth2 and eth3 on the PCIe card, that I totally oversaw this part of my 'kernel line': ip=:eth0:dhcp Probably i just need to put eth2 here. If that's the cure, sorry for the noise. If not, I'll try to see if I can get it running with initrd and udev or renaming the nic. Carsten - 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
Re: [E1000-devel] Changing the ethX names
Carsten Aulbert wrote: > 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. if your add-in nics are e1000 server adapters they can be configured to PXE boot too. You have to enable option rom support in the BISO and the option rom itself. what does your dmesg log look like (serial console maybe?) during boot? Are you sure you don't need e1000e? You didn't mention your kernel version, or the device ID of the e1000 ports. > 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 so, I guess the question is "why would you need to change the order?" our drivers don't use any of those parameters because we are a PCI device and that stuff can't be changed for PCI devices. More appropriate would be something that would let you pick a name for a particular BUS:DEVICE.FN notation. We don't implement the .init handler in our driver anyway. > 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. > kernel kernel/vmlinuz-2.6.23.1-faiinstall > append root=/dev/nfs > nfsroot=/srv/fai/nfsroot,v3,tcp,rsize=32768,wsize=32768 > ip=:eth0:dhcp FAI_FLAGS=verbose,sshd,createvt,reboot > FAI_ACTION=install console=tty0 why not just specify ip=:eth2:dhcp? - 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
Re: [E1000-devel] Changing the ethX names
Carsten, I frequently use this on CentOS as I have some machines with 10 NICs. You can try to see how CentOS/RH do it so that you can use it on your own distribution. In /etc/sysconfig/network-scripts there are files like ifcfg-ethX. There you can specify the MAC and the dev name like eth2. Once you edit the files, the ordering that you specified will always be used. Roman Carsten Aulbert wrote: > Bummer. > > I guess I was too focused to get the 'ordering' right, i.e. to have eth0 > and eth1 on the motherboard and then eth2 and eth3 on the PCIe card, > that I totally oversaw this part of my 'kernel line': > > ip=:eth0:dhcp > > Probably i just need to put eth2 here. > > If that's the cure, sorry for the noise. If not, I'll try to see if I > can get it running with initrd and udev or renaming the nic. > > Carsten > > - > 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 > - 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
Re: [E1000-devel] Changing the ethX names
Hi all, Brandeburg, Jesse wrote: > > if your add-in nics are e1000 server adapters they can be configured to PXE > boot too. You have to enable option rom support in the BISO and the option > rom itself. I don't see these cards in the BIOS right now only the onboard ones. I've enabled everything I could think of which hinted for external cards. Also don't see the option rom advertised during start-up like the first two (Press CTRL+S to enter..._. Is there a tool, which I can use to tell the driver to enable the option rom? > > what does your dmesg log look like (serial console maybe?) during boot? Are > you sure you don't need e1000e? You didn't mention your kernel version, or > the device ID of the e1000 ports. I don't have any device id right now, but try to find that out soon. The install kernel is an oldish 2.6.23. >> kernel kernel/vmlinuz-2.6.23.1-faiinstall >> append root=/dev/nfs >> nfsroot=/srv/fai/nfsroot,v3,tcp,rsize=32768,wsize=32768 >> ip=:eth0:dhcp FAI_FLAGS=verbose,sshd,createvt,reboot >> FAI_ACTION=install console=tty0 > > why not just specify ip=:eth2:dhcp? Yes (found that one also out myself after getting rid of some self-imposed blindness), but the install kernel only sees eth0 and eth1 (which are both on the add-on card, verified with plugging in a cable while it was searching for DHCP server and dmesg told me yes, that's eth0 and yes that's eth1), when specifying eth2 or eth3 I get a kernel panic since it cannot mount the root file system because the device is unknown. So right now, I have the lose-lose situation where I cannot PXE boot from the add-on card (yet) and I don't have the on-board NICs in the install kernel. A possible work-around^Whack would be to use two network connections during installation, but that's really hacky. If you know of a tool to activate PXE on the add-on NICs please let me know. I'll try to find out the IDs now. Cheers Carsten - 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
Re: [E1000-devel] Changing the ethX names
Hi Roman, Roman Chertov wrote: > I frequently use this on CentOS as I have some machines with 10 NICs. > You can try to see how CentOS/RH do it so that you can use it on your > own distribution. In /etc/sysconfig/network-scripts there are files > like ifcfg-ethX. There you can specify the MAC and the dev name like > eth2. Once you edit the files, the ordering that you specified will > always be used. After having a root partition that would indeed be easy, but since I use a NFS mount for the root partition, I need to have the device up and ready before seeing anything like that - see also my other email. Thanks for the reply Carsten - 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
Re: [E1000-devel] Changing the ethX names
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
Re: [E1000-devel] Changing the ethX names
Carsten Aulbert wrote: ions during installation, but that's really hacky. > > If you know of a tool to activate PXE on the add-on NICs please let me > know. I'll try to find out the IDs now. > OK, I suspect the NICs are just too new for the 2.6.23 kernel (and also for the 2.6.27?) The addon NICs are 52546GB ones (8086:1079) while the onbard models are reported to be 82575EB (8086:10a7). I'm currently looking through the device IDs which module to use for these. Cheers Carsten - 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
Re: [E1000-devel] Changing the ethX names
Carsten Aulbert wrote: > I'm currently looking through the device IDs which module to use for these. OK, found the igb kernel driver for that one. I'll try what will happen if this is included. Thanks for listening and suggestions! Carsten - 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
