Cannot upgrade Kernel

[DukeComposed]

It's ok if you want to say that I am stupid, I am the first one to say that I am, just don't call me a liar, please.

No one is saying that--and no one should--and it should be clear that grovelling is not a substitute for doing your homework. The chimera of random repos that you've added to this system look to have finally pulled in something incompatible with kernels of a certain age or type. I've already stated what I would do to fix it and that begins with reading, following, and understanding the How to Break Your System post and taking actions to remove software that MX didn't or can't install from its official repos.

Another option that occurs to me is to install MX on something else, like in a VM, add a liquorix kernel from the AHS repo, verify it boots as expected, and then make a snapshot ISO of that VM and try to boot it on the problem system. That will at the very least confirm what reinstalling the OS would accomplish without actually doing it. There may still be driver issues, but at least then you'd know it's a driver issue in liquorix and not something buried in a hodgepodge of PPAs.

[asqwerth]

It's not just the clearly-marked PPAs [which seem to the "normal" music-related ones that AVLinux says might be ok for Debian], it's the amdgpu and the liquorix 3rd party repos that are in question.

I went to the web page whose instructions the OP followed to install liquorix kernel(s) from the 3rd party liquorix repo, and there is a possibility that that one might be ok, since the web page claims this works for Debian 12. I can't be sure of the accuracy of that statement [there must be a reason MX's packaging team take the effort to build our own liquorix kernels from source], but let's assume for now this repo is not the issue.

However, the OP also added the amdgpu 3rd party repo that is meant for Ubuntu Jammy edition. This one raises huge question marks as there is every possibility that OP has pulled in dependencies [built for Ubuntu Jammy] that are not compatible with the MX23 Debian 12 system. It might seem to work for a while, but there comes a time when a system update finally brings the incompatibilities to light.

I agree the OP needs to check that he is able to boot into MX23 default 6.1 Debian kernel [seems to still be listed in his grub.cfg]. Hopefully if that is possible, then the next step is to disable both these repos and remove all packages installed from there [kernels, graphics-related stuff].

[siamhie]

It's not just the clearly-marked PPAs [which seem to the "normal" music-related ones that AVLinux says might be ok for Debian], it's the amdgpu and the liquorix 3rd party repos that are in question.

I went to the web page whose instructions the OP followed to install liquorix kernel(s) from the 3rd party liquorix repo, and there is a possibility that that one might be ok, since the web page claims this works for Debian 12. I can't be sure of the accuracy of that statement [there must be a reason MX's packaging team take the effort to build our own liquorix kernels from source], but let's assume for now this repo is not the issue.

However, the OP also added the amdgpu 3rd party repo that is meant for Ubuntu Jammy edition. This one raises huge question marks as there is every possibility that OP has pulled in dependencies [built for Ubuntu Jammy] that are not compatible with the MX23 Debian 12 system. It might seem to work for a while, but there comes a time when a system update finally brings the incompatibilities to light.

I agree the OP needs to check that he is able to boot into MX23 default 6.1 Debian kernel [seems to still be listed in his grub.cfg]. Hopefully if that is possible, then the next step is to disable both these repos and remove all packages installed from there [kernels, graphics-related stuff].

I've installed the Liquorix kernel from their web site and have never had any issues. The instructions are this.

Code: Select all

curl -s 'https://liquorix.net/install-liquorix.sh' | sudo bash

which adds to your source list this entry

Code: Select all

