Fingerprint reader not working after sleep

Hey there,

I’m encountering a similar issue with my Ryzen 7 350 fw13’s fringerprint reader in Fedora 42 Gnome, but the underlying cause seems to be different.

After waking from sleep, running lsusb the goodix fingerprint adapter no longer shows in the list of connected devices. systemctl status fprintd also shows the service inactive (dead), unless I run fprintd-list username in which case the service shows no devices, wakes up for a while and then goes inactive again.

I don’t think raising it from sleep can bring the reader back, a full restart does though obviously.

Open to any ideas or suggestions to try.

https://wiki.archlinux.org/title/Fprint#Sleeping_while_fprintd_is_still_running_breaks_fprintd

Fprintd waits 30 seconds after a successful login before quitting, so sleeping during that time period may cause fprintd to break.

This is likely the issue for most people here. I assume that most system lock programs would start itself before the sleep happens, when sleep is called. My Hyprlock did exactly that. This is great for having the system locked immediately, leaving no room for operations at wake. The issue with that is fprintd is also called when the system lock is called. Since sleep goes after the lock wakes, sleep is going to occur during fprintd being active, thus breaking it.

The systemd service that Arch wiki provided solved the issue for me as stated.

Here is a NixOS systemd service following the one provided in the wiki in case any fellow Nix users are reading this too:

# Install the `killall` package yourself
systemd.services.kill-printd = {
  description = "Kill fprintd before sleep";
  before = [ "sleep.target" ]; 
  wantedBy = [ "sleep.target" ];
  serviceConfig = {
    ExecStart = "${lib.getExe pkgs.killall} fprintd";
  };
};

Edit: Found an issue with this systemd service. The parallel auth that the lock sets up to allow the user to use fprintd without having to make a password attempt first is terminated by this service. Will update later when I figure out the proper solution which is likely to be launching the sytem lock at wake instead of before sleep.

1 Like

The issue was indeed what I thought it was. After setting lock to boot after wake instead of before sleep indeed solved my issue completely. This way I still get to enjoy parallel auth on fprintd and the systemd service no longer is needed.

Greetings all,

Trying repro this on Fedora 42 Workstation, fully updated. Been testing this for a few hours. Off and on, trying to get it to happen. Not able to repro this this far on my FW13 7040 series.

For the sake focus, as we focus on Fedora 42 Workstation as an officially supported and tested distro, I will be testing there.

If fprintd is a modern release, you should not see any issues. If you do, then that is a bug that needs to be reported.

What we need from you:

  • Framework laptop exact version FW13 7040 series, AI 300, etc.

  • Distro and desktop affected.

  • We need to capture some indication where fprintd is failing. Something should be appearing in the logs.

  • We need to know fprintd version you are experiencing this with.
    rpm -qi fprintd or apt show fprintd

  • Your fingerprint reader firmware version: fwupdmgr get-devices --show-all | grep -A 12 fingerprint

  • Which applications are open when you closed your lid to suspend and how long before you resumed?

Framework laptop version: FW13 7040 Series
Distro and desktop affected: Fedora 42 with GNOME

dmesg logs:

