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.