Active apt repos in: /etc/apt/sources.list.d/liquorix.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bookworm main
    2: deb-src [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bookworm main

The thing is his QSI shows 6.4.11-1-liquorix-amd64 [6.4-14.1~bookworm] but Liquorix's current kernel is at 6.10-15 (6.10.11-2).
I don't know how they managed to keep that version because when I ran Liquorix's kernel from their repo, it was always getting updated.

[Stevo]

I port the Liquorix kernels over to our repo because they don't take that long, and I have to make changes anyway so that they will run on MX 21; specifically to go back to xz compression instead of zstd, since zstd is not supported in Bullseye kernels.

[giubug]

When I boot the generic 6.1 kernel, there is the loading screen with the blue sun, followed by a black screen. I cannot access terminal from there. I can only hard reset the PC by pressing the button.

[siamhie]

Lets start from scratch. Can you boot from the MX-23 live ISO? Also your topic is misleading, I think. Your wanting to update the kernel, right?

(By the way, I installed the Liquorix kernel from their web site and only the 6.4.15 kernel and headers are available. There is no 6.4.11 version listed).

[linexer2016]

@giubug
I have to enter my support for your dilemma giubug. I too have experienced quite similar issues to which you've described. Notwithstanding some assertions from some on the board that it's because of something you (or indeed me) has installed, I too can't account for anything other than a sudo apt update && sudo apt upgrade some week's ago which after this process saw the introduction of the problem particularly with amdgpu firmware (and I've seen it too with mediatek firmware) that resulted in as I've said, a very similar situation to you. I can no longer change my existing kernel by either upgrade or downgrade and so I've just resigned myself to putting up with the error messages on bootup (pertaining to no compatible firmware for amdgpu and mediatek devices). Even though those devices work fine with the current kernel I am left to run which is 6.5 ahs. Traditionally, I've always liked to have available in case of some system problem, a couple of kernels to select upon boot up but now alas, this is not possible. I may one day just reinstall MX after backing up files as required but for now, it's just an annoyance rather than an imperative.
I would strongly suggest you load and use Timeshift giubug because its saved me a lot of hassle when I've tried to (and failed) like you to update kernels. Hope this gives you some comfort that you are not alone with your problem and I think that whilst there are some very experienced personnel on this forum we might understand that no one is infallible in their understanding of the intricacies of an operating system be it Windows or Linux or any other computer system IMO.

[giubug]

@giubug
I have to enter my support for your dilemma giubug. I too have experienced quite similar issues to which you've described. Notwithstanding some assertions from some on the board that it's because of something you (or indeed me) has installed, I too can't account for anything other than a sudo apt update && sudo apt upgrade some week's ago which after this process saw the introduction of the problem particularly with amdgpu firmware (and I've seen it too with mediatek firmware) that resulted in as I've said, a very similar situation to you. I can no longer change my existing kernel by either upgrade or downgrade and so I've just resigned myself to putting up with the error messages on bootup (pertaining to no compatible firmware for amdgpu and mediatek devices). Even though those devices work fine with the current kernel I am left to run which is 6.5 ahs. Traditionally, I've always liked to have available in case of some system problem, a couple of kernels to select upon boot up but now alas, this is not possible. I may one day just reinstall MX after backing up files as required but for now, it's just an annoyance rather than an imperative.
I would strongly suggest you load and use Timeshift giubug because its saved me a lot of hassle when I've tried to (and failed) like you to update kernels. Hope this gives you some comfort that you are not alone with your problem and I think that whilst there are some very experienced personnel on this forum we might understand that no one is infallible in their understanding of the intricacies of an operating system be it Windows or Linux or any other computer system IMO.

thank you for expressing your thoughts in such a clear and polite manner.
It is somehow comforting to know that somebody else is experiencing similar issues, at least I can stop going through my mind trying to remember what I did to cause this problem.
As a power user, I am extremely grateful to the developers who build and maintain such a powerful and stable operating system that allows us to do all the wonderful things we do with our systems.
When there is a problem, I believe it is our duty to report the problem, because that is about the only thing we can do to help the developers address issues that might otherwise go unnoticed.
It is by no means a cry for help nor an effort to shame the developers for doing a "bad job", on the contrary, at least from my point of view, it's the only way we can contribute to the development of an OS that can be used by the general public.
Murphy's law is universal, if a system has the inbuilt possibilities to be compromised voluntarily or otherwise by the end user, these flaws will sooner or later show, regardless of who's fault it is, which is not the point at all.

[giubug]

Lets start from scratch. Can you boot from the MX-23 live ISO? Also your topic is misleading, I think. Your wanting to update the kernel, right?

(By the way, I installed the Liquorix kernel from their web site and only the 6.4.15 kernel and headers are available. There is no 6.4.11 version listed).

I can boot from MX-23 live ISO, no problem there

[siamhie]

Lets start from scratch. Can you boot from the MX-23 live ISO? Also your topic is misleading, I think. Your wanting to update the kernel, right?

(By the way, I installed the Liquorix kernel from their web site and only the 6.4.15 kernel and headers are available. There is no 6.4.11 version listed).

I can boot from MX-23 live ISO, no problem there

Per your QSI, you have the standard XFCE ISO and not the ahs version.

Code: Select all

Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo/ bookworm main non-free

which means you were able to boot the live ISO to the desktop using the 6.1 kernel which you can't do with your installation.
So it looks like we can rule out a kernel issue and focus on a graphics issue.

I would try removing the corectrl code from your boot options next and try booting the 6.1 kernel again. We will take this one step at a time.

Code: Select all

amdgpu.ppfeaturemask=0xffffffff