Bug 212 - PCMCIA won't work if machine is rebooted from windows
Summary: PCMCIA won't work if machine is rebooted from windows
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer   
(Show other bugs)
Version: 5.2
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1998-11-28 09:53 UTC by Marc MERLIN
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-07-07 23:50:44 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 Marc MERLIN 1998-11-28 09:53:03 UTC 
Just for info, with certain PCMCIA controllers the install
will fail to detect the PCMCIA capabilities of the laptop
if the machine was warm booted after using windows.
This is a known problem with the pcmcia package that seems
to have been worked around in pcmcia-3.0.6.

In the meantime, some note somewhere saying that if pcmcia
isn't detected, the user should try to power off the laptop
and boot it directly under linux would help. I know several
people who have been bitten by this, and lost many hours on
that problem, myself included.
Comment 1 Marc MERLIN 1998-11-29 01:06:59 UTC 
Added missing summary
Comment 2 David Lawrence 1998-11-30 01:31:59 UTC 
We will need to get a laptop that has windows on it to be able to
confirm this problem.
Comment 3 Marc MERLIN 1998-11-30 09:44:59 UTC 
It is likely that you won't be able to reproduce the bug because it
only happens with a one (maybe more?) PCMCIA controller.
The laptop I had a problem with had the following controller:
O2Micro OZ6836 CardBus at mem 0x68000000, 2 sockets
Note You need to log in before you can comment on or make changes to this bug.