Did it work before?
If you re-run the VirtualBox module install, what happens?
The command is ''sudo rcvboxdrv setup’ (from Installation Details)
I upgraded the BIOS on my Framework with the 2.8k screen, I haven’t noticed any issues so far. The one thing I’m missing on the BIOS still is an option to enable ReBAR for the eGPU; is it on the radar?
For Virtual machines to work on FW13 AMD, you need “SVM”.
So, look for svm in
cat /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good amd_lbr_v2 nopl xtopology nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy
svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba perfmon_v2 ibrs ibpb stibp ibrs_enhanced vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local user_shstk avx512_bf16 clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv
svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vgif x2avic v_spec_ctrl vnmi avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid overflow_recov succor smca fsrm flush_l1d amd_lbr_pmc_freeze
Just a note that I updated last night, and its working great so far 
Presumably it’d also be fine if they just permanently enable it.
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. 
1 Like
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!
1 Like
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.
2 Likes
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.
Because TPM2 is mentioned here: As a Linux beginner, I do not dig deep into the causes and effects but I stumble upon this: With OpenSuse Aeon and FW 3.06 it is no longer possible to set up the TPM2 token. This is necessary for every change at BIOS/FW level and was never a problem with 3.05.
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.