Cannot upgrade Kernel

[giubug]

This is why you are having trouble with amdgpu drivers when the other MX users are happy using the stock version in our own repositories, and which is also included on the ISOs.

Maybe you could tell us why this is in your repositories:

Code: Select all

Active apt repos in: /etc/apt/sources.list.d/amdgpu.list
    1: deb https://repo.radeon.com/amdgpu/6.0.2/ubuntu jammy main

I wish I had a time machine to go back and report, but I am pretty sure I didn't add this repo myself. Can it be that it was added when installing another package? I have been using Linux distributions for many years, I do what is necessary to keep my system running and actually use the computer to do things. I am not an expert by any means, I follow instructions on the web, previous solutions when available. I guess many users are in the same situation like me, we appreciate the effort developers put in to create and maintain a distro, but we just want to use our system to do the various things we want to do. when a problem comes up, we do our best to solve it, but a user should not be expected to understand in details the working of an operating system, otherwise how many people will be ready to deal with this kind of complexity when all they want to do is keep using their computer?

[DukeComposed]

I have been using Linux distributions for many years, I do what is necessary to keep my system running and actually use the computer to do things.

Then you will know that different distros have different requirements, function differently, and what works for one Linux distro will not work for another.

I am not an expert by any means, I follow instructions on the web, previous solutions when available. I guess many users are in the same situation like me, we appreciate the effort developers put in to create and maintain a distro, but we just want to use our system to do the various things we want to do.

Most of the experts you're going to meet started out doing the same thing. I personally made a career for a year or so as a Linux consultant based on six or seven years of experience and, when I met an error I'd never seen before, I was just better at Googling than my clients were.

when a problem comes up, we do our best to solve it, but a user should not be expected to understand in details the working of an operating system

There's basic "dos" and "don'ts" for every operating system. Why would Linux be an exception? At the top of the Help forum is a pinned post called How to Break Your System. If you run Windows for any serious length of time you learn not to mess with things in C:\Windows\System32. If you're going to run MX Linux for any serious length of time you're going to read, follow, and understand the How to Break Your System post. At the end of the day Linux offers a lot more independence than commercial operating systems. You might not be ready for that responsibility if "I should not be expected to understand [the] details" is your go-to argument for changing a config setting.

I understand you want to just Get Things Done. So too do we all. You have a responsibility to understand the changes you're making to your machine for one reason: no one else has the means or motive to tell you otherwise. It's your Linux install. You're allowed to break it if you want. When you have that kind of unrestricted freedom in your OS, you don't get to complain that it didn't come with training wheels and a big red "undo" button.

[asqwerth]

But were you following internet instructions that were meant for Ubuntu systems, when you were not running a Ubuntu-based distro? That seems a common-sense thing to check even for everyday non-expert users.

I'm not trying to pile on you even more, but it would be helpful now to dig through your memories to provide the experts on this forum [not me] with as much info as you can remember on what steps you took on or what packages you installed on your computer that was graphics-related. Examples: what websites did you visit, where did you download various packages [deb files] to install, or where did you copy terminal commands to run , etc.

Repos can be added if you copied some terminal commands and ran them, or in some cases it is true that a deb file you installed might automatically add a repo as part of installation.

[giubug]

I have been using Linux distributions for many years, I do what is necessary to keep my system running and actually use the computer to do things.

Then you will know that different distros have different requirements, function differently, and what works for one Linux distro will not work for another.

I am not an expert by any means, I follow instructions on the web, previous solutions when available. I guess many users are in the same situation like me, we appreciate the effort developers put in to create and maintain a distro, but we just want to use our system to do the various things we want to do.

Most of the experts you're going to meet started out doing the same thing. I personally made a career for a year or so as a Linux consultant based on six or seven years of experience and, when I met an error I'd never seen before, I was just better at Googling than my clients were.

when a problem comes up, we do our best to solve it, but a user should not be expected to understand in details the working of an operating system

There's basic "dos" and "don'ts" for every operating system. Why would Linux be an exception? At the top of the Help forum is a pinned post called How to Break Your System. If you run Windows for any serious length of time you learn not to mess with things in C:\Windows\System32. If you're going to run MX Linux for any serious length of time you're going to read, follow, and understand the How to Break Your System post. At the end of the day Linux offers a lot more independence than commercial operating systems. You might not be ready for that responsibility if "I should not be expected to understand [the] details" is your go-to argument for changing a config setting.

I understand you want to just Get Things Done. So too do we all. You have a responsibility to understand the changes you're making to your machine for one reason: no one else has the means or motive to tell you otherwise. It's your Linux install. You're allowed to break it if you want. When you have that kind of unrestricted freedom in your OS, you don't get to complain that it didn't come with training wheels and a big red "undo" button.

