[SOLVED] Splash screen not updated from mga8 to mga9

[MagicD3VIL]

Greetings everyone,
I am facing a weird cosmetic issue. After an upgrade from Mageia 8 to Mageia 9, the first boot splash screen (before the SDDM greeter is shown) wasn't updated to feature Mageia 9 artwork for me. However, the splash screen displayed on the system shutdown was updated, making it even more confusing.

Do you have any tips on how to fix this so the Mageia 9's splash screen is shown for both boot and shutdown instead of Mageia 8's?

Cheers

[doktor5000]

You're referring to the plymouth theme, or before, the bootloader theme for grub (gfxboot)?

Try reinstalling the package mageia-theme, as root:

Code: Select all

urpmi --replacepkgs --replacefiles mageia-theme

[MagicD3VIL]

Weirdly enough, reinstalling the "mageia-theme" package did not help. After running the command, I also got a "Cannot find a boot loader installed" message. Any thoughts?

EDIT: I forgot Code tags are not inline

[doktor5000]

Some more information about your setup might be helpful. Legacy BIOS or UEFI boot, what bootloader do you use, and where is it installed ?

[MagicD3VIL]

Sure thing, I use UEFI boot, and my bootloader is installed on a separate EFI partition. BIOS partition is on /dev/sdc6 and the EFI system is on /dev/sdc4. I am using the default grub2 bootloader.

[doktor5000]

BIOS partition is on /dev/sdc6 and the EFI system is on /dev/sdc4.

If you use UEFI boot, what is a BIOS partition and what do you use it for? That sounds confusing.
Can you post the output of

Code: Select all

lsblk -f

as root ?

[MagicD3VIL]

The BIOS partition is a relic from when I had a Legacy boot. I've switched to UEFI somewhere at Mageia 8 without doing a clean install since it was possible to do so. I think I've left the BIOS partition there in case I had to enable CSM.

The output of lsblk:

Code: Select all

sdc                                                                                         
├─sdc1
│     ntfs         System Reserved 7EFF0B55BCCB93B5                                   
├─sdc2
│     ntfs                              EC680D4B680D15CC                       33,1G    75% /media/SSD
├─sdc3
│     ntfs                              3EFE430EFE42BDC1                                   
├─sdc4
│     vfat   FAT32                      D0AC-1337                                           
├─sdc5
│     ext4   1.0                        a3f5980b-2ae5-4b7a-8ab7-829c838396d0   15,2G    79% /
└─sdc6

I've removed all of the other physical drives from the output since they are not relevant.

[doktor5000]

If you use UEFI boot, why is /boot/efi not mounted ? Sure that you're not still booting via legacy ?

Can you run drakboot to simply change any minor bootloader option to see if it completes? https://doc.mageia.org/mcc/9/en/content ... l#drakboot

[MagicD3VIL]

I have CSM disabled in BIOS so booting without UEFI should fail. Also, the folder '/sys/firmware/efi' exists, so check like `$ [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS` returns UEFI.

Running drakboot via sudo returned "No bootloader found, creating a new configuration" as to which I pressed Cancel. I cannot tell why it is not mounted after boot but I am pretty sure it's on the other partition. I recall that last time when I was fixing Grub (after Windows deleted it while updating) using chroot from LiveCD I also had to mount the EFI partition.

[doktor5000]

Can you check your /etc/fstab for the UEFI partition, and add it there after / for automatic mounting? Then mount it, and run drakboot again.

[MagicD3VIL]

What mount point should I set for the partition? The /boot/EFI is already taken and accessible only as root. The partition is missing from fstab config.

The /boot/EFI currently contains:

Code: Select all

/boot/EFI
└── EFI
    ├── BOOT
    └── mageia

4 directories, 0 files

The mounted partition would contain:

Code: Select all

sudo mount /dev/sdc4 /boot/efi/
tree /boot/efi/
/boot/efi/
├── Boot
│   ├── BCD
│   ├── BCD.LOG
│   ├── BCD.LOG1
│   ├── BCD.LOG2
│   ├── bg-BG
│   │   └── bootmgr.exe.mui
│   ├── BOOTSTAT.DAT
│   ├── bootuwf.dll
│   ├── bootvhd.dll
│   ├── cs-CZ
│   │   ├── bootmgr.exe.mui
│   │   └── memtest.exe.mui
│   ├─ TON OF FILES...
├── bootmgr
├── BOOTNXT
└── EFI
    ├── BOOT
    │   ├── BOOTX64.EFI
    │   ├── fbx64.efi
    │   └── mmx64.efi
    ├── mageia
    │   └── grubx64.efi
    └── Microsoft
        ├── Boot
        ├─ TON OF FILES...

87 directories, 231 files

Cheers

EDIT: When I tried mounting it as /boot then drakboot did not find the bootloader again. Also the usual files from /boot were missing so I don't think that's right

[doktor5000]

The /boot/EFI is already taken and accessible only as root.

What do you mean already taken? Also, you need to mount it as root anyway so that doesn't matter.

Code: Select all

mount /dev/sdc4 /boot/EFI

[MagicD3VIL]

By "taken" I meant that the folder already existed and had a structure, which I later found contained no files anyway. In Dolphin, the folder was also shown with a padlock meaning root-only read access, which I guess confused me even more as something being there.

After mounting the partition as /boot/EFI (weird that having the path /boot/EFI/EFI/mageia/... is correct, having EFI folder twice) the drakboot now finds it! However, while trying to reinstall the mageia-theme, urpmi returns

Code: Select all

remove-boot-splash: Format of /boot/initrd-6.4.9-desktop-2.mga9.img not recognized
remove-boot-splash: Format of /boot/initrd-5.15.122-desktop-1.mga8.img not recognized


Cheers

[doktor5000]

However, while trying to reinstall the mageia-theme, urpmi returns

Code: Select all

remove-boot-splash: Format of /boot/initrd-6.4.9-desktop-2.mga9.img not recognized
remove-boot-splash: Format of /boot/initrd-5.15.122-desktop-1.mga8.img not recognized


Well, there's a pretty old report about that one: https://bugs.mageia.org/show_bug.cgi?id=19049

You could try to reinstall the respective kernels which contain that initrd same as above via urpmi --replacepkgs --replacefiles ...

[MagicD3VIL]

It seems that the issue has been resolved with a recent update. Marking as solved.