FrameworkComputer/SoftwareFirmwareIssueTracker

Framework 13 Ryzen AI 370 - fingerprint reader not working after sleep

Opened this issue · 8 comments

SparcV commented

Device Information

System Model or SKU

Please select one of the following

  • Framework Laptop 13 (AMD Ryzen™ AI 370 Series)

BIOS VERSION

Please provide the bios version.
3.04

DIY Edition information

If you are experiencing an issue on a DIY system, Please also fill out the memory and storage devices you are using.

Memory: 2x Crucial 32GB DDR5 5600
Storage: Samsung SSD 990 EVO Plus 4TB

Port/Peripheral information

Built-in fingerprint reader

Standalone Operation

Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?

  • Yes
  • No

Describe the bug

Simple issue, the fingerprint reader is non-responsive after the machine is put to sleep, does not happen for short periods of sleep under an hour, but overnight for sure.

Requires a complete restart of the OS (Windows 11 24H2) to return to function

Steps To Reproduce

Put the machine to sleep by closing the lid.
Wait some time
Open screen
Use a fingerprint to unlock Windows. The fingerprint is not recognized, and no error.

Expected behavior

After the machine is turned on, the fingerprint reader is to be recognized.

Operating System (please complete the following information):

  • OS/Distribution: Windows 11 Pro
  • Version: 24H2

Additional context

Have the latest drivers from the Framework support site installed.

Goodix Fingerprint Driver | 3.12804.0.270

JohnAZoidberg commented

Requires a complete restart of the OS (Windows 11 24H2) to return to function

What if you use Win+L to lock the screen - can you use the fingerprint reader to unlock it again?

SparcV commented
JohnAZoidberg commented

So you don't need to do a full restart to recover functionality of the fingerprint reader?

I mean after waking up from sleep and seeing the issue, then you log in with password/PIN, then you WIN+L lock - can you use the fingerprint reader then?

Mic92 commented

I have the same issue on NixOS (Linux).
Here is a session after suspend. I am able to recovery the access however by doing a reload of the USB bus:

[root@turingmachine:~]# fprintd-list joerg
No devices available

[root@turingmachine:~]# sudo modprobe -r xhci_pci && sudo modprobe xhci_pci

[root@turingmachine:~]# fprintd-list joerg
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
Fingerprints for user joerg on Goodix MOC Fingerprint Sensor (press):

#0: right-index-finger
My fingerprint sensor on the Framework AMD AI 350 seems to require a reload of the xchi_pci driver after suspend to work again

Interestingly, it hasn't happened in the last few days.
Will report back.

Mic92 commented

In my case the device completely vanished from lsusb.

zaolin commented

same here, usb devices sometimes vanishes after suspend. Also experienced that rarely for the hdmi card.

TheCodeAbode commented

Same here. The device completely vanishes so usbreset is useless and I can't reload the module because it is compiled into the kernel on Fedora 42. Very annoying as I use a very long, complex password and rely on the fingerprint reader to reduce the pain in the butt factor.

Mic92 commented

I don't know if there is a way to for the usb-controller to force rescan otherwise?
I might actually add this as a system service to automate that part.