@Alex_K - what hardware are you installing on? Two m2 slots and an elan fingerprint reader does not sound like a framework laptop.
1 Like
Sorry guys. I came here with a wrong laptop. I have HP G9 laptop which I bough just because I wanted a single cable solution(can charge and TypeC or Thunderbol) with 2 M2 slots and I could extend RAM to 64Gb. Thats the only reasons I bough it.
@lbkNhubert Many thanks for the link. I found out that my device Bus 003 Device 004: ID 04f3:0c7e Elan Microelectronics Corp. ELAN:ARM-M4 is supported, but for some reason when I executed lsusb -v it says Couldn't open device, some information will be missing. I wonder what is so special in HP G9 Zbook Laptop so that finger print device doesn’t work in Ubuntu 22.04.1 / 22.10 & Fedora. Actually it also complaints it can’t open next Bus 003 Device 067: ID 14cd:1212 Super Top microSD card reader (SY-T18) device.
lsusb -v | grep -A110 04f3
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Bus 003 Device 004: ID 04f3:0c7e Elan Microelectronics Corp. ELAN:ARM-M4
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x04f3 Elan Microelectronics Corp.
idProduct 0x0c7e
bcdDevice 3.04
iManufacturer 1 ELAN
iProduct 2 ELAN:ARM-M4
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0053
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 8
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
** UNRECOGNIZED: 09 21 10 01 00 01 22 15 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
Couldn't open device, some information will be missing
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Bus 003 Device 067: ID 14cd:1212 Super Top microSD card reader (SY-T18)
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
@Alex_K you might have better luck w/ HP support (or their forums) or r/linuxhardware for additional help. I’m assuming you came here through an internet search, but this community forum is actually dedicated to Framework laptops. Fingerprint sensors are notorious for having poor Linux compatibility and HP often has dodgy firmware/BIOS issues with Linux so the issues you have are probably very specific to your particular laptop hardware. Good luck!
3 Likes
@lhl Sorry 3 days ago I did not know anything about framework laptops.
I went to HP but once I posted my question their bot provided some links and I find out the HP is useless for Linux. They do not do any support.
Please do a frame.work laptop with 2 or more m2 slots and I will drop HP laptop and buy yours. I really like the flexibility to have 2 M2 slots. Ideally I’d like to have 4 M2 Slots.
Appreciate the feedback, do keep us in mind in the future - we’re always evolving! 
(Marking resolved as our guides indicate which distro provide fingerprint support)
2 Likes
Hello! Im on Fedora 37 (fully updated) with my i1240p Framework, and my Fingerprintreader has stoped working. Cant find the goodixmoc device in lsusb. I reinstalled fprintd and did some reboots. I also deactivated the Fingerprintreader and reactivated it in Bios with no success. I tried the fprint-clear-storage app from this thread, but because there is no goodixmoc device, it cant clear the storage, which isnt the problem anyways.
I dont think my device is blacklisted, the output of the modprobe.d directory is as follows:
modprobe.d
appletalk-blacklist.conf
atm-blacklist.conf
ax25-blacklist.conf
batman-adv-blacklist.conf
firewalld-sysctls.conf
floppy-blacklist.conf
kvm.conf
l2tp_eth-blacklist.conf
l2tp_ip-blacklist.conf
l2tp_netlink-blacklist.conf
l2tp_ppp-blacklist.conf
lockd.conf
netrom-blacklist.conf
nfc-blacklist.conf
nvdimm-security.conf
rds-blacklist.conf
rose-blacklist.conf
sctp-blacklist.conf
tuned.conf
vhost.conf
Does anyone have a solution for this? Thanks!
Nothing struck me at the blacklist level. But the fact that it’s not appearing in lsusb usually means something isn’t being seen at a hardware level.
Obviously I wouldn’t suggest trying to configure the fingerprint reader from a live USB, I would suggest trying to lsusb from the LiveUSB. While we cannot use the reader from this state, if it shows up under lsusb, then that tells us this isn’t hardware.
1 Like
Thanks for looking into this!
As you can see, lsusb gives me in both cases the same output.
So i should consult the support team, because it looks like a hardware fault?
Fedora LiveUSB
6.0.7-301.fc37.x86_64
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 007: ID 2109:8888 VIA Labs, Inc. USB Billboard Device
Bus 003 Device 008: ID 0424:3fb7 Microchip Technology, Inc. (formerly SMSC) Babyface (23368007)
Bus 003 Device 005: ID 1a40:0801 Terminus Technology Inc. USB 2.0 Hub
Bus 003 Device 010: ID 05ac:0250 Apple, Inc. Aluminium Keyboard (ISO)
Bus 003 Device 009: ID 046d:c332 Logitech, Inc. G502 Proteus Spectrum Optical Mouse
Bus 003 Device 006: ID 046d:c077 Logitech, Inc. Mouse
Bus 003 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 003 Device 011: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer
Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 003: ID 0781:558c SanDisk Corp. Extreme Portable SSD
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Fedora Install
6.1.12-200.fc37.x86_64
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 007: ID 2109:8888 VIA Labs, Inc. USB Billboard Device
Bus 003 Device 008: ID 0424:3fb7 Microchip Technology, Inc. (formerly SMSC) Babyface (23368007)
Bus 003 Device 005: ID 1a40:0801 Terminus Technology Inc. USB 2.0 Hub
Bus 003 Device 010: ID 05ac:0250 Apple, Inc. Aluminium Keyboard (ISO)
Bus 003 Device 009: ID 046d:c332 Logitech, Inc. G502 Proteus Spectrum Optical Mouse
Bus 003 Device 006: ID 046d:c077 Logitech, Inc. Mouse
Bus 003 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 003 Device 011: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer
Bus 002 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 005: ID 0781:558c SanDisk Corp. Extreme Portable SSD
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
No problem, happy to help. Doesn’t look like we’re seeing Shenzhen Goodix Technology Co.,Ltd. Goodix anywhere. To save you some steps in the upcoming ticket, do the following now and let support know you’ve done this:
-
Disconnect everything that is not power from the laptop, re-run the commands in the Live Fedora USB. We both know it won’t matter, but it will be asked. Make a note that Shenzhen Goodix Technology Co.,Ltd. Goodix is still not showing up.
-
Open the laptop, double check the connection to the webcam is sound. You can use step 8 in this guide for this. Webcam Replacement Guide - Framework Guides
Then with these things done, open a ticket, link to this post and let support know the Linux lead said this is not a Linux issue and appears to be an issue the camera itself as you’ve checked he connection. They may want photos of the connection.
1 Like
Thank you, will do that!
Just for reference, its about the Fingerprint Scanner and not the Webcam. I will check the connection to the Fingerprint Reader with this Framework Guide for Fingerprint Reader and make a photo like in step 6.
Sounds good.
Is anyone on NixOS willing to share their configs with me? I’ve tried everything in this thread and had troubleshooting sessions with 2 different people after dedicating two weekends to it and I still am not able to get fprintd working as it should. I keep running into a package crc error every step of the way.
We do have a specific Nix related thread for questions and answers. Might be worth re-posting there as well.
Were you able to fix this I recently had the same issue and trying to find a solution to getting the keyring authenticated?
1 Like
Happy to help. Let’s take a look at some logs for any indications of what might be happening.
sudo dmesg | grep authentication
journalctl | grep authentication
sudo dmesg | grep keyring
journalctl | grep keyring
Let’s take a look at the output of those, and see what if anything stands out.
I installed Fedora 38 yesterday and the fingerprint scanner on my laptop has stopped working, running systemctl status fprintd.service gives me:
Apr 19 14:24:55 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:24:55 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:24:55 framework fprintd[28454]: Template storage appears to have been corrupted! Error was: Corrupted message header>
Apr 19 14:24:55 framework fprintd[28454]: A known reason for this to happen is a firmware bug triggered by another storage are>
Apr 19 14:24:55 framework fprintd[28454]: Resetting device storage, you will need to enroll all prints again!
Apr 19 14:24:55 framework fprintd[28454]: Reset failed: Corrupted message header received
Apr 19 14:25:00 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:25:00 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:25:00 framework fprintd[28454]: libusb: error [udev_hotplug_event] ignoring udev action change
Apr 19 14:25:30 framework systemd[1]: fprintd.service: Deactivated successfully.
fprintd-delete ends with:
failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.Internal: Open failed with error: Corrupted message header received
I have not yet found anyone else with this issue, so is it just a problem with F38 being new or did something go wrong when I upgraded from 37?
This feels like something didn’t carry over nicely from 37. Also why I always recommend a /home backup and then a clean install with any distro upgrade (unless rolling release). Early upgrades from one release to another vs clean installs tend to open up issues like this.
Please run this program, then reboot, see if the issue still happens. On a clean install, I have zero issues with the fingerprint reader .
1 Like
Thank you, the program did the trick!
2 Likes