I don’t even see the fingerprint reader, although I definitely have it and I’m sure I saw it listed before! Any idea how to check for this?
All, if you are finding the reader is not showing up, please provide the output of lsusb to we can see what is happening at the hardware level.
To all those who are having issues with your Framework Laptop 13 (13th Gen Intel Core), please provide the output as seen here from Cipher which helps me understand what is happening.
If you are using 11th or 12th gen, this is none of this is needed. This is for those who use 13th Gen Intel Core laptops or have replaced their input kit recently.
$ fwupdmgr refresh --force
Updating lvfs-testing
[ ]
Successfully downloaded new metadata: 1 local device supported
$ fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Selected device: Fingerprint Sensor
Framework Laptop (13th Gen Intel Core)
│
└─Fingerprint Sensor:
Device ID: d432baa2162a32c1554ef24bd8281953b9d07c11
Summary: Match-On-Chip fingerprint sensor
Current version: 01000320
Vendor: Goodix (USB:0x27C6)
Install Duration: 10 seconds
Serial Number: UIDXXXXXXXX_XXXX_MOC_B0
GUIDs: 1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
34def4c7-9461-5a32-a945-5dde0ca57d88 ← USB\VID_27C6&PID_609C&REV_0100
Device Flags: • Updatable
• Device can recover flash failures
• Signed Payload
$ fwupdmgr update 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Devices with no available firmware updates:
• Fingerprint Sensor
• System Firmware
• TPS DMC Family
• TPS6598X PD#0
• TPS6598X PD#1
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI dbx
• USB4 Retimer
• USB4 Retimer
• WD BLACK SN850X 1000GB
No updatable devices
$ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.Internal: Open failed with error: Please update firmware using fwupd
Okay, just replicated this myself on an input kit and had the following results.
I too, was unable to update the firmware using LVFS. However, on a whim, decided to try the fingerprint reader anyway. Registered my print without any issues.
Those who have found that it seems your stuck on 01000252 firmware, try again to register the fingerprint reader using the GUI as you see in the image. This was on a clean install of Fedora 38, fully updated.
@jlcfan in your instance, please try the GUI as I am getting the same error after I registered my prints using the Users GUI.
Removed my print, re-registered it using the GUI - working here. Skip the CLI and try that please.
@Matt_Hartley Success!
I decided to use the manual method as described in your post of August 21 in another thread:
and managed to update the firmware to 01000330:
├─Fingerprint Sensor:
│ Device ID: d432baa2162a32c1554ef24bd8281953b9d07c11
│ Summary: Match-On-Chip fingerprint sensor
│ Current version: 01000330
│ Vendor: Goodix (USB:0x27C6)
│ Install Duration: 10 seconds
│ Serial Number: UIDD84A7896_XXXX_MOC_B0
│ GUIDs: [****]
│ Device Flags: • Updatable
│ • Device can recover flash failures
│ • Signed Payload
Lastly, note:
- Framework Laptop 13" 13th Gen Intel Core
- DIY Edition
- Delivered beginning of September
- MX Linux 23 (Xcfe)
Thanks for your help!
2 Likes
I was able to fix the issue using the manual update posted here by @jlcfan (btw, thank you for bringing that thread to my attention).
- Framework Laptop 13" 13th Gen Intel Core
- DIY Edition
- Delivered end of September
- Pop!_OS 22.04 LTS
1 Like
Okay, awesome. We’re taking notes on who the lvfs method is working for and who is not having success with it. Seems the manual method has had a higher degree of success overall at this time. Good feedback.
Another success using the manual method, appreciate you sharing this.
When folks are able to use it successfully - at this time, the results are still early, but overall it looks like there are some things to work through.
Hello there
I only just got my laptop yesterday. I followed the Ubuntu 22.04 install guide but I’m having no luck with the fingerprint sensor.
In the settings app where you’re supposed to register fingerprints it says: Failed to claim fingerprint device Goodix MOC Fingerprint Sensor: Failed to communicate with fingerprint reader
What puzzles me is that the fingerprint sensor is not listed in the output of fwupdmgr get-devices. It could be that it is just not labelled as such?
When I run lsusb I get:
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 001 Device 002: ID 0bda:5634 Realtek Semiconductor Corp. Laptop Camera
Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And when I run fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3 I get:
fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Laptop (13th Gen Intel Core)
│
├─System Firmware:
│ │ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f
│ │ Summary: UEFI ESRT device
│ │ Current version: 772
│ │ Minimum Version: 1
│ │ Vendor: Framework (DMI:INSYDE Corp.)
│ │ Update State: Success
│ │ GUIDs: 13fd4ed2-cba9-50ba-bb91-aece0acb4cc3
│ │ 230c8b18-8d9b-53ec-838b-6cfc0383493a
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • System requires external power source
│ │ • Needs a reboot after installation
│ │ • Cryptographic hash verification is available
│ │ • Device is usable for the duration of the update
│ │
│ └─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Summary: UEFI revocation database
│ Current version: 83
│ Minimum Version: 83
│ Vendor: UEFI:Linux Foundation
│ Install Duration: 1 second
│ GUIDs: c6682ade-b5ec-57c4-b687-676351208742
│ f8ba2887-9411-5c36-9cee-88995bb39731
│ c0f9e469-9ce5-5752-898d-7637faa819e1
│ f35e120a-eb92-570d-8d38-78aa8ffdeebe
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│ • Only version upgrades are allowed
│ • Signed Payload
│
├─UEFI Device Firmware:
│ Device ID: 349bb341230b1a86e5effe7dfe4337e1590227bd
│ Summary: UEFI ESRT device
│ Current version: 2124
│ Minimum Version: 1000
│ Vendor: DMI:INSYDE Corp.
│ Update State: Success
│ GUID: 865d322c-6ac7-4734-b43e-55db5a557d63
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
├─UEFI Device Firmware:
│ Device ID: 2292ae5236790b47884e37cf162dcf23bfcd1c60
│ Summary: UEFI ESRT device
│ Current version: 310
│ Vendor: DMI:INSYDE Corp.
│ Update State: Success
│ GUID: 0c42b824-818f-428f-8687-5efcaf059bea
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
├─UEFI Device Firmware:
│ Device ID: f95c9218acd12697af946874bfe4239587209232
│ Summary: UEFI ESRT device
│ Current version: 310
│ Vendor: DMI:INSYDE Corp.
│ Update State: Success
│ GUID: 268ccbde-e087-420b-bf82-2212bd3f9bfc
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
└─WD BLACK SN770 500GB:
Device ID: 71b677ca0f1bc2c5b804fa1d59e52064ce589293
Summary: NVM Express solid state drive
Current version: 731100WD
Vendor: Sandisk Corp (NVME:0x15B7)
GUIDs: 9814a081-1232-5464-911f-8fe4b642d28b
87cfda90-ce08-52c3-9bb5-0e0718b7e57e
9c9fd14c-25fd-50c2-86c1-f7c08d1bcd04
1524d43d-ed91-5130-8cb6-8b8478508bae
008bacd9-329d-58e9-a092-c45170fa96b6
Device Flags: • Internal device
• Updatable
• System requires external power source
• Needs a reboot after installation
• Device is usable for the duration of the update
Looks like you followed the setup guide which at step 8, brought you to this thread. And from there, you attempted to follow the LVFS guide above? If you did and tried the LVFS guide above, please try the following:
-
Ignore the errors.
-
If the Users GUI for fingerprint reader section did not work after following the LVFS method step by step, please try this instead.
1 Like
Thanks @Matt_Hartley ! I followed the LVFS guide and at the update step it said:
$ fwupdmgr update 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Devices with no available firmware updates:
• UEFI dbx
No updatable devices
I then tried the link in the second dot point, and at the checking step I got:
sudo fwupdtool get-devices --plugins goodixmoc
Loading… [***************************************]
No detected devices
I tried installing the update anyway and I got:
$ sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab
Loading… [- ]00:40:10:0551 FuEngine failed to get releases for UEFI dbx: No releases found: Not compatible with org.freedesktop.fwupd version 1.7.9, requires >= 1.9.1
00:40:10:0556 FuEngine failed to get releases for UEFI dbx: No releases found: Not compatible with org.freedesktop.fwupd version 1.7.9, requires >= 1.9.1
00:40:11:0416 FuEngine failed to add device /sys/devices/pci0000:00/0000:00:1f.5/spi_master/spi0/spi0.0/mtd/mtd0ro: attribute size returned no data
Loading… [***************************************]
Decompressing… [***************************************]
No supported devices found
Should I open it up and check that the connector is connected properly? ¯\_(ツ)_/¯
You did the link, awesome, appreciate that. Now reboot, then try the GUI again completely ignoring the errors and the not found messaging. Sounds wrong, but try it. 
It works!
FWIW I did actually go all the way through the instructions in the link (including adding the quirk)
Thanks Matt! May you have a bountiful harvest!
2 Likes
Thank you! Delighted to hear the latter approach worked out.
Alright folks, I need a consensus. LVFS fail or success? I had some of you (myself included) using the cab file direct method due to LVFS challenges. What is the verdict?
Please respond with:
Fail/Success, if fail, link to your original post here where the fail is outlined.
Thanks
I’ve seen mostly negative results, so I need to hear from anyone who had success with LVFS please.
1 Like