GTR9 Pro fingerprint reader now works on Linux (open driver)

OMGrant · 2026-07-16T03:16:55+00:00

The GTR9 Pro ships an EgisTec EH577 fingerprint reader (1c7a:0577) that, until now, only worked with Windows Hello. I wrote an open Linux driver for it. It enrolls, verifies, and unlocks KDE on the real sensor. Why it needed a custom driver: the sensor is tiny, 70×57 pixels. libfprint’s built-in matcher does a poor job on an image that small, and generic approaches (phase correlation, SIFT-based matching) hit a false-accept wall at that scale. So instead of matching in the open-source stack, the driver reuses EgisTec’s own matching engine, the one from their signed Windows driver, and runs it natively on Linux. A couple of things people usually ask about: It runs under fprintd’s normal hardening. No disabling MemoryDenyWriteExecute, and it stays inside SELinux confinement (no execmem). You don’t have to loosen anything. It contains no proprietary binaries. You fetch EgisTec’s engine DLL from the Microsoft Update Catalog through the build script and the build adapts it locally, same idea as the ttf-mscorefonts-installer package. The driver code is LGPL-2.1. Setup is one script, bash setup.sh, which clones and builds everything; uninstall is fully reversible. Repo: github.com/OMGrant/eh577-libfprint

Achimd1

Hi Ian,
I tried Step 1 and get this:

❯ sudo pacman -Rns libfprint [sudo]
Password for achimd:
Dependencies are being checked…
Error: Operation could not be prepared (Cannot fulfill dependencies)
:: Removing libfprint violates dependency »libfprint«, required by fprintd
:: Removing libfprint violates dependency »libfprint-2.so=2-64«, required by fprintd
~ ❯

Maybe i have to use this: sudo pacman -Rcns libfprint ?

Beelink CS-Ian Chan

Achimd1 Hi , There
You are correct.
sudo pacman -Rns libfprint fails because the official fprintd package depends on the system libfprint library.

Please run this command to remove libfprint together with dependent packages:

sudo pacman -Rcns libfprint

Warning: This operation will remove the official fprintd service, which is mandatory before compiling our custom eh577-libfprint driver.
After the uninstallation finishes, continue all remaining steps starting from Step 2.

Achimd1

Hi Ian,
in Step 3 i use: sudo udevadm control -–reload-rules

And Step 1-4 works.

After reboot:
cd eh577-libfprint
~/eh577-libfprint main

Terminal 1 show me this: ❯ sudo systemctl stop fprintd
[sudo] Passwort für achimd:
Failed to stop fprintd.service: Unit fprintd.service not loaded.

What now?

Beelink CS-Ian Chan

Achimd1
Hi Achimd1,
This error is completely normal and not a problem.
We have already removed the official fprintd package in Step1, so there is no fprintd.service installed on your system. The command to stop the service will naturally report that the unit cannot be found, you can safely ignore this message.

Please skip the sudo systemctl stop fprintd command and directly launch fprintd in verbose mode:

sudo fprintd -v

Leave this Terminal 1 window open, then open Terminal 2 and run:

fprintd-list $USER

Share the full log output from Terminal 1 so we can check whether the EH577 fingerprint sensor is initialized correctly.

If the debug test works fine later, you can still create the custom fprintd-auto.service to auto-start fprintd after boot.

Achimd1

Hi Ian,
Terminal 1 show me this:

❯ cd eh577-libfprint

~/eh577-libfprint main
❯ sudo fprintd -v
[sudo] Passwort für achimd:
sudo: fprintd: Befehl nicht gefunden

~/eh577-libfprint main

Achimd1

Hi Ian,
this is what i find out:
don’t use “sudo fprint -v”

Terminal 1 i use:
❯ sudo systemctl restart fprintd

and then i checked the status of fprintd:
❯ sudo systemctl status fprintd
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
Active: active (running) since Sun 2026-08-16 17:52:11 CEST; 20s ago
Invocation: aceae2f261634f769bae9878bb256e3d
Docs: man:fprintd(1)
Main PID: 3643 (fprintd)
Tasks: 6 (limit: 76641)
Memory: 5.9M (peak: 6.7M)
CPU: 42ms
CGroup: /system.slice/fprintd.service
└─3643 /usr/lib/fprintd