I am sorry, this thing is turning into a debate, and that's not my intention. All I am saying is, I didn't do anything to change the system, I am well aware of the problems that can arise from messing around with things I don't fully understand in a Linux environment. Windows, i don't know too much about it, it's more or less 20 years that i don't use it anymore. I have been using MX-23 without any issue, updating when necessary and installing software when needed. I don't remember manually adding repos, i am not even sure i know how to do that in a Debian environment. My system has been running without issues. A few months ago i updated it, there is a new Liquorix Image, it doesn't work. I am stuck on this kernel. I point out the problem in the forum, because surely i am not the only one with the issue ( you can google it). if it can be solved, good, if i have to do a clean install, that's also good. Simple.

[DukeComposed]

All I am saying is, I didn't do anything to change the system

We know that's not true from the large number of uncommon package repos that are installed. I also see a dedicated liquorix kernel repository listed, so there isn't even a guarantee you're trying to use an MX-provided liquorix kernel:

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
 

MX Linux repos contain a handful of supported liquorix kernels that can be installed without relying on liquorix.net repositories. If I were in this situation, I'd first remove any non-MX kernels, backup and clean my repo situation, and make sure I'm installing MX-provided packages from MX-specific repos.

[giubug]

All I am saying is, I didn't do anything to change the system

We know that's not true from the large number of uncommon package repos that are installed. I also see a dedicated liquorix kernel repository listed, so there isn't even a guarantee you're trying to use an MX-provided liquorix kernel:

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
 

MX Linux repos contain a handful of supported liquorix kernels that can be installed without relying on liquorix.net repositories. If I were in this situation, I'd first remove any non-MX kernels, backup and clean my repo situation, and make sure I'm installing MX-provided packages from MX-specific repos.

Dude, why all the hate?!? I get it, you are the Master of MX Linux, you are the Professor, the undisputed King of the Hill...
relax a little

[Eadwine Rose]

OK that is enough.. any further things between you two you can take up in PMs. Thanks.

[giubug]

But were you following internet instructions that were meant for Ubuntu systems, when you were not running a Ubuntu-based distro? That seems a common-sense thing to check even for everyday non-expert users.

I'm not trying to pile on you even more, but it would be helpful now to dig through your memories to provide the experts on this forum [not me] with as much info as you can remember on what steps you took on or what packages you installed on your computer that was graphics-related. Examples: what websites did you visit, where did you download various packages [deb files] to install, or where did you copy terminal commands to run , etc.

Repos can be added if you copied some terminal commands and ran them, or in some cases it is true that a deb file you installed might automatically add a repo as part of installation.

I installed the Liquorix Kernel using this guide
https://linuxcapable.com/how-to-install ... ian-linux/
Like I said, there were no problems and the system ran just fine. I updated the Kernel a few times without any problem. The last version that i can use is 6.4.11-1. After that, upgrading the Kernel and rebooting with the new Kernel, results in blinking cursor. Same thing happens if I install a generic Kernel above 6.4.
I have tried to install from MXPI, the results are the same.
Thank you

[giubug]

OK that is enough.. any further things between you two you can take up in PMs. Thanks.

Understood, I apologize if I have caused any trouble.
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.

[asqwerth]

But were you following internet instructions that were meant for Ubuntu systems, when you were not running a Ubuntu-based distro? That seems a common-sense thing to check even for everyday non-expert users.

I'm not trying to pile on you even more, but it would be helpful now to dig through your memories to provide the experts on this forum [not me] with as much info as you can remember on what steps you took on or what packages you installed on your computer that was graphics-related. Examples: what websites did you visit, where did you download various packages [deb files] to install, or where did you copy terminal commands to run , etc.

Repos can be added if you copied some terminal commands and ran them, or in some cases it is true that a deb file you installed might automatically add a repo as part of installation.

I installed the Liquorix Kernel using this guide
https://linuxcapable.com/how-to-install ... ian-linux/
Like I said, there were no problems and the system ran just fine. I updated the Kernel a few times without any problem. The last version that i can use is 6.4.11-1. After that, upgrading the Kernel and rebooting with the new Kernel, results in blinking cursor. Same thing happens if I install a generic Kernel above 6.4.
I have tried to install from MXPI, the results are the same.
Thank you

If you had already added this 3rd party Liquorix repo, then when you open MXPI to install from there, you are also seeing contents of this repo listed in the "enabled" tab of MXPI. Packages from all enabled repos will be listed. There is no certainty you are installing a kernel from MX own repos.

It might be helpful to the experts if you post here the contents of /boot/grub/grub.cfg .

It will give an indication of the various kernels installed on your system, at least those as detected by grub.

For now, you can also open MX Repo Manager, go the last tab, and untick the liquorix repo in order to disable it for now.