Logs and debugging
The laptop has no shell and no adb, so all evidence comes from log files written to the volume. Reading them is how problems are found.
Where they are
Every boot creates gbos/logs/boot-N/ on the volume it booted from (N counts up). For an installed laptop that volume is its internal GBOSSYS partition, which you cannot read from another computer directly. To collect them, boot the USB stick and choose 2, then 1 (Update): it copies the installed system's last three boots to gbos/logs/boot-N/nvme-logs/ on the stick. Then plug the stick into a computer.
Files
hwdetect.txt | Your hardware and what got a driver. Start here for a hardware report. |
kmsg.log | The full kernel log. The first lines include Linux version ... #N, which tells you which kernel actually ran. |
stage0-dmesg.txt | Kernel messages plus stage0 and hook progress. Look for lines starting hook:, hwdetect: and early:, and for NOT patched. |
logcat.txt* | Android's log, rotated; the highest number is the oldest. |
crash.txt | Crashes and tombstone summaries. |
hw.txt | The early hardware inventory: CPU flags, memory, PCI devices and their drivers, block devices. |
audio.txt | Sound cards, PCMs and the audio service state, captured about a minute after boot. |
pstore-prev/ | The previous boot's kernel panic, if there was one. |
Rules of thumb
- Absence of an error is not success. Check the log actually covers the time of the problem; logs have been truncated by filesystem corruption or by booting an old kernel.
- Confirm the kernel. The
Linux version ... #Nline must be the build you meant to test. - Shut down from Android's power menu, not the power button: FAT has no journal, so a hard power-off can corrupt the logs.
- The log directory keeps growing; delete old
boot-Nfolders from another computer if space is short.
A good bug report
- Laptop model and CPU.
- What you expected and what happened.
hwdetect.txtandstage0-dmesg.txtfrom the boot where it happened, pasted in code blocks or attached.- Whether it was live from USB or installed, and the kernel number.
Post it in the support forum.