Bug 109573 - Inserting any PCMCIA-card freezes system.
Summary: Inserting any PCMCIA-card freezes system.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 1
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-09 19:21 UTC by rob versluis
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-09-29 19:38:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description rob versluis 2003-11-09 19:21:55 UTC
Description of problem: Inserting PCMCIA Card freezes the system.


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


How reproducible: Always


Steps to Reproduce:
1. Boot Fedora Core 1
2. Insert any PCMCIA card; It beeps once, then the system freeze.
3.
  
Actual results:
Frozen system.

Expected results:
PCMCIA card support.

Additional info:

Notebook: HP Compaq nx9005

Comment 1 Karsten Hopp 2003-11-09 20:35:38 UTC
definitely not a problem of the Purdue Compiler-Compiler Tool Set 
(PCCTS), change component to kernel 

Comment 2 rob versluis 2003-11-10 18:17:09 UTC
Exclude irq 3, 4, 5, 9, 11 in the /etc/pcmcia/config.opts will solve
the problem.


Comment 3 Jonathan Caves 2004-05-28 19:22:09 UTC
I have an nx9005 now running Fedora Core 2. I have modified
/etc/pcmcia/config/opts and to exclude irqs 3,4,5,9 and am still
suffering system freezes. My pcmcia card is a Buffalo WLI-PCM-L11GP
wireless card.

What next?

Comment 4 David Lawrence 2004-09-29 19:38:36 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/



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