MX Linux Forum • Failed kernel update Mx-23

Page 1 of 1

Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 4:30 am

by Pakos

My Mx 23 install is 2 months old, had a kernel update last month that gave me errors but the system kept working. Yesterday there was another kernel update, but this time i am unable to boot into my system.

I get this at boot: https://imgur.com/JlumOJW.png

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 5:23 am

by m_pav

First thing that comes to mind is you may have a dirty flag on your partitions. Boot with our Live USB, open gparted, right click your MX Linux root partition and select check, then click the button to perform the action. Repeat for all Linux type filesystems except for swap, then reboot and see how things go.

Before you reboot, can I suggest you fire up gsmartctl and see if your drive has errors. You'll know as soon as you select the drive if something is wrong because either the drive will be red before you select it for really bad faults, or the tab labels will be red after you open the drive to see its attributres. The brighter the red, the worse it is. This is assuming you have SATA drives, not NVME, those need a different tool which is not included on the ISO, but I think should be, nvme-cli

Once these things have been addresses, we can assist with the kernel.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 5:58 am

by Pakos

Done, no errors, no red. (sata).. Still no able to boot into, same screen.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 6:41 am

by m_pav

Next step, run MX Boot repair from Live. It'll ask you what drive to use so you can be sure you have the right drive.
Incidentally, this app also works running from an installed system to fix a Live-USB that was damaged by an unsafe removal from a Windows machine.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 6:52 am

by Pakos

I understand, last time when i did this. I kept selecting the wrong drive and made things worse. Could you tell me which one to select?

https://imgur.com/p5KCNfr.png

SDA4 was selected by default.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 7:07 am

by j2mcgreg

@Pakos
Is this the same machine for which you posted a QSI in post #15 in this thread from 2021?
viewtopic.php?t=64949&start=10

Is that ppa still active?

Code: Select all

 Active apt repos in: /etc/apt/sources.list 
           1: deb ppa:agornostal/ulauncher Ulauncher Ulauncher

Back then, your cpu was running way too hot:

Code: Select all

System Temperatures: cpu: 83.0 C mobo: N/A 
           Fan Speeds (RPM): N/A

Has this machine been cleaned and the thermal paste replaced since then?

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 7:11 am

by Pakos

j2mcgreg wrote: Fri Jul 19, 2024 7:07 am Is this the same machine for which you posted a QSI in post #15 in this thread from 2021?
Has this machine been cleaned and the thermal paste replaced since then?

No, i retired that laptop 2 years ago. It's not my daily driver anymore.
Yes, i regularly maintain my machines by cleaning and replacing the thermal pastes.
---
Anyway back to my current machine, which partition to select during boot repair?

https://imgur.com/p5KCNfr.png

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 7:51 am

by j2mcgreg

While you have a live session active, please post the QSI for this machine.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 8:02 am

by Pakos

j2mcgreg wrote: Fri Jul 19, 2024 7:51 am While you have a live session active, please post the QSI for this machine.

Code: Select all

Skander@Mx23:~
$ sudo inxi -Fxz
[sudo] wachtwoord voor Skander:           
System:
  Kernel: 6.1.0-21-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    Desktop: Xfce v: 4.18.1 Distro: MX-23.3_x64 Libretto May 19  2024
    base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Dell product: OptiPlex 9020 v: 00 serial: <filter>
  Mobo: Dell model: 00V62H v: A01 serial: <filter> UEFI: Dell v: A25
    date: 05/30/2019
CPU:
  Info: quad core model: Intel Core i5-4690 bits: 64 type: MCP arch: Haswell
    rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 2263 high: 2283 min/max: 800/3900 cores: 1: 2269 2: 2232
    3: 2268 4: 2283 bogomips: 27936
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: Dell driver: i915 v: kernel arch: Gen-7.5 bus-ID: 00:02.0
  Display: server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1680x1050~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4600 (HSW
    GT2) direct-render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Dell 8
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  API: ALSA v: k6.1.0-21-amd64 status: kernel-api
  Server-1: PipeWire v: 1.0.0 status: n/a (root, process)
Network:
  Device-1: Intel Ethernet I217-LM vendor: Dell driver: e1000e v: kernel
    port: f080 bus-ID: 00:19.0
  IF: eth0 state: down mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
  IF-ID-2: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek 802.11ac NIC type: USB driver: btusb,rtl88x2bu
    bus-ID: 3-12:4
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1
    lmp-v: 4.2
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0
    bus-ID: 00:1f.2
Drives:
  Local Storage: total: 883.1 GiB used: 39.55 GiB (4.5%)
  ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
  ID-2: /dev/sdb vendor: Hitachi model: HTS723232A7A364 size: 298.09 GiB
  ID-3: /dev/sdc type: USB vendor: Samsung model: SSD PM871 2.5 7mm 128GB
    size: 119.24 GiB