Aug 16 17:52:10 cachyos-x8664 systemd[1]: Starting Fingerprint Authentication Daemon…
Aug 16 17:52:11 cachyos-x8664 systemd[1]: Started Fingerprint Authentication Daemon.

After that i opened a second Terminal and leaved the first one open.

In Terminal 2 i run:
❯ fprintd-list achimd
No devices available

Beelink CS-Ian Chan

Achimd1
Hi , There
Now I can clearly identify the root cause of your issue:
You reinstalled the official fprintd and system libfprint packages after running sudo pacman -Rcns libfprint.
This creates a fatal conflict:

After removing official libfprint + fprintd, the custom compiled eh577-libfprint should provide the fprintd binary.
If you reinstall the official fprintd from repository, the original system library takes priority. Our custom driver for EH577 fingerprint sensor will not be loaded, resulting in No devices available.
The error sudo: fprintd: Befehl nicht gefunden means the custom compiled fprintd binary was not correctly installed to your system PATH after compilation.

Please strictly follow this new full cleanup workflow step by step, do not skip any operation:

Step 1 Completely remove official fingerprint packages again

sudo pacman -Rcns libfprint fprintd

Confirm removal when prompted. This fully erases stock fprint services and libraries.

Step 2 Clean old compiled files and recompile the driver

cd ~/eh577-libfprint
bash setup.sh clean
bash setup.sh

Watch the terminal log carefully during compilation:
Verify the EgisTec firmware DLL downloads successfully without network errors. Missing firmware is another common reason the sensor fails to initialize.

Step3 Verify if fprintd binary is installed globally

After compilation finishes, run:

which fprintd

If this returns empty output, the compilation script failed to copy the binary into /usr/bin.
If missing, manually install it (adjust path if needed):

sudo cp ./build/src/fprintd /usr/bin/

Step4 Recreate Udev rule

sudo mkdir -p /etc/udev/rules.d
echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="1c7a", ATTRS{idProduct}=="0577", MODE="0664", GROUP="input", TAG+="systemd"' | sudo tee /etc/udev/rules.d/60-egis-eh577.rules
sudo udevadm control --reload-rules
sudo udevadm trigger

Step5 Permission setup & full reboot

sudo usermod -aG input $USER
sudo reboot

Step6 Debug test after reboot

Do NOT run systemctl restart fprintd at this stage, the official service is uninstalled.
Terminal 1:

sudo fprintd -v

Keep this terminal running.

Open Terminal 2:

fprintd-list $USER

If you still get No devices available, share the complete verbose log output from Terminal 1.

Important Reminder

Never install official libfprint or fprintd from Pacman/AUR while using this EH577 driver. These packages conflict directly and block the custom fingerprint backend.

Achimd1

Hi Ian,
it’s now stuck in step 3:

❯ sudo pacman -Rcns libfprint fprintd
[sudo] Passwort für achimd:
Fehler: Ziel nicht gefunden: libfprint
Fehler: Ziel nicht gefunden: fprintd

~
❯ cd ~/eh577-libfprint

~/eh577-libfprint main

❯ bash setup.sh clean

EH577 fingerprint driver — build & install
Fetches the EgisTec EH577 driver from Microsoft’s official Update Catalog
(your own licensed copy) and builds a native Linux driver around its matcher.

No EgisTec code is bundled or redistributed by this project.

Do you own an EH577 (1c7a:0577) device and want to proceed? [y/N] y
==> checking prerequisites
==> [¼] downloading the vendor matcher from Microsoft Update Catalog
==> resolving download URL from Microsoft Update Catalog (updateID 3b1a2465-bcea-430a-9da5-88f690ff39b1)
https://catalog.s.download.windowsupdate.com/c/msdownload/update/driver/drvs/2019/01/e87e1b0b-7dbc-4414-bfc0-e943862c7164_dd784a9bddcf1302c6a73b11e56f6b7449fc48d8.cab
==> downloading the driver package (.cab) from Microsoft
==> extracting EgisTouchFPEngine0577.dll
==> verifying checksum (must match the pinned official copy)
OK: wrote windows-driver/EgisTouchFPEngine0577.dll (411112 bytes, sha256 verified against the pinned official package)
==> [2/4] building the matcher engine (.so) from your downloaded copy
[gen] WARN patch rva 0×1a80e: unexpected bytes 00 90
[gen] WARN patch rva 0×1a821: unexpected bytes 89 4c
[gen] wrote egimage.bin: 442368 bytes (sizeofimage), hdrsize=1024 nsec=6
built eh577-engine.so (556560 bytes)

INSTALL (root): place the .so where fprintd can reach it and LABEL it a shared library
install -Dm0755 eh577-engine.so /usr/lib/libfprint-2/eh577-engine.so
semanage fcontext -a -t textrel_shlib_t ‘/usr/lib/libfprint-2/eh577-engine.so’
restorecon -v /usr/lib/libfprint-2/eh577-engine.so
The eh577 libfprint driver dlopen()s this .so instead of memfd-loading the PE.
==> [¾] building libfprint + the eh577 driver (side-by-side; distro libfprint untouched)
==> installing driver files into the tree
==> registering the driver in meson
eh577 already present
==> configuring + building (only the eh577 driver)

~/eh577-libfprint main 9s

❯ bash setup.sh

EH577 fingerprint driver — build & install
Fetches the EgisTec EH577 driver from Microsoft’s official Update Catalog
(your own licensed copy) and builds a native Linux driver around its matcher.

No EgisTec code is bundled or redistributed by this project.

~/eh577-libfprint main 7s
❯ which fprintd
which: no fprintd in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)

~/eh577-libfprint main
❯ sudo cp ./build/src/fprintd /usr/bin/
cp: der Aufruf von stat für ‘./build/src/fprintd’ ist nicht möglich: Datei oder Verzeichnis nicht gefunden

~/eh577-libfprint main
❯

Beelink CS-Ian Chan

Achimd1
Hi , There
Thanks for the update .
Please follow these steps ;

Step 1: Fully Clean Old Build Cache

cd ~/eh577-libfprint
bash setup.sh clean
rm -rf build/
rm -rf subprojects/libfprint/build/

Step 2: Inspect the Actual Build Logic in setup.sh

cat setup.sh

Pay close attention to Step 3 where meson/ninja is invoked, and confirm whether fprintd is included in the build targets.

Step 3: Run Meson Configuration Manually to Reveal Full Error Output

cd ~/eh577-libfprint

# Check if a subprojects directory exists
ls -la subprojects/ 2>/dev/null
ls -la subprojects/libfprint/ 2>/dev/null

If subprojects/libfprint/ exists:

cd ~/eh577-libfprint/subprojects/libfprint
meson setup build --prefix=/usr
ninja -C build

If building from the project root:

cd ~/eh577-libfprint
meson setup build --prefix=/usr
ninja -C build

This step will expose the actual compilation errors (missing dependencies, syntax errors, etc.). Please share the complete output.

Step 4: Locate the Actual fprintd Output Path

After a successful build, do not assume the path is ./build/src/fprintd. Use find to locate it:

cd ~/eh577-libfprint
find . -name "fprintd" -type f -executable 2>/dev/null
find . -name "fprintd" -type f 2>/dev/null

Common paths may include:

./build/src/fprintd
./subprojects/libfprint/build/src/fprintd
./build/subprojects/libfprint/src/fprintd

Step 5: Install the fprintd Binary

Once located, copy it to the system path:

sudo cp <actual fprintd path> /usr/bin/fprintd
sudo chmod +x /usr/bin/fprintd
which fprintd

Step 6: Verify the Driver Library Is Installed

ls -la /usr/lib/libfprint-2/eh577-engine.so
ls -la /usr/lib/libfprint-2/ | grep eh577

Step 7: Recreate the Udev Rule and Reboot

echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="1c7a", ATTRS{idProduct}=="0577", MODE="0664", GROUP="input", TAG+="systemd"' | sudo tee /etc/udev/rules.d/60-egis-eh577.rules
sudo udevadm control --reload-rules
sudo udevadm trigger
sudo usermod -aG input $USER
sudo reboot

Step 8: Debug Test After Reboot

Terminal 1 — Run fprintd in foreground with verbose logging:

sudo fprintd -v

Terminal 2 — List enrolled devices:

fprintd-list $USER

Achimd1

Beelink CS-Ian Chan
Hi Ian,
Step 1:
❯ cd eh577-libfprint

~/eh577-libfprint main

