Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

further issues with O2MICRO OZ776 (0b97:7772) #18

wants to merge 1 commit into
base: master
Choose a base branch


Copy link

@baerwolf baerwolf commented May 13, 2016

Hi all.

Recently I was confronted with serious issues regarding the reader within Fujitsu Lifebook E754.
Turns out it is the O2 Micros's OZ776.

Simplified: I was not able to read back some x509 certificates with it. (And other security tools errored while using it.)
(Althought all test passed using an external USB card reader...)
After debugging it more and more became obvious, all disruptions are caused by an LIBUSB_ERROR_TIMEOUT (-7) - the reader simply didn't respond in some cases.

Hereby I want to suggest my patch making the reader fully usable.
In case somebody needs pcscd before-patch- and after-patch logs, please write me, I will make them available then.

BR Stephan

This reader seems bogous, again:
This time it crashes randomly during normal communication.
Requests then weren't answered anymore and bulk reads simply time out.
After reset, resync or powerdown the reader becomes available again.
However most operations are disruped by this -
the reader isn't usable in principle.

This observation is very dependend of the smartcard.
(Perhaps quality grade during production?)
Even cards of same batch trigger different errors within applications.
But it seems all are caused by an libusb-timeout error -7.

This patch resolves all observed disruptions and make the reader
usable in production once again.

Signed-off-by: Stephan Baerwolf <>
Copy link

@LudovicRousseau LudovicRousseau commented Jun 24, 2016

See also the discussion "further issues with O2MICRO OZ776 (0b97:7772)" on the Pcsclite-muscle mailing list at

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

Successfully merging this pull request may close these issues.

None yet

2 participants