Hi.

Since you've been able to boot into a working kernel, you can now add support for vfat for the new kernel.

You can use "dracut" to add the vfat module to your new initrd.

Log in as root and do this (change desktop to server if it is appropriate):
# dracut --add-drivers vfat /boot/initrd-4.9.56-desktop-1.mga6.img 4.9.56-desktop-1.mga6 --force

You can now verify that the new module has been added:
# dracut --list-modules | grep vfat

Cheers,
Stig

CC: (none) => smelror

Pierre

Did You the steps provided by Stig?
Can You report (feedback us) with the results???

Thanks

CC: (none) => neoser10

No; that version was the only one I was unable to boot -- not my problem.  Currently:
$ uname -a
Linux prf.pfortin.com 4.14.13-desktop-1.mga6 #1 SMP Wed Jan 10 12:48:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Just had the same problem with 4.14.56 (reverted to 4.14.50).
Unless there's a requirement that I missed to change the EFI partition type from FAT to something else, vfat is required to mount /boot/EFI in order to complete the boot...

Resolution: WONTFIX => (none)
Status: RESOLVED => REOPENED

No, we still rely on vfat for efi, but for some reason it fails detection on your hw...

CC: (none) => tmb

What explains 'failing detection' on my hw, if all versions I used between 4.9.56 and 4.14.56 work[ed] fine?  
A quick peek at the 4.14.50 and 4.14.56 initrd files shows quite a reduction in content size from 40M to 15M...  seems reasonable to presume that's a lot of removals ($ l -R | wc):
4.14.50-desktop: 1260    1127   19883
4.14.56-desktop:  559     475    7632
4.14.50-server:  1268    1133   20001
4.14.56-server:   559     475    7632

Just updated kernel to 4.14.62 and had no fear about booting it since the initrd size was back to normal:

-rw------- 1 root root 19331857 Apr  7 14:58 initrd-4.14.30-desktop-3.mga6.img
-rw------- 1 root root 19498427 Apr  7 14:58 initrd-4.14.30-server-3.mga6.img
-rw------- 1 root root 19293485 May 29 08:57 initrd-4.14.40-desktop-1.mga6.img
-rw------- 1 root root 19458079 May 29 08:58 initrd-4.14.40-server-1.mga6.img
-rw------- 1 root root 19328797 Jun  3 15:58 initrd-4.14.44-desktop-2.mga6.img
-rw------- 1 root root 19496493 Jun  3 15:58 initrd-4.14.44-server-2.mga6.img
-rw------- 1 root root 19329203 Jun 27 20:16 initrd-4.14.50-desktop-2.mga6.img
-rw------- 1 root root 19494205 Jun 27 20:17 initrd-4.14.50-server-2.mga6.img
-rw------- 1 root root  7274437 Jul 31 23:53 initrd-4.14.56-desktop-1.mga6.img
-rw------- 1 root root  7275534 Jul 31 23:53 initrd-4.14.56-server-1.mga6.img
-rw------- 1 root root 19377603 Aug 13 16:42 initrd-4.14.62-desktop-2.mga6.img
-rw------- 1 root root 19376326 Aug 13 16:42 initrd-4.14.62-server-2.mga6.img

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Resolution: (none) => OLD
CC: (none) => ouaurelien
Status: REOPENED => RESOLVED