❯ bash setup.sh clean

EH577 fingerprint driver — build & install
Fetches the EgisTec EH577 driver from Microsoft’s official Update Catalog
(your own licensed copy) and builds a native Linux driver around its matcher.

No EgisTec code is bundled or redistributed by this project.

~/eh577-libfprint main
❯ rm -rf buld/

~/eh577-libfprint main
❯ rm -rf subprojects/libfprint/build/

~/eh577-libfprint main

Step 2:
❯ cat setup.sh
#!/usr/bin/env bash

setup.sh — one-command build & install of the native EH577 fingerprint driver.

This downloads YOUR OWN copy of the EgisTec EH577 driver from Microsoft’s official

Update Catalog, builds a native libfprint driver around its matcher engine, and

installs it. This project bundles and redistributes ZERO EgisTec bytes — each run

fetches the vendor matcher from Microsoft on your machine (the same model Debian’s

ttf-mscorefonts-installer uses). You must OWN an EgisTec EH577 (USB 1c7a:0577)

fingerprint sensor; the driver is licensed for use on that device.

set -euo pipefail
cd “$(dirname ”$0″)"

echo “==============================================================================”
echo “ EH577 fingerprint driver — build & install”
echo “ Fetches the EgisTec EH577 driver from Microsoft’s official Update Catalog”
echo “ (your own licensed copy) and builds a native Linux driver around its matcher.”
echo “ No EgisTec code is bundled or redistributed by this project.”
echo “==============================================================================”
read -r -p “Do you own an EH577 (1c7a:0577) device and want to proceed? [y/N] ” a
[ “$a” = y ] [ “$a” = Y ] { echo “aborted.”; exit 1; }

echo “==> checking prerequisites”
miss=""
for t in curl 7z gcc meson ninja git sha256sum; do command -v “$t” >/dev/null || miss=“$miss $t”; done
if [ -n “$miss” ]; then
echo “!! missing tools:$miss”
echo “ Fedora: sudo dnf install -y curl p7zip meson ninja-build git gcc dnf-plugins-core && sudo dnf builddep -y libfprint”
echo “ (Debian/Ubuntu: apt install curl p7zip-full meson ninja-build git build-essential; apt build-dep libfprint)”
exit 1
fi

echo “==> [¼] downloading the vendor matcher from Microsoft Update Catalog”
bash fetch-engine-dll.sh windows-driver/EgisTouchFPEngine0577.dll

echo “==> [2/4] building the matcher engine (.so) from your downloaded copy”
bash build-engine-so.sh windows-driver/EgisTouchFPEngine0577.dll

echo “==> [¾] building libfprint + the eh577 driver (side-by-side; distro libfprint untouched)”
bash build-eh577.sh

echo “==> [4/4] installing (needs sudo; SELinux stays enforcing, fprintd stays confined)”
sudo bash eh577-install.sh

cat <<‘DONE’

Done. Next:
fprintd-enroll # enroll a finger (sustained hold _15s)
fprintd-verify # verify (brief hold)
sudo authselect enable-feature with-fingerprint # add fingerprint to login (password still works)

Uninstall: sudo bash eh577-install.sh –uninstall
DONE

~/eh577-libfprint main

Then i run meson configuration manually:
❯ sudo pacman -S –needed git base-devel meson ninja pkgconf \
glib2 libgusb opencv openssl fprintd imagemagick
[sudo] Passwort für achimd:
Warnung: git-2.55.0-1.1 ist aktuell – Überspringe
Warnung: base-devel-1-2 ist aktuell – Überspringe
Warnung: meson-1.12.0-1 ist aktuell – Überspringe
Warnung: ninja-1.13.2-3.1 ist aktuell – Überspringe
Warnung: pkgconf-3.0.5-1.1 ist aktuell – Überspringe
Warnung: glib2-2.88.3-1.1 ist aktuell – Überspringe
Warnung: libgusb-0.4.9-2.1 ist aktuell – Überspringe
Warnung: opencv-5.0.0-9.1 ist aktuell – Überspringe
Warnung: openssl-3.6.3-1.1 ist aktuell – Überspringe
Warnung: fprintd-1.94.5-2.1 ist aktuell – Überspringe
Warnung: imagemagick-7.1.2.29-2.1 ist aktuell – Überspringe
Es gibt nichts zu tun

