Bug 50897 - Unrecognized PCI Ethernet cards
Summary: Unrecognized PCI Ethernet cards
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda
Version: roswell
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-04 16:33 UTC by Aaron Brown
Modified: 2007-04-18 16:35 UTC (History)
0 users

Clone Of:
Last Closed: 2001-08-16 14:51:34 UTC

Attachments (Terms of Use)

Description Aaron Brown 2001-08-04 16:33:31 UTC
Description of Problem:
	Unrecognized common PCI 10/100 Ethernet cards (see below).

How Reproducible:

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
The following Ethernet cards were not recognized by the Roswell installer
(or for that matter the 7.1 installer):

PCI ID		Card Description		Driver
------		----------------		------
11ad:0002	LinkSys LNE100TX Rev A2 (PNIC)	Tulip
11ad:c115	LinkSys LNE100TX v2.0 (PNIC+)	Tulip
125b:1400	ALFA GFC2204 (ASIX)		Tulip
10ec:8139	D-Link 530TX+			RTL8139too

The Tulip driver is included by default, so choosing it from the menu
is all it takes to successfully get around this problem.  The D-Link 530TX+
also requires a separate driver disk and a rather nonintuitive guess as to
which driver to use.

The LinkSys and D-Link cards are very common, the ALFA less so.

Comment 1 Bill Nottingham 2001-08-06 00:40:15 UTC
The first two tulip ids have been in the pcitable since May of last year, and
January of this year respectively. The 8139 id has been there since December of
last year. If it's not getting recognized, something is really wrong with the
installer logic, or the pcitable is getting munged.

125b id added in cvs.

Comment 2 Glen Foster 2001-08-06 21:23:38 UTC
Try to reproduce with a local card (if we have one)... otherwise we may need to
get the card from David Niemi (neimi@adeptech.com)

Comment 3 Brent Fox 2001-08-16 14:51:29 UTC
abrown, any more info here?

Comment 4 Brent Fox 2001-08-27 17:22:42 UTC
Closing due to inactivity.  Please reopen if you have more information.

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