I just moved over to a new SSD so I could get Arch and Win10 dual-booting. All’s working well, except my fingerprint reader has vanished, and I don’t know why. Here’s what I’ve done (13" AMD 7040):
Cloned my disk over to the new (larger) SSD and resized partitions. Swapped in the new SSD, booted, fingerprint reader still worked.
Turned off the TPM (I don’t want Win10 force-updating itself to 11 and the TPM is an easy sacrifice to make to that end) and installed Win10. It came up missing a bunch of drivers (no surprise there) which I found and installed manually. One of the drivers I had to install was the Goodix fingerprint scanner, so up to this point the sensor was showing up as part of the system.
Set grub back to my default bootloader and made a menu entry to boot into Windows from the grub screen.
And at some point during or after step 3 the fingerprint reader just, like, vanished off the system. Doesn’t show up any more in either the Linux or the Windows install (where I literally just had to manually find a driver for it!). Turning the TPM back on doesn’t bring the sensor back (though it was enumerating fine for a while after I turned the TPM off). I have no idea what I’ve done. It is still enabled in the UEFI settings (the last thing I touched in there was making grub the default bootloader after windows was set up and running).
Not a lot, just a bunch of fingerprint auth daemon stuff:
phill ~ $ journalctl -b 0 | grep [fF]ingerprint
Jun 22 20:53:14 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 22 20:53:14 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 22 21:17:56 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 22 21:17:56 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 23 00:13:44 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 23 00:13:44 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 23 01:35:02 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 23 01:35:02 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 23 19:58:39 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 23 19:58:39 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 23 23:06:29 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 23 23:06:29 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 24 02:37:20 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 24 02:37:20 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 24 13:00:27 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 24 13:00:27 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 25 03:46:34 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 25 03:46:34 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 25 04:13:07 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 25 04:13:07 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 25 05:25:01 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 25 05:25:01 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:18:25 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:18:25 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 15:28:52 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 15:28:52 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 15:45:36 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 15:45:36 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 15:50:57 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 15:50:57 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 15:54:27 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 15:54:27 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 16:08:30 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 16:08:30 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 16:24:55 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 16:24:55 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 16:25:28 mekkatorque systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 16:25:28 mekkatorque systemd[1]: Started Fingerprint Authentication Daemon.
Another starting/started pair of lines is added every time I unlock the laptop (that’s why the last few are so close together in time, I was testing that).
That just comes up “No devices available”. Which is unsurprising given I can’t get the device to appear anywhere at all in either Windows (it’s vanished from the device manager) or Linux (lspci, lsusb, fwupdmgr get-devices all fail to show anything that looks like a fingerprint reader, though maybe I just don’t know what to look for or where).
At this point I suspect that the Windows install broke the reader’s firmware shortly after I installed the Goodix driver and now it’s just a tiny little brick. Is there a way to verify or disprove that? Maybe to just reset the reader to new/factory state? Do I have to order a new power button (and risk instantly breaking it, too)? I have tried cutting power for a few hours to see if that might clear/reset something (it didn’t). Disabling and reenabling the reader in BIOS did nothing either…
Can you try updating the finger print firmware again on the linux side ? maybe it’s just a botched update from windows, which hopefully can still be fixed with fwupd from snap.
No luck, I just get “failed to find any device providing 1e8c8470-a49c-571a-82fd-19c9fa32b8c3” right off the top on the “fwupdmgr get-devices” line. (And it’s not just when filtering by that GUID, nothing that looks even vaguely like a fingerprint reader shows up if I run a plain “fwupdmgr get-devices” (which, I guess, corresponds to whatever made the device vanish out of the Windows device manager as well).
Huh. I tried that earlier just to see if it’d do anything and nothing changed. Maybe I’ll muck with it some more.
I’m ultimately aiming to keep the TPM off. (Unless anyone has a better idea for how to make absolutely sure Windows Update doesn’t decide to “helpfully” force-upgrade me to 11. I do not want 11.)
Is there a way to verify or disprove that? Maybe to just reset the reader to new/factory state? Do I have to order a new power button (and risk instantly breaking it, too)? I have tried cutting power for a few hours to see if that might clear/reset something (it didn’t). Disabling and reenabling the reader in BIOS did nothing either…