 | | | Intel E/1000 driver | Intel E/1000 driver 2003-09-17 - By Steven J. Yellin
Back
I have no idea what's going wrong with the e1000 module, but when
software doesn't work, one thing to try is getting the latest version.
You're running an old version of the kernel. Try doing the updates of
everything on your system; then upgrade the kernel to the current RH
latest version, 2.4.20-20.7. That might fix the problem, and even if it
doesn't, you'll have a more secure system.
On Tue, 16 Sep 2003, MW Mike Weiner (5028) wrote:
> I am having some issues with a module I need to load for an intel e1000
> interface using RedHat 7.3 linux-2.4.18-3. For some reason, the new imaged
> machines that I am trying to bring up will not load that module nor
> initialize the interface, so I am stuck with a single 10/100 interface.
> Interestingly enough I get the following in dmesg
> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
> parport0: irq 7 detected
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://www.scyld.com/network/eepro100.html
> eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
> <saw@(protected)> and others
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:30:48:28:8D:CB, IRQ 22.
> Board assembly 000000-000, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> General self-test: passed.
> Serial sub-system self-test: passed.
> Internal registers self-test: passed.
> ROM checksum self-test: passed (0xd0a6c714).
> Intel(R) PRO/1000 Network Driver - version 4.1.7
> Copyright (c) 1999-2002 Intel Corporation.
> And nothing else really, but when I go to manually probe or insert the
> module I get the following:
> [root@(protected) root]# modprobe e1000
> Warning: loading /lib/modules/2.4.18-3smp/kernel/drivers/addon/e1000/e1000.o
> will taint the kernel: non-GPL license - BSD with patent grant
> See http://www.tux.org/lkml/#export-tainted for information about tainted
> modules
> /lib/modules/2.4.18-3smp/kernel/drivers/addon/e1000/e1000.o: init_module: No
> such device
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
> You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.18-3smp/kernel/drivers/addon/e1000/e1000.o: insmod
> /lib/modules/2.4.18-3smp/kernel/drivers/addon/e1000/e1000.o failed
> /lib/modules/2.4.18-3smp/kernel/drivers/addon/e1000/e1000.o: insmod e1000
> failed
> AND
> [root@(protected) root]# insmod e1000
> Using /lib/modules/2.4.18-3smp/kernel/drivers/addon/e1000/e1000.o
> Warning: loading /lib/modules/2.4.18-3smp/kernel/drivers/addon/e1000/e1000.o
> will taint the kernel: non-GPL license - BSD with patent grant
> See http://www.tux.org/lkml/#export-tainted for information about tainted
> modules
> /lib/modules/2.4.18-3smp/kernel/drivers/addon/e1000/e1000.o: init_module: No
> such device
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
> You may find more information in syslog or the output from dmesg [root@(protected)
> root]# lsmod
> Module Size Used by Tainted: P
> autofs 12804 0 (autoclean) (unused)
> eepro100 20816 1
> ext3 70752 4
> jbd 53632 4 [ext3]
> aic79xx 289164 5
> sd_mod 12896 10
> scsi_mod 112272 2 [aic79xx sd_mod]
> Does anyone have any quick solutions they might suggest to get this module
> to load correctly? Or any other suggestions?
> Thank you in advance
> Michael Weiner
>
>
> __ ____ ____ ____ ____ ____ ____ ____ ____ ____
> Valhalla-list mailing list
> Valhalla-list@(protected)
> https://www.redhat.com/mailman/listinfo/valhalla-list
>
--
Steven Yellin
Earn $52 per hosting referral at Lunarpages.
|
|
|