[TRACKING] Fingerprint reader failing to register on 13th gen

Eek! @Matt_Hartley good callout, I mispoke and now verified, I am on Ubuntu 23.04 :100:

Originally no such file, I did not add a quirk manually since my fwupd version was > 1.8.8 (1.8.12). Added the quirk for shiggles & rebooted, output is now:

Plugin = goodixmoc

Fingerprint sensor still showing the same error.

Interesting. You should have had /usr/share/fwupd/quirks.d/goodixmoc.quirk on a default install.

Looks like youā€™re missing a line.

[USB\VID_27C6&PID_609C]

Plugin = goodixmoc

Using the command provided in this doc should have echoed both lines in.

You can add that missing line in manually, reboot and try again.

Hi!

Iā€™m trying to get working the fingerprint by following this guide from the framework guys.
It did not work out so Iā€™m asking for some help here, thanks in advance and sorry if Iā€™m too verbose!

The third command on the list fails with this error message:

sudo fwupdtool get-devices --plugins goodixmoc
Loading...      [-                                      ]21:55:45:0898 FuEngine             failed to add device usb:01:00:09: failed to claim interface 0x00: USB error on device 27c6:609c : Resource busy [-6]
Loading...      [***************************************]
No detected devices

I kept reading the guide to find out if the rest of the commands maybe could help me find some more info and I see that my fwupdmgr has a very very old version, as in the same guide they claim that being on a version less than 1.8.8 is oldā€¦

fwupdmgr --version
runtime   org.freedesktop.fwupd         1.7.9
runtime   com.dell.libsmbios            2.4
compile   org.freedesktop.gusb          0.3.10
compile   com.hughsie.libjcat           0.1.9
runtime   org.kernel                    6.1.0-1021-oem
compile   org.freedesktop.fwupd         1.7.9
runtime   org.freedesktop.gusb          0.3.10

I guess Iā€™m on the same situation as all Ubuntu 22.04 users so I get the same fwupdmgr version, the one that uses the last call for desperate users wanting this working but here Iā€™m also getting a new error:

sudo fwupdtool get-history 
Loading...      [-                                      ]22:18:39:0308 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
22:18:39:0310 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
22:18:39:0784 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...      [***************************************]
No history

In short the question here (just guessing what is all the root of evil) is:
How could I update the fwupdmgr?

Last question is about the automatic firmware update (LVFS), is this something we can expect to happen in days, weeks or months?

1 Like

Hi @juan_andres,

I didnā€™t see this until now as we generally see these questions in the Linux forum or Support, so going to merge this into the main thread.

Just to make sure I understand:

  • You downloaded the cab file.

  • Ran:
    sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab

  • Then with the older version of fwupdmgr, ran:
    echo '[USB\VID_27C6&PID_609C]' | sudo tee -a /usr/share/fwupd/quirks.d/goodixmoc.quirk ; echo 'Plugin = goodixmoc' | sudo tee -a /usr/share/fwupd/quirks.d/goodixmoc.quirk
    And you verified the output of sudo cat /usr/share/fwupd/quirks.d/goodixmoc.quirk

as seeing:

[USB\VID_27C6&PID_609C]

Plugin = goodixmoc

Ubuntu wants users on snaps and we have tested this on not the snap version (newer). So ideally, you should double check the above steps, reply with the output of each.

Hi @Matt_Hartley,

Here you have the output from the first command:

juanillo@frameworkillo:~/Baixades$ sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab
[sudo] contrasenya per a juanillo: 
S'estĆ  carregant...      [-                                      ]22:03:13:0236 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
22:03:13:0238 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
22:03:16:0582 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
S'estĆ  carregant...      [***************************************]
S'estĆ  descomprimint...  [***************************************]
S'estĆ  escrivint...      [*************************************  ]22:03:26:0709 FuEngine             failed to update-cleanup after failed update: failed to get device before update cleanup: failed to wait for detach replug: device d432baa2162a32c1554ef24bd8281953b9d07c11 did not come back
failed to write: failed to reply: transfer timed out

Just in case it could be that I had no execute rights on the cab file I added 764 rights for it and then re-run the same command, the output is failing again but I see one extra line:

juanillo@frameworkillo:~/Baixades$ sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab
S'estĆ  carregant...      [-                                      ]22:09:13:0324 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
22:09:13:0326 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
22:09:13:0743 FuEngine             failed to add device usb:01:00:09: failed to get firmware version: failed to reply: transfer failed
22:09:16:0643 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
S'estĆ  carregant...      [***************************************]
S'estĆ  descomprimint...  [***************************************]
No supported devices found

Second command output:

goodixmoc.quirk
[USB\VID_27C6&PID_609C]
Plugin = goodixmoc

And goodixmoc.quirk content is:

