Redhat ES E1000 Problems

Justin Bennett justin.bennett at dynabrade.com
Mon Dec 29 08:19:09 EST 2003


Ok thanks. I was looking at the intel site, and almost downloaded it for 
a shot, but it was late so I decided to boot the old kernel and go 
home... They are production machines, so I will give it a shot over a 
weekend..

Thanks
Justin

Justin Bennett
Network Administrator
RHCE (Redhat Certified Linux Engineer)
Dynabrade, Inc.
8989 Sheridan Dr.
Clarence, NY 14031
 



Michael Hanulec wrote:

>Justin..
>
>All you need to do is build the latest Intel e1000 source, v5.16 i
>believe.  You can either do this via 'make install' or w/ rpmbuild if you
>have kernel-source installed.  Upon upgrading your kernel they should have
>the proper PCI mapping for what ever 8254x ethernet chipset you happen to
>be running.
>
>This is a common problem with new motherboards and old OS's.
>
>-Mike
>
>--
>hanulec at hanulec.com		cell: 858.518.2647 && 516.410.4478
>https://secure.hanulec.com	      EFnet irc && aol im: hanulec
>
>On Sat, 27 Dec 2003, Justin Bennett wrote:
>
>  
>
>>After upgrading the kernel on 2 of my RedHat 2.1ES boxes to 2.4.9-e.34
>>as reccomeded by redhat using the standard up2date method, my gigabit
>>networking cards didn't work. According to the erratta there was updated
>>drivers also for the e1000 cards in this new kernel. One is a PCI Intel
>>card, the other is an onbord gigabit on a Penguin Computing box. Any one
>>else experienced this? I am booting my old kernel for the moment.
>>
>>--
>>Justin Bennett
>>Network Administrator
>>RHCE (Redhat Certified Linux Engineer)
>>Dynabrade, Inc.
>>8989 Sheridan Dr.
>>Clarence, NY 14031
>>
>>
>>
>>
>>    
>>



More information about the nflug mailing list