Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 159250 - e100 driver does not recognise intel 8086:1229
Summary: e100 driver does not recognise intel 8086:1229
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: John W. Linville
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-31 20:58 UTC by Bill Peck
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-08-03 16:02:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Bill Peck 2005-05-31 20:58:18 UTC
Description of problem:
Attempting a network install of either RHEL4 Gold or RHEL4 U1 will leave you at
the Select Network driver screen.  Manually selecting e100 will just drop you
right back at the same screen.

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

Card is Intel 82557/8/9 [Ethernet pro 100] (rev 08)

PCI ID  8086:1229

How reproducible:

Steps to Reproduce:
1. network install of rhel4 x86_64
Actual results:
nic not recognised

Expected results:
should work like it does under RHEL3.

Additional info:
I'm going to try and install RHEL4 i386 on this machine and see if its x86_64

Comment 1 Bill Peck 2005-05-31 21:03:27 UTC
sure enough, the i386 flavor sees the nic card fine.

Comment 2 John W. Linville 2005-06-01 12:04:28 UTC
Odd...the PCI ID lists are not arch specific...perhaps this is BIOS related?  
Might there be a BIOS update available for this box? 
This definitely strikes me as "wierdness" there any correlation to warm 
vs. cold boot?  Or to what was booted previously? 
Any chance you could install the x86_64 version some other way (i.e. CD or 
using another NIC), and then attach a sysreport to this bug?  Thanks! 

Comment 3 John W. Linville 2005-08-03 16:02:20 UTC
Closed due to inactivity.  Please reopen when requested information becomes 
available.  Thanks! 

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