\[126273.816946\] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
\[126273.821788\] wlp1s0: deauthenticating from 48:2f:6b:09:20:a2 by local choice (Reason: 3=DEAUTH_LEAVING)
\[126273.823953\] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
\[126274.262753\] PM: suspend entry (s2idle)
\[126274.691554\] Filesystems sync: 0.428 seconds
\[126274.804510\] Freezing user space processes
\[126274.807753\] Freezing user space processes completed (elapsed 0.003 seconds)
\[126274.807757\] OOM killer disabled.
\[126274.807759\] Freezing remaining freezable tasks
\[126274.809690\] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
\[126274.809695\] printk: Suspending console(s) (use no_console_suspend to debug)
\[126274.824936\] queueing ieee80211 work while going to suspend
\[126274.924520\] PM: suspend devices took 0.114 seconds
\[126274.926370\] ACPI: EC: interrupt blocked
\[128414.094448\] ACPI: EC: interrupt unblocked
\[128414.306310\] nvme nvme0: D3 entry latency set to 8 seconds
\[128414.309158\] \[drm\] PCIE GART of 512M enabled (table at 0x000000801FD00000).
\[128414.309252\] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming…
\[128414.312309\] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
\[128414.366830\] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
\[128414.366836\] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
\[128414.366838\] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
\[128414.366840\] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
\[128414.366841\] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
\[128414.366843\] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
\[128414.366844\] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
\[128414.366845\] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
\[128414.366847\] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
\[128414.366848\] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
\[128414.366850\] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
\[128414.366852\] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
\[128414.366853\] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
\[128414.370171\] \[drm\] ring gfx_32794.1.1 was added
\[128414.370956\] \[drm\] ring compute_32794.2.2 was added
\[128414.371701\] \[drm\] ring sdma_32794.3.3 was added
\[128414.371733\] \[drm\] ring gfx_32794.1.1 ib test pass
\[128414.371766\] \[drm\] ring compute_32794.2.2 ib test pass
\[128414.371871\] \[drm\] ring sdma_32794.3.3 ib test pass
\[128414.500169\] PM: resume devices took 0.198 seconds
\[128414.500495\] OOM killer enabled.
\[128414.500497\] Restarting tasks … done.
\[128414.502179\] random: crng reseeded on system resumption
\[128414.506279\] PM: suspend exit
\[128414.585244\] nvme nvme0: 12/0/0 default/read/poll queues
\[128417.860358\] wlp1s0: authenticate with 54:1f:8d:76:2f:a7 (local address=62:1c:a0:32:24:bb)
\[128417.875858\] wlp1s0: send auth to 54:1f:8d:76:2f:a7 (try 1/3)
\[128417.883587\] wlp1s0: authenticated
\[128417.886353\] wlp1s0: associate with 54:1f:8d:76:2f:a7 (try 1/3)
\[128417.931978\] wlp1s0: RX AssocResp from 54:1f:8d:76:2f:a7 (capab=0x1431 status=0 aid=3)
\[128417.966312\] wlp1s0: associated
\[128417.966479\] wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 54:1f:8d:76:2f:a7
\[128513.954984\] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
\[128514.213229\] usb 1-4: reset full-speed USB device number 3 using xhci_hcd

journalctl -fu fprintd

Aug 12 03:06:10 framework-13 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon…
Aug 12 03:06:10 framework-13 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Aug 12 03:06:42 framework-13 systemd[1]: fprintd.service: Deactivated successfully.
Aug 12 10:08:32 framework-13 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon…
Aug 12 10:08:33 framework-13 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Aug 12 10:09:01 framework-13 fprintd[180434]: Device reported an error during identify: Cannot run while suspended.
Aug 12 10:45:09 framework-13 systemd[1]: fprintd.service: Deactivated successfully.
Aug 12 10:46:21 framework-13 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon…
Aug 12 10:46:21 framework-13 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Aug 12 10:46:54 framework-13 systemd[1]: fprintd.service: Deactivated successfully.

fprintd Version: fprintd-1.94.5-1.fc42
fingerprint reader firmware version: fwupdmgr doesnt recognize the fingerprint reader for some reason
Which applications are open when you closed the lid: Discord, Signal, Telegram, Firefox, ptyxis, gnome-settings
How long before you resumed: 7 hours.

After a reboot, fwupdmgr does detect the fingerprint reader

│     Summary:            Match-On-Chip fingerprint sensor
│     Current version:    01000334
│     Vendor:             Goodix (USB:0x27C6)
│     Install Duration:   10 seconds
│     Serial Number:      UID2D296D16_XXXX_MOC_B0
│     GUID:               1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\\VID_27C6&PID_609C
│     Device Flags:       • Updatable
│                         • Supported on remote server
│                         • Device stages updates
│                         • Device can recover flash failures
│                         • Signed Payload
│                         • Can tag for emulation

