Bug 77850 - pcmcia.img doesn't recognize Cirrus CL-PD672x
pcmcia.img doesn't recognize Cirrus CL-PD672x
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-14 07:42 EST by Need Real Name
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-11-14 07:42:42 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)

  None (edit)
Description Need Real Name 2002-11-14 07:42:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.18-xfs i686)

Description of problem:
Attempting install of RH 8.0 on IBM Thinkpad 701 using pcmcia.img and
pcmciadd.img.  RH7.1 pcmcia.img detects PCMCIA controller, but RH8.0 pcmcia.img
does not.

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


How reproducible:
Always

Steps to Reproduce:
1.boot floppy with pcmcia.img
2.check alt-F3
3.

Actual Results:  With RH8.1 pcmcia.img alt-F3 displays:

* in startPcmcia()
* pcmcia probe returned: |PCI bridge probe: not found.
Intel PCIC probe: not found.
Databook TCIC-2 probe: not found.
|
* no pcic controller found

Expected Results:  With RH7.1 pcmcia.img alt-F3 displays:

* in startPcmcia()
* pcmcia probe returned: |PCI bridge probe: not found.
Intel PCIC probe: Cirrus CL_PD672x found, 2 sockets.
|
* need to load i82365

Additional info:

System is IBM ThinkPad 701 with 75MHz 486DX4 and 40MB memory.  RH7.1 runs fine,
but need to upgrade to RH8.0 to take advantage of newer versions of
applications.
Comment 1 Michael Fulbright 2002-11-14 17:23:49 EST
Minimum requirement for 8.0 are a Pentium class machine and 64M of RAM.

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