OpenMandriva Lx version: ROME Plasma6.wayland AMD CPU (newer than 2017)
Desktop environment: KDE
Description of the issue: After updating the system a few days ago, OpenMandriva failed to boot after restarting it later that night (I didn’t restart immediately after updating). The issue still remains even now. The following post is from someone else who seems to have the same issue: OM doesn't boot after latest update. Here’s a short video I recorded which demonstrates what happens when I turn on the PC, and at which point in the process things fail: OM failing to boot after update. When I updated, I used the official software updater tool located in the app menu. I didn’t mess around with Discover which I know can cause breakages when used to update system packages in OpenMandriva. I don’t remember which version I was on prior to updating, nor which version I was on after updating; I didn’t pay attention to that when I did it.
Relevant informations:
Linux: 6.14.0-desktop-2omv2590 (can be seen in the video; It’s the kernel, right?)
The install is encrypted with a password
CPU: AMD Ryzen 5 3600
GPU: AMD Radeon RX 6600
Memory: 16GB DDR4 (2x8GB)
Motherboard: MSI MPG B550 Gaming Edge WiFi
Disk OM is installed on: Western Digital 500GB SSD
Things I tried or tested before making this post:
Unplugged desktop and monitor from the wall, reconnected, and attempted to boot again (didn’t boot)
Installed the latest OM ROME (of the same version already installed) onto a live USB to see if it can boot (it does).
The screen at 1:01 in the video is where you need to navigate into console. Choose the “Advanced Options for OpenMandriva” and then a list of installed kernels will display and various types of boot.
The one I used was Kernel 6.13.7 [console] boot. Your kernel # might be different, but hopefully you will get one which boots into a console. When you’re there try and run a dnf command such as “dnf clean all” just to see what results from that action. At that point it will be easier to tell if it is or is not like the problem I had in the other post.
On the surface it looks exactly like the problem I had. It’s interesting that you didn’t update with DIscover and still had the problem.
Do you have another computer you can ssh into this one from to verify whether the machine has booted or not?
If the machine has not continued the boot process you will not get a login prompt using ssh.
This is just to verify if the system is actually booting and/or if there is a drm (direct rendering manager) issue.
I have the same symptoms on 6.14.0 kernel and the reason I ask is we have the same generation of AMD GPU albeit mine is SKU above yours, I can ssh into the machine running the 6.14.0 kernel even after having the same display issues you have reported in your video.
I followed your instructions, but I was confused if I was actually in console mode or not, because it seemed to be asking me to login. Curious if it was my normal Linux password, I put that in, but it didn’t work. So I tried my encryption key, and that also didn’t work.
Out of curiosity, I rebooted the computer again and instead of selecting the console mode for Kernel 6.13.7, I chose the standard one. This actually fixed the issue, at least for now! Using Kernel 6.13.7, I’m able to successfully boot into OM ROME again, just fine. I also noticed something interesting:
When I originally installed OpenMandriva a little over a month ago, I was always confused as to why the computer asked me for my encyption key two times. The first time is the same as what you saw in the video I shared, and the second time (which didn’t happen in the video) I’m pretty sure happened after selecting the OpenMandriva Lx option at 1:01. But when it asks for the encyption key for the second time, it doesn’t do so in a console like in the video - it instead displays an actual proper text box at the centre-bottom of the screen. I was always confused why this happened and why it didn’t just ask me once (preferably using the text box rather than the console shown in the video).
However, at some point I updated the system (this was prior to the most recent update that blocked me from booting). And after updating it, it no longer asked me for the key twice - only once - and only through the console as shown in the video.
The reason I’m saying all this, is because after selecting the Kernel 6.13.7 option, which successfully lets me boot into OM ROME now, I now have this second encyption-key prompt pop up on the screen again. This makes me wonder if the encryption I’m using is connected in some way to the problem.
I’m going to take a guess that you put in your password for the “login” line. Easy mistake to make. At the first “login:” prompt you want to put your username i.e. “Liam” or whatever it is. Then after you hit enter it will ask for the “password:” and that will be your regular OM passsword (not a hardrive or encryption key). In other words the password you set up during installation.
But it sounds like just booting an earlier kernel solved hard part of the problem. That makes me think the problem was/is related to this other post:
When I fixed my own I saw the kernel change from kernel version 6.14.0-2 to kernel version 6.14.0-3 …
The best suggestion I have would be to post here the output of the command to get your kernel versions
rpm -qa|grep kernel
I’m not qualified to suggest anything further than that. You might try @stephane 's comment of getting getting a journalctl -b and posting it here so that it can be examined.
journalctl -b -1 > journal-no-boot.txt
That will create a text file called journal-no-boot.txt …Use dolphin and do a search for it then post it here.
Unfortunately I would have no idea how to make sense of it, but someone here should maybe be able to read it and tell you the best way to keep your machine running.
Also, for the journalctl command, it gets the previous boot, so you would need to let it boot incorrectly first, then boot into the working 6.13 kernel to make the long… as described in this comment:
@bero has started build for kernel 6.13.9 after that a dnf --refresh dsync should take care of this for everyone. Or you can follow the advice in that post.