Title: SteamOS 3.9.5 – Boot loop and first-time setup reset on Lenovo Legion Go 2

Aperta
  • Qualcosa non va?
#3,052 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux
Ambito
operating-systems

Direzione di ricerca

Start by examining SteamOS first-run state persistence, A/B boot recovery, and display session transitions on the Lenovo Legion Go 2. The report names registry.vdf and the Rootfs A/B partitions, but does not identify source files, tests, or a confirmed root cause. Done means explaining or reproducing the reset, boot loop, or mode-switch freeze and identifying a reliable fix.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Device: Lenovo Legion Go 2 (Z2 Extreme, 32 GB RAM)
OS: SteamOS 3.9.5, installed on internal NVMe
Date: November 5, 2026

Bug description

SteamOS unexpectedly became unbootable after normal use, without any system reinstallation or intentional configuration changes.

Sequence of events:

  1. SteamOS was working normally, including Desktop Mode.
  2. An external display detection issue occurred. A reboot initially resolved it.
  3. After further normal use and shutdown, SteamOS failed to boot correctly.
  4. Subsequent boots repeatedly displayed the Lenovo Legion logo or restarted the first-time setup process, despite the system already being configured.
  5. Switching between Desktop and Gaming Mode with an external display also produced a freeze during subsequent testing.

Technical findings

  • Internal SSD: "/dev/nvme0n1"
  • Rootfs A: "/dev/nvme0n1p4" — SteamOS 3.9.5
  • Rootfs B: "/dev/nvme0n1p5" — SteamOS 3.8.28
  • Shared user data: "/dev/nvme0n1p8"
  • Steam's "registry.vdf" was unexpectedly reduced to approximately 366 bytes and lacked the "CompletedOOBEStage1" configuration entry.
  • An existing backup contained valid "CompletedOOBEStage1=1" and "CompletedOOBE=1" entries.

Recovery

Using a SteamOS recovery USB, we entered the installed system through "steamos-chroot", restored the previous "registry.vdf" and explicitly selected rootfs A for booting.

SteamOS eventually booted successfully without reinstalling or losing user data. Recovery was not consistently immediate, suggesting the configuration reset may not be the only issue.

Expected behavior

SteamOS should preserve its completed initial setup state, recover reliably after shutdown, and switch between Desktop/Gaming Mode without freezing or entering a boot loop.

Suspected issue

Possible corruption or unexpected reset of Steam's first-run configuration, potentially associated with external display handling or session transitions.

The root cause has not been confirmed.

Please investigate SteamOS first-run state persistence, A/B boot recovery and external display session transitions on the Legion Go 2.

Lingua principale
Nessun dato sulla lingua
Stelle
2.7k
Fork
89
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ValveSoftware/SteamOS

Tutte le issue di ValveSoftware/SteamOS

Issue simili

Altre issue su Operating Systems

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.