Partition:
  Message: No partition data found.
Swap:
  ID-1: swap-1 type: file size: 4 GiB used: 3 MiB (0.1%)
    file: /live/boot-dev/swap-file
Sensors:
  System Temperatures: cpu: 52.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 266 Uptime: 2h 4m Memory: 7.66 GiB used: 4.31 GiB (56.2%)
  Init: SysVinit runlevel: 5 Compilers: gcc: 12.2.0 Packages: 2158 Shell: Sudo
  v: 1.9.13p3 inxi: 3.3.26

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 8:03 am

by Eadwine Rose

Quick system info, from the menu please, thanks :)

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 8:18 am

by Pakos

Code: Select all

Snapshot created on: 20240619_2017
System:
  Kernel: 6.1.0-21-amd64 [6.1.90-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splash lang=nl_NL kbd=us kbvar=euro
    tz=Europe/Amsterdam persist_static splash
  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.3_x64 Libretto May 19  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: Dell product: OptiPlex 9020 v: 00 serial: <superuser required> Chassis:
    type: 15 serial: <superuser required>
  Mobo: Dell model: 00V62H v: A01 serial: <superuser required> UEFI: Dell v: A25 date: 05/30/2019
CPU:
  Info: model: Intel Core i5-4690 bits: 64 type: MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x27
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
    L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1896 min/max: 800/3900 scaling: driver: intel_cpufreq governor: ondemand
    cores: 1: 1896 2: 1896 3: 1896 4: 1896 bogomips: 27936
  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 disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  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: disabled; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Dell
    driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: VGA-1
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 444x277mm (17.48x10.91") s-diag: 523mm (20.6")
  Monitor-1: VGA-1 model: Philips 220BW serial: <filter> built: 2009 res: 1680x1050 hz: 60
    dpi: 90 gamma: 1.2 size: 474x296mm (18.66x11.65") diag: 552mm (21.7") ratio: 16:10 modes:
    max: 1680x1050 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Dell 8 driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
  API: ALSA v: k6.1.0-21-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I217-LM vendor: Dell driver: e1000e v: kernel port: f080 bus-ID: 00:19.0
    chip-ID: 8086:153a class-ID: 0200
  IF: eth0 state: down mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
  IF-ID-2: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek 802.11ac NIC type: USB driver: btusb,rtl88x2bu bus-ID: 3-12:4
    chip-ID: 0bda:b82c class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: 705c hci-v: 4.2 rev: ab6b
  Info: acl-mtu: 1021:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060 bus-ID: 00:1f.2
    chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 883.1 GiB used: 39.55 GiB (4.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Hitachi model: HTS723232A7A364 size: 298.09 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: B70W scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Samsung model: SSD PM871 2.5 7mm 128GB
    size: 119.24 GiB block-size: physical: 4096 B logical: 512 B type: SSD serial: <filter> rev: 2501
    scheme: MBR
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 3 MiB (0.1%) priority: -2
    file: /live/boot-dev/swap-file
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2158 libs: 1067 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  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/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://nl.mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 271 Uptime: 2h 21m wakeups: 1 Memory: 7.66 GiB used: 4.57 GiB (59.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

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 8:48 am

by j2mcgreg

Code: Select all

Drives:
  Local Storage: total: 883.1 GiB used: 39.55 GiB (4.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Hitachi model: HTS723232A7A364 size: 298.09 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: B70W scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Samsung model: SSD PM871 2.5 7mm 128GB
    size: 119.24 GiB block-size: physical: 4096 B logical: 512 B type: SSD serial: <filter> rev: 2501
    scheme: MBR

You can't mix and match. All of the drives have be UEFI or they all have to be MBR.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 9:16 am

by Charlie Brown

j2mcgreg wrote: Fri Jul 19, 2024 8:48 am... All of the drives have be UEFI or they all have to be MBR.

Some may be GPT and some may be MBR.

Though this is (just) the recommended one for least problems:

Uefi => GPT
Bios (Legacy) => MBR

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 9:23 am

by Pakos

Not sure what the problem is; I thought i installed everything right and that it was way to go, just like previously i have been running for years..

ID-1: This is a Samsung SSD. Divided into two or more partitions, one for Windows and one for MX-23 (boot and swap).
ID-2: This is a Hitachi hard drive that used as storage for movies, nothing else. It uses the NTFS file system so it can be recognized by both Windows and Linux.
ID-3: This is a different Samsung SSD that contains a live snapshot of the system. It is housed in an external USB hard disk enclosure. It is usually not plugged in or used unless there is an emergency, like now.

Although I've used Linux for a long time and understand some of it, I still need a clearer explanation of what's wrong and how to fix it.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 9:27 am

by Charlie Brown

... Since your machine is set to Uefi:

Select ESP (When reinstalling Grub) and
sda2 vfat (for location)
and sda4 (rootMX23...) for "root location".
_______

No matter it works or not: Ahci is recommended (rather than Raid). So, change "sata mode" (in Bios settings) to Ahci.

However, not to make Windows unbootable: First boot to Windows and open Regedit, then make 2 simple changes there.. Finally do the change in Bios, save and exit.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 9:40 am

by Charlie Brown

Edit:

It seems you have a separate boot partition. So, (if that's true) select sda1 (rather than sda4) for root/boot location. ( => ESP, sda2, sda1 )

Also check (when on live session) whether they got full ( especially sda1 and 2 , and others while you're at it).

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 9:44 am

by Pakos

Charlie Brown wrote: Fri Jul 19, 2024 9:27 am ... Since your machine is set to Uefi:

Select ESP (When reinstalling Grub) and
sda2 vfat (for location)
and sda4 (rootMX23...) for "root location".
_______

No matter it works or not: Ahci is recommended (rather than Raid). So, change "sata mode" (in Bios settings) to Ahci.

However, not to make Windows unbootable: First boot to Windows and open Regedit, then make 2 simple changes there.. Finally do the change in Bios, save and exit.

I tried that, but it didn’t help. I’m still seeing the same error (I think): https://imgur.com/zi8SgL2.png.

I now realize that I should have attempted advanced login options at the GRUB menu. I can log back into the system using what seems to be an older kernel that I selected from the boot menu.

Besides the default kernel not able to boot. I still have that previous issue also related to the kernel:

Code: Select all

Skander@Mx23:~/Bureaublad
$ sudo apt-get dist-upgrade
[sudo] wachtwoord voor Skander:           
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar 
Opwaardering wordt doorgerekend... Klaar
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
4 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Wilt u doorgaan? [J/n] j
Instellen van linux-image-6.1.0-23-amd64 (6.1.99-1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-23-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-23-amd64
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
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:
Cleaning build area...
'make' -j4 KVER=6.1.0-23-amd64 KSRC=/lib/modules/6.1.0-23-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.1.0-23-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-23-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: fout bij verwerken van pakket linux-image-6.1.0-23-amd64 (--configure):
 subproces van pakket linux-image-6.1.0-23-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Instellen van linux-headers-6.1.0-23-amd64 (6.1.99-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-23-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-23-amd64
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
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:
Cleaning build area...
'make' -j4 KVER=6.1.0-23-amd64 KSRC=/lib/modules/6.1.0-23-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.1.0-23-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-23-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-23-amd64.postinst line 11.
dpkg: fout bij verwerken van pakket linux-headers-6.1.0-23-amd64 (--configure):
 subproces van pakket linux-headers-6.1.0-23-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
dpkg: vereistenproblemen verhinderen de configuratie van linux-headers-amd64:
 linux-headers-amd64 is afhankelijk van linux-headers-6.1.0-23-amd64 (= 6.1.99-1); maar:
  Pakket linux-headers-6.1.0-23-amd64 is nog niet geconfigureerd.

dpkg: fout bij verwerken van pakket linux-headers-amd64 (--configure):
 vereistenproblemen - blijft ongeconfigureerd
dpkg: vereistenproblemen verhinderen de configuratie van linux-image-amd64:
 linux-image-amd64 is afhankelijk van linux-image-6.1.0-23-amd64 (= 6.1.99-1); maar:
  Pakket linux-image-6.1.0-23-amd64 is nog niet geconfigureerd.

dpkg: fout bij verwerken van pakket linux-image-amd64 (--configure):
 vereistenproblemen - blijft ongeconfigureerd
Fouten gevonden tijdens verwerken van:
 linux-image-6.1.0-23-amd64
 linux-headers-6.1.0-23-amd64
 linux-headers-amd64
 linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
Skander@Mx23:~/Bureaublad
$ sudo apt-get auto-remove
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar 
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
4 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Instellen van linux-image-6.1.0-23-amd64 (6.1.99-1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-23-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-23-amd64
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
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:
Cleaning build area...
'make' -j4 KVER=6.1.0-23-amd64 KSRC=/lib/modules/6.1.0-23-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.1.0-23-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-23-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: fout bij verwerken van pakket linux-image-6.1.0-23-amd64 (--configure):
 subproces van pakket linux-image-6.1.0-23-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Instellen van linux-headers-6.1.0-23-amd64 (6.1.99-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-23-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-23-amd64
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
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:
Cleaning build area...
'make' -j4 KVER=6.1.0-23-amd64 KSRC=/lib/modules/6.1.0-23-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.1.0-23-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-23-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-23-amd64.postinst line 11.
dpkg: fout bij verwerken van pakket linux-headers-6.1.0-23-amd64 (--configure):
 subproces van pakket linux-headers-6.1.0-23-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
dpkg: vereistenproblemen verhinderen de configuratie van linux-headers-amd64:
 linux-headers-amd64 is afhankelijk van linux-headers-6.1.0-23-amd64 (= 6.1.99-1); maar:
  Pakket linux-headers-6.1.0-23-amd64 is nog niet geconfigureerd.

dpkg: fout bij verwerken van pakket linux-headers-amd64 (--configure):
 vereistenproblemen - blijft ongeconfigureerd
dpkg: vereistenproblemen verhinderen de configuratie van linux-image-amd64:
 linux-image-amd64 is afhankelijk van linux-image-6.1.0-23-amd64 (= 6.1.99-1); maar:
  Pakket linux-image-6.1.0-23-amd64 is nog niet geconfigureerd.

dpkg: fout bij verwerken van pakket linux-image-amd64 (--configure):
 vereistenproblemen - blijft ongeconfigureerd
Fouten gevonden tijdens verwerken van:
 linux-image-6.1.0-23-amd64
 linux-headers-6.1.0-23-amd64
 linux-headers-amd64
 linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 9:45 am

by Charlie Brown

I was just going to write that and you did well booting with the old kernel. You can simply remove the problematic one with "MX Cleanup" from menu.

Also (if you like only) you can stop (pause) the auto-updating of the default kernel via "MX Tweak" - "Other" tab.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 9:49 am

by Charlie Brown

... You can also (to get rid of those unnecessary and time-consuming and sometimes problematic dkms packages) click the button below to "remove unused wifi drivers" when on "MX Cleanup" (as you don't have any of those Realtek and Broadcom devices).

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 10:11 am

by Pakos

I did a general cleanup in MX Cleanup, including removing unnecessary wifi drivers. However, when trying to list and remove kernels, it says "https://imgur.com/gMv3NGb.png".
Also, in the MX Tweak "Other" tab, the only thing related to the kernel I could find was an option called "Shutdown the Kernel Sandbox" (at rule 3) https://imgur.com/kXhae3p.png. (Not sure if you meant that)
(The issue at boot up, as wel in the terminal still persists, the previous kernel that is unbootable is still present in the advanced menu at the grub)

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 10:35 am

by Charlie Brown

Pakos wrote: Fri Jul 19, 2024 10:11 am... Not sure if you meant that ...

Nope. That option doesn't appear when the relevant packages are uninstalled. So, normally it shouldn't go on auto-updating ( ..-23 etc..).

If you like only you can even do this: Install the most recent Liquorix kernel from "MX Package Installer" (just 2 clicks from the initial tab) then reboot. If that's successful you may/may not remove the 6.1.xx .

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 10:41 am

by Charlie Brown

Oh là là :

Code: Select all

...
Fouten gevonden tijdens verwerken van:
 linux-image-6.1.0-23-amd64
 linux-headers-6.1.0-23-amd64
 linux-headers-amd64
 linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

so, probably they were stuck (half installed / half removed). So, probably the same thing will go on whatever you install/remove (even with any non-relevant packages) .

So, we might need to "scrape" them first.

In the meantime these two are those ones mentioned above to provide auto-update (for the default (6.1) kernel) :

linux-headers-amd64
linux-image-amd64

That's why it looks like they're uninstalled and no such option in MX Tweak.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 10:59 am

by Charlie Brown

Code: Select all

sudo mv /var/lib/dpkg/info/linux*6.1.0-23* /tmp/ ; sudo mv /var/lib/dpkg/info/linux-headers-amd64 /tmp/ ; sudo mv /var/lib/dpkg/info/linux-image-amd64 /tmp/ ; sudo dpkg --purge --force-remove-reinstreq linux-image-6.1.0-23-amd64 ; sudo dpkg --purge --force-remove-reinstreq linux-headers-6.1.0-23-amd64 ; sudo dpkg --purge --force-remove-reinstreq linux-headers-amd64 ; sudo dpkg --purge --force-remove-reinstreq linux-image-amd64 ; sudo dpkg --configure -a

Reboot.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 11:03 am

by Pakos

Charlie Brown wrote: Fri Jul 19, 2024 10:35 am If you like only you can even do this: Install the most recent Liquorix kernel from "MX Package Installer" (just 2 clicks from the initial tab) then reboot. If that's successful you may/may not remove the 6.1.xx .

Tried to install the most recent Liquirux kernel trough MX Package installer. Got the following error: https://imgur.com/tDGzjzH.png

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 11:05 am

by Charlie Brown

Ok, scrape them with the command above. Just copy-paste-Enter...

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 11:07 am

by Eadwine Rose

And please post text output as text, not as screenshot, thanks.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 11:09 am

by Pakos

Code: Select all

Skander@Mx23:~
$ sudo mv /var/lib/dpkg/info/linux*6.1.0-23* /tmp/ ; sudo mv /var/lib/dpkg/info/linux-headers-amd64 /tmp/ ; sudo mv /var/lib/dpkg/info/linux-image-amd64 /tmp/ ; sudo dpkg --purge --force-remove-reinstreq linux-image-6.1.0-23-amd64 ; sudo dpkg --purge --force-remove-reinstreq linux-headers-6.1.0-23-amd64 ; sudo dpkg --purge --force-remove-reinstreq linux-headers-amd64 ; sudo dpkg --purge --force-remove-reinstreq linux-image-amd64 ; sudo dpkg --configure -a
[sudo] wachtwoord voor Skander:           
mv: kan status van '/var/lib/dpkg/info/linux-headers-amd64' niet opvragen: Bestand of map bestaat niet
mv: kan status van '/var/lib/dpkg/info/linux-image-amd64' niet opvragen: Bestand of map bestaat niet
dpkg: vereistenproblemen verhinderen het verwijderen van linux-image-6.1.0-23-amd64:
 linux-image-amd64 is afhankelijk van linux-image-6.1.0-23-amd64 (= 6.1.99-1).

dpkg: fout bij verwerken van pakket linux-image-6.1.0-23-amd64 (--purge):
 vereistenproblemen - wordt niet verwijderd
Fouten gevonden tijdens verwerken van:
 linux-image-6.1.0-23-amd64
dpkg: vereistenproblemen verhinderen het verwijderen van linux-headers-6.1.0-23-amd64:
 linux-headers-amd64 is afhankelijk van linux-headers-6.1.0-23-amd64 (= 6.1.99-1).

dpkg: fout bij verwerken van pakket linux-headers-6.1.0-23-amd64 (--purge):
 vereistenproblemen - wordt niet verwijderd
Fouten gevonden tijdens verwerken van:
 linux-headers-6.1.0-23-amd64
dpkg: waarschuwing: bestand met de lijst bestanden van pakket'linux-headers-6.1.0-23-common' ontbreekt; aangenomen
wordt dat het pakket momenteel geen geïnstalleerde bestanden heeft
(Database wordt ingelezen ... 313735 bestanden en mappen momenteel geïnstalleerd.)
linux-headers-amd64 (6.1.99-1) wordt verwijderd ...
Configuratiebestanden voor linux-headers-amd64 (6.1.99-1) worden gewist ...
dpkg: waarschuwing: bestand met de lijst bestanden van pakket'linux-headers-6.1.0-23-common' ontbreekt; aangenomen
wordt dat het pakket momenteel geen geïnstalleerde bestanden heeft
(Database wordt ingelezen ... 313733 bestanden en mappen momenteel geïnstalleerd.)
linux-image-amd64 (6.1.99-1) wordt verwijderd ...
Configuratiebestanden voor linux-image-amd64 (6.1.99-1) worden gewist ...
Instellen van linux-headers-6.9.9-1-liquorix-amd64 (6.9-8~mx23ahs) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.9.9-1-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.9.9-1-liquorix-amd64
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.9.9-1-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...
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed

Building module:
Cleaning build area...
'make' -j4 KVER=6.9.9-1-liquorix-amd64 KSRC=/lib/modules/6.9.9-1-liquorix-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.9.9-1-liquorix-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.9.9-1-liquorix-amd64.postinst line 11.
dpkg: fout bij verwerken van pakket linux-headers-6.9.9-1-liquorix-amd64 (--configure):
 subproces van pakket linux-headers-6.9.9-1-liquorix-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Instellen van linux-image-6.9.9-1-liquorix-amd64 (6.9-8~mx23ahs) ...
I: /initrd.img is now a symlink to boot/initrd.img-6.9.9-1-liquorix-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.9.9-1-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.9.9-1-liquorix-amd64
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.9.9-1-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...
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed

Building module:
Cleaning build area...
'make' -j4 KVER=6.9.9-1-liquorix-amd64 KSRC=/lib/modules/6.9.9-1-liquorix-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.9.9-1-liquorix-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: fout bij verwerken van pakket linux-image-6.9.9-1-liquorix-amd64 (--configure):
 subproces van pakket linux-image-6.9.9-1-liquorix-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
 linux-headers-6.9.9-1-liquorix-amd64
 linux-image-6.9.9-1-liquorix-amd64
 
 
 Skander@Mx23:~
$ sudo apt-get autoremove
[sudo] wachtwoord voor Skander:           
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar 
De volgende pakketten zullen VERWIJDERD worden:
  linux-headers-6.1.0-23-amd64 linux-headers-6.1.0-23-common linux-image-6.1.0-23-amd64
0 opgewaardeerd, 0 nieuw geïnstalleerd, 3 te verwijderen en 0 niet opgewaardeerd.
4 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 470 MB schijfruimte vrijkomen.
Wilt u doorgaan? [J/n] j
dpkg: waarschuwing: bestand met de lijst bestanden van pakket'linux-headers-6.1.0-23-common' ontbreekt; aangenomen
wordt dat het pakket momenteel geen geïnstalleerde bestanden heeft
(Database wordt ingelezen ... 313730 bestanden en mappen momenteel geïnstalleerd.)
linux-headers-6.1.0-23-amd64 (6.1.99-1) wordt verwijderd ...
linux-image-6.1.0-23-amd64 (6.1.99-1) wordt verwijderd ...
linux-headers-6.1.0-23-common (6.1.99-1) wordt verwijderd ...
Instellen van linux-headers-6.9.9-1-liquorix-amd64 (6.9-8~mx23ahs) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.9.9-1-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.9.9-1-liquorix-amd64
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.9.9-1-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...
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed

Building module:
Cleaning build area...
'make' -j4 KVER=6.9.9-1-liquorix-amd64 KSRC=/lib/modules/6.9.9-1-liquorix-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.9.9-1-liquorix-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.9.9-1-liquorix-amd64.postinst line 11.
dpkg: fout bij verwerken van pakket linux-headers-6.9.9-1-liquorix-amd64 (--configure):
 subproces van pakket linux-headers-6.9.9-1-liquorix-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Instellen van linux-image-6.9.9-1-liquorix-amd64 (6.9-8~mx23ahs) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.9.9-1-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.9.9-1-liquorix-amd64
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.9.9-1-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...
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed

Building module:
Cleaning build area...
'make' -j4 KVER=6.9.9-1-liquorix-amd64 KSRC=/lib/modules/6.9.9-1-liquorix-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.9.9-1-liquorix-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: fout bij verwerken van pakket linux-image-6.9.9-1-liquorix-amd64 (--configure):
 subproces van pakket linux-image-6.9.9-1-liquorix-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
 linux-headers-6.9.9-1-liquorix-amd64
 linux-image-6.9.9-1-liquorix-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 11:11 am

by Charlie Brown

I was just about to edit and add a * to some parts:

Code: Select all

sudo mv /var/lib/dpkg/info/linux-headers-amd6* /tmp/ ; sudo mv /var/lib/dpkg/info/linux-image-amd6* /tmp/ ; sudo dpkg --purge --force-remove-reinstreq linux-headers-amd64 ; sudo dpkg --purge --force-remove-reinstreq linux-image-amd64 ; sudo dpkg --configure -a

(... Cause we need(ed) to move all related files (not just 2) ).

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 11:16 am

by Pakos

Code: Select all

Skander@Mx23:~/Bureaublad
$ sudo mv /var/lib/dpkg/info/linux-headers-amd6* /tmp/ ; sudo mv /var/lib/dpkg/info/linux-image-amd6* /tmp/ ; sudo dpkg --purge --force-remove-reinstreq linux-headers-amd64 ; udo dpkg --purge --force-remove-reinstreq linux-image-amd64 ; sudo dpkg --configure -a
[sudo] wachtwoord voor Skander:           
mv: kan status van '/var/lib/dpkg/info/linux-headers-amd6*' niet opvragen: Bestand of map bestaat niet
mv: kan status van '/var/lib/dpkg/info/linux-image-amd6*' niet opvragen: Bestand of map bestaat niet
dpkg: waarschuwing: verzoek om linux-headers-amd64 te verwijderen wordt genegeerd omdat het niet geïnstalleerd is
Opdracht 'udo' niet gevonden, maar deze kan worden geïnstalleerd met:
sudo apt install udo
Instellen van linux-headers-6.9.9-1-liquorix-amd64 (6.9-8~mx23ahs) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.9.9-1-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.9.9-1-liquorix-amd64
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.9.9-1-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...
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed

Building module:
Cleaning build area...
'make' -j4 KVER=6.9.9-1-liquorix-amd64 KSRC=/lib/modules/6.9.9-1-liquorix-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.9.9-1-liquorix-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.9.9-1-liquorix-amd64.postinst line 11.
dpkg: fout bij verwerken van pakket linux-headers-6.9.9-1-liquorix-amd64 (--configure):
 subproces van pakket linux-headers-6.9.9-1-liquorix-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Instellen van linux-image-6.9.9-1-liquorix-amd64 (6.9-8~mx23ahs) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.9.9-1-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.9.9-1-liquorix-amd64
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.9.9-1-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...
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed

Building module:
Cleaning build area...
'make' -j4 KVER=6.9.9-1-liquorix-amd64 KSRC=/lib/modules/6.9.9-1-liquorix-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.9.9-1-liquorix-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: fout bij verwerken van pakket linux-image-6.9.9-1-liquorix-amd64 (--configure):
 subproces van pakket linux-image-6.9.9-1-liquorix-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
 linux-headers-6.9.9-1-liquorix-amd64
 linux-image-6.9.9-1-liquorix-amd64

After reboot:

Code: Select all

Skander@Mx23:~
$ sudo apt-get autoremove
[sudo] wachtwoord voor Skander:           
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar 
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
2 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Instellen van linux-headers-6.9.9-1-liquorix-amd64 (6.9-8~mx23ahs) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.9.9-1-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.9.9-1-liquorix-amd64
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.9.9-1-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...
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed

Building module:
Cleaning build area...
'make' -j4 KVER=6.9.9-1-liquorix-amd64 KSRC=/lib/modules/6.9.9-1-liquorix-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.9.9-1-liquorix-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.9.9-1-liquorix-amd64.postinst line 11.
dpkg: fout bij verwerken van pakket linux-headers-6.9.9-1-liquorix-amd64 (--configure):
 subproces van pakket linux-headers-6.9.9-1-liquorix-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Instellen van linux-image-6.9.9-1-liquorix-amd64 (6.9-8~mx23ahs) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.9.9-1-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.9.9-1-liquorix-amd64
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.9.9-1-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...
Sign command: /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.9.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed

Building module:
Cleaning build area...
'make' -j4 KVER=6.9.9-1-liquorix-amd64 KSRC=/lib/modules/6.9.9-1-liquorix-amd64/build...(bad exit status: 1)
Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.9.9-1-liquorix-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: fout bij verwerken van pakket linux-image-6.9.9-1-liquorix-amd64 (--configure):
 subproces van pakket linux-image-6.9.9-1-liquorix-amd64 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
 linux-headers-6.9.9-1-liquorix-amd64
 linux-image-6.9.9-1-liquorix-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 11:19 am

by Charlie Brown

So, (I haven't translated yet, but) it looks ok now (you got rid of 6.1.0-23 and other two packages).

These are normal (not related to this issue):

Code: Select all

Error! Bad return status for module build on kernel: 6.9.9-1-liquorix-amd64

That happens mostly about Nvidia, Broadcom, Virtualbox etc... It just gives info: Roughly it says "these ... drivers are not ok with this kernel" ...

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 1:11 pm

by Pakos

Asked ChatGPT for help and solved the remaining issues by doing this:

Errors encountered while processing:
linux-headers-6.9.9-1-liquorix-amd64
linux-image-6.9.9-1-liquorix-amd64

Code: Select all

sudo apt-get remove --purge linux-headers-6.9.9-1-liquorix-amd64 linux-image-6.9.9-1-liquorix-amd64
sudo apt-get autoremove
sudo apt-get clean
sudo apt-get update
sudo apt-get dist-upgrade

After that, I went into "grub customizer" and removed the broken default boot entry, replacing it with the older kernel entry. Both the error in the terminal and the issue at boot up are gone. I'm not sure if I only masked the problem, but my machine is back to its previous working normal state again.

I bet if I had tried and had a little courage, I could have solved it myself. However, I was quite nervous since it went completely wrong the last time I attempted to fix it on my own. Nonetheless, I really appreciate it. Thank you so much, everyone.

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 2:57 pm

by Charlie Brown

Ok but if I knew that you wanted to remove the Liquorix kernel, too: You could do all of these with 1-2 clicks with "MX Cleanup".

Yes, you could do it yourself however those half installed / stuck 6.1.0-23 should've been removed this way only. Otherwise, no matter what you do (autoremove , Synaptic etc..) it would go on showing that "E: Sub-process /usr/bin/dpkg returned an error code (1)" during all kinds of updates, installing/removing anything ...

Glad to hear it's ok now.

P.S. In case you want the auto-update (for the default 6.1 kernel) back: (re)install those two packages ( linux-headers-amd64 , linux-image-amd64 ), or (re)install the "Debian 64bit" kernel from MXPI ..

Re: Failed kernel update Mx-23

Posted: Fri Jul 19, 2024 3:19 pm

by Pakos

Charlie Brown wrote: Fri Jul 19, 2024 2:57 pm Ok, but if I knew that you wanted to remove the Liquorix kernel too, you could do all of these with 1-2 clicks using "MX Cleanup".

Oh, I assumed we needed to delete the Liquorix kernel since the installation we both were trying to achieve failed earlier.

Yes, you could do it yourself; however, those half-installed/stuck 6.1.0-23 versions should've been removed this way only. Otherwise, no matter what you do (autoremove, Synaptic, etc.), it would continue showing "E: Sub-process /usr/bin/dpkg returned an error code (1)" during all kinds of updates, installations, or removals.

P.S. In case you want the auto-update (for the default 6.1 kernel) back, (re)install those two packages (linux-headers-amd64, linux-image-amd64), or (re)install the "Debian 64bit" kernel from MXPI.

It seemed to fail again, like it did with the Liquorix kernel install.

This is from MXPI:

Code: Select all

Geraakt:1 http://nl.mxrepo.com/mx/repo bookworm InRelease
Geraakt:2 http://deb.debian.org/debian bookworm-updates InRelease
Geraakt:3 http://security.debian.org/debian-security bookworm-security InRelease
Geraakt:4 http://deb.debian.org/debian bookworm InRelease
Ophalen:5 https://packages.microsoft.com/repos/edge stable InRelease [3.590 B]
Ophalen:6 https://packages.microsoft.com/repos/edge stable/main amd64 Packages [9.260 B]
12,8 kB opgehaald in 1s (11,4 kB/s)
Pakketlijsten worden ingelezen...
Pakketlijsten worden ingelezen...
Boom van vereisten wordt opgebouwd...
De statusinformatie wordt gelezen...
linux-image-6.6.11-amd64-unsigned is reeds de nieuwste versie (6.6.11-1~mx23ahs).
linux-headers-6.6.11-amd64 is reeds de nieuwste versie (6.6.11-1~mx23ahs).
broadcom-sta-dkms is reeds de nieuwste versie (6.30.223.271-23).
rtl8812au-dkms is reeds de nieuwste versie (5.13.6+git20240329-1~mx23).
rtl8821cu-dkms is reeds de nieuwste versie (5.12.0+git20230215-1~mx23+3).
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 36 niet opgewaardeerd.
2 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Wilt u doorgaan? [J/n] 
jInstellen van linux-image-6.6.11-amd64-unsigned (6.6.11-1~mx23ahs) .../etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.6.11-amd64./usr/sbin/dkms.mx autoinstall --kernelver 6.6.11-amd64Sign command: /lib/modules/6.6.11-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pubThe /var/lib/dkms/rtl8821cu/5.12.0/6.6.11-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...Sign command: /lib/modules/6.6.11-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:(bad exit status: 1)Error! Bad return status for module build on kernel: 6.6.11-amd64 (x86_64)
Consult /var/lib/dkms/rtl88x2bu/"@PKGVER@"/build/make.log for more information.Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.6.11-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: fout bij verwerken van pakket linux-image-6.6.11-amd64-unsigned (--configure):
 subproces van pakket linux-image-6.6.11-amd64-unsigned werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
dpkg: vereistenproblemen verhinderen de configuratie van linux-headers-6.6.11-amd64:
 linux-headers-6.6.11-amd64 is afhankelijk van linux-image-6.6.11-amd64 (= 6.6.11-1~mx23ahs) | linux-image-6.6.11-amd64-unsigned (= 6.6.11-1~mx23ahs); maar:
  Pakket linux-image-6.6.11-amd64 is niet geïnstalleerd.
  Pakket linux-image-6.6.11-amd64-unsigned is nog niet geconfigureerd.

dpkg: fout bij verwerken van pakket linux-headers-6.6.11-amd64 (--configure):
 vereistenproblemen - blijft ongeconfigureerdFouten gevonden tijdens verwerken van:
 linux-image-6.6.11-amd64-unsigned
 linux-headers-6.6.11-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
Geraakt:1 http://deb.debian.org/debian bookworm-updates InRelease
Geraakt:2 http://security.debian.org/debian-security bookworm-security InRelease
Geraakt:3 http://nl.mxrepo.com/mx/repo bookworm InRelease
Geraakt:4 http://deb.debian.org/debian bookworm InRelease
Geraakt:5 https://packages.microsoft.com/repos/edge stable InRelease
Pakketlijsten worden ingelezen...

Re: Failed kernel update Mx-23 [Solved]

Posted: Fri Jul 19, 2024 3:45 pm

by Charlie Brown

Ok, but the the one you tried to install is 6.6.x , not the 6.1 that would auto-update . (Others won't, other than the Liquorix auto-update package).