Framework 11gen Linux - BIOS 3.20 error

[POSTHUMAN]

If you get an error after trying to update BIOS to 3.20, or if after updating of BIOS you check and see the old version, then:

If you want to update BIOS to version 3.20 for Framework 11gen on Linux, after unzip BIOS 3.20 on your USB, you need:

1. Go to dirictory efi
2. Go to dirictory boot
3. Open file startup.nsh and edit it, that last 2 sentence looks like this:
   FwUpdlcl.efi -F FWupdate.bin -Y -allowsv
   CapsulApp.efi winux.bin firmware.cap

This is a body of startup.nsh that give error

This is a body of startup.nsh that works fine

To be honest, I don’t understand why devs can’t just add -allowsv and delete -OD from the startup.nsh or maybe add it into the guide about updating BIOS in troubleshooting

[Artur]

Hi, not sure if this affected you, but what I had is:

• after powering on and selecting boot from usb it showed that something was already updated
• after automatic reboot it was installing update, but without any progress bar
• after booting and going back to bios I still had 3.17 version

What fixed it was plugging in my laptop to power! I did not see such suggession or any errors pointing to that. After trying again I had same error before automating reboot, but after automatic reboot there was a progress bar on the updating screen and it took quite a bit longer. Then BIOS showed updated version.

[Spence]

I understand your frustration. I knew about the requirement for the laptop to be charging and not just plugged in for the Windows Installer and LVFS method in older update versions and still forgot to plug it in after a distraction from my work flow.

Unfortunately, we should to be following published guides and not just finding the installer running it. I’m not suggesting this is what you did but mention it for the benefit of others that see this topic. Also, the current instructions do not state this for any installation method other than the Windows Installer and does not seem to appear for the EFI shell update in the instructions for any version of the BIOS update versions.

Reading the guide Framework Laptop BIOS and Driver Releases (11th Gen Intel® Core™) through older versions, it did state for the 3.17 version:

"
Instructions for Windows:

Plug your system into a charger before updating firmware.

"

…

"
Linux/LVFS

LVFS may not update if the battery is 100% charged. LVFS uses the battery status to determine if it is safe to apply updates. However if our battery is at 100% and the charger is off, we set the battery charging status to false. In this case you can discharge your battery a few percent, then plug in AC again and run fwupdmgr update.
"

I hope this helps someone in the future…

[Artur]

I was indeed using EFI shell update, so you can see how it was very easy to miss. There was no error message, the EFI updater seemed to have worked, but the update was not getting done. I have previously experienced firmware updates requiring having the laptop plugged in and/or over a certain battery percentage, so that’s why I guessed this is what is happening. I was going through forum posts before I have thought of this solution and nobody mentioned that. That’s why I decided to post what I did under 2 threads.