[SOLVED] SPLASH screen at boot in wrong resolution

[Croton]

Dear fellow users,

if I boot up on my dual boot system the boot menu is displayed in the correct resolution (WQHD 2560x1440), however in the "SPLASH" section the resolution is set back to 1024x768 and the splash animation selected in the MX Boot OPtions just appear in the upper left corner of the screen. If I remove the SPLASH parameter the same happens and I get the system messages just in the upper left corner. If I run "videoinfo" in the Grub shell, it shows WQHD as a supported resolution... Is there a way to have the full boot process running without the resolution switch. It is not urgent but doesn't look really professional as it is

[Croton]

and as always I forgot: running MX 18.3 fully updated with an RX580 graphics card and a dual monitor setup (1280x1024 vertical and the WQHD screen as main).

[dolphin_oracle]

Dear fellow users,

if I boot up on my dual boot system the boot menu is displayed in the correct resolution (WQHD 2560x1440), however in the "SPLASH" section the resolution is set back to 1024x768 and the splash animation selected in the MX Boot OPtions just appear in the upper left corner of the screen. If I remove the SPLASH parameter the same happens and I get the system messages just in the upper left corner. If I run "videoinfo" in the Grub shell, it shows WQHD as a supported resolution... Is there a way to have the full boot process running without the resolution switch. It is not urgent but doesn't look really professional as it is

in your /etc/default/grub,uncomment and set the GRUB_GFXMODE equal to your native resolution. then do a "update-grub" and see if that helps the situation any.

[Croton]

in your /etc/default/grub,uncomment and set the GRUB_GFXMODE equal to your native resolution. then do a "update-grub" and see if that helps the situation any

This does something but doesn't change the splash resolution. In fact I now realized that the Grub menu was apparently just extended to the full monitor - I now get the menu much sharper, with a much smaller text (so it now really is 2560x1440, whereas it was before something like FullHD scaled up to the full screen). Unfortunately it has no effect on the splash animation, which is still only displayed in the upper left corner.

Thank you very much anyway - this at least solves a problem I didn't realize I had before

[Croton]

OK - I almost found the solution I think: Changing the boot parameters to

Code: Select all

quiet splash video=2560x1440

will make the plymouth (I just learned today that I have it) correctly on the main screen - However while introducing an error message display on the left screen.

My guess is I could set my virtual resolution 3584(2560+1024)x2720(1440+1280) and manually align all the themes in

Code: Select all

/usr/share/plymouth/themes/

to display in the middle of my main screen in order to look as expected.

However I'd really like to find an option where only the screen where the GRUB menu is displayed is used by plymouth, as I may not always boot with the secondary monitor on and no physical screen wil be able l display 3584x2720

[Croton]

Ok I now got it - It is still not flicker free but I now know what does what

• The first grub screen, where I can select MX Linux, memtest or Windows has a resolution controlled by

  in your /etc/default/grub,uncomment and set the GRUB_GFXMODE equal to your native resolution

  - this only affects the main monitor

• The "splash animation" selected in the MX Boot options is set by the grub boot parameters

  quiet splash video=2560x1440

  - here I have to select a resolution which is supported by all attached monitors, to make it look clean

• After that there is a quick display (as I login without giving my credentials) of the background selected in the Settings - LightDM-GTK+... tool, so the login manager

There are some problems inherent to my setup - As my second 1280x1024 display is set to vertical, the boot animation will be turned upside down on it. Also as it is rather old it is much slower on the resolution change as the "main" it will inevitably flicker. The dual-boot Windows 10 doesn't display this behavior as the secondary screen is only attached after login.

The original problem is gone for good however