# Goodix Fingerprint sensor
[USB\VID_27C6&PID_60A2]
Plugin = goodixmoc
[USB\VID_27C6&PID_6384]
Plugin = goodixmoc
[USB\VID_27C6&PID_639C]
Plugin = goodixmoc
[USB\VID_27C6&PID_63AC]
Plugin = goodixmoc
[USB\VID_27C6&PID_6594]
Plugin = goodixmoc
[USB\VID_27C6&PID_6496]
Plugin = goodixmoc
[USB\VID_27C6&PID_609C]
Plugin = goodixmoc
[USB\VID_27C6&PID_609C]
Plugin = goodixmoc
[USB\VID_27C6&PID_609C]
Plugin = goodixmoc
1 Like

Even I saw (you can check) a lot of errors, this time the fingerprint was able to be used by the ā€œActivitiesā€->ā€œUsersā€->ā€œEnable fingerprint to log inā€.

I could register 5 of them and then I got a message that this device was being requested by another process. Then an OS error dialog was suggesting me to send info about the crash, I did.

I logged out and I could log in via fingerprint, so Iā€™d say this works :slight_smile:

Thanks for your support!

2 Likes

:white_check_mark: Done, still getting same error & state.

Using the approach found here, did you try reinstalling the cab?

sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab

I have updated the echo to quirks command for those who inadvertently ran it multiple times, thus, spamming the quirks file.

file="/usr/share/fwupd/quirks.d/goodixmoc.quirk"; sudo sed -i '/\[USB\\VID_27C6&PID_609C\]/d' "$file"; sudo sed -i '/Plugin = goodixmoc/d' "$file"; echo -e '[USB\VID_27C6&PID_609C]\nPlugin = goodixmoc' | sudo tee -a "$file" > /dev/null

The above command will put your quirks file to the correct state and deletes anything in that file at all, putting it to the correct state with an empty space, then the two correct lines only - this for those of you on Ubuntu and those with your fwupdmgr --version is older than 1.8.8.

If you suspect youā€™ve run into this, run the above command to correct the quirks file, then reboot, then run

sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab

Reboot

After the first time I tried to install the firmware with the sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab command, I got the transfer error, and when I checked the version it still said that there was no device found. But inmediatly trying a second time (without restarting or using another line) it completed succesfully and when I checked the version got the correct version.

After that I restarted and the fingerprint reader is now working correctly!

Okay folks, I have news on this front (good news) here soon, so watch this forum as I will be linking to the new post.

If you are have not been able to update your reader yet, please see this post.

1 Like

@Matt_Hartley Oy vey! Ran the updated quirks file replacement command (and confirmed with cat after), and also re-installed the cab file. Reboot. Still no dice.

With the update essentially do the same thing, or will that have additional pieces that may solve my issues?

Does the placement of the cab file matter? If so, is there a particular location that youā€™d recommend?

Boy, at this point as we cannot replicate this failure for it cooperating, Iā€™d try the above linked beta for LVFS.

Hi @Matt_Hartley,

Been waiting for a fix for while. Thanks for all your efforts. So Iā€™ve tried following the steps for LVFS and manual update but my Goodix reader is no longer recognised. Never tried a fw update before and never booted Windows. Yes, tried rebooting - but no joy. Any next step troubleshooting ideas??? (Yes was recognised previously and not opened the 13th gen DIY body since).

sudo fwupdtool get-devices --plugins goodixmoc                                                                   23:52:36
Loadingā€¦                 [***************************************]
No detected devices

Did you reboot afterwards and this was with a 13th Gen Intel Framework?

Thanks - a Goodix device doesnā€™t even show up in fwupdmgr get-devices, before or after reboot so thereā€™s nothing for the fw fix to updateā€¦ And yes, 13th Gen Intel DIY, UK, arrived in June I think.

Goodix info was previously obtained here back in July. (Not opened the laptop since): [TRACKING] Fingerprint reader failing to register on 13th gen - #86 by Garfo

UPDATE

Thanks to Juan_Andres instructions here I managed to get it to finally work ([TRACKING] Fingerprint reader failing to register on 13th gen - #165 by juan_andres). <3

TBH feels like youā€™re shooting in the dark as the feedback from the terminal leads you to beleive that devices are either 1). Not available (when in fact they are!), and 2). Devices are not applying the update (when in fact they are!!). Frankly bonkers - but for those reading this - pls donā€™t give up and perservere even with eyes closed!.. :slight_smile: (Hopefully Framework can make this process feedback a little more intuative and friendly in time, and/or choose a better, and quite reasonably - less buggy, fingerprint hardware vendorā€¦ And then give the old proverbial ā€œFingerā€ to good-ole Goodix!). :wink:

1 Like

Does it show up in lsusb?

lsusb | grep Goodix

I donā€™t know too much about computers in general so it was hard to tell if there is a fix for the fingerprint reader on ubuntu. Can someone help me please?
Thank you!