Bug 2327 – tulip.o incorrectly identifies EM 110 TX PCI as EM 100 and doesn't work

Bug 2327 - tulip.o incorrectly identifies EM 110 TX PCI as EM 100 and doesn't work

Summary:	tulip.o incorrectly identifies EM 110 TX PCI as EM 100 and doesn't work

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	modutils (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-04-22 12:28 EDT by derrell.lipman
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

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

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

Groups: None (edit)

Description derrell.lipman 1999-04-22 12:28:26 EDT

With the EM 110 TX PCI (Adaptec Cogent) connected to a 10-
Base-T (only) hub, the tulip module insists that it's an EM
100 card, and on allowing only 100Mb/sec configuration.
None of the "options" passed to insmod seem to have any
effect. The card works; I swapped with a Windows 98 system.

It seems to be of note that this same card required the
driver provided by Adaptec to work with Windows; the
default driver installed from the Windows 98 CDROM didn't
work with it either.

Comment 1 David Lawrence 1999-07-08 12:53:59 EDT

We currently do not have one of these particular cards in our test
lab. We will need to obtain one to accurately replicate this problem.

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