Another ‘nuisance’ on my NovaCustom NV41 (running heads and qubes as pre-installed by Novacustom): Most of my qubes, in particularly my primary work qube, use the debian 12 xfce template (whether this happens, e.g., for fedora templates I can’t say), and every so often when the laptop has gone to sleep (either by closing the lid, or simply after the timeout for inactivity), the debian work qube doesn’t wake up completely. The windows are there, but they do not react to mouse or keyboard. A qube in this state cannot be restarted or shut down from any of the graphical tools I tried, I have to qvm-kill them from dom0.
I initially suspected some application software, but the problem happens even when none of these programs have been running.
Has anyone seen similar (mis)behavior?
How could I debug this (from dom0). I tried attaching a console, but did not get much further.
Thanks for getting back. Knowing that other don’t see similar issues is also a valuable data point (and, btw, your review was the decisive factor to order the NV41).
To be clear; at this point I doubt that anything is wrong with the hardware; I have not seen any hangs/issues during heavy work.
Only this one qube freezes (seems affected); of course, it’s the one I use most heavily and where I have most windows/apps open. That it’s debian12 based may be a completely wrong lead; I base my qubes on debian since it the primary OS in my lab.
I certainly can start other qubes when this happens, but the affected one behaves like a zombie.
So, to add to the inconveniences I note as I use the NV41 more often. Sometimes (1 out of 10 times or so), wireless is gone when the laptop wakes up from sleep.
qvm-kill sys-net
qvm-start sys-net
helps …
My sys-net qube is Fedora based, so if this is related at all to the original problem, then the template might not matter. Here only the wireless subsystem is affected; I can start a terminal without issues, but from quick reading I don’t see anything obvious in the syslogs…
Maybe it’s really heads that causes some small issues.
What is your wifi card? I got this issue with the atheros one, but the problem was gone after a firmware update. Since then, I switched to a much more modern card and no issue with the Intel AX201.
I am afraid I just use the built-in AX201 that came with the laptop. Since it is qubes certified, I assumed it should “just work” …
I just ran into both issues and poked around a bit:
In the sys-net qube, it’s really only the wifi functionality that’s gone … (the rest works fine; e.g., the wired connection reconnects just fine). If all is well, upon restarting NetworkManager, both wired and wifi just come up again fine. But if things go wrong, wifi has vanished for good…
So, this maybe a firmware/driver issue.
The hanging debian based qube is really dead. Upon first attempt to connect a console, I see a kernel oops with some OOM killer triggered, which makes NO sense at all – this qube has plenty of RAM and I was just running a terminal and firefox with 3 tabs open. I took a picture, but I doubt that this helps. Upon restarting (qvm-kill, qvm-start), the kernel oops is not reported in the syslog anymore…
I poked a bit more on the WIFI issue. This seems to have relatively recently bitten Arch Linux users, and their solution is to unload the driver(s) before sleep, and reloading upon wakeup. See: