Redhat ES E1000 Problems

[Justin Bennett]

I tried loading all the e1000 modules with the new kernel (using 
modprobe) They're were several diffrent e1000 modules included. Lilo as 
the boot loaded, Everything looks ok in the /boot area, I'm assuming my 
cards don't like the new e1000 drivers..

 e1000
 e1000_4412k1

I tried loading them both with no luck.

Justin Bennett

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



deadpoint wrote:

> when you boot the new kernel are you able to manually load the kernel 
> module with insmod? it's possible that the kernel is loading the 
> modules for the old kernel and the new kernel doesn't like them. are 
> you using grub or lilo as your boot loader? check lilo.conf and or 
> grub.conf to see which initrd and kernel image are being loaded.
>
> redhat likes to use softlinks in /boot for vmlinuz, initrd, 
> System.map, and module-info. maybe the links are pointing at the wrong 
> files, i.e. the old ones and the kernel is following those links.
>
> good luck
> darin
>
> 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.
>>
>