[SOLVED] Bootup splash error

[laidlaws]

(I have never worked out which splash screen is which.)
On a separate installation of Cauldron, for a while there was no splash screen after selecting Mageia and while it was loading, only a grey screen with 3x "?". That cured itself with time.

I have just upgraded my working Official to Mga 6. To begin with, the Grub2 menu was in a white font on a black background. Running an "update" from my installation media fixed that, but the grey bootup screen has returned. I can probably wait until the next update of the graphics, but is there any fix I can apply now?

[benmc]

Hi

Which desktop, or more importantly, which Desktop Manager?

as root:

Code: Select all

drakedm

try

Code: Select all

urpmi lightdm

then drakedm again and change to "LightDM", then

Code: Select all

reboot

cheers

note: desktop / DM usual arrangement:

Plasma5 => sddm ( is improving as time goes on )
Gnome => gdm
Xfce, Cinnamon, Mate => Lightdm
LXDE => LXDM

[laidlaws]

Thanks. Desktop is XFCE
DM was sddm
Changed to lightdm.

On rebooting the nVidia splash was visible, but no change to the grey startup screen before it.
Old Cauldron with sddm and MATE desktop, shows the new artwork background.

[benmc]

is boot system grub legacy or grub2?

check to see if "mageia-gfxboot-theme 4.5.6.10-1.mga6" has been installed / updated to.

[laidlaws]

Boot manager is Grub2

"mageia-gfxboot-theme 4.5.6.10-1.mga6" has been installed. I uninstalled and reinstalled it. No change.

Since this is only a cosmetic thing, and only during bootup, I might as well leave it. When the RC is available, I will do a clean reinstall.

[laidlaws]

I read somewhere that the fix is to make a fresh initrd. Haven't tried it yet.

[doktor5000]

Then try as root

Code: Select all

dracut -f

or

Code: Select all

bootloader-config --action rebuild-initrds

[laidlaws]

Thanks Doktor. I have just run

Code: Select all

mkinitrd --force


That cured the problem. Marking the thread as solved
I had the same problem in 2 Cauldron installs. It may have arisen because the new graphics came along later.

[laidlaws]

The next two reboots were good, so I assumed that the problem was fixed. Since then, it has been no different from before. I will leave it until the RC is available. No use chasing bugs before then.