Fixed. The problem was not the new bios, but an incomplete removal of VMWare workstation. Once I removed the kvm_amd module and reinstalled it virtualbox VMs ran fine. Sorry for the false attribution.
Correction. Kernel 6.12 defaults to automatic kvm loading, and blocking that fixed the issue (kernel command line addition: kvm.enable_virt_at_load=0, thanks to Mario L., aka superm1). VMWare residuals were probably not the problem.
This is noted in the VirtualBox v7.1.4 release notes : VirtualBox 7.1.4 released - virtualbox.org where it is related to kernel 6.12.
Is it possible the kernel was upgraded at the same time as the BIOS ?
I’m not sure any supported O/S ship with a kernel newer than 6.11, or even that new ! Ubuntu 24.10 (not supported) is only 6.11, for instance.
Thanks for the upgrade.
Is it possible to roll back this BIOS upgrade to the previous version?
Yeah, I updated the kernel, the new BIOS, a new beta release of virtualbox, and installed (and removed) vmware workstation pro all in quick succession. Bad, bad, bad sysop behavior.
The beta virtualbox had a minor bug with guest additions not running the standard video mode properly, VMware didn’t uninstall its kernel modules, the 6.12 kernel update changed kvm loading (the actual cause of the failure), all adding to my self-caused confusion.
Apparently it’s not possible.
Does this not work?
I was also asking this as the current FW16 BIOS 3.05 has an “imortant note” saying:
- After updating to this version you will not be able to downgrade to an earlier version.
I understand that this means you can’t downgrade the specific BIOS upgrade for the FW16.
Now the notes to this FW13 BIOS update do not mention this topic.
But since this is a very important fact, I want to know if this BIOS upgrade can be downgraded again. @Kieran_Levin : could you please let us know?
@everybody else: please do not answer if you don’t know for sure (f.e. made the downgrade yourself).
hum
it seems the note for this BIOS version for the framework 13 is explicit:
https://fwupd.org/lvfs/devices/work.frame.Laptop.Ryzen7040.BIOS.firmware
Please note that after upgrading to this version, you cannot downgrade to a previous version.
running Pop!_OS 22.04 here, I updated it yesterday via *Linux/Other/UEFI Shell update * method (USB). No problem so far.
FW booted successfully right after installation. Suspend works. Bluetooth works fine. Virt-Manager (qemu/libvirt) works fine.
Kernel is 6.9.3
edit: “Linux/Other/UEFI Shell update” not “Linux/LVFS”
IMHO this should definitely be mentioned in the announcement here.
I have the exact same problem as you, the 2.8k screen works fine on my 7640u, but the diagnostic led came on a short while after booting into Windows. I just updated to 3.06 and at the moment, it seems the diagnostic led problem is gone.
Thanks for taking care of the IRQ1 wake issues!
I do have a new problem for a few days, probably since installing installing BIOS 3.06: The charging light constantly switches between charging (orange) and charged (white), as soon as the battery has reached the desired state of charge. I have limited the battery charger to 86%.
No ill effects here. I too got the fingerprint scanner update at the same time.
Kubuntu 24.10 with AMD Ryzen 7840
I had a small issue when updating to 3.0.6 (white screen, see Github issue), but my real hope was that the frequent blue screens in W11 when running on battery will end (those are preceded by sluggish mouse movement, then W11 bombs without leaving a crashdump), unfortunately this has not proven true.
As this is an upgrade from a Lenovo windows setup, there might be any reason for it, however all drivers, all hardware entries have been removed, and W11 inplace reinstall has been done. Reinstalling everything will be a multi day effort, so I’ve been reluctant without knowing the exact reasons for the bluescreens.
I’m finding the fingerprint reader almost never works since the BIOS upgrade from 3.05 to 3.06.
Anyone else finding the same?
Or maybe it’s just that it’s no good in the cold Winter weather that arrived around the same time?
ADDED LATER: Yes, it seems it was the change in temperature. My fingers seem to need to be very slightly moist for this fingerprint reader to work.
I have ectool fwchargelimit 70 and a 140w USB-C power adapter, and the charge light is pulsing about 1/second as it drops below 70% then gets above 70%. Is this expected?
K3n.
no more keyboard functioning properly, every keys pressed is typed like 7 or 8 times and the keyboard is extremely laggy.
running OpenBSD 7.6 on framework AMD Ryzen here, tested with OpenBSD latest snapshot and same situation, I cannot use my laptop anymore… I guess that’s the payment for attempting BETA 
Can i rollback to 3.05 or will it break even more?
@eau
If you plug in an external keyboard does it work? I.e. is the problem only with the laptop keyboard?
There was a discussion about it on this thread so read up if you want, but the answer is: No, you can not downgrade.