### System details

Google Pixelbook (Eve, 2017), Core i5-7Y57 / HD 615, Omarchy 4.0.4, linux-omarchy 7.2.5-3, original Google firmware booting through RW_LEGACY (UEFI)

### What's wrong?

Got Omarchy running on my original 2017 Pixelbook and it's great, except brightness. Changing it updates `/sys/class/backlight/intel_backlight`, but the panel stays exactly as bright as it was.

To see it on an Eve:

1. `omarchy brightness display 30%`
2. `cat /sys/class/backlight/intel_backlight/brightness` shows the new value. The panel doesn't change.

Booting with `i915.enable_dpcd_backlight=1` fixes it: i915 drives the panel's eDP DPCD (AUX) backlight instead, and brightness changes reach the panel.

Before and after on my Eve, stepping brightness to 20% and back to 100%:

| | `intel_backlight` (20% → 100%) | Panel |
|---|---|---|
| Stock | 300 → 1500 (max 1500) | doesn't change |
| With the fix | 6553 → 32767 (max 32767) | dims and brightens |

Would you take a PR? It's ready on a branch:

- `omarchy-hw-google-pixelbook-eve`: exact DMI match (vendor `Google`, product `Eve`)
- `install/hardware/google/fix-pixelbook-eve-backlight.sh`: a limine cmdline drop-in, same as `fix-asus-ptl-display-backlight.sh`
- a migration for existing Eves, modeled on 1786482992: writes the drop-in, rebuilds the boot image, asks for a reboot. It skips a machine already booted with any `i915.enable_dpcd_backlight=` value, a marker stops a second user from rebuilding again, and a failed rebuild stays pending.
- `test/shell.d/pixelbook-eve-backlight-test.sh`, with stubbed DMI and sudo

Branch: https://github.com/Sha01in/omarchy-upstream/tree/add-google-pixelbook-eve-backlight

I tested the migration for real on my Eve: removed my own drop-in, rebuilt and rebooted (brightness broken), then ran the branch's migration under `bash -euo pipefail` like `omarchy-migrate`. It wrote the drop-in, rebuilt the UKI, set `reboot-required` and the marker, and after the reboot the "with the fix" row above is the result. With my old drop-in in place it no-ops. Not tested: a fresh install.

On a stock install the Eve's brightness keys send F5/F6, not brightness keys. That's a separate Chromebook keyboard question.

Audio, status only: the AVS driver's renamed cards (`AVS I2S <codec>`) don't match the `Google-Eve-1.0` profiles in alsa-ucm-conf 1.2.16.1, so no UCM profile loads. alsa-project/alsa-ucm-conf#571, open since June 2025, adds profiles for the new names. On a scratch copy here they load, with one jack-name miss, which I've reported there. Meanwhile `snd_soc_avs obsolete_card_names=1` brings back the old card names, and with the stock profiles the speakers, built-in mic and headphones (stereo, auto-switch on plug-in) all work here. The stock profile has the same headset-mic jack name bug, which I've sent upstream as alsa-project/alsa-ucm-conf#866. I'll open a separate issue for that one-liner.

If anyone else has an Eve, confirming the brightness fix would help.

AI disclosure: I worked this out with Claude Code (Opus 5.5 and Sonnet 5.5) and reviewed everything it changed.