i hit a freeze on a t490 running 4.1.2 today, and it started happening immediately after doing qubes-dom0-update. i am planning to attempt a dnf history undo for this update, but wanted to solicit input before doing it.
i see several reports of t490 freezes on 4.1 and 4.2 here, but limited information about the cause and a fix. i ran qubes-dom0-update on this machine today and it began freezing up immediately afterwards. prior to this update, the machine was running fine and did not freeze. i figure this is a debug opportunity for finding the cause of the freeze.
is it safe to do a dnf history undo in dom0 for the transaction that installed the package updates that led to the freezes? i have never done this before and i am aware that qubes’ configuration is pretty bespoke, so i’m trying to be careful not to make this problem any worse.
My old R4.1.2 installation stopped getting updates after the last dom0 update. I get a salt error when trying to update any template. I know that R4.1 is not supported any more, but this looks like a self-destruct update pushed to stop any further “qubes-style” updates… because dnf, apt, and upgrade-nonroot continue to work in fedora, debian, and whonix based templates respectively.
it would seem that dnf history undo does not work.
i’ve attempted this after making a backup. it is legit suspenseful to make a backup when the machine may seize up at any moment.
is this still a known issue with 4.2 + t490 freezing? i’m asking in hopes of avoiding wasting time installing 4.2 only to have it freeze during install or similar.
i am attempting an install of R4.2.3, but i have already had it freeze on me twice. i managed to figure out how to do custom partition setup using the “advanced” gui because the standard one did not work.
any thoughts on how to get past the installation freezing on t490? afaik, the installer should not have hwp enabled by default, and if it does, i am unsure of how to disable it.
I think it’s enabled in the installer as well.
You can disable it by adding cpufreq=xen:hwp=off to the Xen command line options in the installer’s GRUB menu.
You can see this as an example:
Add it at the end of the line starting with multiboot2.
thanks, that got me over the hump with the freezing.
i did notice that if there is an error during 4.2.3 template and appvm setup, it does not restart the “finish installation” process, so i’m sitting in dom0 without any vms, only dom0.