Bug 177252 - No device nodes for cm4000_cs, cm4040_cs
Summary: No device nodes for cm4000_cs, cm4040_cs
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
(Show other bugs)
Version: 5
Hardware: All Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Whiteboard: MassClosed
Depends On:
TreeView+ depends on / blocked
Reported: 2006-01-08 10:13 UTC by Ville Skyttä
Modified: 2008-01-20 04:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-20 04:40:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Old /etc/pcmcia/smartcard for both cm4000 and cm4040 (950 bytes, text/plain)
2006-01-08 10:13 UTC, Ville Skyttä
no flags Details
/etc/pcmcia/cardman_cs.conf for cm4000 (164 bytes, text/plain)
2006-01-08 10:15 UTC, Ville Skyttä
no flags Details
/etc/pcmcia/cm4040_cs.conf for cm4040 (248 bytes, text/plain)
2006-01-08 10:16 UTC, Ville Skyttä
no flags Details

Description Ville Skyttä 2006-01-08 10:13:32 UTC
Two new PCMCIA smart card reader drivers have been introduced in kernel 2.6.15,
cm4000_cs (OMNIKEY CardMan Mobile 4000) and cm4040_cs (OMNIKEY CardMan Mobile
4040).  The modules load ok at boot, but no device nodes are created.

I tried to figure out how to get the nodes created, but failed so far; no rules
I've tried have had any effect.

I'm attaching the /etc/pcmcia/smartcard script as well as the old vendor shipped
/etc/pcmcia/*.conf files which were used to create the devices in pcmcia-cs world.

In short, cm4040_cs devices should get /dev/cmxN nodes and cm4000_cs /dev/cmmN
(where N is the number of the card).

udevinfos about the cards:

CardMan 4040 (cm4040_cs):
  looking at class device '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:00.1/1.0':
    SYSFS{prod_id2}=="CardMan 4040"

CardMan 4000 (cm4000_cs):
  looking at class device '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:00.1/1.0':

Comment 1 Ville Skyttä 2006-01-08 10:13:32 UTC
Created attachment 122919 [details]
Old /etc/pcmcia/smartcard for both cm4000 and cm4040

Comment 2 Ville Skyttä 2006-01-08 10:15:11 UTC
Created attachment 122920 [details]
/etc/pcmcia/cardman_cs.conf for cm4000

Note: before being included in the kernel, cm4000_cs was called cardman_cs, and
this file still reflects the old name.

Comment 3 Ville Skyttä 2006-01-08 10:16:08 UTC
Created attachment 122921 [details]
/etc/pcmcia/cm4040_cs.conf for cm4040

Comment 4 Harald Hoyer 2006-02-15 12:09:39 UTC
the modules should provide proper dev entries in sysfs

Comment 5 Ville Skyttä 2006-03-17 21:12:58 UTC
FYI, I no longer have hardware to test this with, at least for now, so I'm fine
with closing the bug.

Comment 6 Dave Jones 2006-10-16 18:46:24 UTC
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Comment 7 Jon Stanley 2008-01-20 04:40:27 UTC
(this is a mass-close to kernel bugs in NEEDINFO state)

As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.

If you believe that this bug was closed in error, please feel free to reopen
this bug.

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