Bug 129390 - FC2 does not see 3C985 Gig Nic
Summary: FC2 does not see 3C985 Gig Nic
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 2
Hardware: i586
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-07 15:50 UTC by Charles Tran
Modified: 2015-01-04 22:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-16 04:02:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Charles Tran 2004-08-07 15:50:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:
Gateway 935s 1.4Ghz with 4GB ram 
2 aic-79xxx scsi , one onboard, one external,
3 internal Seagate SCSI 18G drives using onboard controller.
3Com 3C589 GiG ethernet NIC
Promise Vtrak 15100 disk array 15 250GB WD sata drives.
The promise uses Busybox Linux and is attached to
Gateway via SCSI.

During installation of FC2 the 3c589 is not seen.

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

How reproducible:

Steps to Reproduce:
1.Install FC2 on hardware listed above

Actual Results:  3C985 is not recognized by OS

Expected Results:  detection and configuration of NIC during 

Additional info:

This looks like a 2.6 kernel issue, although I have not verified this
with FC1..

Comment 1 Dave Jones 2005-04-16 04:02:56 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.

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