Bug 109844 - memory_cs module missing
Summary: memory_cs module missing
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pcmcia-cs (Show other bugs)
(Show other bugs)
Version: 1
Hardware: i686 Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-12 10:30 UTC by Sergey V. Udaltsov
Modified: 2015-01-04 22:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-27 05:40:52 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 Sergey V. Udaltsov 2003-11-12 10:30:25 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031030

Description of problem:
On my laptop I have O2Micro SmartCard reader (which I know is NOT
supported - but anyway). It is found by cardmgr as Anonymous Memory.
Then cardmgr is trying to load memory_cs - and fails. Just because
kernel-pcmcia-cs (or kernel 2.4.22?) does not include the module
memory_cs.o

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

How reproducible:
Always

Steps to Reproduce:
1. use any pcmcia memory module 
2. /etc/rc.d/init.d/pcmcia restart 

Additional info:
Comment 1 Arjan van de Ven 2003-11-12 10:33:03 UTC 
memory_cs is cardmgr's "Ehhhh I don't know" answer.
It wouldn't have done anything good at all.
Comment 2 Sergey V. Udaltsov 2003-11-12 10:55:17 UTC 
Well, could at least it give some more sensible error message? Or at
least "man memory_cs" should mention it - and not give some info about
the module which is not there (and would not work anyway, as you say).
BTW, IIRC correctly, memory_cs existed in some earlier kernels. Am I
wrong?
Note You need to log in before you can comment on or make changes to this bug.