Description of problem: In an EFI VM. When upgrading from a Mageia 4.1 installed from KDE Mga4 live DVD, vmlinuz-desktop and initrd-desktop.img symlinks are correctly created and work, however the vmlinuz and initrd.img sysmlinks are left pointing to the old Mageia 4 files. When grub2 in another system uses os-prober to generate a grub.cfg pointing to this installation, it uses vmlinuz and initrd.img not the -desktop variants causing a problem. Version-Release number of selected component (if applicable): How reproducible: Only tested once, and stumbled upon when investigating why the plymouth image did not appear to have updated (the controlling grub2 was on another disk). Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Priority: Normal => release_blocker
Re-testing this with more detail: BEFORE UPGRADE: ========================== [root@localhost baz]# urpmi --auto-update medium "Core Release (zmrepo1)" is up-to-date medium "Core Updates (zmrepo3)" is up-to-date medium "Nonfree Release (zmrepo11)" is up-to-date medium "Nonfree Updates (zmrepo13)" is up-to-date medium "Core 32bit Release (zmrepo31)" is up-to-date medium "Core 32bit Updates (zmrepo32)" is up-to-date medium "Nonfree 32bit Release (zmrepo36)" is up-to-date medium "Nonfree 32bit Updates (zmrepo37)" is up-to-date Packages are up to date [root@localhost baz]# ls -l /boot total 29988 -rw-rw-r-- 1 root root 440 Mar 6 12:17 boot.backup.sda -rw-r--r-- 1 root root 151120 Jun 5 2014 config-3.12.21-desktop-2.mga4 -rw-r--r-- 1 root root 154625 Feb 7 00:44 config-3.14.32-desktop-1.mga4 drwxr-xr-x 2 root root 4096 Feb 9 2014 dracut/ drwxrwxrwx 3 root root 4096 Jan 1 1970 EFI/ -rwxr-xr-x 1 root root 535552 Mar 6 12:17 gfxmenu* drwxr-xr-x 2 root root 4096 Mar 6 15:17 grub/ drwxr-xr-x 6 root root 4096 Mar 6 15:19 grub2/ -rw------- 1 root root 7764723 Mar 6 12:09 initrd-3.12.21-desktop-2.mga4.img -rw------- 1 root root 7788541 Mar 6 15:17 initrd-3.14.32-desktop-1.mga4.img lrwxrwxrwx 1 root root 33 Mar 6 15:17 initrd-desktop.img -> initrd-3.14.32-desktop-1.mga4.img lrwxrwxrwx 1 root root 33 Mar 6 15:17 initrd.img -> initrd-3.14.32-desktop-1.mga4.img -rw-r--r-- 1 root root 308314 Oct 18 2013 mageia.bmp -rw-r--r-- 1 root root 224700 Jun 5 2014 symvers-3.12.21-desktop-2.mga4.xz -rw-r--r-- 1 root root 229780 Feb 7 00:44 symvers-3.14.32-desktop-1.mga4.xz -rw-r--r-- 1 root root 2870414 Jun 5 2014 System.map-3.12.21-desktop-2.mga4 -rw-r--r-- 1 root root 2943189 Feb 7 00:44 System.map-3.14.32-desktop-1.mga4 lrwxrwxrwx 1 root root 30 Mar 6 15:17 vmlinuz -> vmlinuz-3.14.32-desktop-1.mga4 -rw-r--r-- 1 root root 3805216 Jun 5 2014 vmlinuz-3.12.21-desktop-2.mga4 -rw-r--r-- 1 root root 3888784 Feb 7 00:44 vmlinuz-3.14.32-desktop-1.mga4 lrwxrwxrwx 1 root root 30 Mar 6 15:17 vmlinuz-desktop -> vmlinuz-3.14.32-desktop-1.mga4 Media switched to cauldron, followed by: urpmi --replacefiles --auto-update --auto (from the wiki) During update:- 5/7: removing grub2-efi-2.00-59.1.mga4.x86_64 ######################################################################################################### Generating grub configuration file ... Found theme: /boot/grub2/themes/maggy/theme.txt Found linux image: /boot/vmlinuz-desktop Found initrd image: /boot/initrd-desktop.img Found linux image: /boot/vmlinuz-3.19.1-desktop-1.mga5 Found initrd image: /boot/initrd-3.19.1-desktop-1.mga5.img Found linux image: /boot/vmlinuz-3.14.32-desktop-1.mga4 Found initrd image: /boot/initrd-3.14.32-desktop-1.mga4.img Found linux image: /boot/vmlinuz-3.12.21-desktop-2.mga4 Found initrd image: /boot/initrd-3.12.21-desktop-2.mga4.img Found Mageia 5 (5) on /dev/sda2 Found Mageia 5 (5) on /dev/sdb1 Found Mageia 5 (5) on /dev/sdc1 done AFTER UPGRADE: ================================ [root@localhost baz]# urpmi --replacefiles --auto-update --auto medium "Core Release (zmrepo1)" is up-to-date medium "Core Updates (zmrepo3)" is up-to-date medium "Nonfree Release (zmrepo11)" is up-to-date medium "Nonfree Updates (zmrepo13)" is up-to-date medium "Core 32bit Release (zmrepo31)" is up-to-date medium "Core 32bit Updates (zmrepo32)" is up-to-date medium "Nonfree 32bit Release (zmrepo36)" is up-to-date medium "Nonfree 32bit Updates (zmrepo37)" is up-to-date Packages are up to date [baz@localhost ~]$ ls -l /boot total 45844 -rw-rw-r-- 1 root root 440 Mar 6 12:17 boot.backup.sda -rw-r--r-- 1 root root 151120 Jun 5 2014 config-3.12.21-desktop-2.mga4 -rw-r--r-- 1 root root 154625 Feb 7 00:44 config-3.14.32-desktop-1.mga4 -rw-r--r-- 1 root root 171245 Mar 10 22:42 config-3.19.1-desktop-1.mga5 drwxr-xr-x 2 root root 4096 Feb 27 19:33 dracut/ drwxrwxrwx 3 root root 4096 Jan 1 1970 EFI/ -rwxr-xr-x 1 root root 562176 Mar 13 20:52 gfxmenu* drwxr-xr-x 2 root root 4096 Mar 13 20:47 grub/ drwxr-xr-x 6 root root 4096 Mar 13 20:51 grub2/ -rw------- 1 root root 7764723 Mar 6 12:09 initrd-3.12.21-desktop-2.mga4.img -rw------- 1 root root 7788541 Mar 6 15:17 initrd-3.14.32-desktop-1.mga4.img -rw------- 1 root root 8221443 Mar 13 20:38 initrd-3.19.1-desktop-1.mga5.img lrwxrwxrwx 1 root root 32 Mar 13 20:38 initrd-desktop.img -> initrd-3.19.1-desktop-1.mga5.img lrwxrwxrwx 1 root root 33 Mar 6 15:17 initrd.img -> initrd-3.14.32-desktop-1.mga4.img -rw-r--r-- 1 root root 308314 Sep 23 20:08 mageia.bmp -rw-r--r-- 1 root root 224700 Jun 5 2014 symvers-3.12.21-desktop-2.mga4.xz -rw-r--r-- 1 root root 229780 Feb 7 00:44 symvers-3.14.32-desktop-1.mga4.xz -rw-r--r-- 1 root root 245720 Mar 10 22:42 symvers-3.19.1-desktop-1.mga5.xz -rw-r--r-- 1 root root 2870414 Jun 5 2014 System.map-3.12.21-desktop-2.mga4 -rw-r--r-- 1 root root 2943189 Feb 7 00:44 System.map-3.14.32-desktop-1.mga4 -rw-r--r-- 1 root root 3222929 Mar 10 22:42 System.map-3.19.1-desktop-1.mga5 lrwxrwxrwx 1 root root 30 Mar 6 15:17 vmlinuz -> vmlinuz-3.14.32-desktop-1.mga4 -rw-r--r-- 1 root root 3805216 Jun 5 2014 vmlinuz-3.12.21-desktop-2.mga4 -rw-r--r-- 1 root root 3888784 Feb 7 00:44 vmlinuz-3.14.32-desktop-1.mga4 -rw-r--r-- 1 root root 4340800 Mar 10 22:42 vmlinuz-3.19.1-desktop-1.mga5 lrwxrwxrwx 1 root root 29 Mar 13 20:38 vmlinuz-desktop -> vmlinuz-3.19.1-desktop-1.mga5 [baz@localhost ~]$ Note that in the above, initrd.img and vmlinuz both point to 3.14.32 not 3.19.1
Strangely, changing the symlinks to point to 3.19.1-desktop-1.mga5 still displays the Mga4 plymouth screen. Only after running dracut -f does the correct plymouth screen display before login, however this is *only* shown when booting from the grub of another install. When booting from it's own grub2 bootloader (after running grub2-install /dev/sda from within this system) the plymouth screen does not appear at all.
Just wondering if the upgrade installs the new plymouth stuff *after* the new initrd is generated so the new initrd has the old plymouth?
CC: (none) => tmb
CC: (none) => ennael1, mageia, thierry.vignaud
The menuentry generated locally in the updated system (sda4) for itself in grub.cfg (saved as grub.cfg_local.txt) and the entry for it generated by os-prober in mga5 mate install (sda2) (saved as grub.cfg_mate.txt) differ somewhat. Booting from grub.cfg_mate.txt boots with plymouth Booting from grub.cfg_local.txt boots with black screen where plymouth should be --------------------------- diff -u grub.cfg_local.txt grub.cfg_mate.txt --- grub.cfg_local.txt 2015-03-14 10:09:05.714359712 +0000 +++ grub.cfg_mate.txt 2015-03-14 10:13:30.642408079 +0000 @@ -1,6 +1,4 @@ -menuentry 'Mageia' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-b6fd4dae-1031-45df-a031-999b7e9ae2f2' { - set gfxpayload=text - insmod gzio +menuentry 'Mageia 5 (5) (on /dev/sda4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-b6fd4dae-1031-45df-a031-999b7e9ae2f2' { insmod part_gpt insmod ext2 set root='hd0,gpt4' @@ -9,8 +7,6 @@ else search --no-floppy --fs-uuid --set=root b6fd4dae-1031-45df-a031-999b7e9ae2f2 fi - echo 'Loading Linux desktop ...' - linux /boot/vmlinuz-desktop root=UUID=b6fd4dae-1031-45df-a031-999b7e9ae2f2 ro splash - echo 'Loading initial ramdisk ...' - initrd /boot/initrd-desktop.img -} + linux /boot/vmlinuz BOOT_IMAGE=linux root=UUID=b6fd4dae-1031-45df-a031-999b7e9ae2f2 splash quiet resume=UUID=c9bc0f6d-5015-4a0a-959d-a07cadc83c88 + initrd /boot/initrd.img +} The major kernel command line differences seem to be that the locally generated one does not have 'ro' and does have 'quiet'.
Re-reading the above it looks wrong but no time just now to repeat and check.
Yes the last comment in #4 should have been: The major kernel command line differences seem to be that the locally generated one has 'ro' and does not have 'quiet'. However testing boots with 'quiet' and without 'ro' the plymouth splash still does not appear when booted from it's own local bootloader, but when booted from another system's grub2 from the entry generated by grub2/os-prober it boots with plymouth - just like the other clean installs from Mga5-RC in this same EFI VM. I'm out of ideas.
Summary: Upgrade from Mga4 does not update vmlinuz or initrd.img => Upgrade from Mga4 does not update vmlinuz or initrd.img symlinks and new initrd still has Mga4 plymouth
Did you do the upgrade with urpmi or via the installer GUI? If via urpmi, this is quite common. There is no way to say "update the initrds right at the end" with urpmi upgrades. Personally I always regenerate the initrds after urpmi has finished to make sure all is well. That said the symlinks not updating is weird although I did have something similar before on one of my machines due to some strange sysconfig file configuration which I was able to fix... if it's a clean MGA4 install however, this obviously shouldn't happen!
(In reply to Colin Guthrie from comment #7) > Did you do the upgrade with urpmi or via the installer GUI? This was using urpmi as per the Mga5 release notes in wiki. > If via urpmi, > this is quite common. There is no way to say "update the initrds right at > the end" with urpmi upgrades. Since this is required after plymouth changes, could this not be added in plymouth %post? > Personally I always regenerate the initrds > after urpmi has finished to make sure all is well. Maybe that should be added to the urpmi upgrade procedure in the wiki? > That said the symlinks > not updating is weird although I did have something similar before on one of > my machines due to some strange sysconfig file configuration which I was > able to fix... if it's a clean MGA4 install however, this obviously > shouldn't happen! Yes this was pretty much 99% clean, only installed a few days previous. The re-test was done using a clone not a completely new VM.
(In reply to Barry Jackson from comment #8) > (In reply to Colin Guthrie from comment #7) > > Did you do the upgrade with urpmi or via the installer GUI? > > This was using urpmi as per the Mga5 release notes in wiki. > > > If via urpmi, > > this is quite common. There is no way to say "update the initrds right at > > the end" with urpmi upgrades. > > Since this is required after plymouth changes, could this not be added in > plymouth %post? > NO! It's a bad design to rebuild all initrds for stuff like this... If you have some broken stuff on your system, it will break all initrds... rendering the system unbootable... That said, I will add conflicts to the kernel on too old plymouth / ... so it gets installed before kernel generates the initrd... That should add the correct mga5 splash to the latest kernel
(In reply to Thomas Backlund from comment #9) > (In reply to Barry Jackson from comment #8) > > Since this is required after plymouth changes, could this not be added in > > plymouth %post? > > > > NO! > > It's a bad design to rebuild all initrds for stuff like this... > > If you have some broken stuff on your system, it will break all initrds... > rendering the system unbootable... Understood > > That said, I will add conflicts to the kernel on too old plymouth / ... so > it gets installed before kernel generates the initrd... > > That should add the correct mga5 splash to the latest kernel I thought there had to be a way - thanks. Regarding the main issue in OP - do you have any ideas?
Can you please test using kernel 3.19.2-1.mga5 - conflict old mageia-gfxboot-theme to get mga5 theme in initrd (mga#15486)
Created attachment 6095 [details] urpmi output
Seems not to have worked, both kernel and mageia-gfxboot-theme are updated in the same transaction at line 881 (in attachment above), but the theme is still Mga4. I notice plymouth is updated much later, but not sure how this all glues together.
Ah hang on - I forgot about the other main issue - I only see the bootsplash in this system when booting from another system, and the other system will be using initrd.img which is pointing to the old initrd. I will edit the sysmlinks and report back.
Nope - still has old theme when symlinks are correct. dracut -f fixes it and new theme is shown. :\
@tmb I have a snapshot of the VM pre dracut if you need anything from there.
(In reply to Barry Jackson from comment #13) > Seems not to have worked, both kernel and mageia-gfxboot-theme are updated > in the same transaction at line 881 (in attachment above), but the theme is > still Mga4. Same transaction is OK as long as the gfxboot gets installed before the kernel but we got: 219/1739: kernel-desktop-3.19.2-1.mga5 260/1739: mageia-gfxboot-theme And I also see: 261/1739: kernel-firmware-nonfree So I suspect we have deploops so rpm breaks the ordering process to get past that
Hm, but we generate initrd in posttrans so it should have caught the stuff anyhow :/ I need to dig into this some more
Hm I guess I need to force plymouth too to get it to update its files too even if the graphical stuff is in the theme package... As for the symlinks not being changed, can you check the logs for some drakx complaints about: "not finding bootloader, only taking care of initrd" If you trigger that, maybe it skips the symlinking too
I saw the "not finding bootloader, only taking care of initrd" earlier when updating another EFI VM - I didn't pipe it to file though.
In another: http://mtf.no-ip.co.uk/pub/linux/Mageia/distrib/cauldron/x86_64/media/core/release/kernel-desktop-3.19.2-1.mga5-1-1.mga5.x86_64.rpm Generating grub configuration file ... Found theme: /boot/grub2/themes/maggy/theme.txt Found linux image: /boot/vmlinuz-desktop Found initrd image: /boot/initrd-desktop.img Found linux image: /boot/vmlinuz-3.19.2-desktop-1.mga5 Found linux image: /boot/vmlinuz-3.19.1-desktop-2.mga5 Found initrd image: /boot/initrd-3.19.1-desktop-2.mga5.img Found linux image: /boot/vmlinuz-3.19.0-desktop-6.mga5 Found initrd image: /boot/initrd-3.19.0-desktop-6.mga5.img Found linux image: /boot/vmlinuz-3.19.0-desktop-5.mga5 Found initrd image: /boot/initrd-3.19.0-desktop-5.mga5.img Found Mageia 5 (5) on /dev/sda4 Found Mageia 5 (5) on /dev/sdb1 Found Mageia 5 (5) on /dev/sdc1 done Cannot find a boot loader installed. Only taking care of initrd ---------------------------------------- lrwxrwxrwx 1 root root 32 Mar 19 23:28 initrd-desktop.img -> initrd-3.19.2-desktop-1.mga5.img lrwxrwxrwx 1 root root 32 Mar 4 20:39 initrd.img -> initrd-3.19.0-desktop-5.mga5.img
CC: (none) => remi
Any improvment on that side ? Some more information needed ?
Blocks: (none) => 15637
This one needs re-testing as I now also force the new plymouth before dracut runs
VM test in progress.
Created attachment 6207 [details] Full urpmi --auto-update output for upgrade Nice - all symlinks now correct and on first boot all themes were new so for me this is fixed. @tmb Attachment just for your reference. Also ll /boot [baz@localhost ~]$ ll /boot total 120144 -rw-r--r-- 1 root root 440 Oct 20 11:10 boot.backup.sda -rw-r--r-- 1 root root 154931 Jun 5 2014 config-3.12.21-desktop586-2.mga4 -rw-r--r-- 1 root root 162737 Sep 13 2014 config-3.14.18-desktop586-3.mga4 -rw-r--r-- 1 root root 162766 Nov 15 23:10 config-3.14.24-desktop586-1.mga4 -rw-r--r-- 1 root root 162799 Feb 7 00:30 config-3.14.32-desktop586-1.mga4 -rw-r--r-- 1 root root 176647 Apr 3 01:40 config-3.19.3-desktop586-1.mga5 drwxr-xr-x 2 root root 4096 Feb 27 19:33 dracut/ -rwxr-xr-x 1 root root 562176 Apr 6 22:55 gfxmenu* drwxr-xr-x 2 root root 4096 Apr 6 22:56 grub/ drwxr-xr-x 6 root root 4096 Apr 6 23:00 grub2/ -rw------- 1 root root 9437742 Apr 6 22:55 initrd-3.12.21-desktop586-2.mga4.img -rw------- 1 root root 8121635 Oct 20 11:09 initrd-3.12.21-desktop586-2.mga4.img.old -rw------- 1 root root 9396256 Apr 6 22:56 initrd-3.14.18-desktop586-3.mga4.img -rw------- 1 root root 8126228 Oct 20 11:18 initrd-3.14.18-desktop586-3.mga4.img.old -rw------- 1 root root 9393704 Apr 6 22:55 initrd-3.14.24-desktop586-1.mga4.img -rw------- 1 root root 8126457 Nov 26 00:23 initrd-3.14.24-desktop586-1.mga4.img.old -rw------- 1 root root 9397607 Apr 6 22:56 initrd-3.14.32-desktop586-1.mga4.img -rw------- 1 root root 8126341 Apr 6 22:04 initrd-3.14.32-desktop586-1.mga4.img.old -rw------- 1 root root 9453434 Apr 6 22:55 initrd-3.19.3-desktop586-1.mga5.img lrwxrwxrwx 1 root root 35 Apr 6 22:47 initrd-desktop586.img -> initrd-3.19.3-desktop586-1.mga5.img lrwxrwxrwx 1 root root 35 Apr 6 22:47 initrd.img -> initrd-3.19.3-desktop586-1.mga5.img -rw------- 1 root root 8890391 Apr 6 22:47 initrd.img.old -rw-r--r-- 1 root root 308314 Sep 23 2014 mageia.bmp -rw-r--r-- 1 root root 224968 Jun 5 2014 symvers-3.12.21-desktop586-2.mga4.xz -rw-r--r-- 1 root root 232476 Sep 13 2014 symvers-3.14.18-desktop586-3.mga4.xz -rw-r--r-- 1 root root 232836 Nov 15 23:10 symvers-3.14.24-desktop586-1.mga4.xz -rw-r--r-- 1 root root 232568 Feb 7 00:30 symvers-3.14.32-desktop586-1.mga4.xz -rw-r--r-- 1 root root 246288 Apr 3 01:40 symvers-3.19.3-desktop586-1.mga5.xz -rw-r--r-- 1 root root 2269020 Jun 5 2014 System.map-3.12.21-desktop586-2.mga4 -rw-r--r-- 1 root root 2425735 Sep 13 2014 System.map-3.14.18-desktop586-3.mga4 -rw-r--r-- 1 root root 2414528 Nov 15 23:10 System.map-3.14.24-desktop586-1.mga4 -rw-r--r-- 1 root root 2415217 Feb 7 00:30 System.map-3.14.32-desktop586-1.mga4 -rw-r--r-- 1 root root 2577160 Apr 3 01:40 System.map-3.19.3-desktop586-1.mga5 lrwxrwxrwx 1 root root 32 Apr 6 22:47 vmlinuz -> vmlinuz-3.19.3-desktop586-1.mga5 -rw-r--r-- 1 root root 3571984 Jun 5 2014 vmlinuz-3.12.21-desktop586-2.mga4 -rw-r--r-- 1 root root 3941536 Sep 13 2014 vmlinuz-3.14.18-desktop586-3.mga4 -rw-r--r-- 1 root root 3920464 Nov 15 23:10 vmlinuz-3.14.24-desktop586-1.mga4 -rw-r--r-- 1 root root 3923552 Feb 7 00:30 vmlinuz-3.14.32-desktop586-1.mga4 -rw-r--r-- 1 root root 4165008 Apr 3 01:40 vmlinuz-3.19.3-desktop586-1.mga5 lrwxrwxrwx 1 root root 32 Apr 6 22:47 vmlinuz-desktop586 -> vmlinuz-3.19.3-desktop586-1.mga5 [baz@localhost ~]$
Attachment 6095 is obsolete: 0 => 1
So closing as fixed
Status: NEW => RESOLVEDResolution: (none) => FIXED