Bug 467928 - Need newer igb driver to support Intel 82576 Gigabit Ethernet Controller (Kawela)
Summary: Need newer igb driver to support Intel 82576 Gigabit Ethernet Controller (Kaw...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.2
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-21 18:20 UTC by Charlotte Richardson
Modified: 2008-10-21 21:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-21 21:59:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Charlotte Richardson 2008-10-21 18:20:46 UTC
Description of problem:
The igb driver in RHEL5.2, igb-1.0.8-k2, does not support this embedded gigabit ethernet controller (Kawela chipset). The new igb driver which can be downloaded from the Intel website, igb-1.2.44.9, supports it. The PCI vendor ID of the new NIC is 0x8086 (of course) and the device ID is 0x10C9. The new driver calls this device E1000_DEV_ID_82576. We can load the driver from a driver disk during initial installation on the systems with this NIC but it is a major nuisance.


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

How reproducible:
100%


Steps to Reproduce:
1. Attempt to install RHEL5.2 over the network using RHEL5.2 DVD.

  
Actual results:
The embedded ethernet devices are not claimed by the igb driver, so the installation cannot be done over the network.


Expected results:
Newer driver would claim the devices allowing the network installation to work.


Additional info:

Comment 1 Charlotte Richardson 2008-10-21 19:42:35 UTC
Looks like support *IS* present in 5.3_Alpha.

Comment 2 Charlotte Richardson 2008-10-21 21:59:34 UTC
Confirmed that this NIC is supported in the driver version in RHEL5.3_Alpha, so closing this Bug as RHEL5.3 meets our timeframe.


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