Hello, my arm devices are not booting anymore :party: ! After two hours debugging, I solve my issue and dig into the root cause. For my BananaPro (armv7hl) that I installed with mageia7 and updates, I'm not using grub2, but u-boot with extlinux.conf which worked pretty good, out of the box. Now the issue, the fdtdir is just not present in the extlinux.conf file, which prevent to boot the BananaPro (all my aarch64 does not boot neither, but I can not access them so I can not say if it is a related issue) drakboot is generating this extlinux.conf for u-boot, in this order: > https://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm#n1582 (focus on line 1601) > https://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm#n1036 (focus on line 1076) > https://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm#n133 > https://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm#n88 This is not aligned anymore with what the kernel package provides: > https://svnweb.mageia.org/packages/updates/9/kernel/current/SPECS/kernel.spec?view=markup#l1396 After manually editing the /boot/extlinux/extlinux.conf file and providing the fdtdir entry for installed kernel, the board boots. Please align drakx tool and kernel package.
CC: (none) => ghibomgx, thierry.vignaud
/boot/extlinux/extlinux.conf : cannot find its origin. extlinux.conf : same fdtdir : same Must be Arm specials. bootloader.pm is from drakxtools-backend. Assigning this intially to tools, CC'ing kernel. Reverse this if appropriate.
Source RPM: drakxtools kernel => drakxtools, kernelCC: (none) => kernelHardware: All => armv7hlAssignee: bugsquad => mageiatools