search

merge / skulls

pre-built coreboot images and documentation on how to flash them for Thinkpad Laptops
GNU General Public License v3.0
681 stars 66 forks source link

T440p - Seabios Verbosity? #206

Open davitchen opened 2 years ago

davitchen commented 2 years ago

There is a little visibility/timing problem of the splash screen. If you starting your device it shows the skulls bunny. After a few seconds, the screens changes and display a seabios version number, and then change back to the splash screen.

Maybe this Parameter is a problem / Config: nonfree-defconfig-45ce84113e CONFIG_SEABIOS_DEBUG_LEVEL=-1

Docs from Seabios: CONFIG_DEBUG_LEVEL

Control how verbose debug output is. The higher the
number, the more verbose SeaBIOS will be.

Set to zero to disable debugging.

So I would suggest CONFIG_SEABIOS_DEBUG_LEVEL=0

merge commented 2 years ago

btw the problem affects every board

ghost commented 2 years ago

There is a little visibility/timing problem of the splash screen. If you starting your device it shows the skulls bunny. After a few seconds, the screens changes and display a seabios version number, and then change back to the splash screen.

Sounds like a good idea. If we set it to zero, will it remove the seabios version & machine uuid and show the splashscreen immediately?

Myles24 commented 2 years ago

There is a little visibility/timing problem of the splash screen. If you starting your device it shows the skulls bunny. After a few seconds, the screens changes and display a seabios version number, and then change back to the splash screen.

Sounds like a good idea. If we set it to zero, will it remove the seabios version & machine uuid and show the splashscreen immediately?

You can actually customize what SeaBios displays on the screen at boot (and remove the version and machine uuid). It should be under coreboot/payloads/external/SeaBIOS/seabios/src/bootsplash.c under the line "// Write to screen".

ghost commented 2 years ago

There is a little visibility/timing problem of the splash screen. If you starting your device it shows the skulls bunny. After a few seconds, the screens changes and display a seabios version number, and then change back to the splash screen.

Sounds like a good idea. If we set it to zero, will it remove the seabios version & machine uuid and show the splashscreen immediately?

You can actually customize what SeaBios displays on the screen at boot (and remove the version and machine uuid). It should be under coreboot/payloads/external/SeaBIOS/seabios/src/bootsplash.c under the line "// Write to screen".

I got some much more serious problem now, tho unrelated: ps2 keyboard for my x131e will stop working in the secondary payload after a while (coreinfo, nvramcui...)

Myles24 commented 2 years ago

There is a little visibility/timing problem of the splash screen. If you starting your device it shows the skulls bunny. After a few seconds, the screens changes and display a seabios version number, and then change back to the splash screen.

Sounds like a good idea. If we set it to zero, will it remove the seabios version & machine uuid and show the splashscreen immediately?

You can actually customize what SeaBios displays on the screen at boot (and remove the version and machine uuid). It should be under coreboot/payloads/external/SeaBIOS/seabios/src/bootsplash.c under the line "// Write to screen".

I got some much more serious problem now, tho unrelated: ps2 keyboard for my x131e will stop working in the secondary payload after a while (coreinfo, nvramcui...)

Are you using the skulls image or compiling a coreboot rom yourself? If you're compiling the rom, make sure you have the ps2 generic driver checked. I haven't encountered this issue before but it doesn't seem like that big of a deal since those payloads are just for some quick config options.

ghost commented 2 years ago

@Myles24 I was actually compiling coreboot from its master branch😅 Can I just pull skulls and change the board config to x131e? Anyways I enabled the ps2 keyboard driver in the devices section and the keyboard would always work in seabios, and only for a while in secondary payloads. Could be libapayload's issue.