Andrei Borzenkov changed bug 978973
What Removed Added
CC   arvidjaar@gmail.com
Flags   needinfo?(rb03884@gmail.com)

Comment # 5 on bug 978973 from
(In reply to Roman Bysh from comment #0)
> Tumbleweed
> 
> Removing the very useful vga selection

Please explain what you mean. I tested bootloader module on current TW and it
still offers "Console Resolution" selection which is translated in grub2

gfxmode=800x600
gfxpayload=keep

This should be entirely equivalent to using vga=800x600 (sorry, forgot hex for
it) on kernel command line. If not, the first suspect here is grub2. Please
give as much details as possible, including architecture and platform (BIOS,
EFI) and your grub.cfg.

> now breaks plymouth as it now shows
> three question marks.

This probably means plymouth is started in text mode. Please show dmesg after
boot for both cases, with and without vga= on kernel command line.

> We've been using it for years why the sudden change?
> 

As long as grub2 is the only supported bootloader, using grub2 native means to
configure resolution sounds logical.

> It seems to work fine with the nouveau driver but when I install an Nvidia
> blob
> I get three question marks.
> 

Sorry, but that is absolutely unintelligible. Works "what"? YaST2 bootloader
module adds vga= kernel parameter when you are using nouveau?

> Plymouth requires a ie. vga=795 so that it can show the boot splash.

You are confused. Plymouth does *not* require it. Plymouth can also show splash
in text mode. This is buggy as you see and has to be reported separately. To
show graphical splash kernel has to start with frame buffer console. That
apparently does not happen in your case, and we need to understand why. It
works on all my VMs BTW so it is not something generally broken.

Let's try to understand the root cause before demanding perpetual workaround.

(In reply to Roman Bysh from comment #4)
> I'm wondering if another bug report for plymouth should be reported.
> 

Three question marks is a bug in console initialization in text mode; there was
already bug report but I am not sure what outcome is. In any case, this is
something between plymouth, systemd and dracut and completely unrelated to
yast.


You are receiving this mail because: