Bug 31211 – Compaq Deskpro EN with NIC

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 31211 - Compaq Deskpro EN with NIC

Summary:	Compaq Deskpro EN with NIC

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael Fulbright
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-03-09 14:57 EST by Warren Mansur
Modified:	2007-04-18 12:32 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-03-09 14:57:44 EST
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 Warren Mansur 2001-03-09 14:57:41 EST

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)


I have a Compaq Deskpro EN (bought in January 2001), which comes with a 
built in NIC "Intel PRO 100/VM".  Upon installation, RedHat 7.0 decided to 
use the eepro100 module.  However, this is incorrect and the module will 
not work.  The correct module is e100.  When I went into LinuxConf and 
selected e100 as the driver, it worked properly.  lspci also does not 
determine what card this is, it only states, "ethernet controller, unknown 
2449".

Reproducible: Always
Steps to Reproduce:
1. Buy a Compaq Deskpro EN with built in Intel PRO 100/VM
2. Install Redhat 7.0
3. Try to use the network
	

Actual Results:  bringing up interface eth0 failed

Expected Results:  bringing up interface eth0 should have succeeded

Comment 1 Bill Nottingham 2001-03-09 19:42:50 EST

This is fixed in the 7.1 betas.

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