Also, Arch users you might still be getting bit by this fwupd 1.9.8 bug
until 1.9.9 is available, you could try temporarily downgrading to 1.9.7.
Iāve been running through the guide but I keep running into a weird bad address error. Iām working to fix the fedora 39 āfailed to claim fingerprint deviceā error
Error:
āÆ sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab
[sudo] password for josie:
Loadingā¦ [******** ]
00:28:40.482 FuEngine failed to add device /sys/devices/pci0000:00/0000:00:08.1/0000:c1:00.0: ioctl error: Bad address [14]
Decompressingā¦ [ - ]
generic GUID requires a CHID, child, parent or sibling requirement
The error even shows up when doing sudo fwupdtool get-devices
I did recheck the ram and connectors. Also tried doing this through a different bootable drive. Still need to try booting into ubuntu and running the commands there.
1 Like
Iām having the same issue as Jose_Aranguren above. Iām on Fedora 39, and Iām unable to enroll my fingerprints through the GUI or command line.
> sudo fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab
Loadingā¦ [******** ]22:54:47.724 FuEngine failed to add device /sys/devices/pci0000:00/0000:00:08.1/0000:c1:00.0: ioctl error: Bad address [14]
Decompressingā¦ [ - ]
generic GUID requires a CHID, child, parent or sibling requirement
Iām using fwupd 1.9.9, could the newer version of this be bad?
Edit: I was able to update the firmware using Ubuntu 23.10 (live USB) with fwupd 1.9.5.
Fedora users, the guide has been updated.
See the TROUBLESHOOTING fwupd is NEWER than 1.9.7 section.
Probably a dumb question, but secure boot can be turned back on after using fwupd to update the Goodix fingerprint firmware?
Iām using Ubuntu 23.10
Yes. You only need to disable it to do the update.
2 Likes
I followed the troubleshooting guide, but I still canāt get my fingerprint reader to work.
I have a 13th gen intel chip.
I just upgraded to Fedora 39 (KDE spin) today, but I never had the fingerprint reader working in 38 either, mainly because I didnāt try.
fwupd version 1.9.5-2.
I disabled Secure Boot, and I successfully got the cab file. When I run the command in step 3, I get the error
23:29:19.391 FuEngine failed to add device usb:03:00:09: failed to claim interface 0x00: USB error on device 27c6:609c : Resource busy [-6]
in the middle of a bunch of lines that say Loadingā¦
At the end it says No supported devices found.
What else can I try?
Iām having the same issue with a my laptop 13 which I just received a few days ago Iām getting:
fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Laptop (13th Gen Intel Core)
ā
āāFingerprint Sensor:
ā Device ID: 4295296d98b3ba38c72f6baa33d24f03a1d428f6
ā Summary: Match-On-Chip fingerprint sensor
ā Current version: 01000330
ā Vendor: Goodix (USB:0x27C6)
ā Install Duration: 10 seconds
ā GUIDs: 34def4c7-9461-5a32-a945-5dde0ca57d88
ā 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
ā Device Flags: ā¢ Updatable
ā ā¢ Device can recover flash failures
ā ā¢ Signed Payload
but when I do:
fwupdmgr update 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
I get:
Devices with no available firmware updates:
ā¢ Fingerprint Sensor
ā¢ UEFI dbx
No updatable devices
Iām running:
Ubuntu 22.04.3 LTS
1 Like
I think I talked to soon. All of sudden the fingerprint seems to be working now. I was able to register 2 fingers.
Not sure what is going on.
Same problem for me today.
I have the Amd version, arrived Thursday, yesterday Iāve installed Manjaro Linux with KDE Plasma.
Same error when I try to enroll with fprintd and same results with fwupdmgr.
UPDATE: After reboot, now fwupdmgr doesnāt even show the fingerprint sensor
UPDATE: Using the windows on boxes method iāve managed to revert back the firmware and solve the issue.
1 Like
If anyone is running arch just use this to downgrade the package to one that works.
pacman -U https://archive.archlinux.org/packages/f/fwupd/fwupd-1.9.6-1-x86_64.pkg.tar.zst
1 Like
Continuing the discussion from [TRACKING] Fingerprint scanner compatibility with linux (ubuntu, fedora, etc):
Hello Devyn,
Thank you for sharing this AppImage, I am experiencing issues with registering fprints and noticed this stopped working.
$ sudo ./fprint-clear-storage-0.0.1-x86_64.AppImage
** (process:74884): WARNING **: 23:11:24.039: Failed to load shared library 'libfprint-2.so.2' referenced by the typelib: /lib64/libgudev-1.0.so.0: undefined symbol: g_once_init_enter_pointer
/tmp/.mount_fprintwwEV5s//opt/fprint_clear_storage.py:7: Warning: cannot retrieve class for invalid (unclassed) type 'void'
ctx = FPrint.Context()
Traceback (most recent call last):
File "/tmp/.mount_fprintwwEV5s//opt/fprint_clear_storage.py", line 7, in <module>
ctx = FPrint.Context()
TypeError: could not get a reference to type class
I suspect the newer libraries on my system could be causing the issue:
libfprint-1.94.6:/lib64/libfprint-2.so.2libgudev-238-5:/lib64/libgudev-1.0.so.0
Aside from being inside an app image, is the script the same as the original python script?
The original Python script seemingly ran successfully and fprint shows that I have no registered fingerprints.
$ fprintd-list $USER
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User mikey has no fingers enrolled for Goodix MOC Fingerprint Sensor.
When I try to register I do not get an error, it just never completes.
Interestingly there is no error when enrolling, and am already at the correct firmware version?
fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3 | grep Current
Current version: 01000248
Edit:
Turns out there is no problem registering a fingerprint, its just that I have to keep tapping several times to train it to my finger.
Hi!
Itās been quite a long time since I worked on this. The python script is the same, but I created the AppImage because at the time libfprint didnāt have the required functionality to make this work, and I had to fork it and bundle that version with it. I believe that has been merged now, so now the python script alone should be good enough.
1 Like