You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have been trying update using fwupdmgr on many of Ubuntu based systems and its been working all good. In this specific instance after performing a reboot post fwpdmgr command, Im seeing 2 different types of errors(on 2 separate instance) and the systems takes a halt. It calls for a force reboot(hard reboot). After hard reboot the system boots and i happen to see the update to next version has been(when the error was capsule size - 0) done and sometimes it would have failed(Unable to open the file).
Attached are the snap shots of the instances that i have observed.
Thanks @hughsie. Our OS for device is confined to Ubuntu 22.04 and have a logical tie up to use 1.4 version. Just wanted to check, in case the upgrade to 1.6 is a non-starter then...is there a way to counter this issue and also your insights as why the file discovery is an issue, though i could see the file being intact before going for a reboot.
Some Observation -
Adding delay of about 30 secs after running fwupdmgr and then going for a reboot helps in discovering the file and reading it successfully. Not sure this logic has a relation to problem directly or indirectly. Can you please help me get the rationale here.
Hi,
I have been trying update using fwupdmgr on many of Ubuntu based systems and its been working all good. In this specific instance after performing a reboot post fwpdmgr command, Im seeing 2 different types of errors(on 2 separate instance) and the systems takes a halt. It calls for a force reboot(hard reboot). After hard reboot the system boots and i happen to see the update to next version has been(when the error was capsule size - 0) done and sometimes it would have failed(Unable to open the file).
Attached are the snap shots of the instances that i have observed.
More details -
FWUPD-EFI version 1.4
FWupdmgr - 1.7.9
Command used for upgrade -
fwupdmgr install --force --allow-older --show-all --no-reboot-check --no-remote-check --assume-yes --allow-reinstall -y -v $file
Every time, before calling fwupdmgr command, any stale *.cap file is cleaned up.
The ESP partition where the cap file is created has a space of 250MB.
Frequency of this issue -
Trying 2 cab file updates back to back (there is a reboot between each update). The issue gets uncovered for the second cab update.
Single cab update for the same cab file does not pose this error(attached).
The text was updated successfully, but these errors were encountered: