And for those who haven't been reinstall more than once, what's your advice for how you be able to stay for so long without any problems?

levong@chrultrabook

-------------------

OS: Arch Linux ARM aarch64

Host: Google burnet board

Kernel: Linux 6.12.50-stb-cbm+

Uptime: 5 mins

Packages: 1081 (pacman)

Shell: zsh 5.9.2

Display (CMN1139): 1366x768 in 12", 60 Hz [Built-in]

DE: Budgie 10.10.2

WM: labwc 0.20.1 (Wayland)

Theme: Arc-Gruvbox [GTK2/3/4]

Icons: kora [GTK2/3/4]

Font: Fira Sans (11pt, SemiBold) [GTK2/3/4]

Cursor: Bibata-Modern-Ice (24px)

Terminal: kitty 0.48.0

Terminal Font: JetBrainsMonoNF-Regular (12pt)

CPU: mt8183 (8) @ 1.99 GHz

GPU: Mediatek mt8183b-mali [Integrated]

Memory: 2.61 GiB / 3.79 GiB (69%)

Swap: Disabled

Disk (/): 6.63 GiB / 28.37 GiB (23%) - btrfs

Battery (GH02047): 57% (7 hours, 45 mins remaining) [Discharging]

Locale: en_CA.UTF-8

I haven't seen anyone else do this so if you are curious here you go.

Arch with DMS QuickShell and Hyprland. I have disabled DMS internal lock screen and uses hyprlock and gaze-hyprlock. Gaze is configured to use face unlock, and it works "sort of".

The thing is that if I lock manually and looks on the screen within a couple of seconds, it unlocks. But if I wait more than, lets say 10 seconds, then I need to enter the password.

Maybe its the settings in hypridle, hyprlock or the pam module that is configured incorrectly. Maybe its my hardware, a Thinkpad X1 Carbon G9 that needs tweaking.

Anyone?

`[20:07:34] anders:~/.config/hypr % cat /etc/pam.d/hyprlock`

`# PAM configuration file for hyprlock`

`# the 'login' configuration file (see /etc/pam.d/login)`

