After installing uboot-tools on F38/RPi-4 fw_printenv and fw_setenv fails and are unusable, see below. Reproducible: Always Steps to Reproduce: 1.Install uboot-tools on RPi-4/F38 2.Run fw_printenv or fw_setenv Actual Results: Error message like "Cannot find file /etc/fw_env.config" Expected Results: Well... On my RPi-4, problem can be worked around by manually installing /etc/fw_env.config with contents like /boot/efi/uboot.env 0x000 0x4000 More context: https://groups.google.com/a/lists.mender.io/g/mender/c/_i2-SQ_IDdk/m/DS3T5UjvBAAJ
I bit sketchy, that was. Here is an example session after moving /etc/fw_env.config -> fw_env.config.bak $ sudo fw_printenv bootdelay Cannot parse config file '/etc/fw_env.config': No such file or directory Failed to find NVMEM device $ sudo mv /etc/fw_env.config.bak /etc/fw_env.config $ sudo fw_printenv bootdelay bootdelay=-2 $
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.