Description of problem: Plymouth only displays ??? with this kernel. Reverting to kernel-desktop-6.4.9-4.mga9.x86_64 works correctly. Steps to Reproduce: Update to latest Mga9 kernel, reboot and plymouth display is replaced by ???.
Created attachment 14083 [details] output of journalctl -xb
CC: (none) => ghibomgx, marja11Assignee: bugsquad => kernel
Try as root dracut -fv And reboot Also try this https://bugs.mageia.org/show_bug.cgi?id=19642#c62 or other tips in the report
(In reply to katnatek from comment #2) > Try as root > > dracut -fv > > And reboot > > Also try this https://bugs.mageia.org/show_bug.cgi?id=19642#c62 or other > tips in the report Yes, thanks, rebuilding the initrd as above fixed it, but surely the initrd should be rebuilt during install of the new kernel shouldn't it? I'm obviously missing something.
(In reply to Barry Jackson from comment #3) > (In reply to katnatek from comment #2) > > Try as root > > > > dracut -fv > > > > And reboot > > > > Also try this https://bugs.mageia.org/show_bug.cgi?id=19642#c62 or other > > tips in the report > > Yes, thanks, rebuilding the initrd as above fixed it, but surely the initrd > should be rebuilt during install of the new kernel shouldn't it? > I'm obviously missing something. https://bugs.mageia.org/show_bug.cgi?id=19049 I don't see the default plymouth be affected before, but maybe it's related to your hardware
(In reply to katnatek from comment #4) > (In reply to Barry Jackson from comment #3) > > (In reply to katnatek from comment #2) > > > Try as root > > > > > > dracut -fv > > > > > > And reboot > > > > > > Also try this https://bugs.mageia.org/show_bug.cgi?id=19642#c62 or other > > > tips in the report > > > > Yes, thanks, rebuilding the initrd as above fixed it, but surely the initrd > > should be rebuilt during install of the new kernel shouldn't it? > > I'm obviously missing something. > > https://bugs.mageia.org/show_bug.cgi?id=19049 > > I don't see the default plymouth be affected before, but maybe it's related > to your hardware (In reply to Barry Jackson from comment #3) > (In reply to katnatek from comment #2) > > Try as root > > > > dracut -fv > > > > And reboot > > > > Also try this https://bugs.mageia.org/show_bug.cgi?id=19642#c62 or other > > tips in the report > > Yes, thanks, rebuilding the initrd as above fixed it, but surely the initrd > should be rebuilt during install of the new kernel shouldn't it? > I'm obviously missing something. If it wouldn't have created the initrd.img the first time, I doubt you could have booted. If you have preserved the older initrd .migand the grub.cfg you could try to find how the files differs from newer (working) to older. Probably it's some other bug somewhere else, e.g. in the draxk bootloader refresh code. It's not the first time that I loose pieces (especially with EFI). IMHO the security there should be also improved, as we have entries in \EFI\ disappearing without knowing which packages the files belongs tooand their checksums.
No I don't have the original initrd so maybe this should be closed until it maybe happens again.
(In reply to Barry Jackson from comment #6) > No I don't have the original initrd so maybe this should be closed until it > maybe happens again. Setting to unconfirmed for now. It can be closed as soon as your kernel is updated (unless it happens again, of course), there is a kernel in updates_testing.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
I assume operator have updated and not seen this any more. So closing. If you see this again please reopen.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => WORKSFORMECC: (none) => fri