`auth recheck` [`pam-gaze.so`](http://pam-gaze.so)

`auth sufficient` [`pam-gaze.so`](http://pam-gaze.so)

`auth include login`

`[20:11:23] anders:~/.config/hypr % cat hyprlock.conf`

`hide_cursor = true`

`general {`

`# grace = 5`

`ignore_empty_input = true`

`# skip_validation_every_key = true`

`}`

`auth {`

`pam {`

`module = hyprlock-gaze`

`}`

`}`

`[20:13:17] anders:~/.config/hypr % sudo cat /etc/gaze/config.toml`

`[security]`

`level = "medium"`

`detector = ""`

`recognizer = ""`

`threshold = 0.0`

`hybrid_policy = ""`

`[cameras]`

`rgb = "primary"`

`ir = ""`

`emitter_enabled = false`

`dark_luma_threshold = 30`

`[auth]`

`timeout = 15`

`abort_if_ssh = true`

`abort_if_lid_closed = true`

`require_confirmation = false`

`resume_grace_ms = 0`

`[enrollment]`

`max_templates = 2`

`min_face_size_ratio = 0.25`

`[liveness]`

`enabled = true`

`threshold = 0.8`

`max_frames = 40`

Why i love Arch Linux a Canadian Linux?!

Because its easy modular compare to other distros. All Linux are modular and you can install or uninstall anything! But you can't do as easy as Arch!

Another thing makes Arch best is it's documentation it's priceless, simple as that! if you know how to read and click the web you can fix Arch easy, especially with Ai today can give you step by step guide.

Then i am not a tinker that all the time tinker with the system and system core and configuration it left and right. I am doing easy things like photo, office, web-Tv live through the web and write my live story, a book.

Another reason i chose Arch is it low requirement use out of the box. Even when i have the top computer (AMD 9950X, 64Gb-6400mhz-ram,2 NVMe gen 5 and tow Gen 4 NVME disks, RX 9700XTX OC, 6K monitor, and more disk)

So why not use another good disktros like OpenSuse, because it's not Arch but i do have on my backup Linux computer a (AMD 3950X 128GB Ram NVMe disks and intel B580 Graphic card.)

Stability, well if you DON'T tinker Arch is very sable in fact. and if you want more stability you can Use LTS kernal as well.

Privacy is another aspect that Arch as out of the box, just need some tuning in setting and all in.

Why Linux general No telemetry, key-login, advertisement in side of Os and outside, no bloatware, it's YOURS the Linux system. No need to Phone home to 800 advertisement company's servers.

Why did YOU chose Arch Linux above other Linux and MS or OS X.

Hi everyone,

I am setting up a ThinkPad E14 Gen 7 (AMD Ryzen 7, ST Microelectronics TPM 2.0) with Arch Linux and trying to build a secure boot chain:

- UEFI Secure Boot with my own keys (sbctl)

- Signed UKI kernel

- systemd-cryptenroll TPM2 auto-unlock for LUKS2

- systemd-pcrlock to bind unlock to the expected boot state

- Btrfs snapshots with recovery workflow

The issue is that I can only get TPM enrollment working with PCR 15.

I originally wanted something like PCR 7 + 11 + 12 (or another recommended combination) because it seems more tied to Secure Boot state, kernel/initrd measurements, and the boot chain. However, whenever I try to use these PCRs, the TPM policy does not match after reboot.

PCR 15 is the only one that consistently works.

Some observations:

- Secure Boot is enabled and verified.

- The system boots through a signed UKI.

- The TPM event log exists and measurements appear normal.

- systemd-pcrlock works after boot, but I had issues predicting/locking some components.

- "systemd-pcrlock predict" showed missing components such as:

- "720-kernel-initrd"

- "750-os-separator"

- "770-nvpcr-separator"

- shutdown/finalization events

I initially generated policies from the Arch ISO/chroot environment, then discovered this was wrong because the TPM measurements were from the live environment and not the real installed boot chain. I regenerated the policy from the real system after boot.

I also tested different PCR combinations:

- PCR 7 only

- PCR 7 + 11

- PCR 7 + 11 + 12

- other combinations involving boot measurements

Most combinations failed TPM unlock after reboot, while PCR 15 worked.

My current setup:

- Arch Linux

- Btrfs on LUKS2

- systemd-boot/UKI

- custom Secure Boot keys

- TPM2 unlock using systemd-cryptenroll

- PCR 15 policy

Questions:

1. Am I misunderstanding the purpose of PCR 15 in this workflow? Is using PCR 15 alone a reasonable choice for LUKS auto-unlock with systemd-pcrlock?

2. Is PCR 7 + 11 + 12 still the recommended approach for this kind of setup, and if so, what could be causing my machine to fail with those PCRs?

3. Are there ThinkPad/AMD firmware limitations that can explain this behavior?

4. Could my UKI generation, kernel command line locking, or pcrlock policy generation order be wrong?

I would appreciate any suggestions about what I might be doing incorrectly before I settle with PCR 15 permanently.

Hi, I'm new to Arch and followed the LearnLinuxTV 2026 installation guide. I erased Windows and installed Arch with LUKS encryption. Installation completed without errors, mkinitcpio and GRUB finished successfully.

After reboot, GRUB asks for the LUKS passphrase. I enter the correct passphrase, but after 3 attempts it drops to emergency mode with:

Failed to start Cryptography Setup for lum.

Dependency failed for Initrd Root Device.

Dependency failed for /sysroot.

Note: this is first time after rebooting after setting up whole process

I installed tlp, tlp-pd. Removed power profile daemon.

I'm currently in GNOME desktop but I will switch to Sway once I'm done with the setup.

I have hp pavilion 15 Ryzen 5 4600h with igpu amd radeon and dgpu nvidia 1650ti.

Please guide to my most power effecient laptop.

My next step is to make sure nvidia dgpu is in D3cold state.