Hi, I have also compiled towitoko drivers, both 2.0.4 and yesterday 2.0.5. The tester program works perfectly, only if I initialize the reader then kill the tester there is no provision for uninitializing the driver on a signal. I mean the LED on my ChipDrive Intern remains green until I start the tester (or pcsc-lite) again, in which case it is reinitialized and the LED turns off (if I have removed the card). Anyway I have compiled pcsc-lite with --enable-debug and tried it several times with the testpcsc client but the pcscd daemon didn't die before my eyes. Maybe it's something with the daemon mechanism. I am going to try building pcsc-lite again but now only with --enable- daemon, not --enable-syslog to check if this makes any difference. Also, I wonder which signal Solaris sends pcscd when I shut Solaris down, as Solaris seems to hang on killing it (or something else which happens only when I have started pcscd as a daemon). Regards, Douglas
> ---------- Mensagem original ----------- > > De : [EMAIL PROTECTED] > Para : [EMAIL PROTECTED] > Cc : > Data : Fri, 1 Feb 2002 01:55:10 -0800 (PST) > Assunto : Re: MUSCLE pcsc-lite-1.0.1 plus Solaris 8 x86 plus Towitoko ChipDrive Intern plus towitoko-2.0.4 drivers > > Hi, > > To find out what is happening I suggest you to enable all the debug > information in pcsc and towitoko driver. > > Also compile pcsc-lite with option no daemon and start it manually in > the foreground on a console. If you see a lot of debug information you > are done. > > Then run your tests and see what the pcscd and the towitoko driver are > doing when the process dies. You can mail the log back to this list or > to me directly. I have successfully tested and run the towitoko drivers > (but without pcsc-lite) on Solaris 8 for Intel. > > Thanks, > Carlos. > > --- Douglas Atique <[EMAIL PROTECTED]> wrote: > > Hello, all. > > I am just arriving at the M.U.S.C.L.E. list and to pcsc-lite. I use > > Solaris 8 as my development platform and tried to configure > > pcsc-lite- > > 1.0.1 as a daemon so that it can lock the card reader serial port all > > > > the time. I have successfully compiled towitoko-2.0.4 drivers and the > > > > tester program works OK. I have also successfully compiled pcsc- lite- > > 1.0.1 and created /etc/reader.conf with the entry I have. Some tests > > complete successfully, like connecting to and disconnecting from the > > reader and waiting for a card to be inserted/removed. But instead of > > remaining up as I expected, the pcscd daemon seems to die silently > > (no logs). Also after a run of any tests with pcscd, when I try to > > shutdown the system Solaris seems to lock up and I can only reboot it > > > > with a hard reset (it's an Intel box, not SPARC) and it usually does > > something bad to my disks. Even if it didn't I would like pcscd to > > behave well. What should I do to 1) find out what is happening? 2) > > solve the problem? > > Thanks in advance, > > Douglas > > > > *************************************************************** > > 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 > > *************************************************************** > > > __________________________________________________ > Do You Yahoo!? > Great stuff seeking new owners in Yahoo! Auctions! > http://auctions.yahoo.com > *************************************************************** > 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 ***************************************************************
