Bug 432406 – RHEL 5.1 kernel does not work with Realtek 8111/8168B Ethernet

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 432406 - RHEL 5.1 kernel does not work with Realtek 8111/8168B Ethernet

Summary:	RHEL 5.1 kernel does not work with Realtek 8111/8168B Ethernet

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Enterprise Linux 5
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	5.1
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Red Hat Kernel Manager
QA Contact:	Martin Jenner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-02-11 15:16 EST by Jos Vos
Modified:	2008-05-08 09:53 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-05-08 09:53:01 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jos Vos 2008-02-11 15:16:00 EST

Description of problem:
The RHEL 5.1 kernel does not recognize/support the Realtek 8111/8168B Ethernet
chip, as found on an Intel DG31PR mainboard and many other boards.  On Fedora 8,
this chip works fine with the F8 kernel.

Version-Release number of selected component (if applicable):
kernel-2.6.18-53.1.6.el5

See also:
http://wiki.centos.org/HardwareList/RealTekRTL8111b

Comment 1 Prarit Bhargava 2008-05-08 09:53:01 EDT

Please be advised, that Bugzilla is not a support tool. It is an
Engineering and Community tool. So although all changes to Enterprise
Linux go through Bugzilla and Red Hat considers issues directly entered
into Bugzilla valuable feedback, there is no SLA around it.

If this is a production issue, please report it to your Red Hat Support contact.

Thank you.

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