That was pretty quick
Congratulations!
1 Like
AMD Ryzen 7040 Series BIOS 3.03 is ready for BETA release .
To recap the details from our recent email to our customers:
With BIOS 3.03 that we plan to ship on Batch 2 and 3 systems, we expect broader support in Linux across different kernel versions. In the meantime on 3.02, certain kernel versions have amdgpu drivers that result in the system hanging.
Note that 7040 Series is still a very new platform and AMD’s open source teams will continue to actively develop and improve Linux kernel driver support beyond the specific firmware fix in 3.03.
Here soon you will see the details and instructions to get 3.03 BETA for testing.
This thread will be the official beta test thread for this BIOS release. I have installed it and tested it myself on multiple laptops successfully.
LVFS support will be provided. Details coming soon. Stay tuned.
28 Likes
Thanks, bud!
1 Like
Did you change the BIOS version format from X.YY (such as 3.03) used in your Intel BIOSes to X.Y.Z (such as 3.0.3) in Framework Laptop 13 AMD Ryzen 7040?
An editor at Phoenix is using the X.YY version for the AMD BIOS in the comment below.
AMD apparently validated the new Framework laptop on Linux but did so on the 3.00 BIOS, only for the 3.01 BIOS to break things and in turn is what was pre-loaded on the reviewer units… AMD Linux folks were responsive in confirming and figuring out the solution. Now I’m just waiting on Framework to provide a new BIOS.
How does the result of the BIOS version printing command below look like on Fedora 39 beta on Framework Laptop 13 AMD Ryzen 7040?
$ sudo dmidecode -s bios-version
Below is my result on Framework Laptop 13 11 gen Intel as a reference for someone who is interested in.
$ sudo dmidecode -s bios-version
03.10
3 Likes
As a reference, here is a comment from Kieran for the 11th gen Intel BIOS version format, and linked BIOS information PDF file.
1 Like
Spoke to those in the know, there was a typo and it is fixed - 3.03
5 Likes
Thank you for confirming it. We are humans making mistakes. 
I hope that you will correct the version in your next email to avoid a small confusion for users.
Yep, we just made those changes as well. We’re moving very quickly and there were some typos in text only. Previous email included. New email is set and corrected from the appropriate teams.
1 Like
I can understand you guys moving very quickly. Thank you for editing to fix the typos in the first comment on this thread too. There is one remaining typo.
With BIOS 3.0.3
3 Likes
Fixed.
4 Likes
Cross quoting from a different thread:
I am one of the batch 1 folk, and I’m happy to run a bunch of tests using a bunch of different kernels and/or kernel patches. As I think I mentioned in the other thread, I compile my own kernels anyway. Testing a variety of kernels is trivial.
… but I can’t do any of that until my Framework actually ships. 
4 Likes
I have mine and I’d love to get support for more kernels. Is it only 6.5.6 and newer that are supported currently with BIOS 3.02? Do we know which kernel versions 3.03 will support? Do we have any sort of timeline for this BIOS beta being released?
Thank you!
My AMD Framework just arrived so I’d love to give 3.03 a try. Currently running Fedora 39 but after an update it seems to have issues while starting KDE. A systemctl soft-reboot does get it into a usable state, it’s just a bit silly to have to do that. dmesg shows that amdgpu resets, so I’m thinking this is related to that BIOS bug.
I’m seeing a lot of KDE does _____ with the new AMD boards. Very likely involving AMDGPU and the bios as you indicated.
We are very actively working on getting the next BIOS release squared away and once it’s ready for testing, it’ll appear on the forums.
6 Likes
I’m seeing a lot of KDE does _____ with the new AMD boards. Very likely involving AMDGPU and the bios as you indicated.
I’m actually having a similar issue with gnome on Fedora 39 Beta. I need to run systemctl restart gdm after everything boots up before I can actually see the login screen.
I put more on that being a Beta OS rather than on the BIOS! Would love if the upcoming BIOS update was the solution 
(Happy to trial 3.0.3 as well here!)
Arcolinux worked out of the box but would also prefer to have the newest firmware.
Would also like to be able to specify the amount of VRAM up to 16GB in the BIOS though I’m sure that’s a long shot.
OpenSUSE Tumbleweed is a little goofy. GNOME works as long as you use SDDM.
I’m having issues with fwupd for some reason. It was working 2 days ago, but now it’s timing out. I’ve tried blowing away everything including the uefi/tpm/secure boot- but the it’s still timing out. Maybe between updates? Having this issue in both Fedora 39 and Tumbleweed.
I’m interested in beta testing 3.03!
Any ETA on the next ubuntu C kernel or bios? Don’t need a date, just wondering if it’s days away or weeks away. Same with the ubuntu kernel fixes, is there anywhere to subscribe about that one? I haven’t seen a thread for it.
I ask because my only problems are really with the freezing of the device getting annoying at times.
I’m having issues with fwupd for some reason. It was working 2 days ago, but now it’s timing out. I’ve tried blowing away everything including the uefi/tpm/secure boot- but the it’s still timing out. Maybe between updates? Having this issue in both Fedora 39 and Tumbleweed.
I’ve had some issues with this on Arch as well, where the fwupd service times out trying to do something with the fingerprint reader. Since I haven’t yet been able to get the fingerprint reader working anyway, I removed the fprintd service, and haven’t had any issues with it since.
I’m also interested in testing 3.03, if we still need testers!