missing early linux console output when using SeaVGABIOS about skulls

[paulmenzel]

On 11/23/18 11:29, Martin Kepplinger wrote: When building using our "free" config (mv `config-xxx backup-config-xxx && mv free-config-xxx config-xxx && ./build.sh`) we don't have early linux boot console output on the display.

Do you have the coreboot framebuffer driver (GOOGLE_FRAMEBUFFER_COREBOOT) selected in the Linux configuration? […]

[merge]

I didn't, but changed that now which doesn't help though. It feels like GRUB needs a change here because it's "loading init ramdisk" keeps displayed until Linux graphics takes over.

[paulmenzel]

On 11/23/18 14:19, Martin Kepplinger wrote: I didn't, but changed that now which doesn't help though. It feels like GRUB needs a change here because it's "loading init ramdisk" keeps displayed until Linux graphics takes over.

Why do you think, GRUB needs a change. It seems to be doing everything fine. By the way, what GRUB version do you use? Anyway, please paste the Linux kernel messages.

[merge]

I'm running Debian stable's GRUB 2.02~beta3-5+deb9u1

dmesg is ok and unchanged. It's only about display behaviour during booting. With SeaVGABIOS GRUB is being displayed until Linux does modesetting and systemd's messages are displayed.

I only suspect a GRUB config might change that. I'm sure at all. When using Intel's vga bios, all early kernel messages are displayed in low resolution until Linux switches graphics mode.

[paulmenzel]

On 11/26/18 12:19, Martin Kepplinger wrote: I'm running Debian stable's GRUB 2.02~beta3-5+deb9u1

Please try a newer one, best built from GRUB’s master branch.

dmesg is ok and unchanged.

That is good to know, but I’d like to take a look at those.

[merge]

I can try installing a new GRUB at some point... Are there specific relevant changes?

seavgabios_dmesg.txt