This issue happens daily for me. I’m not sure if this is relevant or if the default configs within Fedora have changed, but this install is just about 1 year old and the issue was happening ever since I installed.

Thank you Matt for your interest in helping us resolve this issue

1 Like

Same issue for me:

FW13 AI 350

Fedora 42 with GNOME

journalctl -fu fprintd

Shows nothing beyond service starting and deactivated, doesnt even show device error in logs like aaz2234’s

lsusb doesnt even show the fingerprint reader attached.

I do see some strange USB ACPI issues on resume that appear.

After reboot lsusb does show device again.

Fwupdmgr also shows the device after reboot.
│ Summary: Match-On-Chip fingerprint sensor
│ Current version: 01000334
│ Vendor: Goodix (USB:0x27C6)
│ Install Duration: 10 seconds
│ Serial Number: UIDB260EBCC_XXXX_MOC_B0
│ GUID: 1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
│ Device Flags: • Updatable
│ • Supported on remote server
│ • Device stages updates
│ • Device can recover flash failures
│ • Signed Payload
│ • Can tag for emulation

1 Like

Same specs as eng_kinght:
FW13 Ryzen 7 350
2x16 5600MHz ram

Fedora 42 Workstation updated this morning
fprintd-1.94.5-1.fc42.src.rpm
fwupdmgr:

│     Summary:            Match-On-Chip fingerprint sensor
│     Current version:    01000334
│     Vendor:             Goodix (USB:0x27C6)
│     Install Duration:   10 seconds
│     Serial Number:      UID901FAD2A_XXXX_MOC_B0
│     GUID:               1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
│     Device Flags:       • Updatable
│                         • Supported on remote server
│                         • Device stages updates
│                         • Device can recover flash failures
│                         • Signed Payload
│                         • Can tag for emulation
│   

Fingerprint disappears only sometimes and after an indefinite amount of sleep. Could be after a few minutes, could be after a few hours of sleep. Doesn’t show on lsusb unless I reboot.

It seems like some other issues are occuring too after sleep, such as some apps showing a crash in notification center. Another thing I noticed in smartctl is that my ssd that I’ve only had for a few months shows 4000+ power cycles (few hundred hours of use though) and ~3800 unsafe shutdowns, presumably caused by the laptop going to sleep or even repeatedly waking up from it for different reasons.

I’d really like to be able to trace all these problems and resolve them because this is unacceptable when even Windows has less issues with these things while being… Windows.
I was expecting to get a more stable experience with Fedora out of the box on a device that presumably supports it officially, but Linux is Linux so I can let that slide as long as the development teams for both software and hardware can collaborate with the end users, us, to solve these problems.

Thanks Matt for reaching out on this and I’m looking forward to your reply and suggestions

1 Like

I’m having similar issues. It’s intermittent. It seems to happen when I plug the laptop in and then open the lid to resume from sleep.

Framework 13 AI340

Fedora 42 Gnome

Sleep time was 30-40 minutes.

Firefox, terminal, plex, signal, calculator, resource monitor, discord, calculator, text editor

Idle…: 0%
│     Summary:            Match-On-Chip fingerprint sensor
│     Current version:    01000334
│     Vendor:             Goodix (USB:0x27C6)
│     Install Duration:   10 seconds
│     Serial Number:      UID1C430D8E_XXXX_MOC_B0
│     GUID:               1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
│     Device Flags:       • Updatable
│                         • Supported on remote server
│                         • Device stages updates
│                         • Device can recover flash failures
│                         • Signed Payload
│                         • Can tag for emulation

