Updating via EFI, it’s been stuck like this for a while now, does that mean it’s done ?
Sorry for the dumb question and thanks for any answer
@Matt_Hartley @Kieran_Levin Any feedback on the charging issues with BIOS 3.03? Not only about the Steam Deck Chargers not working at all, but also about showing a battery full LED when the battery isn’t completely charged.
1 Like
I had the same issue earlier in the thread, as long as you have the 4 green checkmarks in the bottom right, you can press the power button to turn off. You will want to re-run the BIOS update to properly downgrade the PD firmwares, which didn’t work for me until I used the official Framework charger during the BIOS update.
For some reason, when using my apple charger, the BIOS update would hang at that exact spot.
1 Like
Strange though, because I did use the framework charger. Everything seems to be working fine so far anyway. Thanks for the reply
While it should charge with compatible chargers, my focus is does it work as expected with Framework chargers with this particular release. It does with Framework chargers.
If there issues with other compatible chargers, feel free to open or add to a thread and we can get this to the engineering team.
Per our guide and per AMD, no, this is not to be used. This is for Intel only.
If it’s set on AMD it’s going to cause major problems for suspend.
2 Likes
With the overwhelming benefits seen in upgrading 3.02 to 3.03, I am pleased to announce we are releasing 3.03 as a release and is no longer beta.
Feedback given on this release has been cataloged and passed on.
13 Likes
Does this mean the current 3.03 is now considered stable or will there be a different release of 3.03 as stable? This is a little ambiguous to me.
1 Like
As with previous BIOS updates that have gone from beta to release, there is no change to the BIOS update file, it will just be linked as release on the BIOS/Drivers page on the support site. If you have already updated to 3.03 you don’t have to do anything else, and you can even recommend others come to this thread to get the installer file (otherwise they can go here: Framework Laptop BIOS and Driver Releases (AMD Ryzen™ 7040 Series) though it seems this page has yet to be updated with the new release as of the writing of this response).
3 Likes
It’s updated.
1 Like
Correct. Today was the last day of beta. 3.03 is the stable release - we want folks off of 3.02.
4 Likes
Can confirm. I thought I was hallucinating that it ever worked, but I’m glad I’m not the only one. Thankfully, my primary charger (a 60 W Aukey dual port GaN charger) still works.
Not sure where to post this to be most useful to the FrameWork people updating the Knowledge Base: The french Knowledge Base BIOS and driver update article, which is ironically written in English, is not up to date. The driver bundle linked is an old one, and it has no link to the 3.0.3 BIOS, stating: “No New BIOS at this time. The Factory-Installed BIOS (3.03) is the latest version”.
EDIT1: wording
EDIT2: This is actually true for all non-English versions of that article, only the English (US) version is up to date.
1 Like
Yeah, fair enough. But since I already had a couple chargers laying around, I decided against getting another one.
I already added the bug to this thread (since it was introduced by BIOS 3.03) and linked Kieran + you. Am I supposed to create a new thread solely for this issue?
Those who tested 3.03 in beta but who don’t want to opt-in beta releases from LVFS in general may now want to disable the lvfs-testing remote :
fwupdmgr disable-remote lvfs-testing
7 Likes
I actually had a similar problem, but from within Windows 11. While I tried updating the BIOS to 3.0.3 (Beta) the official charger stopped working when Windows rebooted to initialize the FW update. This in turn made the BIOS update fail. The charger I then used (Dell 65W from my XPS 13) worked.
For what it’s worth, there’s a newer AMD GPU driver available for Windows (direct from AMD) as of yesterday. It’s only been a day but this one seems to be a little more stable than the previous one for me, which had crashed 3 or 4 times.
Hi, I can’t get BIOS 3.03 to install via fwupdmgr. It says successfully installed firmware, prompts me to reboot, but then throws EFI Error Code: 03 after reboot.
I’m using Fedora 39 Beta. Already run dnf update. Three USB-C + one USB-A modules attached. Anker 737 PD adapter plugged in. Fingerprint reader already updated / working.
I’ve taken steps to attempt the “Linux/Other/UEFI Shell update” method by unzipping the archive in the root directory of the EFI partition of a Linux Mint installer I have, but I’m uncertain if I should really just drop the unzipped folder into any random EFI partition on any random USB drive I have laying around, regardless of the other files that already exist in the partition. I don’t want to brick my system.
Step 5 states, “Let startup.nsh run automatically,” implying I should either be able to see the file, and select it, or it should just start the update on its own (perhaps after navigating to the directory / partition that contains it?). I can browse the directories in the EFI partition, but I only see .efi files, not the .nsh file.
Any help you can provide would be super appreciated! 
I don’t have my AMD laptop yet, but I’ve done the UEFI shell update method on my 11th gen FW13. I took a blank USB stick, extracted the folder and copied only the files (not even the folder, just the files from the folder) onto the otherwise blank USB drive. Then with the USB drive still connected to the computer I re-booted and used F12 to get into the boot menu. I chose the USB drive and the firmware update ran. When the firmware update finished the system rebooted and I went into the BIOS and confirmed the updated firmware. Removed the USB, exited the BIOS and the system booted normally, with updated firmware. I’ve heard that this method cause issues in some cases, but I had zero issues.
Thanks! I tried this, and made progress. In that it recognized the USD drive, and automatically started the process when I selected it, but then I hit the same roadblock a bunch of other people seem to be getting: Error Code: 21.