UareU 5300 not working
i purchased a Digital Persona U.are.U 4500. It has usb vendor:device_id of 0x05ba:0x000e. I patched the driver uru4000.c which is stated that it works for 4500 too, to accept vendor/device_id but then i am stuck again in INIT_GET_HWSTAT. In #205 (closed) @hadess stated that he had an error with a 4500. Was this an older model with different device_id ?
here my debug trace :
Selected device 0 (Digital Persona U.are.U 4000/4000B/4500) claimed by uru4000 driver
(process:25739): libfprint-image_device-DEBUG: 08:16:41.648: Image device open completed
(process:25739): libfprint-device-DEBUG: 08:16:41.648: Device reported open completion
(process:25739): libfprint-device-DEBUG: 08:16:41.648: Completing action FPI_DEVICE_ACTION_OPEN in idle!
Opened device. (process:25739): libfprint-image_device-DEBUG: 08:16:41.648: Activating image device
(process:25739): libfprint-SSM-DEBUG: 08:16:41.648: [uru4000] INIT_NUM_STATES entering state 0
(process:25739): libfprint-uru4000-DEBUG: 08:16:41.648: read 1 regs at 7
(process:25739): libfprint-SSM-DEBUG: 08:16:41.648: [uru4000] SSM INIT_NUM_STATES failed in state 0 with error: endpoint stalled or request not supported
(process:25739): libfprint-SSM-DEBUG: 08:16:41.648: [uru4000] INIT_NUM_STATES completed with error: endpoint stalled or request not supported
(process:25739): libfprint-image_device-DEBUG: 08:16:41.649: Image device activation failed
(process:25739): libfprint-device-DEBUG: 08:16:41.649: Device reported generic error (endpoint stalled or request not supported) during action; action was: FPI_DEVICE_ACTION_CAPTURE
(process:25739): libfprint-device-DEBUG: 08:16:41.649: Device reported capture completion
(process:25739): libfprint-device-DEBUG: 08:16:41.649: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
(process:25739): libfprint-WARNING **: 08:16:41.649: Error capturing data: endpoint stalled or request not supported
(process:25739): libfprint-image_device-DEBUG: 08:16:41.649: Image device close completed
(process:25739): libfprint-device-DEBUG: 08:16:41.649: Device reported close completion
libusb: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know
libusb: error [do_close] A cancellation hasn't even been scheduled on the transfer for which the device is closing
(process:25739): libfprint-device-DEBUG: 08:16:41.654: Completing action FPI_DEVICE_ACTION_CLOSE in idle!