Hello, all! This is my first time posting here, so please excuse me if I seem a little unprofessional.
I like this OS since I saw it on the Non-Woke Software List published by The Lunduke Journal. However, this issue has been going on for quite some time now, although it doesn’t hinder its usability. I tried everything described below, in addition to installing device-mapper (it was pre-installed with the latest version), to no avail.
Requirements:
I have searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the Release Notes and Errata
OpenMandriva Lx version:
ROME/Rolling (25.04)
Desktop environment (KDE, LXQT…):
KDE Plasma 6.3.4 (Wayland)
Description of the issue (screenshots if relevant):
When I install a newer kernel and attempt to boot from it, it gets stuck at the kernel loading screen. I then press the power button, and it almost instantly restarts.
Relevant information (hardware involved, software version, logs or output…):
Commands used:
sudo dnf distro-sync (I updated the system via dnfdragora, so this came up dry) sudo dnf --refresh dsync (reinstalled some packages, but still did not fix the issue) journalctl -b -1 > journal-no-boot.txt (shows log of last successful boot, but nothing about the failed one)
Edit: You can try removing the non-working kernels and then installing them again if you have not already done so. You can find older kernels here. Do not worry if they are called Cooker kernels all kernels are built in Cooker and should work OK in ROME or Rock. I have used Cooker kernels in Rock at times myself.
Check in /boot and be sure you have initrd-*.img file for the not working kernels.
This seems less likely but try dnf in --refresh task-plasma6-x11 and try booting into X11 instead of Wayland. You switch to X11 in lower left hand corner of sddm login screen.
It is between difficult to problem solve something with no evidence at all. If you can’t figure this out I suggest you talk to OM devs at OM Chat.
You only have initrd .img for kernel-6.12.1-1 so that is the only one that can boot. You do want to sudo dnf mark install kernel-desktop-6.12.1-1 as @WilsonPhillips suggests to keep that kernel until we resolve this issue.
To build initrd .img’s for the other kernels you do:
ls -1 /lib/modules
Then you copy and paste the module directory from there for each kernel, one at the time and use dracut to build the initrd like this:
dracut -f /boot/initrd-$version.img $version
where $version is taken exactly from one of the folders listed in ls -1 /lib/modules. So for example:
Note for all users if you do your package management from cli you can see if a new kernel install actually builds an initrd .img in the grub2 scriptlet that will run after the install. It will be under this line Generating grub configuration file ... like this where I just installed 2 kernels on the system used in the example post above, you will see Generating grub configuration file ... run twice in this screen-shot:
After resizing the partitions with another tool (turned out that my boot partition was too small to house the img files), wasting my life away trying to fix it not booting at all, chrooting into the main partition, and running all the necessary commands, everything works now! Thanks a million!
: