Bug 2230475 - fw_printenv and fw_setenv unusable after installation
Summary: fw_printenv and fw_setenv unusable after installation
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: uboot-tools
Version: 38
Hardware: aarch64
OS: Linux
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2023-08-09 14:44 UTC by Alec Leamas
Modified: 2023-08-11 12:35 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: ---

Attachments (Terms of Use)

Description Alec Leamas 2023-08-09 14:44:25 UTC
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:  

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

Comment 1 Alec Leamas 2023-08-11 12:35:53 UTC
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

Note You need to log in before you can comment on or make changes to this bug.