Name        : fprintd
Version     : 1.94.5
Release     : 1.fc42
Architecture: x86_64
Install Date: Sat 03 May 2025 08:04:14 PM EDT
Group       : Unspecified
Size        : 849801
License     : GPL-2.0-or-later AND GFDL-1.1-or-later
Signature   : RSA/SHA256, Wed 09 Apr 2025 02:52:13 AM EDT, Key ID c8ac4916105ef944
Source RPM  : fprintd-1.94.5-1.fc42.src.rpm
Build Date  : Wed 09 Apr 2025 02:34:27 AM EDT
Build Host  : buildhw-x86-10.iad2.fedoraproject.org
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : http://www.freedesktop.org/wiki/Software/fprint/fprintd
Bug URL     : https://bugz.fedoraproject.org/fprintd
Summary     : D-Bus service for Fingerprint reader access
Description :
D-Bus service to access fingerprint readers.



[380762.539148] Timekeeping suspended for 1954.402 seconds
[380762.539199] PM: Triggering wakeup from IRQ 7
[380762.539281] ACPI: PM: Wakeup unrelated to ACPI SCI
[380762.539286] PM: resume from suspend-to-idle
[380762.539961] ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 exit
[380762.540225] ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 ms exit
[380762.540414] ACPI: \_SB_.PEP_: Successfully transitioned to state screen on
[380762.540841] ACPI: EC: interrupt unblocked
[380762.864096] PM: noirq resume of devices complete after 323.676 msecs
[380762.864148] GPIO 8 is active: 0x18146b00
[380762.867351] PM: early resume of devices complete after 3.120 msecs
[380762.868698] GPIO 8 is active: 0x18141b00
[380762.870259] GPIO 8 is active: 0x18141b00
[380762.872395] [drm] PCIE GART of 512M enabled (table at 0x0000008001700000).
[380762.872446] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
[380762.877042] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
[380762.897306]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[380762.925282]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[380762.944233] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[380762.944237] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[380762.944239] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[380762.944240] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[380762.944241] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[380762.944242] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[380762.944243] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[380762.944244] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[380762.944245] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[380762.944246] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[380762.944247] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[380762.944248] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec_0 uses VM inv eng 1 on hub 8
[380762.944249] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
[380762.944250] amdgpu 0000:c1:00.0: amdgpu: ring vpe uses VM inv eng 4 on hub 8
[380762.948839] [drm] ring gfx_32790.1.1 was added
[380762.949254] [drm] ring compute_32790.2.2 was added
[380762.949671] [drm] ring sdma_32790.3.3 was added
[380762.949706] [drm] ring gfx_32790.1.1 ib test pass
[380762.949731] [drm] ring compute_32790.2.2 ib test pass
[380762.949796] [drm] ring sdma_32790.3.3 ib test pass
[380763.126348] PM: resume of devices complete after 258.989 msecs
[380763.129628] PM: resume devices took 0.262 seconds
[380763.129859] OOM killer enabled.
[380763.129861] Restarting tasks ... done.
[380763.131367] random: crng reseeded on system resumption
[380763.150426] nvme nvme0: 12/0/0 default/read/poll queues
[380763.157358] PM: suspend exit
[380763.634119] Lockdown: s2idle-hook: debugfs access is restricted; see man kernel_lockdown.7
[380764.253323] usb 1-1: reset full-speed USB device number 2 using xhci_hcd
[380764.544223] usb 1-1: reset full-speed USB device number 2 using xhci_hcd
[380791.584107] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[380791.590396] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[380791.593136] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[380791.603427] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[380792.373260] Lockdown: s2idle-hook: debugfs access is restricted; see man kernel_lockdown.7
[380792.500770] PM: suspend entry (s2idle)
[380792.524016] Filesystems sync: 0.023 seconds
[380792.604991] Freezing user space processes
[380792.608035] Freezing user space processes completed (elapsed 0.003 seconds)
[380792.608045] OOM killer disabled.
[380792.608047] Freezing remaining freezable tasks
[380792.609280] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[380792.609286] printk: Suspending console(s) (use no_console_suspend to debug)
[380793.656646] PM: suspend of devices complete after 1043.969 msecs
[380793.656662] PM: start suspend of devices complete after 1047.323 msecs
[380793.656666] PM: suspend devices took 1.047 seconds
[380793.657329] Clearing debounce for GPIO #0 during suspend.
[380793.657339] Disabling GPIO #5 interrupt for suspend.
[380793.657343] Disabling GPIO #8 interrupt for suspend.
[380793.657363] Disabling GPIO #84 interrupt for suspend.
[380793.658050] PM: late suspend of devices complete after 1.379 msecs
[380793.658572] ACPI: EC: interrupt blocked
[380793.702755] PM: noirq suspend of devices complete after 44.534 msecs
[380793.702771] ACPI: \_SB_.PCI0.GPP0.SWUS: LPI: Constraint not met; min power state:D3hot current power state:D0
[380793.702776] ACPI: \_SB_.PCI0.GPP1.SWUS: LPI: Constraint not met; min power state:D3hot current power state:D0
[380793.703135] ACPI: \_SB_.PEP_: Successfully transitioned to state screen off
[380793.703484] ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 ms entry
[380793.703756] ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 entry
[380793.704275] PM: suspend-to-idle
[380793.704313] amd_pmc: SMU idlemask s0i3: 0xffff9afd
[382072.517912] Timekeeping suspended for 1277.834 seconds
[382072.517971] PM: Triggering wakeup from IRQ 9
[382072.518053] ACPI: EC: ACPI EC GPE status set
[382072.518076] ACPI: EC: ACPI EC GPE dispatched
[382072.525326]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [ACAD] (Device) Value 0x80 (Status Change) Node 00000000139345a6
[382072.525643]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [VGA_] (Device) Value 0x81 (Information Change) Node 00000000c00eff1a
[382073.535790]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [BAT1] (Device) Value 0x80 (Status Change) Node 0000000010bc48b0
[382073.536036] ACPI: EC: ACPI EC work flushed
[382073.536268] ACPI: PM: Rearming ACPI SCI for wakeup
[382073.536319] amd_pmc: SMU idlemask s0i3: 0xffff1afd
[382073.536323] PM: Triggering wakeup from IRQ 9
[382073.536378] ACPI: EC: ACPI EC GPE status set
[382073.536397] ACPI: PM: Rearming ACPI SCI for wakeup
[382073.536438] amd_pmc: SMU idlemask s0i3: 0xffff1afd
[382074.418769] Timekeeping suspended for 0.977 seconds
[382074.418852] PM: Triggering wakeup from IRQ 9
[382074.418959] ACPI: EC: ACPI EC GPE status set
[382074.418978] ACPI: EC: ACPI EC GPE dispatched
[382074.425391]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [ACAD] (Device) Value 0x80 (Status Change) Node 00000000139345a6
[382074.425702]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [VGA_] (Device) Value 0x81 (Information Change) Node 00000000c00eff1a
[382075.435900]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [BAT1] (Device) Value 0x80 (Status Change) Node 0000000010bc48b0
[382075.436162] ACPI: EC: ACPI EC work flushed
[382075.436382] ACPI: PM: Rearming ACPI SCI for wakeup
[382075.436439] PM: Triggering wakeup from IRQ 9
[382075.436440] amd_pmc: SMU idlemask s0i3: 0xffff9afd
[382075.436514] ACPI: EC: ACPI EC GPE status set
[382075.436532] ACPI: PM: Rearming ACPI SCI for wakeup
[382075.436573] amd_pmc: SMU idlemask s0i3: 0xffff9afd
[382076.956653] Timekeeping suspended for 1.978 seconds
[382076.956732] PM: Triggering wakeup from IRQ 9
[382076.956890] ACPI: EC: ACPI EC GPE status set
[382076.956911] ACPI: EC: ACPI EC GPE dispatched
[382076.964501]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [ACAD] (Device) Value 0x80 (Status Change) Node 00000000139345a6
[382076.964927]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [VGA_] (Device) Value 0x81 (Information Change) Node 00000000c00eff1a
[382077.975024]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [BAT1] (Device) Value 0x80 (Status Change) Node 0000000010bc48b0
[382077.975286] ACPI: EC: ACPI EC work flushed
[382077.975518] ACPI: PM: Rearming ACPI SCI for wakeup
[382077.975566] PM: Triggering wakeup from IRQ 9
[382077.975575] amd_pmc: SMU idlemask s0i3: 0xffff1afd
[382077.975627] ACPI: EC: ACPI EC GPE status set
[382077.975642] ACPI: PM: Rearming ACPI SCI for wakeup
[382077.975683] amd_pmc: SMU idlemask s0i3: 0xffff1afd
[382078.627814] PM: Triggering wakeup from IRQ 9
[382078.627941] ACPI: EC: ACPI EC GPE status set
[382078.627965] ACPI: EC: ACPI EC GPE dispatched
[382078.634400]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [LID0] (Device) Value 0x80 (Status Change) Node 00000000ac58bb49
[382078.634457] ACPI: EC: ACPI EC work flushed
[382078.634474] ACPI: PM: Wakeup after ACPI Notify sync
[382078.634476] PM: resume from suspend-to-idle
[382078.635262] ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 exit
[382078.635519] ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 ms exit
[382078.635704] ACPI: \_SB_.PEP_: Successfully transitioned to state screen on
[382078.636126] ACPI: EC: interrupt unblocked
[382078.924254] PM: Triggering wakeup from IRQ 1
[382078.968448] PM: noirq resume of devices complete after 332.736 msecs
[382078.971641] PM: early resume of devices complete after 3.022 msecs
[382078.976665] [drm] PCIE GART of 512M enabled (table at 0x0000008001700000).
[382078.976720] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
[382078.978769] Timekeeping suspended for 0.626 seconds
[382078.980943] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
[382078.994429]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.229829]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.232236] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[382079.232240] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[382079.232242] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[382079.232243] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[382079.232245] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[382079.232245] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[382079.232246] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[382079.232247] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[382079.232248] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[382079.232250] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[382079.232251] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[382079.232252] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec_0 uses VM inv eng 1 on hub 8
[382079.232253] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
[382079.232254] amdgpu 0000:c1:00.0: amdgpu: ring vpe uses VM inv eng 4 on hub 8
[382079.236404]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.238491] [drm] ring gfx_32790.1.1 was added
[382079.238725] [drm] ring compute_32790.2.2 was added
[382079.238968] [drm] ring sdma_32790.3.3 was added
[382079.238987] [drm] ring gfx_32790.1.1 ib test pass
[382079.239004] [drm] ring compute_32790.2.2 ib test pass
[382079.239026] [drm] ring sdma_32790.3.3 ib test pass
[382079.253672] PM: resume of devices complete after 282.022 msecs
[382079.254506]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.258362] PM: resume devices took 0.287 seconds
[382079.258626] OOM killer enabled.
[382079.258627] Restarting tasks ... done.
[382079.260658] random: crng reseeded on system resumption
[382079.284557]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.285564] PM: suspend exit
[382079.315487]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.343615]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.371619]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.400683]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.419645]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.446598]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.469605]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.497581]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.663585]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.693650]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382079.721541]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.424624]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.444024]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.466024]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.484906]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.506037]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.521042]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.549047]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.567029]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.588022]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.608653]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.628686]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.648002]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.666822]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.688068]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.708025]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.708093] ucsi_acpi USBC000:00: unknown error 0
[382080.732034]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.750040]    evmisc-0132 ev_queue_notify_reques: Dispatching Notify on [UBTC] (Device) Value 0x80 (Status Change) Node 000000003398ca49
[382080.783750] nvme nvme0: 12/0/0 default/read/poll queues
[382080.805343] Lockdown: s2idle-hook: debugfs access is restricted; see man kernel_lockdown.7
[382111.295393] usb 1-1: reset full-speed USB device number 2 using xhci_hcd
[382111.554433] usb 1-1: reset full-speed USB device number 2 using xhci_hcd

