Screen garbled in Seabios, does not boot, Kernel panic (X60)
I tried updating from Coreboot-4.4 to current HEAD on my Thinkpad X60. The build went fine, but afterwards:
- screen was partly disorted / garbled (big green artifacts in the bottom part)
- first attempt to boot resulted in kernel panic
- could get machine to boot only after rebooting and then it booted normally
Downgraded now to 4.4, and things are working okay again.
#1 Updated by Daniel Kulesz over 2 years ago
I had the same issue with the official 4.5 release. Then I switched off the following option:
Display => Keep VESA framebuffer
Since then, everything is back to normal. However, in 4.4 it used to work with the option enabled (just double-checked), so I would consider this a regression.
#4 Updated by Daniel Kulesz over 2 years ago
- File IMG_20161118_161249.jpg added
I retried in master as of cd2afc0df034670a83479aded514b22b99124cf5. Here is what changed:
- again, first attempt to boot after flashing resulted in kernel panic (blinking scroll lock led)
- the issue that the device does not boot up at the first time got better. Lockup during boot happens only occasionally but is not easily reproducible.
- however, the device sometimes does not init correctly (empty screen, backlight on)
- when using the "Keep VESA framebuffer" option, the screen is still garbled during bootup, and also when booting into text-based Payloads such as meminfo or memtest86+. Memtest86+ itself does not report any memory issues (when running coreboot without the VESA option since no output is visible when activated).
I am attaching pictures for some of the symptoms.
#10 Updated by Daniel Kulesz almost 2 years ago
- File config.txt added
- File config.short.txt added
- File cbfs.txt added
- File coreboot_console.txt added
- File coreboot_timestamps.txt added
- File kernel_log.txt added
- File payload_config.txt added
- File revision.txt added
- File rom_checksum.txt added
Here are the logs.
#11 Updated by Daniel Kulesz almost 2 years ago
One more thing I noticed in the VESA "broken" Mode:
If I hit "Esc" in Seabios after cold boot and choose the boot device, the system will always hang. If I do not hit Esc but let it continue booting, the Linux kernel will succeed in initializing the graphics most of the time. Some timing issue?