Repository navigation
Detect the FocalTech power-button reader by vendor:product - #16228
atwardowski wants to merge 1 commit into
Conversation
The Framework Laptop 12's reader in the power button reports "FocalTech FT9769DL ESS", naming neither the function nor the vendor, and FocalTech also makes touchscreens, so the bare vendor ID cannot go in the vendor list. Pin the 2808:079a pair with the same no-kernel-driver requirement the vendor list carries, keeping a same-vendor touchscreen that binds usbhid rejected.
[Medium impact] The PR appears safe to merge. SummaryAdds detection for the Framework Laptop 12’s FocalTech fingerprint reader by its USB pair,
No actionable issues found. Tests were inspected but not run. Reviews (1) · Last reviewed commit: "Detect the FocalTech power-button reader..." · Reviewed by Greptile |
|
Thanks for tracking this down on the Framework Laptop 12, and for confirming the reader enrolls end to end once it is detected. This is one of three open pull requests fixing the same cause: FocalTech readers name neither the function nor a known vendor in their product string, and On the touchscreen concern: FocalTech's USB touch controllers bind What was checked: the diff, the detector and its tests at This waits on the maintainer, who chooses between the competing fixes. If #11387 lands, this one can be closed. |
Problem
On a Framework Laptop 12, `omarchy setup security fingerprint` reports
"No fingerprint sensor detected" even though the laptop's built-in reader
(in the power button) is present and working.
The reader enumerates as `2808:079a` with the product string
"\"FocalTech FT9769DL ESS\"" and no kernel driver bound to its
interface — the correct libusb/reader signature. It matches nothing in
`omarchy-hw-fingerprint`: the product string names neither the function
nor the vendor, and FocalTech's vendor ID is deliberately absent from the
vendor list because FocalTech also makes touchscreens.
Fix
Add a vendor:product match (`2808:079a`) in `bin/omarchy-hw-fingerprint`.
The pair is pinned rather than added to the vendor list, and it keeps the
same no-kernel-driver requirement the vendor list carries, so a same-vendor
FocalTech touchscreen that binds usbhid is still rejected.
Tests
detected, and the same pair with a kernel driver bound is rejected.
Full test file passes (25/25).
Framework Laptop 12, and the full setup wizard then enrolled, verified,
and configured PAM for the built-in reader end to end.