2.4.20 Modprobe setting of eth0,eth1 does not seem to work

From: jmerkey@s1.uscreditbank.com
Date: Fri Jun 06 2003 - 16:39:39 EST

Next message: Mitchell Blank Jr: "Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)"
Previous message: J.C. Wren: "Is there a bug with su, and /dev/std*?"
Next in thread: Lauro, John: "RE: 2.4.20 Modprobe setting of eth0,eth1 does not seem to work"
Maybe reply: Lauro, John: "RE: 2.4.20 Modprobe setting of eth0,eth1 does not seem to work"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

text/plain attachment: modules.conf

-
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/

Next message: Mitchell Blank Jr: "Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)"
Previous message: J.C. Wren: "Is there a bug with su, and /dev/std*?"
Next in thread: Lauro, John: "RE: 2.4.20 Modprobe setting of eth0,eth1 does not seem to work"
Maybe reply: Lauro, John: "RE: 2.4.20 Modprobe setting of eth0,eth1 does not seem to work"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Jun 07 2003 - 22:00:31 EST