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

[Lauro, John]

I assume you mean between keyboard and chair???

Anyways...

If I do anything semi-advanced with e1000 cards, I end up getting
Intel's drivers.  It's a minor pain when switching kernel versions
(especially to a different version number) as the default scripts
assume you are already booted (uname -r) in the kernel you are
building for and are not part of the kernel source tree...

I suggest you try e1000-5.0.43 from Intel, and also iANS-2.3.35 (or
higher if either of them have updates).

I don't know if you are doing any advanced features like vlan tagging
or not.  Anyways, it's one area that drivers from Intel's site does
work better then the native stock kernel drivers.  Specifically as an
example, virtual Ethernets over different vlan tags when combined with
vmware gsx server works with Intel's iANS, but not with the stock vlan
support.

I know, it doesn't answer your question...  but it gives you something
else to try...

> -----Original Message-----
> From: [e-mail]
[mailto:[e-mail]]
> Sent: Friday, June 06, 2003 5:40 PM
> To: [e-mail]
> Cc: [e-mail]
> 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
>