Bug 163 - 5.2 installer does not detect pcmcia card 3c589
Summary: 5.2 installer does not detect pcmcia card 3c589
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
(Show other bugs)
Version: 5.2
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1998-11-23 07:03 UTC by gvlx
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-06-28 16:40:33 UTC
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.)

Description gvlx 1998-11-23 07:03:43 UTC 
The Redhat 5.2 installer disks do not detect a pcmcia
card 3c589D.

HOWEVER, the RH 5.1 did.

Which means that no net install is possible while
using this card (unless I use the RH5.1 installer but
that is a little bit awkward).

This might be related to bug #104?
Comment 1 David Lawrence 1998-11-23 17:32:59 UTC 
We will try to get a 3c589D card into the lab. We only have a 3c589B
right now and it works fine.
Comment 2 gvlx 1998-11-25 10:49:59 UTC 
Additional information:

Platform:
Toshiba Satellite 320 CDS
CPU:P233MMX RAM:32MB HD:EIDE-4.1GB CD:ATAPI-24X

As a side note, Suse 5.3 Installer does not detected the PCIC
(but RH does).

The installation seems to work fine on the Toshiba Satellite 4000 CDS
which should have the exact same hardware except for PII233.
Comment 3 David Lawrence 1999-06-28 16:40:59 UTC 
We will still try to get the pcmcia card into the test lab for testing
but it is an older model that will prove to be difficult to find and
may have to be donated to us by some caring individual. Until then
please submit your problem to our mailing lists to see if anyone else
has encountered this and if they have a solution that we can work
with.
Note You need to log in before you can comment on or make changes to this bug.