I guess now it's a bit late to warn people not to update the firmware on their #framework laptops, but here is what somebody did to fix them, when the company didn't help. at all.
quantum5.ca/2026/08/16/fixing-…
spoiler: it ends well, but not thanks to framework
also, the ending of the article is *epic*.
Fixing a bricked AMD 7040 series Framework 13” laptop with $20 tools
My experience fixing my Framework 13” laptop with AMD 7060 series that was bricked due to a failed BIOS update with US$20 worth of tools, instead of replacing the motherboard as suggested by Framework support.Quantum
like this
reshared this
Caleb Maclennan
in reply to Elena ``of Valhalla'' • • •Elena ``of Valhalla''
in reply to Caleb Maclennan • •@Caleb Maclennan sorry, “warn people not to upgrade their firmware *right now*”
unless their current version has been fixed, and it's no longer bricking their laptops requiring an expensive motherboard change.
(admittedly, I think it's already been a few weeks and it's possible that the current firmwares are working, I don't have a firmware laptop to check)
Thad
in reply to Elena ``of Valhalla'' • • •Well, shit, I've got that model. And purchased it just over a year ago.
It's currently running but I'm not sure if I've flashed that update or not; guess I better check (and if not, figure out how to block it to make sure I don't). Thanks for the heads-up.
Elena ``of Valhalla'' likes this.
Thad
in reply to Thad • • •Okay, I think I got it figured out; I ran fwupdmgr get-updates, found the GUID under "System Firmware", and added "DisabledDevices=[guid]" to /etc/fwupd/fwupd.conf.
Hopefully that works; obviously I'll try to keep an eye on what I'm updating and hopefully I'd catch it if it ever did try to update the system firmware, but it's good to know there's a net in case I make a mistake.
Thanks again for the heads-up. That could have been a real headache.
Elena ``of Valhalla'' likes this.
Andrew Bartlett
in reply to Elena ``of Valhalla'' • • •