1 Like

The problem has been basically resolved for me on fedora 42, by just updating normally

1 Like

True, same for me. It’s basically flawless now

Not for me.

Still after sleep for a certain time, fingerprint reader is gone after the next reboot.

Hi there, not sure if this is related to your problems, but I was having similar issues which were related to power management. I am on Omarchy / Arch Linux on Framework 13, AMD Ryzen AI 5 340. Dmesg is showing that Goodix fingerprint reader failed to resume from sleep. I tried to disable power management for reader (via udev rule), also did USB quirks in kernel cmd line, without luck.

Finally it got “resolved”, well workarounded, by unbinding and rebinding USB xHCI controller, which is hosting the reader. Now it works, but is is ugly way of restarting a device, which is unable to weak up from sleep.

I used this script, which I placed in systemd: /usr/lib/systemd/system-sleep/95-xhci-c1-reset.sh

#!/bin/sh
# Rebind USB controller 0000:c1:00.4 after resume to restore Goodix fingerprint reader.

PCI_FUNC="0000:c1:00.4"
GOODIX_ID="27c6:609c"
DRIVER_PATH="/sys/bus/pci/drivers/xhci_hcd"

case "$1" in
  post)
    # Give the system a moment to resume normally
    sleep 2

    # Check if the fingerprint reader is missing
    if ! lsusb -d "$GOODIX_ID" >/dev/null 2>&1; then
      logger -t fp-rebind "Goodix missing after resume, resetting xHCI controller $PCI_FUNC"
      # Unbind and rebind only that PCI function
      echo "$PCI_FUNC" > "$DRIVER_PATH/unbind"
      sleep 1
      echo "$PCI_FUNC" > "$DRIVER_PATH/bind"
      sleep 2
      # Restart fprintd so it picks up the reader again
      systemctl try-restart fprintd.service
    fi
    ;;
