-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
LIBUSB_ERROR_NO_DEVICE after reader reset #208
Comments
What is the output of the command |
I do not have the "VIX TECHNOLOGY SECURE READER" reader in the list of CCID device. |
/usr/sbin/pcscd --versionpcsc-lite version 2.2.0 We have added our reader (https://vixtechnology.com/products/devices) to the ccid package, see attached output of parse. |
Try building pcsc-lite with libudev instead of libusb. Another idea is to enable |
Any news? |
Our platform is busybox based, so no libudev, but we implemented a workaround to restart the pcsc daemon when the reader is re-detected on the USB bus. |
So problem fixed on your side. |
Versions
pcsc v2.3.0
ccid v1.6.1
Platform
Linux Kernel v6.1.28
VIX TECHNOLOGY SECURE READER (USB)
Issue
We have been using pcsc and ccid for a long time and has been working well with Linux Kernel 5.4.31
We recently upgraded to Kernel 6.1.28, pcsc and ccid still working well, however there seems to be an issue when the reader is reset (or power cycled through a USB hub), pcsc will fail to re-detect the reader, logs showing libusb_open failed: LIBUSB_ERROR_NO_DEVICE.
This requires a restart of pcscd, then reader is working again.
Again, this issue seems only apparent in Linux Kernel 6.1.28, no issue in Kernel 5.4.31.
Log attached
taipan2_log_pcscd230_ccid161.txt
The text was updated successfully, but these errors were encountered: