Hi,
Thanx for all the suggestions from the group. Unfortunately although
this is a new keyboard with integrated reader - and alleged supported
with the SCM driver, i have no way to confirm that the hardware actually
works since i have eradicated Windows from my life.
One thing that made me progress a bit further and is not documented
anywhere (thanx to David Corcoran) is that you need the usbdevfs
mounted manually on /proc/bus/usb a.la
mount -t usbdevfs none /proc/bus/usb
and make sure you have usbdevfs compiled in your kernel. This made
the pcscd claim the driver at the very least.
Oh well, it wasn't the main reason for the purchase of the keyboard
with integrated reader and 2 USB ports.
Thanx
Mitch
-------- Original Message --------
Subject: Re: MUSCLE SCM SCR-301 0.9.0 USB driver in Linux
Date: Mon, 4 Mar 2002 19:16:13 +0000
From: "Douglas Atique" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Hi, Mitch.
I don't know your reader, nor do I use Linux, but I have had some
problems with Towitoko readers on Solaris recently. One thing I
learned is to test the driver separately from pcsc-lite. In my case,
Carlos Prados provided a test program with the driver that let me
test the driver before I even built pcscd. If your driver comes with
such a program, give it a try.
Hope this helps.
Regards,
Douglas
> ---------- Mensagem original -----------
>
> De : [EMAIL PROTECTED]
> Para : [EMAIL PROTECTED]
> Cc :
> Data : Mon, 4 Mar 2002 17:18:51 +0000 (GMT)
> Assunto : MUSCLE SCM SCR-301 0.9.0 USB driver in Linux
>
>
> Hi all,
>
> Has anyone got this driver to work with pcscd ?
> The driver compiled and installed fine, and the userland
> pcscd daemon runs fine. Messages on the console
>
> Mar 4 16:56:54 client pcscd: Warning couldn't open config
file /etc/reader.conf.
> Mar 4 16:56:54 client pcscd: pcscdaemon.c 202: main: PC/SC Lite
Daemon Ready.
>
> For USB you don't need the /etc/reader.conf file, so i ignore the
message
> above. Then i run the testpcsc command and get in the console
>
> Mar 4 16:57:01 client pcscd: winscard_msg.c 210: SHMProcessEvents:
Common channel packet arrival.
> Mar 4 16:57:28 client pcscd: winscard.c 66:
SCardEstablishContext: Establishing Context: 16984768
>
> and on the command line i get (i had to add a fflush(stdout) to
test.c or
> else i don't see the "Please insert reader ...." message)
>
> # ./testpcsc
>
> MUSCLE PC/SC Lite Test Program
>
> Testing SCardEstablishContext : Command successful.
> Testing SCardGetStatusChange
> Please insert a working reader :
>
>
> I shove my card in and out, upside down, downside up, but no
response
> after that. If i strace the command i get
>
> write(1, "Please insert a working reader "..., 35Please insert a
working reader : ) = 35
> open("/tmp/pcsc/.pcsctmp", O_RDWR) = 5
> flock(5, LOCK_EX|LOCK_NB) = -1 EAGAIN (Resource
temporarily unavailable)
> close(5) = 0
> open("/tmp/pcsc/.pcsctmp", O_RDWR) = 5
> flock(5, LOCK_EX|LOCK_NB) = -1 EAGAIN (Resource
temporarily unavailable)
> close(5) = 0
> nanosleep({0, 200000000}, NULL) = 0
> [The last 4 lines repeat ad-infinitum]
>
> the prog loops because of
>
> rv = SCardGetStatusChange( hContext, INFINITE, 0, 0 );
>
> in test.c, but why isn't it recogonising my card ? This is a vaild
> card and i have tried 2 or 3 different cards unsuccesfully. This
leads
> me to believe that this is a problem with the driver and not me or
> my hardware. So has anyone else gotten this to work ??
>
> Control-C releases the driver correctly
>
>
> Mar 4 17:11:50 client pcscd: winscard.c 77: SCardReleaseContext:
Releasing Context: 16998555
> Mar 4 17:11:50 client pcscd: pcscdaemon.c 88: SVCServiceRun:
Client 10 has disappeared.
>
>
> My setup:
>
> # uname -a
> Linux client 2.4.18 #61 Mon Mar 4 15:02:26 GMT 2002 i686 unknown
>
> # dmesg|grep -i SmartOS
> Product: SmartOS USB Reader
> # dmesg|grep -i 0x66
> usb.c: USB device 4 (vend/prod 0x66/0x1001) is not claimed by any
active driver.
>
> 0x66/0x1001 is the vend/prod id for the SCM driver
>
> #
egrep '66|1001' /usr/local/pcsc/drivers/scm310Driver.bundle/Contents/I
nfo.plist
> <string>0x0066</string>
> <string>0x1001</string>
>
>
> pcsc-lite version 1.0.1.
>
>
> Any ideas ?
>
> Mitch
>
> ***************************************************************
> Unix Smart Card Developers - M.U.S.C.L.E.
> (Movement for the Use of Smart Cards in a Linux Environment)
> http://www.linuxnet.com/
> To unsubscribe send an email to [EMAIL PROTECTED] with
> unsubscribe sclinux
> ***************************************************************
>
>
***************************************************************
Unix Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/
To unsubscribe send an email to [EMAIL PROTECTED] with
unsubscribe sclinux
***************************************************************
***************************************************************
Unix Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/
To unsubscribe send an email to [EMAIL PROTECTED] with
unsubscribe sclinux
***************************************************************
