EDIT: Seems like people run into trouble. Run these commands as non-root. You’ll get password prompts when needed.
Installed successfully on Pop!_OS 20.04.
Switch to lvfs testing: fwupdmgr enable-remote lvfs-testing
Update firmware repo: fwupdmgr get-updates
Update fwupdmgr update
You can also install from GNOME settings in “Firmware” after enabling testing repo.
Framework will reboot and install the BIOS, spin the fans VERY loud for a few minutes.
After restart all works OK. Fingerprint reader, sound, Fn keys, etc. Cheers!
Confirmed the update works using the steps from Gio_Mag. I’m on Ubuntu 21.04. The system rebooted and the firmware update took quite a bit longer than I expected (several minutes) but did eventually complete successfully. The progress bar does not seem to move at a regular pace; it started out at around 40% and then quickly went to ~99% and then just sat there at “nearly done” for several minutes before it finally completed and rebooted. Not the best experience, but I’m just happy it worked at all!
Having the Framework firmware updates integrated into the Linux ecosystem like this is a huge deal. Thank you to the Framework team for making the effort.
@gjason, not sure but I’m running fwupdmgr without sudo… it’s asking for authorization AFTER you run get-updates and update…
Or try GNOME gui after get-update. What does it show?
Tried again, following the non-root fwupdmgr get-updates then fwupdmgr update route. Answered yes to the reboot prompt there, but nothing happened on reboot.
The whole process was running with AC connected and Secure Boot disabled (tried with enabled too, no change).
Still no luck getting the update to happen.
@Benjamin_Bridges since you’re on F35, presumably you also have the 15.4-5 version of shim* installed (dnf list installed shim*). I have 15.4-5 and I don’t see anything in updates-testing for this package.
I wonder if other configuration changes play a role here. Are you on an encrypted root FS? (shouldn’t matter since /boot and /boot/efi are not on root/encrypted, but I can’t think what else could be different here)
These are the two FW upgrade files I can think of that correspond to “staged” upgrades that aren’t being actioned on boot:
-rwx------. 1 root root 76418 Dec 5 12:42 /boot/efi/EFI/fedora/fw/fwupd-3b8c8162-188c-46a4-aec9-be43f1d65697.cap
-rwx------. 1 root root 35699096 Dec 5 12:42 /boot/efi/EFI/UpdateCapsule/fwupd-b3bdb2e4-c5cb-5c1b-bdc3-e6fc132462ff.cap
@Kieran_Levin Thanks a bunch. I was able to get it, and it seems to work fine. I was waiting for the mouse-after-suspend patch on fedora descendants, so hopefully it works.
@dimitris I just checked, looks like I was wrong. Everything seemed like it worked but I just checked and no dice. Everything looks fine but on reboot no update. My bad.
@Benjamin_Bridges thanks. Pattern seems to be Fedora-specific - AFAICT everyone who has successfully updated using LVFS has been on non-Fedora distros.
I’ll try to keep the follow-ups in the Fedora-specific thread then, to reduce noise in this one. There’s a reference there to a shim github issue that seems related, and whose fix appears to be addressed/merged in e.g. Ubuntu but only in the main branch and an as-yet unreleased release branch in Fedora.
I was informed before that BIOS 3.06 would fix the issue with increased voltage coming across the bottom left and top right expansion card ports, causing a safety shut off until reboot. I have installed 3.06 and this is still an issue. Is a fix being worked on?
Context: here is the original post where it is discussed that 3.06 fixed a high inrush current issue on the aforementioned ports.
