Bug 81884 - e1000.o module will not load of kickstart floppy
e1000.o module will not load of kickstart floppy
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-14 16:06 EST by Ray Parish
Modified: 2007-04-18 12:49 EDT (History)
0 users

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


Attachments (Terms of Use)

  None (edit)
Description Ray Parish 2003-01-14 16:06:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
I rebuilt the modules.cgz file and included the e1000.o driver
When booting off the kickstart floppy, I am presented with a list of network
drivers. I choose the Interl Pro/1000 Driver and I get:

undefined symbols on tty3

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


How reproducible:
Always

Steps to Reproduce:
1.follow http://acd.ucar.edu/~fredrick/linux/e1000
2.
3.
    

Actual Results:  undefined symbols

Expected Results:  e1000 module to load

Additional info:

How does one go about getting e1000 driver support for kickstart installations?
Comment 1 Jeremy Katz 2003-01-15 00:12:08 EST
If you get unresolved symbols, you didn't rebuild the driver against the same
kernel.
Comment 2 Ray Parish 2003-01-15 09:36:01 EST
Can you please tell me how to get the BOOT kernel source?
I installed the kernel-2.4.8-3BOOT, and booted to it. I have the
kernel-source-2.4.8-3, which i compiled the module against.
Comment 3 Jeremy Katz 2003-01-22 01:04:57 EST
Please see the driver disk development kit at http://people.redhat.com/~dledford/

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