Hi, The code for eToken was written by some volunteer (I don't remember his name but his mails should be in archive for August, this year). Aladdin didn't release support for Linux oficcially yet. That's right, there was firmware problem working with OHCI, but it does not look like this problem
Vladimir Beker Aladdin. Securing the Global Village. P.O. Box 11141, Tel Aviv 61110 Israel Tel: +972 3 636-2222; Fax: +972 3 537-5796 Visit us at our Web site! http://www.eAladdin.com Aladdin supports Idealist. Visit http://www.idealist.org On 09/21/2002 03:55:33 PM ZE2 "[EMAIL PROTECTED]" wrote: > >Hi listmembers, > >i had a problem with aladdin etoken running under Windows98/2k/XP. It >made the hole system hang (impossible to shutdown having a token stick >to the pc. >Some Tokens (Pro-Version using Firmware 4.1.5.3 seem to hava problems >with OHCI-chipsets (told the support of alladin in germany). They >replaced my etokens (now Firmware 4.1.5.7) and it runs without problems. > >I�ve read that you use UHCI but my hint would be to contact aladdin >because i struggled 2 week with that little problem (change board, >usbcard, etc). > >Hope it helps >Bye Peter > > >Arno Wilhelm wrote: >> Hello, >> >> >> I am just testing the Aladding eToken usb tokens under Linux Redhat 7.2 >> and it seems that the driver has a problem. When I run the modified pcsc >> testutility several times *without changing it in anyway* I often get >> different results. >> >> E.g the first time it it is run it produces this output: >> >> >MUSCLE PC/SC Lite Test Program >> > >> >Testing SCardEstablishContext : Command successful. >> >Testing SCardGetStatusChange >> >Please insert a working reader : Command successful. >> >Testing SCardListReaders : Command successful. >> >Reader 01: Aladdin eToken PRO 0 0 >> >Enter the reader number : 01 >> > >> >Waiting for card insertion >> > : Command successful. >> >Testing SCardConnect : SCardConnect: protocoll = T1 >> >Command successful. >> >Testing SCardStatus : Command successful. >> >Current Reader Name : Aladdin eToken PRO 0 0 >> >Current Reader State : 34 >> >Current Reader Protocol : 1 >> >Current Reader ATR Size : c >> >Current Reader ATR Value : 3B E2 00 FF C1 10 31 FE 55 C8 02 9C >> >Got an Aladding eToken. >> >Sending 5 bytes: >> >0x00 0xA4 0x00 0x0C 0x00 >> >Command successful. >> >Received 2 bytes: >> >0x90 0x00 >> >Testing SCardDisconnect : Command successful. >> >Testing SCardReleaseContext : Command successful. >> > >> >PC/SC Test Completed Successfully ! >> >> Here everything works fine: the protocoll is recogniced and the command >> succeeds. But the second time the programm runs it gives this output: >> >> >MUSCLE PC/SC Lite Test Program >> > >> >Testing SCardEstablishContext : Command successful. >> >Testing SCardGetStatusChange >> >Please insert a working reader : Command successful. >> >Testing SCardListReaders : Command successful. >> >Reader 01: Aladdin eToken PRO 0 0 >> >Enter the reader number : 01 >> > >> >Waiting for card insertion >> > : Command successful. >> >Testing SCardConnect : SCardConnect: Unknown protocoll (0) >! >> >Command successful. >> >Testing SCardStatus : Command successful. >> >Current Reader Name : Aladdin eToken PRO 0 0 >> >Current Reader State : 34 >> >Current Reader Protocol : 1 >> >Current Reader ATR Size : c >> >Current Reader ATR Value : 3B E2 00 FF C1 10 31 FE 55 C8 02 9C >> >Got an Aladding eToken. >> >Sending 5 bytes: >> >0x00 0xA4 0x00 0x0C 0x00 >> >Card protocol mismatch. >> >Received 2 bytes: >> >0x00 0x00 >> >Testing SCardDisconnect : Command successful. >> >Testing SCardReleaseContext : Command successful. >> > >> >PC/SC Test Completed Successfully ! >> >> Here you can see that the protocoll is not recogniced and the command >> does not succeed. It returns "Card protocol mismatch.". >> >> I have tried it several times and sometimes it does not even recognice >> the ATR anymore. Often it helps when I restart pcscd or even the >> computer! What could the reason for this strange behavour be? Is it the >> usb bus, some sort of timing issues or anything else? >> >> >> Regards, >> >> Arno Wilhelm >> >> >> P.S.: >> >> Here is some debugging data: >> >> > uname -a >> Linux quirx 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown >> >> > cat /etc/redhat-release >> Red Hat Linux release 7.2 (Enigma) >> >> > /sbin/pcscd --version >> pcsc-lite version 1.1.1. >> Copyright (C) 1999-2002 by David Corcoran <[EMAIL PROTECTED]>. >> Report bugs to <[EMAIL PROTECTED]>. >> >> > tail -n 50 /var/log/messages >> ..... >> ..... >> Sep 20 14:29:25 quirx kernel: hub.c: USB new device connect on bus1/2, >> assigned device number 4 >> Sep 20 14:29:27 quirx kernel: usb.c: USB device 4 (vend/prod >> 0x529/0x50c) is not claimed by >> any active driver. >> Sep 20 14:29:30 quirx kernel: usb_control/bulk_msg: timeout >> Sep 20 14:29:30 quirx kernel: usb_control/bulk_msg: timeout >> Sep 20 14:29:30 quirx /etc/hotplug/usb.agent: ... no modules for USB >> product 529/50c/100 >> >> > cat /proc/bus/usb/devices >> T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 >> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 >> D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 >> P: Vendor=0000 ProdID=0000 Rev= 0.00 >> S: Product=USB UHCI Root Hub >> S: SerialNumber=e400 >> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA >> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub >> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms >> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 5 Spd=1.5 MxCh= 0 >> D: Ver= 1.00 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 >> P: Vendor=0529 ProdID=050c Rev= 1.00 >> S: Manufacturer=AKS >> S: Product=eToken Pro 4153 >> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 34mA >> I: If#= 0 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) >> >> > cat /proc/bus/usb/drivers >> usbdevfs >> hub >> > > > > > > >_______________________________________________ >Muscle mailing list >[EMAIL PROTECTED] >http://lists.musclecard.com/mailman/listinfo/muscle > ******************************* IMPORTANT ! ********************************** The content of this email and any attachments are confidential and intended for the named recipient(s) only. If you have received this email in error please notify the sender immediately. Do not disclose the content of this message or make copies. This email was scanned by eSafe Mail for viruses, vandals and other malicious content. ****************************************************************************** _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
