[Muscle] Does anyone have the SCM SCR-301 USB Reader working?
Charles Jones
linuxchuck at gmail.com
Thu Jul 19 20:33:59 PDT 2007
Hello,
I have the SCM SCR-301 USB card reader (part number 902890 rev 1.0)
I've "googled" all over the net and found some dead-end references from
2002, and 2005 about people trying to use the SCM SCR-301. I've even found,
and tried the driver that is listed as the SCM SCR-301 (0.9.0) driver on the
MUSCLE website. (This driver is named as if it is for a model 310, but the
description and README say otherwise.) So far, I get power to the card
reader (green light comes on), but it's not being recognized by pcscd. Here
is some of my system information that should be applicable:
Slackware 11
Kernel 2.6.19.1
lsusb output: Bus 2 Device 10: ID 04e6:1001 SCM Microsystems, Inc.
pcsc-lite-1.4.3
pcsc-tools-1.4.9
ccid-1.3.0
pcsc-perl-1.4.6
coolkey-1.1.0
scm310driver from MUSCLE driver list (listed as SCR-301 in description)
All packages were compiled from source on my system, no errors were
encountered.
Some specifics that I've tried after a standard installation, but did not
work:
I noticed the product/vendor ID in the SCR-301 driver bundle does not match
the lsusb output. So I modified Info.plist and usbserial.c from 0x0066 to
0x1001. Not sure if this would be the problem, but decided to try it. It
did not appear to help. I have reverted to the original sources since there
was no improvement from the change.
I do have the udev rules in place, and it successfully calls "pcscd
--hotplug" upon insertion. However, pcscd does not recognize that a reader
is even attached.
Here is some of the pcscd output:
./pcscd -f -d
pcscdaemon.c:294:main() pcscd set to foreground with debug send to stderr
debuglog.c:213:DebugLogSetLevel() debug level=debug
pcscdaemon.c:507:main() pcsc-lite 1.4.3 daemon ready.
hotplug_libusb.c:401:HPEstablishUSBNotifications() Driver
scm310Driver.bundle does not support IFD_GENERATE_HOTPLUG
hotplug_libusb.c:410:HPEstablishUSBNotifications() Polling forced every 1
second(s)
On a plugin event (for the reader, not the card), I see this from pcscd:
pcscdaemon.c:566:signal_reload() Reload serial configuration
pcscdaemon.c:578:signal_reload() End reload serial configuration
pcscdaemon.c:566:signal_reload() Reload serial configuration
pcscdaemon.c:578:signal_reload() End reload serial configuration
pcscdaemon.c:566:signal_reload() Reload serial configuration
pcscdaemon.c:578:signal_reload() End reload serial configuration
pcscdaemon.c:566:signal_reload() Reload serial configuration
pcscdaemon.c:578:signal_reload() End reload serial configuration
pcscdaemon.c:566:signal_reload() Reload serial configuration
pcscdaemon.c:578:signal_reload() End reload serial configuration
pcscdaemon.c:566:signal_reload() Reload serial configuration
pcscdaemon.c:578:signal_reload() End reload serial configuration
Then nothing further.
This card reader does work under windows. I use it regularly, but would
prefer to connect it to my primary Linux system if possible.
I would greatly appreciate any assistance from anyone out there who has
successfully used this model of reader on a linux system.
Thank you,
Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drizzle.com/pipermail/muscle/attachments/20070719/78fd1bd2/attachment.html
More information about the Muscle
mailing list