I installed this on my laptop with the 2.8k display and Linux. The installation proceeded without issues, though I did have to wipe the /var/cache/fwupd directory and rerun sudo fwupdmgr refresh in order to get it to show up. On the first reboot after installation, it printed a bunch of usb usb1-port1: Cannot enable. Maybe the USB cable is bad? messages to the kernel log and the Ethernet module wouldn’t work. I shut down the system, removed power, and waited for the EC to shut down (when the lights on the Ethernet module turned off). After plugging it back in and booting again, everything seems to be working fine. That’s not a new issue though; I have noted USB screwiness on the first boot after previous firmware updates too. Other than that, everything seems to be working fine.
Yes, it (virtualbox VMs) worked before the bios update. I re-ran the module install, and also reinstalled the whole package, svm is listed by “cat /proc/cpu” for each cpu. Something changed with the bios update.
The full error message:
VirtualBox can’t enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE).
| Result Code: | NS_ERROR_FAILURE (0x80004005) |
|---|---|
| Component: | ConsoleWrap |
| Interface: | IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} |
rmmod amd_kvm didn’t help
FWIW, qemu/libvirt unaffected for me under Arch.
Thank you, that is helpful info.
Finally! Hallelujah.
I used the EFI shell updater, yesterday; all working great so far. Including staying suspended when plugging/unplugging power, and closing the lid, while still being able to wake with a keyboard button press. 
Recent kernels have included a workaround; did you happen to test with that disabled by any chance?
The kernel workaround/quirk is only enabled for specific firmware versions, so it is automatically not enabled for this latest version 3.06
This came up when firmware 3.05 was released, without the EC firmware fix, requiring the kernel workaround/quirk be extended to another firmware version: Framework Laptop 13 Ryzen 7040 BIOS 3.05 Release and Driver Bundle - #16 by Mario_Limonciello
Of course; my memory misfired a bit previously, thanks for the reminder!
I think that the ACPI TPM2 table is broken in 3.06, but from what I can tell it was the same in 3.05.
I use VMs alot so this was an important check for me also. Default settings on bios inc auto gpu memory.
No issues with virtualbox OS edition(ubuntu repo) on 24.04, I did install boxes and it complained about not being able to access the kvm module though. This was the first time i ran boxes though so cant rule out misconfiguration gremlins.
svm and svm_lock are both in my cpu information. framework 13 7640u / 24.04.1, 32gb kingston 5600 jdec ram
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.