Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 111745 - ne2k-pci.o fails to load
ne2k-pci.o fails to load
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-12-09 12:10 EST by Pierre Thibaudeau
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-12-09 18:22:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pierre Thibaudeau 2003-12-09 12:10:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
ne2k-pci.o does not load correctly. As a result, the corresponding
Ethernet interface does not start.

(Works fine on 2.4.22-1.2115.)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot with newly installed kernel 2.4.22-1.2129

Actual Results:  eth0 does not come up.

Expected Results:  eth0 should be available.

Additional info:

Here's what I get when I try to force loading in single user mode:

sh-2.05b# modprobe eth0
unresolved symbol NS8390_init_Rb9026806
unresolved symbol ei_interrupt_Rb93d8fa5
unresolved symbol ei_open_Rc1c671de
unresolved symbol alloc_ei_netdev_R059df9b6
unresolved symbol ei_close_R1bc9c6c7
/lib/modules/2.4.22-1.2129.nptl/kernel/drivers/net/ne2k-pci.o: insmod
/lib/modules/2.4.22-1.2129.nptl/kernel/drivers/net/ne2k-pci.o failed
/lib/modules/2.4.22-1.2129.nptl/kernel/drivers/net/ne2k-pci.o: insmod
eth0 failed
Comment 1 Pierre Thibaudeau 2003-12-09 18:26:25 EST
Was causes by incorrect installation of additional modules (from
outside source).

Note You need to log in before you can comment on or make changes to this bug.