I don’t know if I have ever looked into it too deeply before, but can anyone clarify if I originally downloaded a beta version of the bios and it has now changed/updated to stable, is it the same “version” just relabled stable? Or, if there were minor changes that occurred, I need to download again?
Yes it’s just the same version. No need to update again to the same version. You can verify by running a hash (such as md5) against the beta and “stable” downloads to see they are exactly the same.
So again, they are marking a version we are all having throttling issues on as “stable”…….sigh.
EDIT: Oh, and this 4.02 has also regressed to waking the computer up (from sleep) when power is connected or disconnected. This happened on 3.06 and 3.07, and was one of the many reasons I downgraded back to 3.05. Seems we are unable to get anything better than 3.05 for our FW16s. Yeah…..but it’s “stable”, heh.
4 Likes
Since updating to 4.02, the computer complains on every boot that the keyboard and numpad are outdated. No updates to either device show up in fwupdmgr.
At least the computer seems to work anyway, but the BIOS warning is annoying. :-)
1 Like
Please update your keyboard https://knowledgebase.frame.work/keyboard-firmware-update-framework-laptop-16-r1LayV4Age
I’m having this issue too, That link says to run fwupdmgr get-updates && fwupdmgr update, however this does not see any updates. Is it possible the keyboard updates are still labelled beta?
This link, seems to suggest that the update is “Not suitable for production systems”
How though? Those instructions don’t work.
Edit: I got the UF2 instructions to work, though it was a little bewildering as well. Copying files without a working keyboard was… interesting. 
Thanks for clarifying for me, much appreciated. And dang it that’s a bummer. Apparently I am going to have to test mine again to see if it is affected by the sleep/wake throttle issue. I’ve been trying to follow what folks are posting for each version since 3.06 and it definitely seems to be a trend that we go back and forth on somethings and others have carried all the way through. Super unfortunate. Funny thing (sarcasm) is, I will likely be starting from square one once my AI 370 gets shipped in batch 1. Hoping since they have had it out for the 13 first they at least have a better grip on what direction to take it as it lands in the homes of consumers for the 16.
Always have an external keyboard for that type of operations
I am having the same issue. The firmware has probably not synced over to the servers we use yet. But 5 days is a long delay for that.
1 Like
If fwupdmgr get-updates isn’t finding the update yet, you can download the .cab file from LVFS: Laptop 16 Keyboard - ANSI and then run fwupdmgr local-install filename.cab (i.e. fwupdmgr local-install 53bafa8c884106d1d996201a5f672c612a563880fdfef18448b823b9692dbcb6-framework_ansi_0.31.cab). No need to figure out how to copy files without a working keyboard.
P.S. That’s for the ANSI keyboard. Numpad link is LVFS: Laptop 16 Numpad, and if you have other keyboards then follow the links from Keyboard Firmware Update (Framework Laptop 16) to get the appropriate .cab file.
1 Like
After BIOS update today via fwupdmgr from 3.x to 4.02 my external screen which is plugged in via USB-C module and a USB-C to DisplayPort cable stopped working. The external monitor is no longer recognized. I have tried many things already, among them resetting BIOS to default values via F9 key, turning off monitor and Laptop, unplugging both from the power supply for some minutes, unplugging and reinserting all modules into the FW16 including the USB-C/TB module I’m using to connect to my monitor, etc.
The only thing that works is replacing my USB-C module with the DisplayPort module and using the thick and rigid DisplayPort cable again. However, this is not a satisfactory solution for me, as I also need to use the USB-C module from time to time. Please look into the issue and provide a BIOS update that resolves this problem.
PS: Using Fedora 43 with all updates installed. I still have the AMD Ryzen 7 7840HS CPU with discrete AMD Radeon RX 7700S GPU.
what monitor are you using. I’ve updated to 4.02 and do not have any issues with my usb-c monitor ASUS-MB16AC and ASUS-MB16AMT
I’ve just done the update using fwupdmgr as described at the top of this topic on Arch and got updated to 3.07.
No further bios or keyboard/numpad updates available.
I think the problem is that LVFS won’t automatically upgrade the firmware because it’s tagged as unstable, hence it will show no update available.
Realistically, the fix is for Framework to promote it to stable status so automatic upgrades will happen
2 Likes
I’m using the IIYAMA ProLite X4071UHSU-B1. It’s an older model but I didn’t have any problems before the update.
You could try enabling the lvfs-testing repo by typing
fwupdmgr enable-remote lvfs-testing
and after that
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update
But of course, this is at your own risk, as they are still beta drivers.
I received an email from Framework this morning, Software updates for your Framework Laptop 16 (AMD Ryzen™ 7040 Series) - BIOS 4.02 and Windows Driver Bundle v3.01.
No mention of beta.
Perhaps they should have made the update available before sending out the email!
1 Like
I’m experiencing a similar issue. Philips 1000 series monitor through an Anker 14 in 1 dock, laptop has Ryzen 7840 and the 7700 GPU. The problem occurs with windows 11 and Mint 22.2, very occasionally it picks up the external monitor correctly but prior to bios 4.0 it had worked flawlessly for approaching a year.
Same issue. RGB keyboard. Seems to still be working but BIOS warning every time.
I guess I need to go find the 3.05 BIOS…
I’m on Windows and I’m using RGB keybiard. I updated it to the latest version and I do not have any issues. It looks like it is not marked as stable, but one of the user shared details how to update it in linux Framework Laptop 16 BIOS v4.02 and Driver v3.01 Releases (AMD Ryzen™ 7040 Series) STABLE - #29 by Robin_Munn
Would love to see this fixed in LVFS – I have been trying to update for a day or so to no avail and I’m glad to see I’m not the only one.