esac

Dont forget to chmod+x the file.

Original error in dmesg:

[ 1576.335739] usb 1-1: PM: dpm_run_callback(): usb_dev_resume returns -22
[ 1576.335752] usb 1-1: PM: failed to resume async: error -22
[ 1576.339433] usb 1-1: USB disconnect, device number 2

After trying to disable power management just for reader, I also got:

usb 1-1: device not accepting address
usb 1-1: reset failed, -110
usb 1-1: device descriptor read/64, error -71

Hope this helps anyone.

Also worth mentioning that I am on kernel 6.17.1-arch1-1 and I have updated all firmwares in my Framework to latest versions as of this day.

3 Likes

I still have the same issue on Fedora 42. Any updates?

Your systemd script works for me as well. Fedora 42 on 6.16.9-200.

I had noticed the same thing, when the usb controller is forcibly reset it would resolve the problem. You just did it better :stuck_out_tongue: .

Still hoping for a less cludgie way. Either firmware on the Goodix or bios related fixes.

2 Likes

Glad to help. I am also looking forward to fix this issue by Framework or Goodix to avoid quirks and helpers. Anyway, this is the only thing which is not working on my Framework so I am overall happy with this laptop. :slight_smile:

This fix works for me too. Shame that we have to resort to these methods for something that should be a simple fix.

thank you this helped me as well :slight_smile:

This no longer works on Fedora 43. I’m really getting tired of having non functioning hardware.

1 Like

Also Fedora version 43 breaks bluetooth due to malfunctioning firmware. Probably not Framework fault, but Mediatek bug regressing from recent versions.

Ok, now I am on Fedora 43.20251126.0 Atomic. Blueeooth works again, fingerprint reader mostly works with my quirk suggested earlier here. New issue is the non-functional keyboard echo in LUKS unlock screen during boot, but if you type the password blindly, it works. I feel like this version is liveable.