On 03/31/2016 04:56 PM, Petter Reinholdtsen wrote:
[Petter Reinholdtsen]
My only ideas is something is wrong with the armel architecture
support of some of the packages involved, or the Raspberry Pi is
unable to provide enough power to the smart card reader and smart card
for the smart card to work. Not quite sure how to figure out if any
of these ideas are correct.
Here are some information and somethings to try.
(1) Power consumption of smartcard readers/token is small. For
example, it's just a few mA for Gnuk Token. So, I don't think
power consumption matters.
(2) On the other hand, the root hub of RPi matters. It is good idea
to use USB hub with independent power supply to figure out the USB
problem. Or, I found the boot cmdline option of "dwc_otg.speed=1"
for RPi to specify the USB speed to 12Mbps.
(3) We don't need to use pcscd. We can just use internal CCID driver
of GnuPG and I think it is better because software components
become simpler. At least, simpler is better when debugging. Try
with "service pcscd stop" or "apt-get remove pcscd".
(4) To debug scdaemon, please have the following configuration file.
Note that it may log your PIN information, so, don't send the log
when you do authenticate the card (or change your PIN before your
experiment and debug).
------------------------ .gnupg/scdaemon.conf
debug-level guru
debug-all
debug-ccid-driver
log-file /run/user/1000/scd.log # change UID=1000 here.
verbose
------------------------
I use Gnuk Token daily with Wandboard (armhf) and Orange PI PC (armhf)
through a USB hub on the USB keyboard. I have been using a variant of
SheevaPlug (armel) for the development of NeuG (when I let the device
generate 64GiB of output) with a USB hub. All work well.
--