~/eh577-libfprint main

Step 3:
❯ ls -la subprojects/ 2>/dev/null

~/eh577-libfprint main
❯ ls -la subprojects/libfprint/ 2>/dev/null

~/eh577-libfprint main

No Subprojects are existing?

Beelink CS-Ian Chan

Achimd1 Hi , There
Hi Achimd1,

The root cause is clear now:

You reinstalled official fprintd package via pacman -S … fprintd, which conflicts with this custom driver.
Your repo misses git submodule libfprint, subprojects/ folder is empty. The build‑engine‑so.sh succeeds (eh577‑engine.so built fine), but libfprint and fprintd binary are never compiled. That’s why which fprintd returns nothing.
Typo rm -rf buld/ also left old build cache.

Please follow these steps strictly:

Step0 Remove official fingerprint stack completely

sudo pacman -Rcns libfprint fprintd

Do NOT install fprintd from pacman/AUR later.

Step1 Re‑clone repo with submodules

rm -rf ~/eh577-libfprint
git clone --recurse-submodules https://github.com/xxx/eh577-libfprint.git ~/eh577-libfprint
cd ~/eh577-libfprint
ls -la subprojects/

Now subprojects/libfprint/ should exist.

Step2 Full clean & rebuild

bash setup.sh clean
bash setup.sh

Step3 Locate & install fprintd binary

find . -name "fprintd" -type f -executable
sudo cp ./build/subprojects/libfprint/src/fprintd /usr/bin/fprintd
sudo chmod +x /usr/bin/fprintd
which fprintd

Must return /usr/bin/fprintd.

Step4 Udev rule & permissions

sudo mkdir -p /etc/udev/rules.d
echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="1c7a", ATTRS{idProduct}=="0577", MODE="0664", GROUP="input", TAG+="systemd"' | sudo tee /etc/udev/rules.d/60-egis-eh577.rules
sudo udevadm control --reload-rules
sudo udevadm trigger
sudo usermod -aG input $USER

Step5 Full reboot

sudo reboot

Step6 Debug test after reboot
Terminal 1:

sudo fprintd -v

Keep this terminal open.

Terminal 2:

fprintd-list $USER

If you still get No devices available, share the full verbose log from Terminal1.

Note: Those [gen] WARN patch rva warnings are expected, they are not build errors.
Do not run systemctl start fprintd (official package is removed). Only use foreground sudo fprintd -v for debugging.
Once debug works, you can deploy the custom fprintd-auto.service for auto‑start on boot.

Achimd1

Beelink CS-Ian Chan
Hi Ian,
thank you so much for your understnading and your help!!!
this is what i did now:

sudo pacman -Rcns libfprint fprintd
[sudo] Passwort für achimd:
Abhängigkeiten werden geprüft …

Paket (2) Alte Version Netto-Veränderung

fprintd 1.94.5-2.1 -0,94 MiB
libfprint 1.94.100-1.1 -2,27 MiB

Gesamtgröße der entfernten Pakete: 3,20 MiB

:: Möchten Sie diese Pakete entfernen? [J/n] J
:: Pre-transaction-Hooks werden gestartet …
(1/1) Performing snapper pre snapshots for the following configurations…
==> root: 201
:: Paketänderungen werden verarbeitet …
(½) Entfernung läuft fprintd [——————————–] 100%
(2/2) Entfernung läuft libfprint [——————————–] 100%
:: Post-transaction-Hooks werden gestartet …
(⅙) Updating udev hardware database…
(2/6) Reloading system manager configuration…
(3/6) Reloading device manager configuration…
(4/6) Arming ConditionNeedsUpdate…
(⅚) Reloading system bus configuration…
(6/6) Performing snapper post snapshots for the following configurations…
==> root: 202

~ 11s
❯ rm -rf ~/eh577-libfprint

~
❯ git clone –recurse-submodules https://github.com/xxx/eh577-libfprint.git ~/eh577-libfprint
Klone nach ‘/home/achimd/eh577-libfprint’…
Username for ‘https://github.com’:

What is the passwor?
I don’t have one!

Achimd1

Hello Ian,
Its O.K. now, i solved my password trouble, i try now the next steps!

Beelink CS-Ian Chan

Achimd1
Hi , There

