Fingerprint sensor update 334 failed, FP reader invisible since then

Community Support
,
1

Hello,

The fingerprint reader on my Debian 12 / Framework 13 intel 12th generation worked for a few months perfectly.

I recently updated the fingerprint reader firmware via “fwupdmgr” from version 330 to 334

Sadly, the upgrade failed, and the Fingerprint Reader didn’t work since.

fwupdmgr get-history is telling me this:

Framework Laptop (12th Gen Intel Core)

Fingerprint Sensor:
   Device ID:          d432baa2162a32c1554ef24bd8281953b9d07c11
   Previous version:   01000330
   Update State:       Failed
   Update Error:       failed to get device before update reload: failed to wait for detach replug: device d432baa2162a32c1554ef24bd8281953b9d07c11 did not come back
   Last modified:      2024-08-21 18:57
   GUID:               1e8c8470-a49c-571a-82fd-19c9fa32b8c3
   Device Flags:       ? Supported on remote server
                       ? Reported to remote server
                       ? Device can recover flash failures
                       ? Updatable
                       ? Signed Payload
 
  New version:      01000334
      Remote ID:        lvfs-testing
      License:          Unknown
      Description:      
      The vendor did not supply any release notes.

also, fwupdtool get-devices replies with this red line (amongst other)

FuEngine failed to probe device usb:01:00:09: USB error on device 27c6:609c : Entity not found [-5]
(this usb device IS my fingerprintreader :confused: )

Question: Does anyone have an idea how to fix that? could be by finishing the upgrade or installing an older version?

2

I hesitated to search for help here for a few days …

… and obviously the problem was solved hours after I post my issue here :wink:

My company is using “usbguard” to prevent unknown device to be connected to the USB bus. During the update, maybe something changed in the device itself, that made usbguard refuse to load the fingerprint reader …

I readded the FP Reader to usbguard allowed list and now it’s working again

sorry for this useless bugreport
<3

2 Likes
3

Perhaps you considered this post “useless,” but I encountered this exact issue last week. Thankfully I found your post and was able to reconfigure usbguard as well. :slight_smile: