Bug 171060 - Marvell Yukon 88E8050 ethernet interface not supported
Marvell Yukon 88E8050 ethernet interface not supported
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: John W. Linville
Brian Brock
Depends On:
Blocks: 168429
  Show dependency treegraph
Reported: 2005-10-17 15:57 EDT by Jack Neely
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: RHSA-2006-0132
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-07 15:29:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jack Neely 2005-10-17 15:57:54 EDT
Description of problem:
The Marvell Yukon 88E8050 PCI Express 1.0a gigabit ethernet interface is not
supported on RHEL 4 Update 2.  This hardware is included in the Intel 915GRV
uATX Motherboard.
Comment 2 John W. Linville 2005-10-18 16:19:03 EDT
Please try the test kernels here: 
These contain the new upstream skge and sky2 drivers.  I think your hardware 
is covered by sky2, which is not yet mainstream.  However, please do report on 
whether or not it works for you, and any problems you might observe...thanks! 
Comment 3 Jack Neely 2005-10-20 13:22:21 EDT
kernel-smp-2.6.9-22.3.EL.jwltest.76 does work.  Ethernet device appears as normal.
Comment 4 John W. Linville 2005-10-20 14:32:04 EDT
Cool!  Can you confirm that you are using the sky2 (and not skge) driver?  
Comment 5 Jack Neely 2005-10-20 15:09:53 EDT
Yes.  I'm using the sky2 module.  Thanks!
Comment 9 Red Hat Bugzilla 2006-03-07 15:29:30 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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