Framework 13 Intel 12th - fingerprint reader not working after sleep

[rmeissn]

Device Information

System Model or SKU

Please select one of the following

• Framework Laptop 12 (13th Gen Intel® Core™)
• Framework Laptop 13 (11th Gen Intel® Core™)
• Framework Laptop 13 (12th Gen Intel® Core™)
• Framework Laptop 13 (13th Gen Intel® Core™)
• Framework Laptop 13 (AMD Ryzen™ 7040 Series)
• Framework Laptop 13 (AMD Ryzen™ AI 300 Series)
• Framework Laptop 13 (Intel® Core™ Ultra Series 1)
• Framework Laptop 16 (AMD Ryzen™ 7040 Series)
• Framework Laptop 16 (AMD Ryzen™ AI 300 Series)
• Framework Desktop (AMD Ryzen™ AI 300 PRO Series)

BIOS VERSION

3.19.

DIY Edition information

Memory: 2x Corsair CMSX32GX4M2A3200C22
Storage: WD_BLACK SN850X 1000GB (620361WD)

Standalone Operation (Laptop Only)

• Yes
• No

Describe the bug

The fingerprint reader (Bus 003 Device 004: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix Fingerprint USB Device) seems to regularly reset after/while system suspend (s2idle). This causes two issues:

1. higher battery drain during suspend (about 50% in 10h)
2. When the system asks for fingerprint verification (e.g. through using sudo), it quickly cycles all three tries and falls back to password authentication (same for login after suspend, etc.).

I think it does not happen on each suspend, but quite often. After suspend, I can still see the device through lsusb. fprintd is also listing the device, but can't make it work. After restarting fprind.service, it works again.
In dmesg, I regularly see:

[25125.253137] usb 3-9: reset full-speed USB device number 4 using xhci_hcd
[25360.585101] usb 3-9: reset full-speed USB device number 4 using xhci_hcd
[25360.872764] usb 3-9: reset full-speed USB device number 4 using xhci_hcd
[25605.908921] WARNING! power/level is deprecated; use power/control instead
[25812.436129] usb 3-9: reset full-speed USB device number 4 using xhci_hcd
[25812.703955] usb 3-9: reset full-speed USB device number 4 using xhci_hcd
[26261.974132] usb 3-9: reset full-speed USB device number 4 using xhci_hcd
[26262.243133] usb 3-9: reset full-speed USB device number 4 using xhci_hcd

This behaviour started recently (I think about 2 weeks ago). I'm using Fedoras default TuneD. I'm on battery power and I am applying the energy saving profile (not balanced).

Steps To Reproduce

Steps to reproduce the behavior:

1. Boot System & Login
2. Close Laptop Lid and let it sit for some minutes
3. Reopen Laptop and try to login through fingerprint
4. Sometimes, the login attempt fails and you can't login through the fingerprint reader

Expected behavior

The fingerprint reader properly suspends and wakes from suspend. It is working after suspend without restarting services.

Operating System (please complete the following information):

• OS/Distribution: Fedora 43
• Linux Kernel Version: Linux framework 6.18.10-200.fc43.x86_64 SMP PREEMPT_DYNAMIC Wed Feb 11 17:20:05 UTC 2026 x86_64 GNU/Linux

Additional context

Might be related to #102

Gemini (allowed to read through my system and system logs) thinks that the fingerprint reader resets regulary and registers again on the usb bus. "This means that the Intel SoC can never enter the deep sleep state S0i3 (Deep Sleep) because the USB controller (XHCI) is constantly woken up by hardware interrupts."

I've already disassembled the keyboard cover and refitted all cables - I suspected one might have been loose or dust got on. This changed nothing.

fwupd info about the fingerprint reader:

Ausgewähltes Gerät: Fingerprint Sensor
Framework Laptop (12th Gen Intel Core)
│
└─Fingerprint Sensor:
      Gerätekennung:      22393fc023ab027cc856e804c7ad83af5bb1a8ca
      Zusammenfassung:    Match-On-Chip fingerprint sensor
      Aktuelle Version:   01000334
      Anbieter:           Goodix (USB:0x27C6)
      Installationsdauer: 10 Sekunden
      Seriennummer:       UID58A7C6B1_XXXX_MOC_B0
      GUID:               1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
      Geräte-Bitschalter: • Aktualisierbar
                          • Unterstützt auf dem entfernten Server
                          • Gerät führt Aktualisierungen in Etappen durch
                          • Das Gerät kann sich nach Fehlern beim Aufspielen wiederherstellen
                          • Signierte Nutzdaten
                          • Kann für die Emulation markieren