It’s on Arch and Debian as well which means it’s on basically every distro
Ah ok, I’d heard Netflix had the issue as well but I don’t use it so I couldn’t confirm. Maybe it’s time to reconsider my prime subscription, although I do still use it for 1 day delivery
God yes please, got to be better than who we’re stuck with at the moment
I ended up solving it by installing kde plasma. I’d previously tried with as minimal an install as possible to narrow down the problem, but it seems all I had to do was carry on setting things up as I’d originally wanted!
You might at some point, you don’t actually need secure boot turned on for Windows 11 your PC just needs to be capable of secure boot and use UEFI mode rather than legacy boot
Nah I don’t really need the latest kernel, I’m just worried the it’s kernel will eventually be updated and get the same problem
That makes sense, for the amount I use this laptop I won’t worry about it for now! It wasn’t noticeably dusty when I opened it yesterday, and the errors occur immediately after booting so I wouldn’t expect it to heat up that fast
In that case if it still works should I just ignore the error for now and replace the card if it causes any issues?
Thanks that’s sorted it! I must have not noticed the error before as I usually install btrfs-progs after chrooting and it looks like installing it triggers mkinitcpio to run again anyway
How?
By safe I guess I more meant should I be doing anything beforehand. I’m running snapper on btrfs so even if I do completely destroy everything it’s not too much of an issue but I’d rather avoid it if possible!
I found out how to check for orphaned packages with pacman thanks to another comment so I’ve removed them now
Wow I seem to have loads
I never knowingly installed these, the only packages I’ve intentionally installed from the AUR are heroic games launcher and 7-zip. And the only kde programs I’ve manually installed is the plasma-meta package, kde connect and ksnip. I think they were previously part of the plasma-meta package and have now been removed or replaced with the plasma 6 versions
I just tried increasing it but the maximum I can set is 255 and that made no difference unfortunately. All the Windows VMs are also set at 8 and they don’t have any problems
I hope its not a hardware issue, the 2 VMs were running on 2 separate hosts within the cluster so hopefully that’s unlikely! Thanks for taking a look
I’ve just edited the main post with links for the journalctl output. The purpose was just to test some network config, I managed to do what I needed anyway but I’m just curious as to why I had issues with these VMs!
I just left it as default which is 1 display and 8mb video memory
Not sure if that’s wrong or not tbh, I use snapper instead of timeshift and I wanted /home included in the snapshots anyway (I think it let me set them up as 2 separate jobs). The reason I went with subvolumes instead of separate partitions is that I didn’t have to worry about sizing. I also know I can reinstall to my root subvolume without affecting the others, depending on the installer for your distro I don’t know how easy that is vs just having separate partitions. I played around with it in a VM for a while to see what the backup and restore process is like before I actually committed to anything!
Why do you have a btrfs volume and an ext4 volume? I went btrfs and used sub volumes to split up my root and home but I’m not sure if that’s the best way to do it or not
It should give you the option to abort the shutdown and sort out whatever process it is though! Or at least let you kill it manually from the shutdown terminal. I know you can technically do that with the emergency shell but I don’t like leaving that enabled. Thankfully I rarely get this issue anymore anyway