Page 1 of 1
Cannot upgrade Kernel
Posted: Thu Sep 26, 2024 9:57 am
by giubug
Hello all,
Code: Select all
System:
Kernel: 6.4.11-1-liquorix-amd64 [6.4-14.1~bookworm] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1
BOOT_IMAGE=/boot/vmlinuz-6.4.11-1-liquorix-amd64 root=UUID=<filter> ro quiet splash
amdgpu.ppfeaturemask=0xffffffff
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23.4_x64 Libretto July 31 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: BM1AF_BP1AF_BM6AF v: Rev X.0x serial: <superuser required>
UEFI: ASUSTeK (Licensed from AMI) v: 1102 date: 03/12/2014
CPU:
Info: model: Intel Xeon E3-1240 v3 bits: 64 type: MT MCP arch: Haswell level: v3 note: check
built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 3417 high: 3582 min/max: 800/3401 boost: enabled scaling:
driver: acpi-cpufreq governor: performance cores: 1: 3391 2: 3394 3: 3393 4: 3392 5: 3393 6: 3582
7: 3401 8: 3392 bogomips: 54277
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB
filling, PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Polaris 20 XL [Radeon RX 580 2048SP] driver: amdgpu v: kernel arch: GCN-4
code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports:
active: DVI-D-1 empty: DP-1, DP-2, DP-3, HDMI-A-1 bus-ID: 01:00.0 chip-ID: 1002:6fdf
class-ID: 0300 temp: 53.0 C
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: DVI-D-1 mapped: DVI-D-0 model: Samsung C27F591 serial: <filter> built: 2017
res: 1920x1080 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9
modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 23.3.0-devel renderer: AMD Radeon RX 580 2048SP (polaris10 LLVM 17.0.4
DRM 3.52 6.4.11-1-liquorix-amd64) direct-render: Yes
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK 8
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aaf0 class-ID: 0403
API: ALSA v: k6.4.11-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: JACK v: 1.9.21 status: active tools: jack_control,qjackctl
Server-2: PipeWire v: 1.0.0 status: off with: 1: pipewire-pulse status: off 2: wireplumber
status: off 3: pw-jack type: plugin tools: pw-cat,pw-cli,wpctl
Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-jack type: module
tools: pacat,pactl,pavucontrol
Network:
Device-1: Intel Ethernet I217-V vendor: ASUSTeK driver: e1000e v: kernel port: f040
bus-ID: 00:19.0 chip-ID: 8086:153b class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Realtek RTL8188GU 802.11n WLAN Adapter (After Modeswitch) type: USB driver: rtl8710bu
bus-ID: 1-1.4:3 chip-ID: 0bda:b711 class-ID: 0000 serial: <filter>
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 1.13 TiB used: 426.76 GiB (36.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: A-Data model: SP550 size: 223.57 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3AB scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: CC47 scheme: GPT
Partition:
ID-1: / raw-size: 307.32 GiB size: 301.43 GiB (98.08%) used: 33.21 GiB (11.0%) fs: ext4
dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 623.94 GiB size: 613.08 GiB (98.26%) used: 393.55 GiB (64.2%) fs: ext4
dev: /dev/sdb3 maj-min: 8:19
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 53.5 C mobo: 38.0 C gpu: amdgpu temp: 53.0 C
Fan Speeds (RPM): fan-1: 1462 fan-2: 1248 fan-3: 0 fan-4: 0 fan-5: 0 gpu: amdgpu fan: 417
Power: 12v: N/A 5v: N/A 3.3v: 3.41 vbat: 3.22 gpu: amdgpu watts: 16.18
Repos:
Packages: 3134 pm: dpkg pkgs: 3118 libs: 1700 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 16
No active apt repos in: /etc/apt/sources.list
No active apt repos in: /etc/apt/sources.list.d/amdgpu-proprietary.list
Active apt repos in: /etc/apt/sources.list.d/amdgpu.list
1: deb https://repo.radeon.com/amdgpu/6.0.2/ubuntu jammy main
Active apt repos in: /etc/apt/sources.list.d/checkra1n.list
1: deb [signed-by=/usr/share/keyrings/checkra1n.gpg] https://assets.checkra.in/debian /
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian-ppas-2.list
1: deb http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu focal main
2: deb http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu focal main
3: deb http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu focal main
4: deb http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian-ppas.list
1: deb http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu bionic main
2: deb http://ppa.launchpad.net/kxstudio-debian/music/ubuntu bionic main
3: deb http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu bionic main
4: deb http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu bionic main
5: deb http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu bionic main
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
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
Active apt repos in: /etc/apt/sources.list.d/rocm.list
1: deb [arch=amd64] https://repo.radeon.com/rocm/apt/6.0.2 jammy main
No active apt repos in: /etc/apt/sources.list.d/steam-beta.list
Active apt repos in: /etc/apt/sources.list.d/steam-stable.list
1: deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
2: deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
Active apt repos in: /etc/apt/sources.list.d/winehq-bookworm.sources
1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bookworm main
Info:
Processes: 312 Uptime: 1h 48m wakeups: 1 Memory: 15.53 GiB used: 4.45 GiB (28.6%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
when I upgrade the headers , neither Generic nor Liquorix 6.10.11-1 work. there will be a blinking cursor when booting.
Please let me know what information is required to solve this issue.
Grateful
Re: Cannot upgrade Headers
Posted: Thu Sep 26, 2024 10:26 am
by j2mcgreg
As I understand it (could be wrong) a kernel and its headers are a matched pair and you can't upgrade one of the two on its own. Doing so would be like putting a Honda transmission into a Nissan and expecting good things.
Re: Cannot upgrade Headers
Posted: Thu Sep 26, 2024 10:28 am
by timkb4cq
linux-headers versions have to exactly match the kernel (linux-image) version you are running. If you install a kernel with the MX Package Installer it will automatically install the matching headers.
Re: Cannot upgrade Headers
Posted: Thu Sep 26, 2024 10:36 am
by giubug
yes yes, sorry for the confusion, I mean headers and kernel. just the regular upgrade in terminal. I tried in the package installer also, with the same results.
Re: Cannot upgrade Headers
Posted: Thu Sep 26, 2024 10:48 am
by j2mcgreg
giubug wrote: Thu Sep 26, 2024 10:36 am
yes yes, sorry for the confusion, I mean headers and kernel. just the regular upgrade in terminal. I tried in the package installer also, with the same results.
When you used MXPI, were you accessing the Popular Apps tab or the Enabled Repos tab? If it's the latter, it's possible that you grabbed the wrong headers package by mistake.
Re: Cannot upgrade Headers
Posted: Thu Sep 26, 2024 10:56 am
by giubug
In the package installer, I searched for linux-image, installed the latest ones available in Debian backports:
linux-image-6.10.6+bpo-amd64
linux-image-6.10.11-1-liquorix-amd64
thank you
Re: Cannot upgrade Headers
Posted: Thu Sep 26, 2024 11:03 am
by timkb4cq
I suspect that the issue is related to this:
1: deb [arch=amd64]
https://repo.radeon.com/rocm/apt/6.0.2 jammy main
Apart from using Ubuntu repos on a debian based system (generally bad idea and an easy way to accidentally break your installl) the rocm framework is closely tied to the amdgpu driver which partially resides in the kernel. That's why AMD lists rocm compatible OS versions - which doesn't include debian stable. I suspect you're stuck with the kernel you have unless you remove rocm, or go through the compatibility list and install the default kernel version from one of those systems.
I wish you luck, but by using so many Ubuntu repos you have created a frankenOS for which we can have no certain answers.
Re: Cannot upgrade Headers
Posted: Thu Sep 26, 2024 11:10 am
by Stevo
That particular 6.4 Liquorix kernel is no longer in our repository. When Liquorix starts packaging a new major version, such as 6.5 over 6.4, we delete all the previous version's releases except the last, which in 6.4's case is 6.4.15-2 (6.4-20). This is to free up some of our not unlimited space on the repository servers.
We will also delete kernels if they are discovered to have a major security flaw.
Re: Cannot upgrade Headers
Posted: Thu Sep 26, 2024 11:38 am
by giubug
timkb4cq wrote: Thu Sep 26, 2024 11:03 am
I suspect that the issue is related to this:
1: deb [arch=amd64]
https://repo.radeon.com/rocm/apt/6.0.2 jammy main
Apart from using Ubuntu repos on a debian based system (generally bad idea and an easy way to accidentally break your installl) the rocm framework is closely tied to the amdgpu driver which partially resides in the kernel. That's why AMD lists rocm compatible OS versions - which doesn't include debian stable. I suspect you're stuck with the kernel you have unless you remove rocm, or go through the compatibility list and install the default kernel version from one of those systems.
I wish you luck, but by using so many Ubuntu repos you have created a frankenOS for which we can have no certain answers.
I sincerely don't remember adding this repo, and I am not sure how to go about removing it... my feeling is that when I boot one of the aforementioned images, something goes wrong with amdgpu driver, but I say this because the blinking cursor has been always there for me when there have been problems in the past with GPU drivers, nvidia especially. But i don't remember having any problems with GPU drivers in this MX23 installation.
If there is a way to fix this, i would be very thankful.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 2:11 am
by Stevo
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
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 2:24 am
by giubug
Stevo wrote: Fri Sep 27, 2024 2:11 am
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?
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 3:02 am
by DukeComposed
giubug wrote: Fri Sep 27, 2024 2:24 am
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.
giubug wrote: Fri Sep 27, 2024 2:24 am
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.
giubug wrote: Fri Sep 27, 2024 2:24 am
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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 3:08 am
by 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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 3:34 am
by giubug
DukeComposed wrote: Fri Sep 27, 2024 3:02 am
giubug wrote: Fri Sep 27, 2024 2:24 am
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.
giubug wrote: Fri Sep 27, 2024 2:24 am
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.
giubug wrote: Fri Sep 27, 2024 2:24 am
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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 4:03 am
by DukeComposed
giubug wrote: Fri Sep 27, 2024 3:34 am
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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 4:52 am
by giubug
DukeComposed wrote: Fri Sep 27, 2024 4:03 am
giubug wrote: Fri Sep 27, 2024 3:34 am
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
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 5:07 am
by Eadwine Rose
OK that is enough.. any further things between you two you can take up in PMs. Thanks.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 5:42 am
by giubug
asqwerth wrote: Fri Sep 27, 2024 3:08 am
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
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 5:44 am
by giubug
Eadwine Rose wrote: Fri Sep 27, 2024 5:07 am
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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 6:19 am
by asqwerth
giubug wrote: Fri Sep 27, 2024 5:42 am
asqwerth wrote: Fri Sep 27, 2024 3:08 am
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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 6:55 am
by giubug
Thank you
Code: Select all
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=1360x768
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
insmod gfxmenu
loadfont ($root)/boot/grub/themes/StylishDark_mx/DejaVuSans-Bold14.pf2
loadfont ($root)/boot/grub/themes/StylishDark_mx/DejaVuSans10.pf2
loadfont ($root)/boot/grub/themes/StylishDark_mx/DejaVuSans12.pf2
loadfont ($root)/boot/grub/themes/StylishDark_mx/ascii.pf2
insmod jpeg
insmod png
set theme=($root)/boot/grub/themes/StylishDark_mx/theme.txt
export theme
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'MX 23.4 Libretto' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.10.11-1-liquorix-amd64 ...'
linux /boot/vmlinuz-6.10.11-1-liquorix-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.10.11-1-liquorix-amd64
}
submenu 'Advanced options for MX 23.4 Libretto' $menuentry_id_option 'gnulinux-advanced-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
menuentry 'MX 23.4 Libretto, with Linux 6.10.11-1-liquorix-amd64' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.10.11-1-liquorix-amd64-advanced-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.10.11-1-liquorix-amd64 ...'
linux /boot/vmlinuz-6.10.11-1-liquorix-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.10.11-1-liquorix-amd64
}
menuentry 'MX 23.4 Libretto, with Linux 6.10.11-1-liquorix-amd64 (systemd)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.10.11-1-liquorix-amd64-init-systemd-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.10.11-1-liquorix-amd64 ...'
linux /boot/vmlinuz-6.10.11-1-liquorix-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff init=/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.10.11-1-liquorix-amd64
}
menuentry 'MX 23.4 Libretto, with Linux 6.10.6+bpo-amd64' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.10.6+bpo-amd64-advanced-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.10.6+bpo-amd64 ...'
linux /boot/vmlinuz-6.10.6+bpo-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.10.6+bpo-amd64
}
menuentry 'MX 23.4 Libretto, with Linux 6.10.6+bpo-amd64 (systemd)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.10.6+bpo-amd64-init-systemd-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.10.6+bpo-amd64 ...'
linux /boot/vmlinuz-6.10.6+bpo-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff init=/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.10.6+bpo-amd64
}
menuentry 'MX 23.4 Libretto, with Linux 6.4.11-1-liquorix-amd64' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.4.11-1-liquorix-amd64-advanced-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.4.11-1-liquorix-amd64 ...'
linux /boot/vmlinuz-6.4.11-1-liquorix-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.4.11-1-liquorix-amd64
}
menuentry 'MX 23.4 Libretto, with Linux 6.4.11-1-liquorix-amd64 (systemd)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.4.11-1-liquorix-amd64-init-systemd-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.4.11-1-liquorix-amd64 ...'
linux /boot/vmlinuz-6.4.11-1-liquorix-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff init=/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.4.11-1-liquorix-amd64
}
menuentry 'MX 23.4 Libretto, with Linux 6.1.0-10-amd64' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-10-amd64-advanced-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.1.0-10-amd64 ...'
linux /boot/vmlinuz-6.1.0-10-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.1.0-10-amd64
}
menuentry 'MX 23.4 Libretto, with Linux 6.1.0-10-amd64 (systemd)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-10-amd64-init-systemd-dc18715d-edc0-4a54-9136-e7a9ef06a79b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
echo 'Loading Linux 6.1.0-10-amd64 ...'
linux /boot/vmlinuz-6.1.0-10-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff init=/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.1.0-10-amd64
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
if [ "${grub_platform}" == "efi" ]; then
if [ "${grub_cpu}" == "x86_64" ]; then
true
menuentry "Memory Test (64-bit UEFI)" {
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 dc18715d-edc0-4a54-9136-e7a9ef06a79b
else
search --no-floppy --fs-uuid --set=root dc18715d-edc0-4a54-9136-e7a9ef06a79b
fi
chainloader /boot/uefi-mt/mtest-64.efi
}
fi
fi
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'MX 21.3 Wildflower (21.3) (on /dev/sda1)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-6.7.10-1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet
initrd /boot/initrd.img-6.7.10-1-liquorix-amd64
}
submenu 'Advanced options for MX 21.3 Wildflower (21.3) (on /dev/sda1)' $menuentry_id_option 'osprober-gnulinux-advanced-b8238fe5-12b5-4849-8263-81fc74f6ce56' {
menuentry 'MX 21.3 Wildflower, with Linux 6.7.10-1-liquorix-amd64 (on /dev/sda1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-6.7.10-1-liquorix-amd64--b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-6.7.10-1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet
initrd /boot/initrd.img-6.7.10-1-liquorix-amd64
}
menuentry 'MX 21.3 Wildflower, with Linux 6.7.10-1-liquorix-amd64 (systemd) (on /dev/sda1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-6.7.10-1-liquorix-amd64--b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-6.7.10-1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet init=/lib/systemd/systemd
initrd /boot/initrd.img-6.7.10-1-liquorix-amd64
}
menuentry 'MX 21.3 Wildflower, with Linux 6.6.12-1-liquorix-amd64 (on /dev/sda1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-6.6.12-1-liquorix-amd64--b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-6.6.12-1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet
initrd /boot/initrd.img-6.6.12-1-liquorix-amd64
}
menuentry 'MX 21.3 Wildflower, with Linux 6.6.12-1-liquorix-amd64 (systemd) (on /dev/sda1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-6.6.12-1-liquorix-amd64--b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-6.6.12-1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet init=/lib/systemd/systemd
initrd /boot/initrd.img-6.6.12-1-liquorix-amd64
}
menuentry 'MX 21.3 Wildflower, with Linux 6.4.14-1-liquorix-amd64 (on /dev/sda1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-6.4.14-1-liquorix-amd64--b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-6.4.14-1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet
initrd /boot/initrd.img-6.4.14-1-liquorix-amd64
}
menuentry 'MX 21.3 Wildflower, with Linux 6.4.14-1-liquorix-amd64 (systemd) (on /dev/sda1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-6.4.14-1-liquorix-amd64--b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-6.4.14-1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet init=/lib/systemd/systemd
initrd /boot/initrd.img-6.4.14-1-liquorix-amd64
}
menuentry 'MX 21.3 Wildflower, with Linux 5.15.0-10.1-liquorix-amd64 (on /dev/sda1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.15.0-10.1-liquorix-amd64--b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-5.15.0-10.1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet
initrd /boot/initrd.img-5.15.0-10.1-liquorix-amd64
}
menuentry 'MX 21.3 Wildflower, with Linux 5.15.0-10.1-liquorix-amd64 (systemd) (on /dev/sda1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.15.0-10.1-liquorix-amd64--b8238fe5-12b5-4849-8263-81fc74f6ce56' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b8238fe5-12b5-4849-8263-81fc74f6ce56
else
search --no-floppy --fs-uuid --set=root b8238fe5-12b5-4849-8263-81fc74f6ce56
fi
linux /boot/vmlinuz-5.15.0-10.1-liquorix-amd64 root=UUID=b8238fe5-12b5-4849-8263-81fc74f6ce56 ro pci=realloc audit=0 intel_pstate=disable vga=895 threadirqs efi=runtime quiet init=/lib/systemd/systemd
initrd /boot/initrd.img-5.15.0-10.1-liquorix-amd64
}
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 8:06 am
by giubug
Following your suggestion, I have disabled the 3rd party Liquorix repo, installed Liquorix 6.10.11-2 64 bit from Popular Application tab.
This is the console output
Code: Select all
Hit:1 http://deb.debian.org/debian bookworm-updates InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm InRelease
Hit:5 https://repo.radeon.com/amdgpu/6.0.2/ubuntu jammy InRelease
Hit:6 http://deb.debian.org/debian bookworm InRelease
Hit:7 https://repo.steampowered.com/steam stable InRelease
Hit:8 https://dl.winehq.org/wine-builds/debian bookworm InRelease
Hit:9 https://repo.radeon.com/rocm/apt/6.0.2 jammy InRelease
Hit:10 http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu focal InRelease
Hit:11 http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu focal InRelease
Hit:12 https://liquorix.net/debian bookworm InRelease
Hit:13 http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu focal InRelease
Hit:14 https://assets.checkra.in/debian InRelease
Hit:15 http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu focal InRelease
Hit:16 http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu bionic InRelease
Hit:17 http://ppa.launchpad.net/kxstudio-debian/music/ubuntu bionic InRelease
Hit:18 http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu bionic InRelease
Hit:19 http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu bionic InRelease
Hit:20 http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu bionic InRelease
Reading package lists...
Hit:1 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://repo.radeon.com/amdgpu/6.0.2/ubuntu jammy InRelease
Hit:6 https://repo.steampowered.com/steam stable InRelease
Hit:7 http://deb.debian.org/debian bookworm InRelease
Get:8 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 Packages [101 kB]
Hit:9 https://dl.winehq.org/wine-builds/debian bookworm InRelease
Hit:10 https://repo.radeon.com/rocm/apt/6.0.2 jammy InRelease
Hit:11 http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu focal InRelease
Get:12 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs i386 Packages [86.6 kB]
Get:13 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs i386 Contents (deb) [5,656 kB]
Hit:14 http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu focal InRelease
Hit:15 https://liquorix.net/debian bookworm InRelease
Hit:16 https://assets.checkra.in/debian InRelease
Hit:17 http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu focal InRelease
Hit:18 http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu focal InRelease
Hit:19 http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu bionic InRelease
Hit:20 http://ppa.launchpad.net/kxstudio-debian/music/ubuntu bionic InRelease
Hit:21 http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu bionic InRelease
Hit:22 http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu bionic InRelease
Hit:23 http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu bionic InRelease
Get:24 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 Contents (deb) [6,864 kB]
Fetched 12.7 MB in 8s (1,638 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
rtl8821cu-dkms is already the newest version (5.12.0+git20230215-1~mx23+3).
The following package was automatically installed and is no longer required:
kbuild
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
virtualbox virtualbox-ext-pack virtualbox-guest-additions-iso virtualbox-qt
Suggested packages:
linux-doc-6.10 crda vde2
The following NEW packages will be installed:
linux-headers-6.10.11-2-liquorix-amd64 linux-image-6.10.11-2-liquorix-amd64
virtualbox-guest-additions-iso
The following packages will be upgraded:
broadcom-sta-dkms rtl8812au-dkms rtl8821ce-dkms virtualbox virtualbox-dkms
virtualbox-ext-pack virtualbox-qt
7 upgraded, 3 newly installed, 0 to remove and 55 not upgraded.
4 not fully installed or removed.
Need to get 248 MB of archives.
After this operation, 297 MB of additional disk space will be used.
Do you want to continue? [Y/n]
y
Get:1 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 virtualbox-ext-pack all 7.0.20-1~mx23+1 [12.2 kB]
Get:2 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 virtualbox amd64 7.0.20-dfsg-1~mx23+1 [29.6 MB]
Get:3 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 virtualbox-qt amd64 7.0.20-dfsg-1~mx23+1 [24.7 MB]
Get:4 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 virtualbox-dkms amd64 7.0.20-dfsg-1~mx23+1 [740 kB]
Get:5 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 virtualbox-guest-additions-iso all 7.0.20-1~mx23+1 [39.5 MB]
Get:6 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 broadcom-sta-dkms all 6.30.223.271-24~mx23+1 [2,204 kB]
Get:7 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 linux-headers-6.10.11-2-liquorix-amd64 amd64 6.10-15~mx23ahs [14.4 MB]
Get:8 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 linux-image-6.10.11-2-liquorix-amd64 amd64 6.10-15~mx23ahs [116 MB]
Get:9 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 rtl8812au-dkms all 5.13.6+git20240329-1~mx23 [18.6 MB]
Get:10 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 rtl8821ce-dkms all 5.5.2.1+git20240526-0~mx23 [2,560 kB]
Preconfiguring packages ...
Fetched 248 MB in 1min 21s (3,051 kB/s)(Reading database ... (Reading database ... 5%
(Reading database ... 10%(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%
(Reading database ... 447500 files and directories currently installed.)Preparing to unpack .../0-virtualbox-ext-pack_7.0.20-1~mx23+1_all.deb ...License has already been accepted.Unpacking virtualbox-ext-pack (7.0.20-1~mx23+1) over (7.0.10-1~mx23+1) ...Preparing to unpack .../1-virtualbox_7.0.20-dfsg-1~mx23+1_amd64.deb ...Unpacking virtualbox (7.0.20-dfsg-1~mx23+1) over (7.0.10-dfsg-2~mx23+1) ...Preparing to unpack .../2-virtualbox-qt_7.0.20-dfsg-1~mx23+1_amd64.deb ...Unpacking virtualbox-qt (7.0.20-dfsg-1~mx23+1) over (7.0.10-dfsg-2~mx23+1) ...Preparing to unpack .../3-virtualbox-dkms_7.0.20-dfsg-1~mx23+1_amd64.deb .../usr/sbin/dkms.mx status -m virtualbox -v 7.0.10/usr/sbin/dkms.mx remove -m virtualbox -v 7.0.10 --all/usr/sbin/dkms.mx status -m vboxdrv/usr/sbin/dkms.mx status -m vboxnetflt/usr/sbin/dkms.mx status -m vboxnetadpUnpacking virtualbox-dkms (7.0.20-dfsg-1~mx23+1) over (7.0.10-dfsg-2~mx23+1) ...Selecting previously unselected package virtualbox-guest-additions-iso.Preparing to unpack .../4-virtualbox-guest-additions-iso_7.0.20-1~mx23+1_all.deb ...Unpacking virtualbox-guest-additions-iso (7.0.20-1~mx23+1) ...Preparing to unpack .../5-broadcom-sta-dkms_6.30.223.271-24~mx23+1_all.deb .../usr/sbin/dkms.mx status -m broadcom-sta -v 6.30.223.271/usr/sbin/dkms.mx remove -m broadcom-sta -v 6.30.223.271 --allModule broadcom-sta-6.30.223.271 for kernel 6.1.0-10-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.
wl.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-10-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Module broadcom-sta-6.30.223.271 for kernel 6.4.11-1-liquorix-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.
wl.ko.xz:
- Uninstallation - Deleting from: /lib/modules/6.4.11-1-liquorix-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Module broadcom-sta-6.30.223.271 for kernel 6.7.12-1-liquorix-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.wl.ko.xz:
- Uninstallation
- Deleting from: /lib/modules/6.7.12-1-liquorix-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Module broadcom-sta-6.30.223.271 for kernel 6.8.4-1-liquorix-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.
wl.ko.xz:
- Uninstallation - Deleting from: /lib/modules/6.8.4-1-liquorix-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Module broadcom-sta-6.30.223.271 for kernel 6.8.9-2-liquorix-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.
wl.ko.xz:
- Uninstallation
- Deleting from: /lib/modules/6.8.9-2-liquorix-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Unpacking broadcom-sta-dkms (6.30.223.271-24~mx23+1) over (6.30.223.271-23) ...Selecting previously unselected package linux-headers-6.10.11-2-liquorix-amd64.Preparing to unpack .../6-linux-headers-6.10.11-2-liquorix-amd64_6.10-15~mx23ahs_amd64.deb ...Unpacking linux-headers-6.10.11-2-liquorix-amd64 (6.10-15~mx23ahs) ...Selecting previously unselected package linux-image-6.10.11-2-liquorix-amd64.Preparing to unpack .../7-linux-image-6.10.11-2-liquorix-amd64_6.10-15~mx23ahs_amd64.deb ...Unpacking linux-image-6.10.11-2-liquorix-amd64 (6.10-15~mx23ahs) ...Preparing to unpack .../8-rtl8812au-dkms_5.13.6+git20240329-1~mx23_all.deb .../usr/sbin/dkms.mx status -m 8812au/usr/sbin/dkms.mx remove -m 8812au -v 5.13.6 --allModule 8812au-5.13.6 for kernel 6.1.0-10-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.
8812au.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-10-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Module 8812au-5.13.6 for kernel 6.4.11-1-liquorix-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.
8812au.ko.xz:
- Uninstallation - Deleting from: /lib/modules/6.4.11-1-liquorix-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Deleting module 8812au-5.13.6 completely from the DKMS tree.Unpacking rtl8812au-dkms (5.13.6+git20240329-1~mx23) over (5.13.6+git20230720-1~mx23+1) ...Preparing to unpack .../9-rtl8821ce-dkms_5.5.2.1+git20240526-0~mx23_all.deb .../usr/sbin/dkms.mx status -m rtl8821ce -v 5.5.2.1+git20230504Unpacking rtl8821ce-dkms (5.5.2.1+git20240526-0~mx23) over (5.5.2.1+git20230504-0~mx23+1) ...Setting up linux-image-6.10.11-2-liquorix-amd64 (6.10-15~mx23ahs) ...I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.10.6+bpo-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.10.6+bpo-amd64I: /vmlinuz is now a symlink to boot/vmlinuz-6.10.11-2-liquorix-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.10.11-2-liquorix-amd64/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.10.11-2-liquorix-amd64./usr/sbin/dkms.mx autoinstall --kernelver 6.10.11-2-liquorix-amd64Error! Could not locate dkms.conf file.
File: /var/lib/dkms/virtualbox/7.0.10/source/dkms.conf does not exist.Sign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Building module:
wl.ko.xz:
Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/Sign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signedWarning: The /var/lib/dkms/rtl8821cu/5.12.0/6.10.11-2-liquorix-amd64/x86_64/dkms.conf for module rtl8821cu includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built. Skipping...dkms: autoinstall for kernel: 6.10.11-2-liquorix-amd64./etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.10.11-2-liquorix-amd64W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_1_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_1_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_0_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_0_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_3_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_3_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_2_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_2_sos.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_rlc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_mec.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_imu.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_imu.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_imu.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_rlc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_me.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_rlc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mec.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_pfp.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_rlc_1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sdma_4_4_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sdma_6_1_1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sdma_6_1_0.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_mes1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vcn_5_0_0.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_6_1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_6.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_5.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_3.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vpe_6_1_1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vpe_6_1_0.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_6.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/smu_14_0_3.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_14_0_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/dcn_3_5_1_dmcub.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/dcn_3_5_dmcub.bin for module amdgpu/etc/kernel/postinst.d/zz-update-grub:Found theme: /boot/grub/themes/StylishDark_mx/theme.txtFound linux image: /boot/vmlinuz-6.10.11-2-liquorix-amd64Found initrd image: /boot/initrd.img-6.10.11-2-liquorix-amd64Found linux image: /boot/vmlinuz-6.10.11-1-liquorix-amd64Found initrd image: /boot/initrd.img-6.10.11-1-liquorix-amd64Found linux image: /boot/vmlinuz-6.10.6+bpo-amd64Found initrd image: /boot/initrd.img-6.10.6+bpo-amd64Found linux image: /boot/vmlinuz-6.4.11-1-liquorix-amd64Found initrd image: /boot/initrd.img-6.4.11-1-liquorix-amd64Found linux image: /boot/vmlinuz-6.1.0-10-amd64Found initrd image: /boot/initrd.img-6.1.0-10-amd64Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efiFound MX 21.3 Wildflower (21.3) on /dev/sdb1Adding boot menu entry for EFI firmware configurationSetting up virtualbox-guest-additions-iso (7.0.20-1~mx23+1) ...Setting up rtl8821ce-dkms (5.5.2.1+git20240526-0~mx23) ...Loading new rtl8821ce-5.5.2.1+git20240526 DKMS files.../usr/sbin/dkms.mx add -m rtl8821ce -v 5.5.2.1+git20240526Deprecated feature: MODULES_CONF (/usr/src/rtl8821ce-5.5.2.1+git20240526/dkms.conf)Building for 6.1.0-10-amd64 6.10.11-2-liquorix-amd64/usr/sbin/dkms.mx status -m rtl8821ce -v 5.5.2.1+git20240526 -k 6.1.0-10-amd64Building initial module for 6.1.0-10-amd64/usr/sbin/dkms.mx build -m rtl8821ce -v 5.5.2.1+git20240526 -k 6.1.0-10-amd64 -k 6.4.11-1-liquorix-amd64 -k 6.1.0-10-amd64 -k 6.10.11-2-liquorix-amd64 -a x86_64Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Done./usr/sbin/dkms.mx status -m rtl8821ce -v 5.5.2.1+git20240526 -k 6.1.0-10-amd64Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)/usr/sbin/dkms.mx install -m rtl8821ce -v 5.5.2.1+git20240526 -k 6.1.0-10-amd64 -k 6.4.11-1-liquorix-amd64 -k 6.1.0-10-amd64 -k 6.10.11-2-liquorix-amd64 -a x86_64Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
rtl8821ce.ko:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-10-amd64/updates/dkms/Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
rtl8821ce.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation - Installing to /lib/modules/6.4.11-1-liquorix-amd64/updates/dkms/Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Module rtl8821ce/5.5.2.1+git20240526 already installed on kernel 6.1.0-10-amd64 (x86_64), skip. You may override by specifying --force.Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
rtl8821ce.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms//usr/sbin/dkms.mx status -m rtl8821ce -v 5.5.2.1+git20240526 -k 6.10.11-2-liquorix-amd64Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Building initial module for 6.10.11-2-liquorix-amd64/usr/sbin/dkms.mx build -m rtl8821ce -v 5.5.2.1+git20240526 -k 6.10.11-2-liquorix-amd64 -k 6.4.11-1-liquorix-amd64 -k 6.1.0-10-amd64 -k 6.10.11-2-liquorix-amd64 -a x86_64Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Done./usr/sbin/dkms.mx status -m rtl8821ce -v 5.5.2.1+git20240526 -k 6.10.11-2-liquorix-amd64MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Setting up rtl8812au-dkms (5.13.6+git20240329-1~mx23) ...
Configuration file '/etc/modprobe.d/8812au.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** 8812au.conf (Y/I/N/O/D/Z) [default=N] ?
/usr/sbin/dkms.mx add -m 8812au -v 5.13.6Creating symlink /var/lib/dkms/8812au/5.13.6/source -> /usr/src/8812au-5.13.6/usr/sbin/dkms.mx build -m 8812au -v 5.13.6 -k 6.4.11-1-liquorix-amd64 -k 6.1.0-10-amd64 -k 6.10.11-2-liquorix-amd64 -a x86_64Sign command: /lib/modules/6.4.11-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.4.11-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Building module:Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:Signing module /var/lib/dkms/8812au/5.13.6/build/8812au.koSign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Building module:/usr/sbin/dkms.mx install -m 8812au -v 5.13.6 -k 6.4.11-1-liquorix-amd64 -k 6.1.0-10-amd64 -k 6.10.11-2-liquorix-amd64 -a x86_64
8812au.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.4.11-1-liquorix-amd64/updates/dkms/
8812au.ko:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-10-amd64/updates/dkms/
8812au.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/Finished running dkms install steps.Finished setting crda country code.Setting up linux-headers-6.10.11-2-liquorix-amd64 (6.10-15~mx23ahs) .../etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.10.11-2-liquorix-amd64./usr/sbin/dkms.mx autoinstall --kernelver 6.10.11-2-liquorix-amd64MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Error! Could not locate dkms.conf file.
File: /var/lib/dkms/virtualbox/7.0.10/source/dkms.conf does not exist.Sign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signedWarning: The /var/lib/dkms/rtl8821cu/5.12.0/6.10.11-2-liquorix-amd64/x86_64/dkms.conf for module rtl8821cu includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built. Skipping...dkms: autoinstall for kernel: 6.10.11-2-liquorix-amd64.Setting up broadcom-sta-dkms (6.30.223.271-24~mx23+1) ...Removing old broadcom-sta-6.30.223.271 DKMS files.../usr/sbin/dkms.mx remove -m broadcom-sta -v 6.30.223.271 --allModule broadcom-sta-6.30.223.271 for kernel 6.10.11-2-liquorix-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.
wl.ko.xz:
- Uninstallation
- Deleting from: /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Loading new broadcom-sta-6.30.223.271 DKMS files.../usr/sbin/dkms.mx add -m broadcom-sta -v 6.30.223.271Error! DKMS tree already contains: broadcom-sta-6.30.223.271
You cannot add the same module/version combo more than once.dpkg: error processing package broadcom-sta-dkms (--configure):
installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 3
Setting up virtualbox-dkms (7.0.20-dfsg-1~mx23+1) ...Loading new virtualbox-7.0.20 DKMS files.../usr/sbin/dkms.mx add -m virtualbox -v 7.0.20Building for 6.1.0-10-amd64 6.10.11-2-liquorix-amd64/usr/sbin/dkms.mx status -m virtualbox -v 7.0.20 -k 6.1.0-10-amd64Building initial module for 6.1.0-10-amd64/usr/sbin/dkms.mx build -m virtualbox -v 7.0.20 -k 6.1.0-10-amd64 -k 6.4.11-1-liquorix-amd64 -k 6.1.0-10-amd64 -k 6.10.11-2-liquorix-amd64 -a x86_64Done./usr/sbin/dkms.mx status -m virtualbox -v 7.0.20 -k 6.1.0-10-amd64/usr/sbin/dkms.mx install -m virtualbox -v 7.0.20 -k 6.1.0-10-amd64 -k 6.4.11-1-liquorix-amd64 -k 6.1.0-10-amd64 -k 6.10.11-2-liquorix-amd64 -a x86_64
vboxdrv.ko:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-10-amd64/updates/dkms/
vboxnetadp.ko:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-10-amd64/updates/dkms/
vboxnetflt.ko:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-10-amd64/updates/dkms/
vboxdrv.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation - Installing to /lib/modules/6.4.11-1-liquorix-amd64/updates/dkms/
vboxnetadp.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.4.11-1-liquorix-amd64/updates/dkms/
vboxnetflt.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.4.11-1-liquorix-amd64/updates/dkms/Module virtualbox/7.0.20 already installed on kernel 6.1.0-10-amd64 (x86_64), skip. You may override by specifying --force.
vboxdrv.ko.xz:
Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/
vboxnetadp.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/
vboxnetflt.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation - Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms//usr/sbin/dkms.mx status -m virtualbox -v 7.0.20 -k 6.10.11-2-liquorix-amd64Building initial module for 6.10.11-2-liquorix-amd64/usr/sbin/dkms.mx build -m virtualbox -v 7.0.20 -k 6.10.11-2-liquorix-amd64 -k 6.4.11-1-liquorix-amd64 -k 6.1.0-10-amd64 -k 6.10.11-2-liquorix-amd64 -a x86_64Done./usr/sbin/dkms.mx status -m virtualbox -v 7.0.20 -k 6.10.11-2-liquorix-amd64Setting up virtualbox-qt (7.0.20-dfsg-1~mx23+1) ...Setting up virtualbox (7.0.20-dfsg-1~mx23+1) .... vboxnetadp.Setting up virtualbox-ext-pack (7.0.20-1~mx23+1) ...virtualbox-ext-pack: downloading: https://download.virtualbox.org/virtualbox/7.0.20/Oracle_VM_VirtualBox_Extension_Pack-7.0.20.vbox-extpack
The file will be downloaded into /var/cache/virtualbox-ext-packLicense accepted.100%
Successfully installed "Oracle VM VirtualBox Extension Pack".Processing triggers for desktop-file-utils (0.26-1) ...Processing triggers for hicolor-icon-theme (0.17-2) ...Processing triggers for gnome-menus (3.36.0-1.1) ...Processing triggers for man-db (2.11.2-2) ...Processing triggers for shared-mime-info (2.2-1) ...Processing triggers for mailcap (3.70+nmu1) ...Errors were encountered while processing:
broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
Hit:1 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm InRelease
Hit:2 https://repo.radeon.com/amdgpu/6.0.2/ubuntu jammy InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 http://security.debian.org/debian-security bookworm-security InRelease
Hit:5 http://deb.debian.org/debian bookworm-updates InRelease
Hit:6 https://repo.steampowered.com/steam stable InRelease
Hit:7 http://deb.debian.org/debian bookworm InRelease
Hit:8 https://repo.radeon.com/rocm/apt/6.0.2 jammy InRelease
Hit:9 https://dl.winehq.org/wine-builds/debian bookworm InRelease
Hit:10 http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu focal InRelease
Hit:11 https://liquorix.net/debian bookworm InRelease
Hit:12 http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu focal InRelease
Hit:13 https://assets.checkra.in/debian InRelease
Hit:14 http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu focal InRelease
Hit:15 http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu focal InRelease
Hit:16 http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu bionic InRelease
Hit:17 http://ppa.launchpad.net/kxstudio-debian/music/ubuntu bionic InRelease
Hit:18 http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu bionic InRelease
Hit:19 http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu bionic InRelease
Hit:20 http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu bionic InRelease
Reading package lists...
When I reboot using the new Kernel, the loading screen with the blue sun appears, albeit at a lower resolution. when loading is finished, there is the blinking cursor again. I can Ctrl+Alt+F1 go into a terminal and reboot from there. To me these are all signs of GPU drivers not loading properly.
Should I disable the 3rd party amdgpu repo as well? I am worried about bricking my system, which otherwise works fine.
Thank you for the help
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 8:29 am
by Eadwine Rose
I can Ctrl+Alt+F1 go into a terminal
and what does
startx
do?
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 8:58 am
by giubug
Server cannot be started.
How to provide you with more informations?
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 10:13 am
by Kermit the Frog
What if you boot without the
amdgpu.ppfeaturemask=0xffffffff ?
( Press E when on Grub, delete that parameter , press F10 to go on boot. )
Meanwhile your card is supported by 6.10 :
( From Mine):
Code: Select all
$ uname -r
6.10.3-1-liquorix-amd64
alias: pci:v0000
1002d0000
6FDFsv*sd*bc*sc*i*
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 10:25 am
by siamhie
Code: Select all
Repos:
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
Do you still have Debian's 6.1 kernel installed? If so, can you boot with that.
I'm curious about this section from grub
Code: Select all
linux /boot/vmlinuz-6.10.11-1-liquorix-amd64 root=UUID=dc18715d-edc0-4a54-9136-e7a9ef06a79b ro quiet splash amdgpu.ppfeaturemask=0xffffffff
Are you running corectrl?
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 10:29 am
by giubug
Are you running corectrl?
yes, corectrl is necessary or my GPU will black out
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 11:16 am
by siamhie
giubug wrote: Fri Sep 27, 2024 10:29 am
Are you running corectrl?
yes, corectrl is necessary or my GPU will black out
corectrl is a utility for controlling Radeon GPU fans and overclocking.
Code: Select all
Device-1: AMD Polaris 20 XL [Radeon RX 580 2048SP] driver: amdgpu v: kernel arch: GCN-4
I had no problems running my RX580 in MX without corectrl.
I also noticed this repo.
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
Did you install your GPU drivers from the AMD web site?
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 12:19 pm
by giubug
In order to use the RX580 with good results in high demanding tasks, the card actually needs to be underclocked. there is much information about this topic on the web.
amdgpu worked straight out of the box with MX23. I definitely did not install the drivers from the AMD website. I went through that ordeal in a previous install of MX21, made a mess of it there, did a clean install of MX23 and the GPU worked just fine.
Under heavy load, the GPU would easily black out. Corectrl is used to fine tune voltages and clock rates. after underclocking, there is a net increase in performance (counterintuitive) and no more black outs.
whether installing corectrl automatically adds this repo, i couldn't be sure about that. but I am sure I didn't add that repo manually.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 12:41 pm
by siamhie
giubug wrote: Fri Sep 27, 2024 12:19 pm
whether installing corectrl automatically adds this repo, i couldn't be sure about that. but I am sure I didn't add that repo manually.
I'm well aware of corectrl (having used it myself before moving to
LACT) but it doesn't add the AMD repo.
Have you tried booting with the default 6.1 kernel?
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 3:30 pm
by DukeComposed
giubug wrote: Fri Sep 27, 2024 5:44 am
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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 9:40 pm
by 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].
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 10:05 pm
by siamhie
asqwerth wrote: Fri Sep 27, 2024 9:40 pm
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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 10:21 pm
by 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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 10:32 pm
by 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.
Re: Cannot upgrade Headers
Posted: Fri Sep 27, 2024 10:53 pm
by 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).
Re: Cannot upgrade Kernel
Posted: Sat Sep 28, 2024 6:16 am
by 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.
Re: Cannot upgrade Kernel
Posted: Sat Sep 28, 2024 9:15 am
by giubug
linexer2016 wrote: Sat Sep 28, 2024 6:16 am
@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.
Re: Cannot upgrade Headers
Posted: Sat Sep 28, 2024 9:17 am
by giubug
siamhie wrote: Fri Sep 27, 2024 10:53 pm
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
Re: Cannot upgrade Headers
Posted: Sat Sep 28, 2024 9:41 am
by siamhie
giubug wrote: Sat Sep 28, 2024 9:17 am
siamhie wrote: Fri Sep 27, 2024 10:53 pm
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.
Re: Cannot upgrade Kernel
Posted: Sat Sep 28, 2024 10:35 am
by giubug
removed
First attempt was unsuccessful.
2nd attempt was successful. Linux 6.1.0-10-amd64
Re: Cannot upgrade Kernel
Posted: Sat Sep 28, 2024 10:57 pm
by siamhie
giubug wrote: Sat Sep 28, 2024 10:35 am
removed
First attempt was unsuccessful.
2nd attempt was successful. Linux 6.1.0-10-amd64
Keeping that feature turned off for the time being, let's see if you can update to the latest Liquorix kernel provided by MX.
First open MX Repo Manager and go to the Individual sources tab. In the mx.list section check the box that has the "bookworm ahs" entry and apply.
Now open a terminal and type "sudo apt update" to update your sources. (window on the left)
After you have done that open MX Package Installer and on the Popular Applications tab, go to the Kernels section.
Select the Liquorix 64 bit (ahs update package) and click Install. (window on the right)
After you've installed the kernel, go ahead and reboot the computer into the 6.10.11-2 kernel.
Let us know if that works. (remember you have the 6.1.0-10 kernel to fall back on if anything goes wrong)
Re: Cannot upgrade Kernel
Posted: Sun Sep 29, 2024 12:30 am
by giubug
I followed your instructions, his is the console output
Code: Select all
Hit:1 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm InRelease
Hit:2 https://repo.steampowered.com/steam stable InRelease
Hit:3 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 https://repo.radeon.com/amdgpu/6.0.2/ubuntu jammy InRelease
Hit:5 http://security.debian.org/debian-security bookworm-security InRelease
Hit:6 http://deb.debian.org/debian bookworm-updates InRelease
Hit:7 http://deb.debian.org/debian bookworm InRelease
Hit:8 https://repo.radeon.com/rocm/apt/6.0.2 jammy InRelease
Hit:9 https://dl.winehq.org/wine-builds/debian bookworm InRelease
Hit:10 https://liquorix.net/debian bookworm InRelease
Hit:11 http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu focal InRelease
Hit:12 http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu focal InRelease
Hit:13 https://assets.checkra.in/debian InRelease
Hit:14 http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu focal InRelease
Hit:15 http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu focal InRelease
Hit:16 http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu bionic InRelease
Hit:17 http://ppa.launchpad.net/kxstudio-debian/music/ubuntu bionic InRelease
Hit:18 http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu bionic InRelease
Hit:19 http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu bionic InRelease
Hit:20 http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu bionic InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
broadcom-sta-dkms is already the newest version (6.30.223.271-24~mx23+1).
rtl8812au-dkms is already the newest version (5.13.6+git20240329-1~mx23).
rtl8821ce-dkms is already the newest version (5.5.2.1+git20240526-0~mx23).
rtl8821cu-dkms is already the newest version (5.12.0+git20230215-1~mx23+3).
virtualbox-dkms is already the newest version (7.0.20-dfsg-1~mx23+1).
The following package was automatically installed and is no longer required:
kbuild
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
linux-headers-6.10.11-2-liquorix-amd64 linux-image-6.10.11-2-liquorix-amd64
Suggested packages:
linux-doc-6.10 crda
The following NEW packages will be installed:
linux-headers-6.10.11-2-liquorix-amd64 linux-headers-liquorix-amd64
linux-image-6.10.11-2-liquorix-amd64 linux-image-liquorix-amd64
0 upgraded, 4 newly installed, 0 to remove and 55 not upgraded.
1 not fully installed or removed.
Need to get 131 MB of archives.
After this operation, 233 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 linux-headers-6.10.11-2-liquorix-amd64 amd64 6.10-15~mx23ahs [14.4 MB]
Get:2 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 linux-image-6.10.11-2-liquorix-amd64 amd64 6.10-15~mx23ahs [116 MB]
Get:3 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 linux-headers-liquorix-amd64 amd64 6.10-15~mx23ahs [30.8 kB]
Get:4 https://mxlinux.cs.nycu.edu.tw/mx-workspace/mx/repo bookworm/ahs amd64 linux-image-liquorix-amd64 amd64 6.10-15~mx23ahs [30.8 kB]
Fetched 131 MB in 52s (2,501 kB/s)Selecting previously unselected package linux-headers-6.10.11-2-liquorix-amd64.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%
(Reading database ... 447552 files and directories currently installed.)Preparing to unpack .../linux-headers-6.10.11-2-liquorix-amd64_6.10-15~mx23ahs_amd64.deb ...Unpacking linux-headers-6.10.11-2-liquorix-amd64 (6.10-15~mx23ahs) ...Selecting previously unselected package linux-image-6.10.11-2-liquorix-amd64.Preparing to unpack .../linux-image-6.10.11-2-liquorix-amd64_6.10-15~mx23ahs_amd64.deb ...Unpacking linux-image-6.10.11-2-liquorix-amd64 (6.10-15~mx23ahs) ...Selecting previously unselected package linux-headers-liquorix-amd64.Preparing to unpack .../linux-headers-liquorix-amd64_6.10-15~mx23ahs_amd64.deb ...Unpacking linux-headers-liquorix-amd64 (6.10-15~mx23ahs) ...Selecting previously unselected package linux-image-liquorix-amd64.Preparing to unpack .../linux-image-liquorix-amd64_6.10-15~mx23ahs_amd64.deb ...Unpacking linux-image-liquorix-amd64 (6.10-15~mx23ahs) ...Setting up linux-image-6.10.11-2-liquorix-amd64 (6.10-15~mx23ahs) ...I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.10.6+bpo-amd64I: /initrd.img.old is now a symlink to boot/initrd.img-6.10.6+bpo-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.10.11-2-liquorix-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.10.11-2-liquorix-amd64/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.10.11-2-liquorix-amd64./usr/sbin/dkms.mx autoinstall --kernelver 6.10.11-2-liquorix-amd64Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Error! Could not locate dkms.conf file.
File: /var/lib/dkms/virtualbox/7.0.10/source/dkms.conf does not exist.Sign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-fileBinary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Building module:
8812au.ko.xz:
Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/Sign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Building module:
wl.ko.xz:Running module version sanity check. - Original module - No original module exists within this kernel
- Installation - Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/Sign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signedDeprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
Building module:
'make' -j8 KVER=6.10.11-2-liquorix-amd64 USER_MODULE_NAME=rtl8821ce
rtl8821ce.ko.xz:
Running module version sanity check. - Original module - No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/Sign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signedWarning: The /var/lib/dkms/rtl8821cu/5.12.0/6.10.11-2-liquorix-amd64/x86_64/dkms.conf for module rtl8821cu includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built. Skipping...dkms: autoinstall for kernel: 6.10.11-2-liquorix-amd64./etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.10.11-2-liquorix-amd64W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_1_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_1_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_0_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_0_toc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_3_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_3_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_2_ta.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_2_sos.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_rlc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_mec.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_imu.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_imu.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_imu.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_rlc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_me.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mec.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_rlc_1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sdma_4_4_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sdma_6_1_1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sdma_6_1_0.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_mes1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_1_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vcn_5_0_0.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_6_1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_6.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_5.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_3.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vpe_6_1_1.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/vpe_6_1_0.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_6.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/smu_14_0_3.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_14_0_2.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/dcn_3_5_1_dmcub.bin for module amdgpuW: Possible missing firmware /lib/firmware/amdgpu/dcn_3_5_dmcub.bin for module amdgpu/etc/kernel/postinst.d/zz-update-grub:Found theme: /boot/grub/themes/StylishDark_mx/theme.txtFound linux image: /boot/vmlinuz-6.10.11-2-liquorix-amd64Found initrd image: /boot/initrd.img-6.10.11-2-liquorix-amd64Found linux image: /boot/vmlinuz-6.10.11-1-liquorix-amd64Found initrd image: /boot/initrd.img-6.10.11-1-liquorix-amd64Found linux image: /boot/vmlinuz-6.10.6+bpo-amd64Found initrd image: /boot/initrd.img-6.10.6+bpo-amd64Found linux image: /boot/vmlinuz-6.4.11-1-liquorix-amd64Found initrd image: /boot/initrd.img-6.4.11-1-liquorix-amd64Found linux image: /boot/vmlinuz-6.1.0-10-amd64Found initrd image: /boot/initrd.img-6.1.0-10-amd64Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efiFound MX 21.3 Wildflower (21.3) on /dev/sda1Adding boot menu entry for EFI firmware configurationSetting up linux-headers-6.10.11-2-liquorix-amd64 (6.10-15~mx23ahs) .../etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.10.11-2-liquorix-amd64./usr/sbin/dkms.mx autoinstall --kernelver 6.10.11-2-liquorix-amd64Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)Error! Could not locate dkms.conf file.
File: /var/lib/dkms/virtualbox/7.0.10/source/dkms.conf does not exist.Sign command: /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.10.11-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signedThe /var/lib/dkms/rtl8821cu/5.12.0/6.10.11-2-liquorix-amd64/x86_64/dkms.conf for module rtl8821cu includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built. Skipping...dkms: autoinstall for kernel: 6.10.11-2-liquorix-amd64.Setting up linux-headers-liquorix-amd64 (6.10-15~mx23ahs) ...Setting up broadcom-sta-dkms (6.30.223.271-24~mx23+1) ...Removing old broadcom-sta-6.30.223.271 DKMS files.../usr/sbin/dkms.mx remove -m broadcom-sta -v 6.30.223.271 --allModule broadcom-sta-6.30.223.271 for kernel 6.10.11-2-liquorix-amd64 (x86_64).Before uninstall, this module version was ACTIVE on this kernel.
wl.ko.xz:
- Uninstallation
- Deleting from: /lib/modules/6.10.11-2-liquorix-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.Loading new broadcom-sta-6.30.223.271 DKMS files.../usr/sbin/dkms.mx add -m broadcom-sta -v 6.30.223.271Error! DKMS tree already contains: broadcom-sta-6.30.223.271
You cannot add the same module/version combo more than once.dpkg: error processing package broadcom-sta-dkms (--configure):
installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 3Setting up linux-image-liquorix-amd64 (6.10-15~mx23ahs) ...Errors were encountered while processing:
broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
Unfortunately, no luck. I tried two times, also removed the amdgpu option in Grub menu. Blinking cursor, but Ctrl+Alt+Del restarts the computer. I tried to startx , the error message is connection cannot be established
Re: Cannot upgrade Kernel
Posted: Sun Sep 29, 2024 1:20 am
by linexer2016
@giubug
@siamhie
I've been following this thread with some interest due (as stated to giubug in particular) quite similar issues with my set up. I'm running 6.5 ahs with xfce and boot with sysvinit not systemd if that is any factor.
I have tried before the various ways to review repo manager and update kernels from MXPI also to no avail - I can't do anything but keep my current (and only) kernel as described.
giubug, rather than relying on the three finger salute you may like to use Timeshift. That as I've previously mentioned, has saved me a lot of issues in getting my system back up and running without having to boot to a command screen and using the startx and etc route that has been mentioned here.
Re: Cannot upgrade Kernel
Posted: Sun Sep 29, 2024 2:22 am
by siamhie
giubug wrote: Sun Sep 29, 2024 12:30 am
I followed your instructions, his is the console output
Code: Select all
You cannot add the same module/version combo more than once.dpkg: error processing package broadcom-sta-dkms (--configure):
installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 3Setting up linux-image-liquorix-amd64 (6.10-15~mx23ahs) ...Errors were encountered while processing:
broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
Unfortunately, no luck. I tried two times, also removed the amdgpu option in Grub menu. Blinking cursor, but Ctrl+Alt+Del restarts the computer. I tried to startx , the error message is connection cannot be established
You seem to be running into issues with that broadcom module.
Try this. Boot back up into the working 6.1 kernel, run MX Cleanup and select Remove unused WiFi drivers.
If it removes the broadcom drivers then try installing the Liquorix kernel again.
Re: Cannot upgrade Kernel
Posted: Sun Sep 29, 2024 2:23 am
by Stevo
You're getting an issue with building a Broadcom wi-fi driver we include on the ISO with a 6.10 kernel. But you don't need it, so the simplest thing to solve this is to use MX Cleanup to remove all the extra unused wi-fi drivers we ship by default, because we want it to work to "just work". We suggest removing unused drivers right after the installation, or even in the Live session, because they are a waste of time to build if you don't use them.
That's an issue with just installing a newer kernel by itself, because we do have updated drivers that will work with newer kernels, but they are in the Advanced Hardware Support (ahs) section of the repositories. They just work if you add the ahs section and upgrade, or if you use the AHS edition (MX-KDE uses it, but with the stock Bookworm 6.1 kernel).
Re: Cannot upgrade Kernel
Posted: Mon Sep 30, 2024 11:11 pm
by giubug
siamhie wrote: Sun Sep 29, 2024 2:22 am
giubug wrote: Sun Sep 29, 2024 12:30 am
I followed your instructions, his is the console output
Code: Select all
You cannot add the same module/version combo more than once.dpkg: error processing package broadcom-sta-dkms (--configure):
installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 3Setting up linux-image-liquorix-amd64 (6.10-15~mx23ahs) ...Errors were encountered while processing:
broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
Unfortunately, no luck. I tried two times, also removed the amdgpu option in Grub menu. Blinking cursor, but Ctrl+Alt+Del restarts the computer. I tried to startx , the error message is connection cannot be established
You seem to be running into issues with that broadcom module.
Try this. Boot back up into the working 6.1 kernel, run MX Cleanup and select Remove unused WiFi drivers.
If it removes the broadcom drivers then try installing the Liquorix kernel again.
I followed the steps outlined in your solution, but the situation has not changed.
Should I disable the Ubuntu Jammy amdgpu Repo?
Re: Cannot upgrade Kernel
Posted: Tue Oct 01, 2024 12:06 am
by siamhie
giubug wrote: Mon Sep 30, 2024 11:11 pm
siamhie wrote: Sun Sep 29, 2024 2:22 am
giubug wrote: Sun Sep 29, 2024 12:30 am
I followed your instructions, his is the console output
Code: Select all
You cannot add the same module/version combo more than once.dpkg: error processing package broadcom-sta-dkms (--configure):
installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 3Setting up linux-image-liquorix-amd64 (6.10-15~mx23ahs) ...Errors were encountered while processing:
broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
Unfortunately, no luck. I tried two times, also removed the amdgpu option in Grub menu. Blinking cursor, but Ctrl+Alt+Del restarts the computer. I tried to startx , the error message is connection cannot be established
You seem to be running into issues with that broadcom module.
Try this. Boot back up into the working 6.1 kernel, run MX Cleanup and select Remove unused WiFi drivers.
If it removes the broadcom drivers then try installing the Liquorix kernel again.
I followed the steps outlined in your solution, but the situation has not changed.
Should I disable the Ubuntu Jammy amdgpu Repo?
Yes. As others have pointed out already, disable all Ubuntu repos, the Liquorix repo, the amdgpu repo so that you only have the Debian and MX repos enabled. MX Repo Manager can help with this.
You can enable them (if you wish) at a later time but we are trying to get you updated to the latest kernel from the MX repo.
Re: Cannot upgrade Kernel
Posted: Tue Oct 01, 2024 3:15 am
by LinuxSpring1
One newbie question. Ubunutu is based on Debian. So is MX Linux. So if a driver is built by AMD for Ubuntu that should ideally work with Debian and its derivatives too. But in this case it fails. Why is that the case?
Also the issue appears to be fixed because of the
post by
@siamhie which called for removing the corectrl code from boot options
Re: Cannot upgrade Kernel
Posted: Tue Oct 01, 2024 3:42 am
by Eadwine Rose
LinuxSpring1 wrote: Tue Oct 01, 2024 3:15 am
One newbie question. Ubunutu is based on Debian. So is MX Linux. So if a driver is built by AMD for Ubuntu that should ideally work with Debian and its derivatives too. But in this case it fails. Why is that the case?
Please open your own topic to discuss this.
Re: Cannot upgrade Kernel
Posted: Tue Oct 01, 2024 7:20 am
by siamhie
LinuxSpring1 wrote: Tue Oct 01, 2024 3:15 am
Also the issue appears to be fixed because of the
post by @siamhie which called for removing the corectrl code from boot options
The issue isn't fixed because OP still can't install the 6.10 Liquorix kernel from the MX repo.
They are able to boot to the desktop with the 6.1 kernel (from the repo) with the
amdgpu.ppfeaturemask=0xffffffff boot option removed.
They are using that variable to undervolt their GPU with corectrl.
Re: Cannot upgrade Kernel
Posted: Tue Oct 01, 2024 12:07 pm
by Stevo
LinuxSpring1 wrote: Tue Oct 01, 2024 3:15 am
One newbie question. Ubunutu is based on Debian. So is MX Linux. So if a driver is built by AMD for Ubuntu that should ideally work with Debian and its derivatives too. But in this case it fails. Why is that the case?
Also the issue appears to be fixed because of the
post by @siamhie which called for removing the corectrl code from boot options
I should wait for the new topic, but it's for the same reason you are playing with fire if adding upstream
Debian packages to MX stable: they are very probably not going to be built against the same system libraries as your stable Debian release. They may seem to work fine, but could also then also have subtle bugs later that will be very difficult to root out.
Re: Cannot upgrade Kernel
Posted: Wed Oct 02, 2024 8:34 am
by giubug
Update: after trying many times, I can not longer boot in 6.1 Generic Kernel.
Re: Cannot upgrade Kernel
Posted: Wed Oct 02, 2024 9:05 am
by siamhie
giubug wrote: Wed Oct 02, 2024 8:34 am
Update: after trying many times, I can not longer boot in 6.1 Generic Kernel.
At this point, I would just re-install. With so many various repos installed, it's hard to distinguish which one is causing problems.
The good news is you have got a separate home partition, so no need to back up config files.
Code: Select all
Partition:
ID-1: / raw-size: 307.32 GiB size: 301.43 GiB (98.08%) used: 33.21 GiB (11.0%) fs: ext4
dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 623.94 GiB size: 613.08 GiB (98.26%) used: 393.55 GiB (64.2%) fs: ext4
dev: /dev/sdb3 maj-min: 8:19
I would download a new copy of MX-23 and this time grab the ahs version (third link).
https://mxlinux.org/download-links/