Putting Linux on my RTX Spark laptop because I don't have a Microsoft account
- ID
- 37308
- Status
- summarized
- Published
- 20 Oct 2026, 5:08 AM
- Fetched
- 20 Oct 2026, 5:19 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://josie.lol/blog/linux-rtx-spark
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 20 Oct 2026, 5:20 PM
- Tags
- Audience
- developersai_ml_learnersvibe_coders
What happened
Josephine Pfeiffer documented getting Arch Linux ARM running on an ASUS ProArt P16 H7607BA-SE033W (128 GB RAM, 6,144 CUDA cores, 2 TB SSD, 3840×2400 120 Hz) despite Windows-only official support. The build required a patched hid-asus for the keyboard, a custom audio machine driver, ACPI overrides derived from the laptop's own tables, and an extension to upstream Archinstall 4.5; after all that, Arch keeps pace with Windows in 7-Zip and reports the same 116.0 GiB memory pool to both the OS and CUDA. The repo ships build scripts, hash-pinned inputs, and hardware packages signed with the author's Arch Linux Package Maintainer key, with instructions to dump your own ACPI tables and extract speaker firmware locally.
Why it matters
If you were weighing this class of machine for local open-weight model work, the write-up confirms the Windows-only driver situation is surmountable without losing the 116.0 GiB unified pool CUDA sees — that number, not the OS, is the reason to buy it. But the cost is real: a patched hid-asus, a bespoke audio driver, per-machine ACPI overrides, and firmware H7607BA.300 assumed. Decide whether you're willing to dump your own ACPI tables and rebuild against a specific firmware revision before spending on the hardware; there is no official support path if a BIOS update breaks it.
Discussion angle
Unified memory vs discrete VRAM for local inference: at what point does a 116 GiB CUDA-visible pool on a laptop beat a smaller-VRAM desktop GPU, and is the Windows-driver dependency a temporary gap or the permanent shape of 'AI PC' hardware?