before on 4.1 with default or rlly any config my laptop was snappy, i could run multiple qubes at the time time with no performance issues, after updating and upgrading or the other way around to 4.2 even with default config my laptop is now extremely slow that i want to bash my head with the monitor, jk i would never bash my head because an upgrade reuined my user experience and now i’m stuck with a useless device :smiley, literally every task takes x2 or x3 the amount of time, the mouse is delayed, can’t even use personal qube without extreme delay although my specs are more than fine for me to run multiple qubes at once
You can always try a clean 4.2 install and restore your backed up templates and AppVMs, see if that makes a change.
What does xenpm get-cpufreq-para report in dom0? “Suddenly slow after an update” could be something with the power management, though I don’t think Qubes does much with it.
The last section of the first post is a Hardware Compatibility List report, which is useful for troubleshooting, but also to have a record of how different pieces of hardware behave with Qubes OS.
It happens that @flavio keeps tracks of those reports, that are usually posted in the HCL category of the forum.
Because this topic was opened in a different category, I brought attention to it because @flavio might otherwise not have seen this topic.
Try the various kernels that are available to you.
In dom0 you can install three different flavours: kernel, kernel-510 and kernel-latest.
In fact you can just install all of these via qubes-dom0-update kernel kernel-510 kernel-latest and try each of them (each package will install 3 kernels, so 9 in total) from the respective GRUB menu entry.
Was thinking of doing this, I’ll give it a try, i had the issues with overall lag on “latest kernel”, that’s what i used, I didn’t install any other kernel
Unable to install, i tried latest kernel Option and regular install, keep getting mid install “failed to set new efi boot target. This is most likely kernel or firmware bug” @gonzalo-bulnes@apparatus
Also cannot use keyboard or mouse, or the installation process won’t start at all, need to always do acpi=off to prevent the issue from happening, then I’ll need external hardware while installing
I have, it doesn’t solve the kernel issue, it only allows the install ui to appear without error when disabling acpi, other than that I’m unable to install
The message “failed to set new efi boot target. This is most likely kernel or firmware bug” doesn’t mean that the installation completely failed. It just means that it couldn’t add the EFI entry automatically and you need to do this manually:
The official doc is outdated and the current way to do this is this one: