New installation of Mageia 8 Beta 2 with - Classic ISO (x86_64) - do it offline (no add online repositories) - choose default presets and Plasma. results of a grub2 menu without Mageia branding. $ rpm -qa | grep grub2-mageia-theme grub2-mageia-theme is not installed. Workaround, add online repositories and do: # urpmi grub2-mageia-theme Make sure update-grub is run. Reboot. Booh: Grub2 has good branding. Assigning. Note that beta 1 ISO have this branding. Note that do a netinstall : branding OK. Not tested: Live ISO install.
Can't reproduce, tested with both legacy or UEFI boot. Please attach /root/drakx/report.bug.xz from your installed system.
Created attachment 12078 [details] report.bug.xz from new installation of Mageia 8 Beta 2 Classic ISO x86_64 As requested.
mageia-gfxboot-theme-4.5.14.11-2.mga8.x86_64 is installed in your logs…
Yeah, but if you look this output from /root/drakx/ddebug.log * running: grub2-mkconfig -o /boot/grub2/grub.cfg with root /mnt * grub2-mkconfig logs: Création du fichier de configuration GRUB⊠Image Linux trouvée : /boot/vmlinuz-5.9.12-desktop-1.mga8 Image mémoire initiale trouvée : /boot/initrd-5.9.12-desktop-1.mga8.img grub2-probe : erreur : impossible de trouver un périphérique GRUB pour /dev/sdb1. Vérifiez device.map.. Windows Boot Manager trouvé sur /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi fait * running: grub2-set-default linux with root /mnt * running: sh /boot/grub2/install.sh with root /mnt And this from update-grub as root AFTER install of grub2-mageia-theme rpm: Création du fichier de configuration GRUB… Thème trouvé : /boot/grub2/themes/maggy/theme.txt Image Linux trouvée : /boot/vmlinuz-5.9.12-desktop-1.mga8 Image mémoire initiale trouvée : /boot/initrd-5.9.12-desktop-1.mga8.img Windows Boot Manager trouvé sur /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration fait gfxboot is for BIOS, not UEFI?
mageia-gfxboot-theme is for legacy GRUB, not GRUB2. From the logs I would deduce that the bootloader method selected was "GRUB2 with text menu" not "GRUB2 with graphical menu". But unless you manually changed it, I can see no reason why it didn't default to the latter.
Assignee: mageia => mageiatools
(In reply to Martin Whitaker from comment #5) > mageia-gfxboot-theme is for legacy GRUB, not GRUB2. > > From the logs I would deduce that the bootloader method selected was "GRUB2 > with text menu" not "GRUB2 with graphical menu". But unless you manually > changed it, I can see no reason why it didn't default to the latter. I managed to reinstall this beta 2 on my system. Before landing to Summary page, DrakX asks for use of nvidia nonfree drivers on this system. And right after it, I verify that it wants to make grub2 purely in console version. See attached photo.
I have reproduced this on a system with an old NVIDIA graphics card, both with and without choosing to use the proprietary graphics driver. The fault is only in the default selection - if you choose to configure the bootloader at the summary screen, you can select grub2-graphical and it is installed correctly. I can't reproduce this bug on my laptop with hybrid NVIDIA/Intel graphics, even if I choose to configure the NVIDIA card only.
CC: (none) => mageia
The trigger for this bug is GRUB2 being already installed in the ESP (either from a previous or another Mageia installation). This caused the installer to falsely set the current bootloader method to non-graphical GRUB2.
Source RPM: grub2-2.04.0-25.mga8.src.rpm => drakxtoolsAssignee: mageiatools => mageiaStatus comment: (none) => fixed in git
Status: NEW => ASSIGNED
Many thanks Martin. Happy ending here.
Fixed in RC iso.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED