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!
Is it possible to distribute the firmware another way than fwupd? I cannot get the fwupd service to start on my system. It just hangs. I’ve disabled fprintd as others have suggested.
https://community.frame.work/t/amd-ryzen-7040-series-bios-3-03-beta-release/37479/20?u=zach1
This happened to me.
The only way is to download a free windows iso and then install it. Download the framework windows 11 driver bundle and it will correct the fingerprint firmware.
I’ve experienced similar timeouts with fwupd trying to get the fingerprint sensor working, however adding those 2 lines mentioned at the end of the guide to this file usr/share/fwupd/quirks.d/goodixmoc.quirk actually fixed the issue for me and now I can use the sensor.
I’ve experienced similar timeouts with fwupd trying to get the fingerprint sensor working, however adding those 2 lines mentioned at the end of the guide to this file usr/share/fwupd/quirks.d/goodixmoc.quirk actually fixed the issue for me and now I can use the sensor.
Good callout, I just got fprintd re-enabled and working correctly with GDM and the GNOME lock screen, and fwupd is happy too. Now just patiently waiting for updates to be available there. The sensor works without the quirks file, but the quirks file is needed for fwupd
For everyone playing along at home:
2 Likes
About the fwupd I’ve managed to run it using X11 to avoid the amdgpu timout errors and it worked fine.
I’ve used the live version of Manjaro XFCE for that.
2 Likes