Messages in this thread | | | Subject | RE: 2.4.20 Modprobe setting of eth0,eth1 does not seem to work | Date | Tue, 10 Jun 2003 16:11:00 -0700 | From | "Leech, Christopher" <> |
| |
Jeff,
It looks like you're following instructions from an old document about working with ISA network drivers. Modern PCI drivers can safely probe for devices, do not need manual IRQ settings, and do not require loading multiple copies of the driver. The various "option ethX -o e1000-X" lines in your modules.conf are not needed, as loading e1000 once will find all supported devices and register all of your eth interfaces. Also e1000 does not recognize either the io or irq parameters, so those settings do nothing.
If you need force specific assignments of interface names to network devices, the best way to do it is to map names to MAC addresses. The tool used to rename network interfaces is nameif, and a document describing it's use can be found at http://www.xenotime.net/linux/doc/network-interface-names.txt
- Chris
> -----Original Message----- > From: jmerkey@s1.uscreditbank.com > [mailto:jmerkey@s1.uscreditbank.com] > Sent: Friday, June 06, 2003 2:40 PM > To: linux-kernel@vger.kernel.org > Cc: jmerkey@utah-nac.org > Subject: 2.4.20 Modprobe setting of eth0,eth1 does not seem to work > > In 2.4.20 if I attempt to use the Intel multiport e1000 drivers with > modules.conf trying to hard set the eth0,eth1, etc. > assignments modprobe does > not appear to be assigning the adapter aliases correctly. I > am assuming > this may be due to an interface issue between the Keyboard > and monitor. :-) > > Modules.conf file attached. Anyone got any ideas here? > > Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |