[GUIDE] LVFS Fingerprint Reader Firmware for Framework Laptop 13, 13th Gen Intel Core & AMD 7040 Series fingerprint reader on Fedora 39 and Ubuntu 22.04

Framework Laptop 13 Linux
,
7

Just tested with a Framework 13 7840U running Fedora 39. Had a keyboard issue that needed to be RMA’d and new keyboard was experiencing the failed to claim issue after installation. Followed the steps in the guide and was able to update the firmware with a few minor issues. Firmware was initally 01000320 and firmware was upgraded to 01000330.

  1. Was using zsh as my shell so the dnf disable repo command required me to escape the *
  2. Had a communication timeout error during the firmware update which resulted in a failed update and bug report being sent. After restarting the machine the firmware was up to date on the fingerprint sensor and validated it’s functionality in Fedora.

Will keep an eye on things but aside from the hickups seems to be working. Let me know if this was the wrong spot to post this or if additional info would be helpful!

8

This is immensely helpful! Thank you! :slight_smile:

9

I thought I had followed the instructions correctly but I still see the original error message (Failed to claim fingerprint device Goodix MOC Fingerprint sensor…). New (batch 9) machine assembled yesterday.

Framework Laptop 13 AMD Ryzen 7040Series
AMD® Ryzen 5 7640u w/ radeon 760m graphics × 12
Ubuntu 22.04.3 LTS

All steps followed and feedback matched the post above except for the final screenshot. My version had an extra line: Device requests: Image.

Screenshot from 2023-12-15 17-48-12-cropped
Screenshot from 2023-12-15 17-48-12-cropped1034×668 322 KB

Afterwards I was notified of more software updates and saw the following error.

Screenshot from 2023-12-15 17-50-11-cropped
Screenshot from 2023-12-15 17-50-11-cropped1044×464 169 KB

10

Hi @Matt_Hartley :wave:

Batch 9 DIY (assembled yesterday)
AMD Ryzen 5 7640
Fedora 39

So I rode the trying-to-enrol-a-fingerprint rollercoaster yesterday. Fingerprint setup wasn’t prompted during the Fedora installation process, and when I went to my User settings, I was greeted with the “Failed to claim fingerprint…” alert. Went through the guide you linked above, which led to the firmware upgrade (and rollback for me, as I was apparently on 1.9.10). All was going well until I reached:

fwupdtool get-history

This wouldn’t work without a sudo command appended (run as-is above, I got a massively long list of permission denied responses). With sudo, it returned:

Loading… [******* ]07:04:08.092 FuEngine failed to add device usb:01:00:04: failed to claim interface 0x00: USB error on device 27c6:609c : Resource busy [-6]
Loading… [************************************** ]
No history

Checked the forums and r/framework again, found multiple users saying they’d had success running the firmware update/rollback while booting in recovery mode, but it was late and I was worried I’d doze off and make a stupid mistake.

Fast forward to just now, checked the forums and lo and behold, this thread showed up (not sure why it didn’t yesterday - used the same search terms). Followed your Fedora guide, and all was going well until I reached:

then lastly
fwupdmgr update 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
This should complete, then you will choose to reboot.

It didn’t complete. It returned:

failed to write: failed to reply: transfer time out

Luckily, I scrolled up and noticed this was apparently normal for Ubuntu, so I rolled the dice and rebooted.

The fingerprint scanner worked! :confetti_ball:

I entered my prints and locked the screen to test. Prints failed. Logged in with password.

Went back to Settings > Users and was greeted with the dreaded “Failed to claim fingerprint device…” alert again :sob:

So… back to square one. Any ideas? Feel like repeating the cycle again might not be the way to go :thinking:

11

Hi! @Matt_Hartley!
Your procedure worked for my FW 13 R5 7640 Batch 10 with Fedora 39 Kernel 6.6.6-200!
Thank you so much! :clap:

1 Like
12

This worked for me too under Fedora 39 Linux 6.6.6-200.fc39.x86_64 on the 13" AMD 7040 Series Framework, Batch 11. Thank you for the clear instructions!

1 Like
13

I believe it won’t work with secure boot, i had all these issues when i first tried to do anything with the update tool…

14

My new Framework 13 AMD arrived today (Ubuntu 22.04.3 LTS) and I’m struggling to get the fingerprint reader working. I worked through the official guide, and it was still reporting “Failed to claim fingerprint device…”

I tried the above guide (a few times), and my experience starts to differ when running:

name@name-framework:~$ fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Selected device: Fingerprint Sensor
Framework Laptop 13 (AMD Ryzen 7040Series)
│
└─Fingerprint Sensor:
      Device ID:          23ec719b6aabc2d2dac5176c232f0da7a21881b0
      Summary:            Match-On-Chip fingerprint sensor
      Current version:    01000320
      Vendor:             Goodix (USB:0x27C6)
      Install Duration:   10 seconds
      Serial Number:      UIDXXXXXXXX_XXXX_MOC_B0
      GUID:               1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
      Device Flags:       • Updatable
                          • Device can recover flash failures
                          • Signed Payload
      Device Requests:    • Image
    
name@name-framework:~$ fwupdmgr get-updates 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Selected device: Fingerprint Sensor
Devices with no available firmware updates: 
 • Fingerprint Sensor
No updatable devices
name@name-framework:~$ fwupdmgr update 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Devices with no available firmware updates: 
 • Fingerprint Sensor
 • WD BLACK SN770 500GB
No updatable devices

The only other error I noticed, not sure if it’s helpful, was here:

name@name-framework:~$ fwupdmgr enable-remote lvfs-testing
╔══════════════════════════════════════════════════════════════════════════════╗
║ Enable new remote?                                                           ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ The LVFS is a free service that operates as an independent legal entity and  ║
║ has no connection with Ubuntu. Your distributor may not have verified any    ║
║ of the firmware updates for compatibility with your system or connected      ║
║ devices. All firmware is provided only by the original equipment             ║
║ manufacturer.                                                                ║
║                                                                              ║
║ This remote contains firmware which is not embargoed, but is still being     ║
║ tested by the hardware vendor. You should ensure you have a way to manually  ║
║ downgrade the firmware if the firmware update fails.                         ║
║                                                                              ║
║ Enabling this functionality is done at your own risk, which means you have   ║
║ to contact your original equipment manufacturer regarding any problems       ║
║ caused by these updates. Only problems with the update process itself        ║
║ should be filed at https://bugs.launchpad.net/ubuntu/.                       ║
╚══════════════════════════════════════════════════════════════════════════════╝
Agree and enable the remote? [Y|n]: y
Authenticating…          [               /                       ]
Do you want to refresh this remote now? (Requires internet connection) [Y|n]: y
Downloading…             [         |                             ]
(/snap/fwupd/5438/bin/fwupdmgr:3471): Fwupd-CRITICAL **: 12:32:54.454: fwupd_checksum_guess_kind: assertion 'checksum != NULL' failed
Downloading…             [*********************************      ]
Successfully enabled and refreshed remote
15

Correct, from the instructions above for Ubuntu and Fedora, disable secure boot. :slight_smile:

16

Confirming you did remove fwupd via apt and install the snap?

sudo apt remove fwupd

Reboot

snap install fwupd

Reboot

fwupdmgr enable-remote lvfs-testing

  • You will be asked to confirm with Y once, and then once again.
  • You will then see “Successfully enabled and refreshed remote.”
  • Now that you have the more current version of fwupd installed after rebooting as instructed above. We’ll run the next steps:

fwupdmgr refresh --force

  • then run

fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3

Also

NOTE: You will absolutely see this error:

failed to write: failed to reply: transfer time out

  • This is fine. Give it two minutes, then I want you to reboot using this command:

sudo systemctl reboot -i

What is happening is fwupd is still “running”, however, the update is done, so we’re forcing the issue.

  • Once you log back in, your installation will be complete and you will be able to enroll fingerprints using Users in the settings.
17

Please run the steps again. But, this time I’d start off with this, no software center whatsoever please:

sudo apt update && sudo apt upgrade -y && snap refresh

Then rerun the steps. Please screenshot the results of the follow with the bullet points:

  • sudo apt update && sudo apt upgrade -y && snap refresh

Reboot

  • sudo apt remove fwupd (even if it’s removed, run again anyway)

  • snap install fwupd (even if it’s installed, run again anyway)

Reboot

  • fwupdmgr enable-remote lvfs-testing
  • You will be asked to confirm with Y once, and then once again.
  • You will then see “Successfully enabled and refreshed remote.”
  • Now that you have the more current version of fwupd installed after rebooting as instructed above. We’ll run the next steps:
  • fwupdmgr refresh --force

then run

  • fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3

This shows the older firmware as expected.

  • fwupdmgr get-updates 1e8c8470-a49c-571a-82fd-19c9fa32b8c3

then run

  • fwupdmgr update 1e8c8470-a49c-571a-82fd-19c9fa32b8c3

NOTE: You will absolutely see this error:

failed to write: failed to reply: transfer time out

This is fine. Give it two minutes, then I want you to reboot using this command:

  • sudo systemctl reboot -i

After rebooting again:

  • fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3

And this will be the final screenshot.

This is a lot of screenshots, but, it will show me specifically where things are falling off.

18

Test this again after a few reboots.

19

Sorry @Matt_Hartley I had to end up installing Windows. I had a deadline at work : )

Thank you for following up.

1 Like
20

Hi @Matt_Hartley , I am new to Linux, but here’s my attempt:

Framework Laptop 13 AMD Ryzen 7040Series
Ubuntu 22.04.3 LTS
BIOS: 03.03
Just set computer up today and did all the updates.

Before finding this thread, I followed these steps:

but it didn’t work for me. I then tried the steps above and got the same results as JT_TurtleOnABike. I followed the steps in your reply to them, including the reboots. Since I’m a new user I can only attach two pictures at a time, but here are the first two:

Screenshot from 2023-12-20 18-30-41
Screenshot from 2023-12-20 18-30-411572×1462 335 KB

Screenshot from 2023-12-20 18-38-20
Screenshot from 2023-12-20 18-38-201572×1066 201 KB

21

The 3rd and 4th:

Screenshot from 2023-12-20 18-46-51
Screenshot from 2023-12-20 18-46-511572×1390 284 KB

Screenshot from 2023-12-20 18-52-08
Screenshot from 2023-12-20 18-52-081572×1066 214 KB

22

The 5th and 6th (last):

Screenshot from 2023-12-20 18-55-02
Screenshot from 2023-12-20 18-55-021644×1390 333 KB

Screenshot from 2023-12-20 18-57-31
Screenshot from 2023-12-20 18-57-311572×1066 214 KB

I now realize that I should have tried again when it failed to download the metadata for lvfs-testing. I might try again tomorrow. For now, I’m out of replies to this topic, since I’m a new user. Also, if it matters at all- my computer suddenly slowed down a lot after the fwupdmgr enable-remote lvfs-testing line, to the point where every mouse movement took about 3 seconds. Was fine once I rebooted.

23

No worries, I totally get it - when you need to get stuff done, you do what is needed. Appreciate you closing the loop on this. :slight_smile: