Problem installing driver for ACR38T SIM card reader

[rjames]

Folks,
This device comes with an installation process in which a "configure" shell script builds a make file for subsequent Make and Make Install stages.
For me this fails with an error due to not having found libusb, with the suggestion of installing libusb or setting some environment variable arguments for LIBUSB_CFLAGS and LIBUSB_LIBS.
I do have libusb installed.
In poking around the problem I have discovered pkg-config which the shell script uses to test for these things but in trying it out from a terminal it just doesn't seem to return anything.
Specifically, I have found /usr/share/pkgconfig and /usr/lib/pkgconfig which contains libpcsclite.pc, which features somewhere in the install script, but calling for example pkg-config libpcsclite from the terminal gives just no response.
Can anyone suggest how to proceed from here? What next new thing do I have to learn?
Regards,
Jim

[rjames]

Has anyone out there succeeded in installing ACR38T SIM Card Reader?
I am getting no response from ACS or from SmartCard Focus from whom I bought the card.
Just getting hold of a built driver rather than having to compile it myself would be great.

[leigh123linux]

Try

su
yum install libusb-devel pcsc-lite-devel

Then try again

[rjames]

Dear Leigh,

That helped a little ;-).

The ./configure script ran with only a minor error - a syntax error in a procedure to handle "missing" - which at least did not stop the show.

The subsequent make finished with error -
test -f tokenparser.c || /bin/sh ../config/ylwrap tokenparser.l .c tokenparser.c -- flex
../config/ylwrap: line 110: flex: command not found

At this stage it all gets a bit deep for me - all I want to do is to manage my phone!

Unable to get any response from ACS support I think I'll return the gadget to them and try ot find another supplier - unless there is anyone out there who has succeeded and can provide me with a built version?

With thanks for your help,

Jim

[leigh123linux]

Try installing flex

su
yum install flex

[rjames]

Had never heard of flex - that was simple!

That moved me on to the problem of them having used directory names with spaces which caused 'unexpected token' which I was able to fix for myself!!

Then it all ran to a conclusion, that some ACR38 stuff was installed in /usr/lib/pcsc/drivers/.....
BUT the Monosim menu starts up and halts with 'No PCSC smartcard reader founded on pc'

Three possibilities occur to me -

Is there another step required but not documented - mounting or something?

Did I make the wrong choice between the CCID and non-CCID directories supplied?
I had used CCID.
I tried just repeating the process with non-CCID and saw a couple of nothing-to-do reports at the
make-install stage: install-exec-am and install-data-am

Maybe I now need to clean up all the debris and start all over again. Is that just a matter of
removing the /usr/lib/pcsc/drivers contents?

(If we do reach a conclusion on this I must document it all tidily for the benefit of others.)

[leigh123linux]

Try enabling the hot-plugging and udev support, I had a quick look at the code and these options might be useful

./configure --enable-udev --enable-usb-interrupt  --prefix=/usr

You will probably need to install libudev-devel

su
yum install libudev-devel

[rjames]

Getting warmer -

There was then a message scrolling by in the middle of the make-install progress which was to
*****************
copy the src/pcscd_acsccid.rules file in udev directory (/etc/udev/rules.d/)
*****************
Looking in rules.d I see that the .rules files all have a prefix number e.g 40-multipath.rules.
How do I choose an appropriate number for mine?

[leigh123linux]

Originally Posted by rjames

Getting warmer -

There was then a message scrolling by in the middle of the make-install progress which was to
*****************
copy the src/pcscd_acsccid.rules file in udev directory (/etc/udev/rules.d/)
*****************
Looking in rules.d I see that the .rules files all have a prefix number e.g 40-multipath.rules.
How do I choose an appropriate number for mine?

Try 99

[rjames]

I take it that the number is pretty well arbitrary. 99 is in use, 98 was free.

So I did that - copied the .rules file into rules.d with a prefix, shut down, re-started, and still monosim not finding a reader.

I'm now delving into man pages on udev and hoping to check the process right through.

Stage 1 is that a do see the device listed under lsusb. Next thing is to try to see some reaction to it in the udev mechanism, then hopefully some error messages buried somewhere?

I might be some time!

Jim