Your message dated Tue, 08 Apr 2025 23:01:56 +0000 with message-id <e1u2hx6-007pdp...@fasolo.debian.org> and subject line Bug#1091979: fixed in u-boot-menu 4.2.4 has caused the Debian Bug report #1091979, regarding u-boot-menu: Fails to add fdt or fdtdir entries to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1091979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: u-boot-menu Version: 4.2.3 Severity: normal Hi, I installed Debian Trixie on my MNT Reform with imx8mq with separate /boot partition and a snippet from the resulting /boot/extlinux/extlinux.conf looks like this: default l0 menu title U-Boot menu prompt 1 timeout 50 label l0 menu label Debian GNU/Linux trixie/sid 6.12.6-mnt-reform-arm64 linux /vmlinuz-6.12.6-mnt-reform-arm64 initrd /initrd.img-6.12.6-mnt-reform-arm64 append ro no_console_suspend cryptomgr.notests loglevel=3 ${bootargs} console=tty1 The lines that should contain an fdt or fdtdir entry are missing. Lets look at the sh -x output to figure out why they were not generated: 1 P: Writing config for vmlinuz-6.12.6-mnt-reform-arm64... 2 + _NUMBER=0 3 + _ENTRY=1 4 + [ -e /boot/initrd.img-6.12.6-mnt-reform-arm64 ] 5 + _INITRD=initrd /initrd.img-6.12.6-mnt-reform-arm64 6 + [ -e ] 7 + [ -e /boot6.12.6-mnt-reform-arm64/ ] 8 + [ -d /boot6.12.6-mnt-reform-arm64/ ] 9 + [ -f /boot/dtb-6.12.6-mnt-reform-arm64 ] 10 + [ /usr/lib/linux-image- = ] 11 + _FDT= Line 6 checks an empty value because U_BOOT_FDT is unset. Line 7 and 8 cannot work because there is a missing slash between ${_BOOT_PATH} and ${U_BOOT_FDT_DIR}. Line 9 finds /boot/dtb-6.12.6-mnt-reform-arm64 but the check in line 10 fails because {U_BOOT_FDT_DIR} is unset. Why is it unset? Because even though read-config found a separate /boot partition in has_separate_boot(), U_BOOT_SYNC_DTBS was set to false, so _FDT_DIR was never set to "/dtb-" and even if it were set to that, the check in line 10 would still fail because "/usr/lib/linux-image-" is not equal to "/dtb-". So to summarize: 1. why is a fdt or fdtdir line not added by default? 2. why are there missing slashes in line 7 and 8? 3. why do i have to enable U_BOOT_SYNC_DTBS? I already use flash-kernel for that 4. why is there a check for "/usr/lib/linux-image-" if _FDT_DIR gets set to "/dtb-"? One workaround is to set: U_BOOT_FDT_DIR="/dtbs/" which will then add fdtdir entries that look correct. The slashes are critical because they are missing in the u-boot-update script. Thanks! cheers, josch
--- End Message ---
--- Begin Message ---Source: u-boot-menu Source-Version: 4.2.4 Done: Vagrant Cascadian <vagr...@debian.org> We believe that the bug you reported is fixed in the latest version of u-boot-menu, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1091...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vagrant Cascadian <vagr...@debian.org> (supplier of updated u-boot-menu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 08 Apr 2025 15:33:04 -0700 Source: u-boot-menu Architecture: source Version: 4.2.4 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard <d...@jones.dk> Changed-By: Vagrant Cascadian <vagr...@debian.org> Closes: 1036730 1061687 1091979 1095811 Changes: u-boot-menu (4.2.4) unstable; urgency=medium . [ Johannes Schauer Marin Rodrigues ] * etc/kernel/post{inst,rm}.d/zz-u-boot-menu: check whether u-boot-menu is still installed before proceeding (Closes: #1061687) . [ Markus Burri ] * Separate devicetree overlay directory for each kernel (Closes: #1095811, #1036730) . [ Vagrant Cascadian ] * Use /dtbs/ directory when using U_BOOT_SYNC_DTBS, to avoid breaking installations where flash-kernel is installed. (Closes: #1091979) * debian/control: Update Standards-Version to 4.7.2. * u-boot-menu postinst: Do not call u-boot-update with a full path. * read-config: Mark as executable. Checksums-Sha1: 0af65a428153d2ba558e05bdf065e64d2ada4b1a 1055 u-boot-menu_4.2.4.dsc 17effd3e862ff929fc8a45a7388a3cca7fc5d8f0 15164 u-boot-menu_4.2.4.tar.xz 156993ba77bc482cf0f9a63e8675771ac3bfe3b0 5021 u-boot-menu_4.2.4_arm64.buildinfo Checksums-Sha256: 2d3a4b8464178b53f2358a68ac36daa1fa6bee0886619059805480e52d29bbe5 1055 u-boot-menu_4.2.4.dsc 39f66f1714754677a41045e73e685cd9710b9b4dec2e025195aeddd56fb33174 15164 u-boot-menu_4.2.4.tar.xz 163765f7eda22de75881d22dbb525d91006a2f4928394c38f983e2cbaf5a9b68 5021 u-boot-menu_4.2.4_arm64.buildinfo Files: d610637662ec371b7e145bb72494ca23 1055 admin optional u-boot-menu_4.2.4.dsc 12c3e189728d36e225d8e9178ada0908 15164 admin optional u-boot-menu_4.2.4.tar.xz d72fc5511a408874223faa07623c4eb3 5021 admin optional u-boot-menu_4.2.4_arm64.buildinfo -----BEGIN PGP SIGNATURE----- iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZ/WlwhMcdmFncmFudEBk ZWJpYW4ub3JnAAoJENxRj8h/lxaqeUAA/jqncq8WoxGaL+G/1bInpk81lc/O5Ua8 xIXqYIVCAKn1AQC1oi4DuiBE3XWkxARXiA4rzry9Yq7r+Z9WCusGdx+1BQ== =dFQY -----END PGP SIGNATURE-----
pgpk87xQJHlBo.pgp
Description: PGP signature
--- End Message ---
