Which Linux distro are you using?
Debian GNU
Which release version?
Linux 12 (bookworm) + snap LVFS (fwupd 2.0.18 → from forky?)
Which kernel are you using?
Kernel 6.1.0-41-amd64
Which BIOS version are you using?
0.0.4.1 → 0.0.4.2
Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series)
Processor: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics
Memory: 57387MB (64Gb physical)
OpenGL Renderer: AMD Radeon Graphics (gfx1103_r1, LLVM 15.0.6, DRM 3.49, 6.1.0-41-amd64)
In between the lines I’ll explain what happened. The exact output is not captured unfortunately, just the commands with the “history”.
READ FULL before trying to install or update anything!
In advance the default state: Debian 12 bookworm with freshly compiled Python 3.12.12 and as fallback 3.11.8.
First I am successfully updating to 0.0.4.1 FW with the keyboard and numpad update.
Command list for all committed commans related to this “experiment”:
442 fwupdmgr enable-remote lvfs-testing
Getting the newest testing FW-s, on the downloadpage it said in this version, is not included in the stable versions.
443 fwupdmgr get-updatesfwupdmgr refresh --force
444 fwupdmgr refresh --force
445 fwupdmgr get-updates
446 fwupdmgr update
nothing from bookworm repo.
447 sudo snap install fwupd --classic
455 sudo snap install core
458 snap run fwupdmgr get-devices
459 snap run fwupd.fwupdmgr --version
now getting somewhere: the fwupd is on the desired version.
460 snap run fwupd.fwupdmgr get-updates
nothing.
462 sudo snap refresh fwupd --channel=latest/edge
no help from this chanel.
464 sudo systemctl stop fwupd
465 sudo systemctl disable fwupd
466 sudo systemctl mask fwupd
the problem was the original fwupd from the repo is running it’s own service and getting the “another service has claimed the dbus name org.freedesktop.fwupd” so stop and mask the non-snap version.
467 sudo snap restart fwupd
468 sudo snap run fwupd.fwupdmgr --version
469 sudo snap run fwupd.fwupdmgr refresh
470 sudo snap run fwupd.fwupdmgr get-updates
471 sudo snap run fwupd.fwupdmgr update
Now the download is completed. the 0.0.4.2 is on the computer, but the daemon cant make restart the laptop, cant make the “/run/reboot-required.XXXXXX”: Permission denied.
473 sudo snap connect fwupd:system-observe
475 sudo snap connect fwupd:mount-observe
476 sudo snap connect fwupd:modem-manager
Not helping same error.
477 sudo snap run fwupd.fwupdmgr update
478 sudo snap run fwupd.fwupdmgr update --force
479 sudo snap run fwupd.fwupdmgr update --no-reboot-check
Nothing. Atleast the good version is running the bookworm (2.0.18).
480 sudo snap remove fwupd
482 sudo snap install fwupd --devmode
483 sudo snap start fwupd
484 sudo snap run fwupd.fwupdmgr update
Could not activate remote peer: activation request failed: unit is masked. So in the systemctl the fwupd is masked… now this is the reason.
486 sudo systemctl unmask fwupd
***This is the point where it is starting to be interesting: (or if you have interest repeating after me). After this point on my OS the KDE Discover for FW updates is not working, because the snap version of the fwupd is not connected to the KDE!
487 sudo apt remove -y fwupd
488 sudo apt autoremove -y
489 sudo snap remove fwupd
490 sudo snap install fwupd --classic
Removing everything (including the base repo’s installation) and reinstalling the classic snap version.
491 sudo snap start fwupd
492 sudo snap run fwupd.fwupdmgr --version
493 sudo snap run fwupd.fwupdmgr update
494 sudo snap run fwupd.fwupdmgr get-updates
Same error, cant make the reboot request.
495 sudo snap run fwupd.fwupdmgr update
496 sudo snap run fwupd.fwupdmgr get-updates
NOW asking if I want to upload the logs from the BIOS update… no because it not happened yet, but we are a reboot away! (tought by me…)
497 sudo reboot
System turn off. System start, memory ckeck, BIOS update started! Runned along, Update Successfull! Restarting…
black screen, fan: 100%. After 20 min, Long press on the power button and start again: BIOS UPDATING 0.0.4.2→0.0.4.2… 2 more time again without the 20 min wait. Damaged BIOS file or broken updater application?
On this point I was hopeless… “I’m bricked my laptop in an update loop.”
How next: removed the power adapter… the updater failed. Then restarted, and again. After 3 failure: THE GRUB IS BACK! The BIOS did start 0.0.4.2.
good. “Now get one usb stick and get the EFI updater.”
The last thing: getting reinstalled from the EFI installer, because this was more then my heart can handle.
EFI installer was good on the first try, did the 0.0.4.2→0.0.4.2 and no fail.
Update successful.
498 sudo snap run fwupd.fwupdmgr --version
499 sudo snap run fwupd.fwupdmgr get-updates
Lastly checking the versions and uploading the statistics from the update.