After installing KDE on a fresh install using the kde-settings-qubes
I can no longer boot.
Tried to add the skip_autostart
param during the boot, but didn’t help.
After the LUKS pass, it just hang with the message of “FIle locking disabled” and also prints “thermal thermal_zone?: Disabled thermal zone with critical trip point”.
Any help, please?
Try this to see if you’ll find more errors in the boot log:
Maybe kde-settings-qubes
failed to install because there was not enough free space in dom0 root and it’s causing the system boot to fail.
You can try to decrypt and mount your Qubes OS dom0 root partition from some other OS (e.g. from Linux Live OS) and check if there is enough free space or run fsck on it.
You referring to the disk space, correct? Because I modified the max amount of RAM allocated to the dom0 as well and that may caused some issue, even though I didn’t see any errors during the installation of the KDE and try to modify this param during boot with no success.
Can the secondary GPU may cause issues with the boot because of the KDE, maybe? I can’t disable it as I don’t have access to the qvm-pci
or lspci
during boot.
I’m referring to the root partition of dom0:
[user@dom0 ~]$ df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/qubes_dom0-root 20G 16G 3.5G 82% /
How much RAM did you allocate to dom0?
Did you change it in your last successful boot and didn’t check if it worked?
Or it worked before with reduced dom0 RAM?
Did you modify the correct option? The default should be dom0_mem=max:4096M
.
I don’t know.
Try to switch to another TTY using Ctrl+Alt+F2 when the boot hangs.
Kde doesn’t run until the second password login. You have to choose if from a drop-down. It would still be set to xfce default. Hard to believe you’d run out of hard drive space on a fresh install unless your hard drive is tiny.
Did it also do a dom0 kernel update ? It would have checked for one when you installed kde
1.5GB
I could boot with 1.5GB using XFCE
Yes
You’re right, it did require to run updates first with the qubes-dom0-update
and it did update something along with installing KDE.
I was also using the latest kernel(6.10 I think) when this happened and now I’m reinstalling with the default.
I’ll try to update first and reboot and get the secondary GPU’s address to block it if needed, before installing KDE and see how it goes.
Anything else I should consider before checking this out?
I think it is more likely to be the kernel or disk space. I’d check the dom0 disk space is enough. And I’d do all the dom0 updates and reboot before you install kde. That way you can narrow it down to the update or kde install. I’m not sure if kde will run well with only 1.5gb memory… it isn’t as lightweight as xfce
There are been recent issues with kernel updates related to graphics cards and USB drivers
It’s working for me. I have no idea what went wrong, could be I did something by mistake or overlooked something.
Thank you both