MX Linux Forum

probably nothing related to grub, but rather with an invalid fstab. Also note: device names like /dev/sda, /dev/sdb
can change they are not static. Depending on linux kernel version and whether you plugged in an e.g. USBstick, you might get next boot other device names. A more stable alternative ...

The only thing I can come up with is that the initramfs was still hardcoded to try to resume from your swap partition using a UUID.


Maybe. But why would it try to resume from swap in the first place? This was a desktop installation that never goes to sleep. I have seen initramfs complain about ...

This may be a known issue, though I didn't see it when searching the forum. I ran across the same problem running Kubuntu 20.04 and Debian Bullseye. I seem to recall someone posting about this on the Ubuntu forums as well. Again, since I'm not running MX Linux I can't provide any further details ...

Set GRUB_DISABLE_LINUX_UUID=true then did update-grub. Modified /etc/fstab to replace UUID entries with traditional device names. When I rebooted I was left in a console with an error message about a missing "machine-id" or some such. Since I'm no longer running MX Linux because of this and other ...

I doubt this post will see the light of day, but I'll try anyway. Several responsdents have complained about the lack of feedback by the OP. Well, I am the OP and I have posted quite detailed feedback. The problem is that the forum appears to be moderated and the moderator(s) has deleted several of ...

Interesting. Apparently the forum moderators don't like bug reports, in spite of this being a form for bug reports. I've made two subsequent posts on this topic providing the information requested and neither of them have shown up.

Also missing is whether the sysvinit boot would succeed with the Nvidia driver installed--then we could say that only the systemd boot was affected. Without that datum, it might have been one of the standard "Nvidia driver boots to black screen" type problems that we see every so often, since I ...

I require systemd to enable my VPN client software, which is otherwise unusable. After successfully booting with systemd on a fresh install of MX Linux KDE my VPN software was functional. I then installed the Nvidia driver using MX Tools and rebooted the system. When using systemd to boot the system ...

Potential new user here. I agree with kjunix regarding the goal of having MX Linux incorporating the latest LTS version of plasma. I've been a KDE user since version 1.1 and tried numerous distros over time looking for one that best supports KDE while providing a stable, secure, flexible platform. I ...