Bug 88607
| Summary: | Cannot perform network install on Intel e1000 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Nick Strugnell <nstrug> |
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED WORKSFORME | QA Contact: | Mike McLean <mikem> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.1 | CC: | jturner |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-06-29 20:51:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Used hexeditor to change the licence from BSD to GPL - still won't load so that wasn't the problem When it loads, does it actually also show information about eth0? Closing due to inactivity - please reopen if you have additional information to add. Does anyone have access to a machine with an e1000 card to test this? I no longer do (this was on a client site) so I can't answer Jeremy's question. We do not have one available here for testing - do you have e1000's Jay? e1000 is very common and this is the only report I've seen of problems; guessing it was just something weird with the hardware or the boot media. (In reply to comment #4) > Does anyone have access to a machine with an e1000 card to test this? I no > longer do (this was on a client site) so I can't answer Jeremy's question. I have had - still do - several NFS KS installations with e1000. Long ago, from the time I changed the boot media from diskett to CD, no problem of this kind I've experienced anymore. |
Description of problem: When trying to do a network install on an HP XW8000 workstation, anaconda prompts as expected for the driver disk to load the e1000 driver. Anaconda then returns with 'Failed to load e1000', even though the F4 console shows that the module loaded - there is only a tain warning as the module is BSD rather than GPL-licenced. When installing from CDROM, and therefore not needing the network driver, the e1000 works fine after the reboot into the installed kernel. Version-Release number of selected component (if applicable): 2.4.9-e.12 - the boot kernel supplied on the official media set How reproducible: always Steps to Reproduce: 1. Start network install from netboot disk or by specifiying a network ks on the CDROM 2. Insert driver disk when prompted 3. Select e1000 driver Actual results: Driver could not be loaded message (even though I think the driver has loaded) Expected results: Driver loads, proceed with net install Additional info: I believe that the driver is actually loading as the monitoring console shows messages. In particular there is a kernel taint warning. I think that anaconda is misinterpreting the return value of insmod and thinks that the module has not loaded - insmod returns a kernel taint warning and this probably changes the return value.