Thanks for your efforts. Please keep us posted.

Achimd1

Beelink CS-Ian Chan

Hi Ian,
iit stucks at Step 1 here:

❯ cd ~/eh577-libfprint

~/eh577-libfprint main
❯ ls -la subprojects/
“subprojects/”: No such file or directory (os error 2)

~/eh577-libfprint main
❯

Beelink CS-Ian Chan

Achimd1
Hi , There

Root cause

Even though you used --recurse‑submodules during git clone, GitHub HTTPS triggered an authentication prompt and interrupted submodule download.
The main repository finished downloading, but the libfprint submodule was never fetched. So the whole subprojects directory was not created.
The eh577‑engine.so might build fine, but without libfprint source under subprojects you cannot compile the custom fprintd binary.

Fix Option A — Repair existing repo (no re‑clone)

cd ~/eh577-libfprint
ls -la .gitmodules

# Initialize and fetch missing submodules
git submodule update --init --recursive

After it completes, verify the folder exists:

ls -la subprojects/

You should now see subprojects/libfprint.

If you still get GitHub username/password pop‑ups, your network has HTTPS access issues with GitHub. Use Option B instead.

Fix Option B — Full clean re‑clone (recommended)

rm -rf ~/eh577-libfprint
git clone --recurse-submodules https://github.com/OMGrant/eh577-libfprint.git ~/eh577-libfprint
cd ~/eh577-libfprint
ls -la subprojects/

If you see a GitHub login prompt again, press Ctrl+C immediately — public repos do not require credentials; the prompt indicates network interception.

Verify submodule status

git submodule status

A leading - symbol = submodule not checked out (failed).
No leading - = submodule successfully checked out.

Continue with original guide after submodules work

bash setup.sh clean
bash setup.sh

# Locate your custom built fprintd binary
find . -name "fprintd" -type f -executable

Copy this binary to /usr/bin, install udev rules and reboot for testing.

Important notes

Do NOT install distro packages sudo pacman -S fprintd libfprint. System‑provided packages will overwrite your custom driver and result in No devices available.
SELinux warnings like [gen] WARN patch rva 0x1a80e are normal debug output, not build errors and can be safely ignored.
Do not start the systemd fprintd.service. Debug manually in foreground with sudo fprintd -v.

Troubleshooting if git submodules keep failing

Ensure your git version is up‑to‑date.
HTTPS connections to GitHub may be blocked; you may need git proxy settings.
Public repositories over HTTPS do not need login credentials. Any password prompt means network interference.

Achimd1

Beelink CS-Ian Chan
Hi Ian,
Fix Option A: no success

~/eh577-libfprint main
❯ ls -la .gitmodules
“.gitmodules”: No such file or directory (os error 2)

Fix Option B: no success

❯ rm -rf ~/eh577-libfprint

~
❯ git clone –recurse-submodules https://github.com/OMGrant/eh577-libfprint.git ~/eh577-libfprint
Klone nach ‘/home/achimd/eh577-libfprint’…
remote: Enumerating objects: 114, done.
remote: Counting objects: 100% (114/114), done.
remote: Compressing objects: 100% (85/85), done.
remote: Total 114 (delta 56), reused 83 (delta 28), pack-reused 0 (from 0)
Empfange Objekte: 100% (114/114), 622.73 KiB | 11.12 MiB/s, fertig.
Löse Unterschiede auf: 100% (56/56), fertig.

~
❯ cd eh577-libfprint

~/eh577-libfprint main
❯ ls -la subprojects/
“subprojects/”: No such file or directory (os error 2)

No distro packages installed

git version 2.55.

It seems to be very difficult to install the driver and thus get it working…

Beelink CS-Ian Chan

Achimd1
Hi , There

The issue you are seeing is caused by a copy‑paste character error. In your git clone command you used a Unicode long dash – instead of the standard ASCII double dash --. Git ignored the --recurse‑submodules parameter, so the required subprojects folder and .gitmodules files were never downloaded. Your git version 2.55 itself is fine.

Please run these exact commands in your terminal (all dashes are standard ASCII):

# Clean up old broken repository
rm -rf ~/eh577-libfprint

# Clone repository with correct submodule flag
git clone --recurse-submodules https://github.com/OMGrant/eh577-libfprint.git ~/eh577-libfprint

cd ~/eh577-libfprint

# Double‑initialize submodules as safety fallback
git submodule update --init --recursive

# Verify subprojects folder exists
ls -la subprojects/

Install build dependencies

For Arch / CachyOS

sudo pacman -S meson ninja libfprint git libusb

For Ubuntu 24.04 / 26.04

sudo apt update
sudo apt install meson ninja-build libfprint-2-dev git libusb-1.0-0-dev

Compile & install the driver

cd ~/eh577-libfprint
meson setup build
ninja -C build
sudo ninja -C build install

Apply udev rules and restart fingerprint service

sudo udevadm control --reload-rules
sudo udevadm trigger
systemctl restart fprintd

Important: After finishing above steps, log out and log back in (a full reboot is also acceptable). Simply restarting the fprintd service is sometimes not enough.

Check if fingerprint device is detected:

fprintd-list $(whoami)

You should now see the fingerprint enrolment option inside your desktop settings.

You can also confirm hardware ID with lsusb, the EH577 fingerprint reader should show 2c7c:0577.

If you still encounter problems, please share output of lsusb and terminal error messages.

Best regards,

Achimd1

Hell Ian,
it’s the same before, no submodules:

❯ rm -rf ~/eh577-libfprint

~
❯ git clone –recurse-submodules https://github.com/OMGrant/eh577-libfprint.git ~/eh577-libfprint
Klone nach ‘/home/achimd/eh577-libfprint’…
remote: Enumerating objects: 114, done.
remote: Counting objects: 100% (114/114), done.
remote: Compressing objects: 100% (85/85), done.
remote: Total 114 (delta 56), reused 83 (delta 28), pack-reused 0 (from 0)
Empfange Objekte: 100% (114/114), 622.73 KiB | 5.32 MiB/s, fertig.
Löse Unterschiede auf: 100% (56/56), fertig.

~
❯ cd ~/eh577-libfprint

~/eh577-libfprint main
❯ git submodule update –init –recursive

~/eh577-libfprint main
❯ ls -la subprojects/
“subprojects/”: No such file or directory (os error 2)

No succes.

Beelink CS-Ian Chan

Achimd1 Hi Achim,

The repository structure has been updated recently, and it no longer uses git submodules or the subprojects/ directory mentioned in the older guide. That’s why ls -la subprojects/ returns “No such file or directory”.
You can skip all manual git submodule commands and use the built-in setup.sh script to handle dependencies and building automatically.

Please run these commands step by step:

# Remove old folder
rm -rf ~/eh577-libfprint

# Clone source code
git clone https://github.com/OMGrant/eh577-libfprint.git ~/eh577-libfprint
cd ~/eh577-libfprint

# Clean old build files and start automatic build
bash setup.sh clean
bash setup.sh

Full workflow including dependencies, udev rules and service setup (Arch / CachyOS)

# Install required build packages
sudo pacman -S --needed git base-devel meson ninja pkgconf glib2 libgusb opencv openssl fprintd imagemagick

rm -rf ~/eh577-libfprint
git clone https://github.com/OMGrant/eh577-libfprint.git ~/eh577-libfprint
cd ~/eh577-libfprint

bash setup.sh clean
bash setup.sh

# Create udev rule for EH577 fingerprint reader
sudo tee /etc/udev/rules.d/60-egis-eh577.rules <<'EOF'
SUBSYSTEM=="usb", ATTRS{idVendor}=="1c7a", ATTRS{idProduct}=="0577", MODE="0664", GROUP="input", TAG+="systemd"
EOF
sudo udevadm control --reload-rules
sudo udevadm trigger

# Add current user to input group
sudo usermod -aG input $USER

# Restart fingerprint service
sudo systemctl enable --now fprintd
sudo systemctl restart fprintd

Verification commands

lsusb | grep 1c7a:0577
fprintd-list $USER

If fprintd-list detects the EH577 device, you can enroll fingerprints with fprintd-enroll.

Troubleshooting tip

If the device is still not recognized, stop the service and run fprintd in verbose debug mode to check detailed logs:

sudo systemctl stop fprintd
sudo fprintd -v

Also, remove the default system libfprint package if you encounter conflicts:

sudo pacman -R libfprint

Let me know how it goes after trying this.

« Previous Page Next Page »