When you powered off the laptop, did you also unplug all devices and also unplug the power brick from the usb-c and wait more than 40 seconds before plugging stuff in again?
Yes, I unplugged everything including the charger.
- Try going into the BIOS and reset it to factory defaults. One of the bios options is something like that.
- Try resetting the main board. Following the pressing of the chassis open switch many time etc. Accurate instructions are on other threads. Search for “chassis open”.
Turns out it was my USB-C dock that I had connected to the laptop during the BIOS update that was the issue. I had to remove power from my Anker 568 dock and unplug it to fully power cycle the dock before it would work again.
1 Like
It’s a security feature. That way malware can’t downgrade your BIOS to use a previously patched vulnerability.
3 Likes
I just enabled lvfs-testing but I still don’t see any updates after running
fwupdmgr refresh
fwupdmgr get-updates
I don’t want to apply the update though the EFI file with USB because I’ve never before had a chance to use fwupd for UEFI updates and I want to see it in action.
Does anyone know how to get it to see the update?
fwupdmgr refresh --force
then
fwupdmgr get-updates
then
fwupdmgr update
$ fwupdmgr refresh --force
Updating lvfs-testing
Downloading… [ | ]
Updating lvfs
Downloading… [***************************************]
Successfully downloaded new metadata: Updates have been published for 0 of 6 local devices
$ fwupdmgr get-updates
Devices with no available firmware updates:
• Fingerprint Sensor
• HDMI Expansion Card
• Lexar SSD NM790 4TB
• System Firmware
• UEFI dbx
• USB2.1 Hub
No updatable devices
This is my current version checked with the dmidecode commmand from the knowledgebase:
Vendor: INSYDE Corp
Version: 03.03
Release Date: 03/27/2024
Address: 0xE0000
product: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
vendor: Advanced Micro Devices [AMD]
physical id: 4
bus info: cpu@0
version: 25.116.1
Is it possible to disable the anti-rollback using Smokeless UMAF(set the FAR switch to disable)? Similar to this(switching off instead of switching on on that reply). Generally some users like me don’t like some features and want to opt-out
I do not enable testing, but for me (fedora 41) I have:
Devices with no available firmware updates:
• Fingerprint Sensor
• SSD 990 PRO 4TB
• USB2.1 Hub
Devices with the latest available firmware version:
• System Firmware
• UEFI dbx
No updates available
look strange that you, at least, do not see latest firmware for ‘System Firmware’ and ‘UEFI dbx’.
what have you with
fwupdmgr get-remotes
@lpapadakos
You need to put sudo in front of those. The firmware metadata downloaded goes into a folder only root can write to, but any user can read.
e.g.
sudo fwupdmgr refresh --force
sudo fwupdmgr get-updates
Ok so I retried these same commands with sudo.
Still no UEFI update, but I got one for the fingerprint sensor (!) and installed it.
Then I opened the GUI utility gnome-firmware which AFAIK uses fwupd, and in it I could see the UEFI update, but only if the AC power was attached (the update stopped showing up in real time if I unplugged the laptop).
Even with the AC power attached, the commands (both with sudo and without) still showed no update.
As such I pressed the button inside gnome-firmware and it got to downloading and installing the update.
I assumed it would make a new UEFI entry to run the installation binary but efibootmgr -u reported no change from my normal efi variables.
gnome-firmware prompted me to reboot and I did. Then the update was installed, then it rebooted again with the new BIOS.
So I have these notes:
- Very nice and smooth experience from
gnome-firmwareand Framework in the EFI installer. - Somehow the ordinarily reliable option, the cli tool, was not working. I also don’t understand why there’s a difference between using sudo and not using it. If anything I would expect it to not run without root and show me an error message, if root is required for operation.
Interesting. What does give you?
fwupdmgr --version | grep 'org.freedesktop.fwupd'
Idle…: 0%
compile org.freedesktop.fwupd 2.0.1
runtime org.freedesktop.fwupd-efi 1.7
runtime org.freedesktop.fwupd 2.0.1
I use Arch BTW 
1 Like
Hmmm, it’s current. Best to file here: Issues · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub
Commented on your issue:
1 Like
Here it is:
Side note: I gotta say, it’s pretty cool that I can talk to someone from the OEM directly like this, and especially that said person caters to Linux installations for the equipment
6 Likes
I don’t see that option in my FW16 BIOS. So I don’t know if that’s possible. I can also understand wanting to roll back if it breaks functionality on previous working stuff.
Nobody is forcing a BIOS update on the computer. The user has to initiate it.
There is nothing wrong with staying with an old BIOS if everything is functioning as intended for the user. It is the additional functionality and security fixes that are being missed out on.
If there is concern about something not working; then by all means do NOT install a BETA BIOS and wait for the full release or even a few releases after. Again, if nothing abnormal is going on; leave it alone.
2 Likes
I have always done BIOS updates through the EFI in the past…
How do you know if you are downloading and updating a BETA bios with the fwupdmgr get-updates?
Does it give you a list and you can select each one individually like 1,2,4,7 or is it just all updates unless you specify which one on a command line? (Clearly I have not used Linux in a really long time)
It must not be packaged the same as EFI updates and every component has its own callout (i.e. EC, fingerprint, charger, system, left controller, right controller, WiFi, SSD, etc.)
Thank you @Kieran_Levin and your team for the hard work you are doing! Hat tip to @Matt_Hartley for always being on top of things! 
1 Like