### System details

Samsung Galaxy Book6 Pro NP960XJG-KG1US (PAMB), Intel Core Ultra X7 358H (Panther Lake), Omarchy 4.0.4-1, `libfprint-git 1:1.94.100.r10.g6f9479c-1`

### What's wrong?

## Summary

The power-button fingerprint reader on a Samsung Galaxy Book6 Pro is visible to USB and to `omarchy-hw-fingerprint`, but `fprintd` has no device. Omarchy's pinned `libfprint-git` ships the `egismoc` driver for other LighTuning/Egis Match-on-Chip IDs, and does **not** include this one: `1c7a:05d5` (ETU906Axx-E).

This is a missing device ID, not a detection bug. `omarchy setup security fingerprint` would get past the hardware check, then fail enrollment with "Enrollment failed. Please try again." — the same silent-driver-gap as #11841.

Related camera report on the same machine: #12347.

## Hardware / system

- Machine: Samsung Galaxy Book6 Pro — PAMB (`NP960XJG-KG1US`)
- BIOS: `PAMB.1.5.74.371` (2026-04-09)
- Reader: LighTuning / EGIS ETU906Axx-E in the power button
- USB: `Bus 003 Device 002: ID 1c7a:05d5 LighTuning Technology Inc. ETU906Axx-E`
- Product string: `ETU906Axx-E`, manufacturer `EGIS`, serial `136C51PE5B69`, `bcdDevice` 16.48
- Omarchy: `4.0.4-1`
- Kernel: `linux-omarchy 7.2.5-3`
- `libfprint-git 1:1.94.100.r10.g6f9479c-1` (already installed; Omarchy's upstream-tracking snapshot)
- `fprintd 1.94.5-2`
- PAM fingerprint is **not** configured (setup never completed)

## Symptoms

```
$ lsusb | grep 1c7a
Bus 003 Device 002: ID 1c7a:05d5 LighTuning Technology Inc. ETU906Axx-E

$ omarchy-hw-fingerprint; echo $?
0

$ fprintd-list "$USER"
No devices available
```

`60-autosuspend-libfprint-2.hwdb` lists many `1C7A` PIDs (`0582`, `0583`, `05A1`, `05A5`, `05AA`, …) but **not** `05D5`. `fprintd-enroll` therefore has nothing to talk to.

## What I tried / ruled out

- Reader is bound to no kernel driver (expected; libfprint uses libusb).
- `omarchy-hw-fingerprint` already treats vendor `1c7a` as a fingerprint reader, so Omarchy *does* see the hardware.
- Stock vs `linux-omarchy` is irrelevant; this is userspace `egismoc` ID matching.

## Root cause / known working ID add

Same laptop + same USB ID is documented as working after adding one `egismoc` table entry (TYPE2 prefix, 20 enroll stages — same flags as `05b1`):

https://github.com/dszczyt/awesome-galaxy_book6 (section 11)

```c
{ .vid = 0x1c7a, .pid = 0x05d5, .driver_data = EGISMOC_DRIVER_CHECK_PREFIX_TYPE2 | EGISMOC_DRIVER_MAX_ENROLL_STAGES_20 },
```

That matches how Omarchy already treats new readers: `omarchy-setup-security-fingerprint` comments that `libfprint-git` exists so "a new reader only needs a pin bump in omarchy-pkgs."

Caveat from other recent Egis MoC devices: some firmware wants SDCP or enrollment will appear to succeed and then vanish (#10309, libfprint SDCP work). I have **not** enrolled on this `05d5` yet because the ID is not in the shipped driver. The Book6 report above says TYPE2+20 is enough on this PID.

## Suggested fix

1. Add `1c7a:05d5` to `egismoc_id_table` (and the autosuspend hwdb) in the `libfprint-git` snapshot Omarchy ships.
2. Until then, `omarchy setup security fingerprint` should refuse with "reader present, no libfprint driver" instead of a generic enroll failure (#11841).

Happy to test a rebuilt `libfprint-git` on this machine.