I almost miss the old BSOD's in a twisted way.... they ruined it's usefulness with Vista.
It actually became funny getting a BSOD (and sometimes a temporary one?) just for ejecting a CD too quickly.
Won't boot on 6.14.1-1-liquorix-amd64 kernel panic [Solved]
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
I will never miss the Blue Screen Of Death. Last year there was a discussion on a useless computer forum that is run by a bunch of egotistical lowest form of life that were praising that there will be a Blue Screen Of Death will be implemented into LINUX. 
I found that subject to be so repulsive that it made me regurgitate. It was only till "Linux for Seniors" from YouTube told me the real meaning of bash was actually born again shell. I always thought that bash was the sound you would hear from bashing the computer when you would get a Blue Screen Of Death. 
I found that subject to be so repulsive that it made me regurgitate. It was only till "Linux for Seniors" from YouTube told me the real meaning of bash was actually born again shell. I always thought that bash was the sound you would hear from bashing the computer when you would get a Blue Screen Of Death. I am command line illiterate. 
I copy & paste to the terminal. Liars, Wiseguys, Trolls, and those without manners will be added to my ignore list. 
I copy & paste to the terminal. Liars, Wiseguys, Trolls, and those without manners will be added to my ignore list. -
DukeComposed
- Posts: 1389
- Joined: Thu Mar 16, 2023 1:57 pm
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Stephen Bourne wrote the shell for 7th Edition Unix, called the Bourne Shell. When Bash was developed ten years later as an improvement on the Bourne shell, the pun was too good to pass up.
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Code: Select all
Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/550.144.03/build/make.log for more information.I think everyone should remove unused wi-fi DKMS drivers. They really slow down any kernel update, for no reason. The 6.14 Liquorix kernel seems have much improved internal Realtek drivers, for those that are wondering what good it is.
For those that don't want to provide any QSI or system information--using a third-party driver that won't build on a new kernel is something we wasted time discovering.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Agree No "One" is to blame. yet question would come in resort to - "why Release" an Update of Program selections of files and or kernel release. Specially if it was not Tested Correctly prior release to general update desktop process.
Seeing Revoke or removed such from the update program after its pop to update desktop wide. This is no different from other Kernel Specially releases of how MX outputs via such broad Updates as to how many fail as to how many succeed in update process. With new problems generated.
Sorry to express and others also have expressed the same.. The Soup crappers. No QSI no Fix support is only to tarnish the MX reputation. Have not some to see and consider value to use of MX Distro Release. as it slips from all time #1 distro to now 2nd and what next. 3rd or 4th fall outs.
would a thought to consider. under the users group.n.Blog users.
why not create a Listing post a Form to fill or even just check " New Release " Kernel or update #. - as to "Update release" with users that worked and those that did not. check box be simple yad or zenity simple.
Same with or the all similar process on this particular board as too - Problems and checking the "Solved" Status.
would not an idea to - Problem found ...abc and Solution correction as to "What was done to correct or fix some abnormality in cause of such issue.
Such DB would prevent endless searching and could help any one searching for a problem they .. And this could behold even New Users to Linux as too " I'm experiencing such issue" to list thru Problems and Solved listings as to ..
yes this fits my issue I can resort to this "Solved" state and try such process to fix their issue.
So when users come to the forums they can find a solution or information they may " Learn By " which might provide an immediate answer to try and rectify their issue.
such removing problematic people skills and or seeing constant bold issue not being address directly and an incorrect toss to solution be cast as it is by current to some supporters.
Seeing Revoke or removed such from the update program after its pop to update desktop wide. This is no different from other Kernel Specially releases of how MX outputs via such broad Updates as to how many fail as to how many succeed in update process. With new problems generated.
Sorry to express and others also have expressed the same.. The Soup crappers. No QSI no Fix support is only to tarnish the MX reputation. Have not some to see and consider value to use of MX Distro Release. as it slips from all time #1 distro to now 2nd and what next. 3rd or 4th fall outs.
would a thought to consider. under the users group.n.Blog users.
why not create a Listing post a Form to fill or even just check " New Release " Kernel or update #. - as to "Update release" with users that worked and those that did not. check box be simple yad or zenity simple.
Same with or the all similar process on this particular board as too - Problems and checking the "Solved" Status.
would not an idea to - Problem found ...abc and Solution correction as to "What was done to correct or fix some abnormality in cause of such issue.
Such DB would prevent endless searching and could help any one searching for a problem they .. And this could behold even New Users to Linux as too " I'm experiencing such issue" to list thru Problems and Solved listings as to ..
yes this fits my issue I can resort to this "Solved" state and try such process to fix their issue.
So when users come to the forums they can find a solution or information they may " Learn By " which might provide an immediate answer to try and rectify their issue.
such removing problematic people skills and or seeing constant bold issue not being address directly and an incorrect toss to solution be cast as it is by current to some supporters.
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Again, a dkms build failure of a deprecrated DKMS package, that you don't even use, is not a kernel panic. A kernel panic is something you see in the dmesg output, and it provides a memory trace for debugging.
jj 5117 wrote: Thu Apr 10, 2025 10:59 am Hi @Stevo,
An instance example for the bug reports on kernel 6.14.1-1. May it be useful. I can't help much, but I can do this. :) :
My instance did report a kernel panic. I don't have booting splashes and stuff.
QSIInstaller's Echo:Code: Select all
Snapshot created on: 20250203_0855 System: Kernel: 6.13.8-4-liquorix-amd64 [6.13-9~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0 intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/vmlinuz-6.13.8-4-liquorix-amd64 root=UUID=<filter> ro Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7 dm: SDDM Distro: MX-23.5_ahs_x64 Libretto October 15 2023 base: Debian GNU/Linux 12 (bookworm) Machine: Type: Laptop System: LENOVO product: 82JQ v: Legion 5 Pro 16ACH6H serial: <superuser required> Chassis: type: 10 v: Legion 5 Pro 16ACH6H serial: <superuser required> Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN serial: <superuser required> UEFI: LENOVO v: GKCN57WW date: 06/16/2022 Battery: ID-1: BAT0 charge: 75.9 Wh (95.1%) condition: 79.8/80.0 Wh (99.8%) volts: 16.0 min: 15.4 model: Sunwoda L20D4PC1 type: Li-poly serial: <filter> status: not charging cycles: 11 CPU: Info: model: AMD Ryzen 7 5800H with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0 microcode: 0xA50000C Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB Speed (MHz): avg: 2006 high: 4442 min/max: 1200/3200 boost: enabled scaling: driver: acpi-cpufreq governor: ondemand cores: 1: 2396 2: 1200 3: 2268 4: 1200 5: 1684 6: 1200 7: 2583 8: 1200 9: 2626 10: 1300 11: 4442 12: 3200 13: 2489 14: 1200 15: 1922 16: 1200 bogomips: 102208 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: reg_file_data_sampling status: Not affected Type: retbleed status: Not affected Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode 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: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q] vendor: Lenovo driver: nvidia v: 550.144.03 non-free: 530.xx+ status: current (as of 2023-03) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 2 speed: 5 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:24dd class-ID: 0300 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-3:3 chip-ID: 04f2:b67d class-ID: 0e02 Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 2560x1600 s-dpi: 96 s-size: 678x424mm (26.69x16.69") s-diag: 800mm (31.48") Monitor-1: DP-4 res: 2560x1600 hz: 60 dpi: 189 size: 344x215mm (13.54x8.46") diag: 406mm (15.97") modes: N/A API: OpenGL v: 4.6.0 NVIDIA 550.144.03 renderer: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 direct-render: Yes Audio: Device-1: NVIDIA GA104 High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b class-ID: 0403 Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480 Device-3: AMD Family 17h/19h/1ah HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403 API: ALSA v: k6.13.8-4-liquorix-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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Lenovo RTL8111/8168/8411 driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: eth0 state: down mac: <filter> Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter vendor: Lenovo driver: mt7921e v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 14c3:7961 class-ID: 0280 IF: wlan0 state: up mac: <filter> IF-ID-1: nordtun state: unknown speed: 10000 Mbps duplex: full mac: N/A Bluetooth: Device-1: Foxconn / Hon Hai MediaTek Bluetooth Adapter type: USB driver: btusb v: 0.8 bus-ID: 3-4:4 chip-ID: 0489:e0cd class-ID: e001 serial: <filter> Report: hciconfig ID: hci0 rfk-id: 2 state: down bt-service: N/A rfk-block: hardware: no software: yes address: <filter> Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: peripheral accept Drives: Local Storage: total: 1.86 TiB used: 1.07 TiB (57.2%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: N/A size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: RKT303.4 temp: 26.9 C scheme: GPT Partition: ID-1: / raw-size: 267.98 GiB size: 262.72 GiB (98.04%) used: 67.52 GiB (25.7%) fs: ext4 dev: /dev/dm-0 maj-min: 253:0 mapped: luks-<filter> ID-2: /boot raw-size: 2 GiB size: 1.9 GiB (95.01%) used: 443.9 MiB (22.8%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2 ID-3: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 134.6 MiB (26.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 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: 46.2 C mobo: 46.0 C gpu: nvidia temp: 37 C Fan Speeds (RPM): N/A Repos: Packages: pm: dpkg pkgs: 3141 libs: 1647 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0 pm: flatpak pkgs: 0 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/5.7.2/ubuntu focal main Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main 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/mx.list 1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free 2: deb http://la.mxrepo.com/mx/repo/ bookworm ahs Active apt repos in: /etc/apt/sources.list.d/nordvpn.list 1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main Active apt repos in: /etc/apt/sources.list.d/rocm.list 1: deb [arch=amd64] https://repo.radeon.com/rocm/apt/5.7.2 focal main Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources 1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main Info: Processes: 352 Uptime: 22m wakeups: 2 Memory: 15.48 GiB used: 1.82 GiB (11.8%) 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: UEFIEcho from MX Cleanup for unused wi-fi:Code: Select all
full upgrade apt update Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB] Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:3 http://la.mxrepo.com/mx/repo bookworm InRelease [25.3 kB] Hit:4 http://deb.debian.org/debian bookworm InRelease Get:5 http://security.debian.org/debian-security bookworm-security/main amd64 Packages [252 kB] Hit:6 https://repo.radeon.com/amdgpu/5.7.2/ubuntu focal InRelease Get:7 https://brave-browser-apt-release.s3.brave.com stable InRelease [7,546 B] Hit:8 https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease Get:9 http://security.debian.org/debian-security bookworm-security/main i386 Packages [245 kB] Get:10 http://la.mxrepo.com/mx/repo bookworm/main amd64 Packages [239 kB] Hit:11 https://repo.radeon.com/rocm/apt/5.7.2 focal InRelease Hit:12 https://repo.librewolf.net librewolf InRelease Get:13 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages [20.6 kB] Get:14 http://la.mxrepo.com/mx/repo bookworm/main i386 Packages [229 kB] Get:15 http://la.mxrepo.com/mx/repo bookworm/ahs amd64 Packages [126 kB] Get:16 http://la.mxrepo.com/mx/repo bookworm/ahs i386 Packages [96.9 kB] Get:17 http://la.mxrepo.com/mx/repo bookworm/ahs amd64 Contents (deb) [12.7 MB] Get:18 http://la.mxrepo.com/mx/repo bookworm/ahs i386 Contents (deb) [6,892 kB] Fetched 21.0 MB in 5s (4,427 kB/s) Reading package lists... Done apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-headers-6.13.8-2-liquorix-amd64 (6.13-7~mx23ahs) linux-image-6.13.8-2-liquorix-amd64 (6.13-7~mx23ahs) The following packages will be upgraded: brave-browser (1.77.95 => 1.77.97) librewolf (137.0-3 => 137.0.1-1) linux-libc-dev (6.12.20-1~mx23ahs => 6.12.21-1~mx23ahs) mx-boot-options (25.2.06 => 25.4.01) mx-packageinstaller (25.5 => 25.5.01) 5 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. 4 not fully installed or removed. Need to get 210 MB of archives. After this operation, 311 MB disk space will be freed. Get:1 http://la.mxrepo.com/mx/repo bookworm/ahs amd64 linux-libc-dev all 6.12.21-1~mx23ahs [2,542 kB] Get:2 https://brave-browser-apt-release.s3.brave.com stable/main amd64 brave-browser amd64 1.77.97 [125 MB] Get:4 http://la.mxrepo.com/mx/repo bookworm/main amd64 mx-boot-options amd64 25.4.01 [233 kB] Get:5 http://la.mxrepo.com/mx/repo bookworm/main amd64 mx-packageinstaller amd64 25.5.01 [396 kB] Get:3 https://repo.librewolf.net librewolf/main amd64 librewolf amd64 137.0.1-1 [82.1 MB] Fetched 210 MB in 31s (6,798 kB/s) (Reading database ... 548599 files and directories currently installed.) Removing linux-headers-6.13.8-2-liquorix-amd64 (6.13-7~mx23ahs) ... Removing linux-image-6.13.8-2-liquorix-amd64 (6.13-7~mx23ahs) ... /etc/kernel/prerm.d/dkms: dkms: removing: 8812au 5.13.6 (6.13.8-2-liquorix-amd64) (x86_64) /usr/sbin/dkms.mx remove -m 8812au -v 5.13.6 -k 6.13.8-2-liquorix-amd64 -a x86_64 Module 8812au-5.13.6 for kernel 6.13.8-2-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8812au.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. depmod... dkms: removing: broadcom-sta 6.30.223.271 (6.13.8-2-liquorix-amd64) (x86 _64) /usr/sbin/dkms.mx remove -m broadcom-sta -v 6.30.223.271 -k 6.13.8-2-liq uorix-amd64 -a x86_64 Module broadcom-sta-6.30.223.271 for kernel 6.13.8-2-liquorix-amd64 (x86 _64). Before uninstall, this module version was ACTIVE on this kernel. wl.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. depmod... dkms: removing: nvidia-current 550.144.03 (6.13.8-2-liquorix-amd64) (x86 _64) /usr/sbin/dkms.mx remove -m nvidia-current -v 550.144.03 -k 6.13.8-2-liq uorix-amd64 -a x86_64 Module nvidia-current-550.144.03 for kernel 6.13.8-2-liquorix-amd64 (x86 _64). Before uninstall, this module version was ACTIVE on this kernel. nvidia-current.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. nvidia-current-modeset.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. nvidia-current-drm.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. nvidia-current-peermem.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. nvidia-current-uvm.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. depmod... dkms: removing: rtl8821ce 5.5.2.1+git20250208 (6.13.8-2-liquorix-amd64) (x86_64) /usr/sbin/dkms.mx remove -m rtl8821ce -v 5.5.2.1+git20250208 -k 6.13.8-2 -liquorix-amd64 -a x86_64 grep: /lib/modules/6.13.8-2-liquorix-amd64/build/.config: No such file o r directory Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Module rtl8821ce-5.5.2.1+git20250208 for kernel 6.13.8-2-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. rtl8821ce.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. depmod... dkms: removing: rtl8821cu 5.12.0 (6.13.8-2-liquorix-amd64) (x86_64) /usr/sbin/dkms.mx remove -m rtl8821cu -v 5.12.0 -k 6.13.8-2-liquorix-amd 64 -a x86_64 Module rtl8821cu-5.12.0 for kernel 6.13.8-2-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8821cu.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. depmod... dkms: removing: virtualbox 7.0.22 (6.13.8-2-liquorix-amd64) (x86_64) /usr/sbin/dkms.mx remove -m virtualbox -v 7.0.22 -k 6.13.8-2-liquorix-am d64 -a x86_64 Module virtualbox-7.0.22 for kernel 6.13.8-2-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. vboxnetadp.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. vboxnetflt.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-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 versi on. depmod... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-6.13.8-2-liquorix-amd64 /etc/kernel/postrm.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.14.1-1-liquorix-amd64 Found linux image: /boot/vmlinuz-6.13.8-4-liquorix-amd64 Found initrd image: /boot/initrd.img-6.13.8-4-liquorix-amd64 Found linux image: /boot/vmlinuz-6.7.12-1-liquorix-amd64 Found initrd image: /boot/initrd.img-6.7.12-1-liquorix-amd64 Found linux image: /boot/vmlinuz-6.6.11-amd64 Found initrd image: /boot/initrd.img-6.6.11-amd64 Found linux image: /boot/vmlinuz-6.5.0-1mx-ahs-amd64 Found initrd image: /boot/initrd.img-6.5.0-1mx-ahs-amd64 Found mtest-64.efi image: /uefi-mt/mtest-64.efi Adding boot menu entry for EFI firmware configuration done (Reading database ... 516929 files and directories currently installed.) Preparing to unpack .../brave-browser_1.77.97_amd64.deb ... Unpacking brave-browser (1.77.97) over (1.77.95) ... Preparing to unpack .../librewolf_137.0.1-1_amd64.deb ... Unpacking librewolf (137.0.1-1) over (137.0-3) ... Preparing to unpack .../linux-libc-dev_6.12.21-1~mx23ahs_all.deb ... Unpacking linux-libc-dev (6.12.21-1~mx23ahs) over (6.12.20-1~mx23ahs) .. . Preparing to unpack .../mx-boot-options_25.4.01_amd64.deb ... Unpacking mx-boot-options (25.4.01) over (25.2.06) ... Preparing to unpack .../mx-packageinstaller_25.5.01_amd64.deb ... Unpacking mx-packageinstaller (25.5.01) over (25.5) ... Setting up librewolf (137.0.1-1) ... Setting up linux-headers-6.14.1-1-liquorix-amd64 (6.14-2~mx23ahs) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.14.1-1-liquorix-amd 64. /usr/sbin/dkms.mx autoinstall --kernelver 6.14.1-1-liquorix-amd64 Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/etc/dkms/framework.conf) Sign command: /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-fi le Binary /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... unset ARCH; env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.14.1-1-liq uorix-amd64............(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-a md64 (x86_64) Consult /var/lib/dkms/nvidia-current/550.144.03/build/make.log for more information. Deprecated feature: MODULES_CONF (/etc/dkms/framework.conf) Sign command: /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-fi le Binary /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Building module: Cleaning build area... 'make' -j16 KVER=6.14.1-1-liquorix-amd64 USER_MODULE_NAME=rtl8821ce CONF IG_RTW_DEBUG=n.....(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-a md64 (x86_64) Consult /var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/build/make.log for m ore information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.14.1-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/li nux-headers-6.14.1-1-liquorix-amd64.postinst line 11. dpkg: error processing package linux-headers-6.14.1-1-liquorix-amd64 (-- configure): installed linux-headers-6.14.1-1-liquorix-amd64 package post-installati on script subprocess returned error exit status 1 Setting up linux-libc-dev (6.12.21-1~mx23ahs) ... Setting up linux-image-6.14.1-1-liquorix-amd64 (6.14-2~mx23ahs) ... I: /initrd.img is now a symlink to boot/initrd.img-6.14.1-1-liquorix-amd 64 /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.14.1-1-liquorix-amd 64. /usr/sbin/dkms.mx autoinstall --kernelver 6.14.1-1-liquorix-amd64 Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Deprecated feature: MODULES_CONF (/etc/dkms/framework.conf) Sign command: /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-fi le Binary /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... unset ARCH; env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.14.1-1-liq uorix-amd64.............(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-a md64 (x86_64) Consult /var/lib/dkms/nvidia-current/550.144.03/build/make.log for more information. Deprecated feature: MODULES_CONF (/etc/dkms/framework.conf) Sign command: /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-fi le Binary /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git202 50208/source/dkms.conf) Building module: Cleaning build area... 'make' -j16 KVER=6.14.1-1-liquorix-amd64 USER_MODULE_NAME=rtl8821ce CONF IG_RTW_DEBUG=n.....(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-a md64 (x86_64) Consult /var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/build/make.log for m ore information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.14.1-1-liquorix-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.14.1-1-liquorix-amd64 (--co nfigure): installed linux-image-6.14.1-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1 Setting up mx-packageinstaller (25.5.01) ... dpkg: dependency problems prevent configuration of linux-headers-liquori x-amd64: linux-headers-liquorix-amd64 depends on linux-headers-6.14.1-1-liquorix -amd64 (= 6.14-2~mx23ahs); however: Package linux-headers-6.14.1-1-liquorix-amd64 is not configured yet. dpkg: error processing package linux-headers-liquorix-amd64 (--configure ): dependency problems - leaving unconfigured Setting up brave-browser (1.77.97) ... Setting up mx-boot-options (25.4.01) ... dpkg: dependency problems prevent configuration of linux-image-liquorix- amd64: linux-image-liquorix-amd64 depends on linux-image-6.14.1-1-liquorix-amd 64 (= 6.14-2~mx23ahs); however: Package linux-image-6.14.1-1-liquorix-amd64 is not configured yet. dpkg: error processing package linux-image-liquorix-amd64 (--configure): dependency problems - leaving unconfigured 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 menu (2.1.49) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Errors were encountered while processing: linux-headers-6.14.1-1-liquorix-amd64 linux-image-6.14.1-1-liquorix-amd64 linux-headers-liquorix-amd64 linux-image-liquorix-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) full upgrade complete (or was canceled) this terminal window can now be closed Press any key to close...Ya'll are Great! Thank you!Code: Select all
Reading package lists... Done Building dependency tree... Done Reading state information... Done Package 'rtl8814au-dkms' is not installed, so not removed Package 'rtl8821au-dkms' is not installed, so not removed The following packages will be REMOVED: rtl8812au-dkms* rtl8821ce-dkms* rtl8821cu-dkms* 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. 4 not fully installed or removed. After this operation, 105 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 516927 files and directories currently installed.) Removing rtl8812au-dkms (5.13.6+git20250221-0~mx23) ... /usr/sbin/dkms.mx status -m 8812au /usr/sbin/dkms.mx remove -m 8812au -v 5.13.6 --all Module 8812au-5.13.6 for kernel 6.5.0-1mx-ahs-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8812au.ko: - Uninstallation - Deleting from: /lib/modules/6.5.0-1mx-ahs-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. depmod.... Module 8812au-5.13.6 for kernel 6.6.11-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8812au.ko.xz: - Uninstallation - Deleting from: /lib/modules/6.6.11-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. depmod..... Module 8812au-5.13.6 for kernel 6.7.12-1-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8812au.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. depmod..... Module 8812au-5.13.6 for kernel 6.13.8-4-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8812au.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-4-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. depmod... Module 8812au-5.13.6 for kernel 6.14.1-1-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8812au.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.14.1-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. depmod... Deleting module 8812au-5.13.6 completely from the DKMS tree. Removing rtl8821ce-dkms (5.5.2.1+git20250208-0~mx23) ... /usr/sbin/dkms.mx status -m rtl8821ce -v 5.5.2.1+git20250208 Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) /usr/sbin/dkms.mx remove -m rtl8821ce -v 5.5.2.1+git20250208 --all Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Module rtl8821ce-5.5.2.1+git20250208 for kernel 6.5.0-1mx-ahs-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. rtl8821ce.ko: - Uninstallation - Deleting from: /lib/modules/6.5.0-1mx-ahs-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. depmod... Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Module rtl8821ce-5.5.2.1+git20250208 for kernel 6.6.11-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. rtl8821ce.ko.xz: - Uninstallation - Deleting from: /lib/modules/6.6.11-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. depmod.... Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Module rtl8821ce-5.5.2.1+git20250208 for kernel 6.7.12-1-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. rtl8821ce.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. depmod.... Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20250208/source/dkms.conf) Module rtl8821ce-5.5.2.1+git20250208 for kernel 6.13.8-4-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. rtl8821ce.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-4-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. depmod... Deleting module rtl8821ce-5.5.2.1+git20250208 completely from the DKMS tree. Removing rtl8821cu-dkms (5.12.0+git20250219-1~mx23) ... /usr/sbin/dkms.mx status -m rtl8821cu -v 5.12.0 /usr/sbin/dkms.mx remove -m rtl8821cu -v 5.12.0 --all Module rtl8821cu-5.12.0 for kernel 6.5.0-1mx-ahs-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8821cu.ko: - Uninstallation - Deleting from: /lib/modules/6.5.0-1mx-ahs-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. depmod... Module rtl8821cu-5.12.0 for kernel 6.6.11-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8821cu.ko.xz: - Uninstallation - Deleting from: /lib/modules/6.6.11-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. depmod.... Module rtl8821cu-5.12.0 for kernel 6.7.12-1-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8821cu.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. depmod.... Module rtl8821cu-5.12.0 for kernel 6.13.8-4-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8821cu.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.13.8-4-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. depmod... Module rtl8821cu-5.12.0 for kernel 6.14.1-1-liquorix-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. 8821cu.ko.zst: - Uninstallation - Deleting from: /lib/modules/6.14.1-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. depmod... Deleting module rtl8821cu-5.12.0 completely from the DKMS tree. Setting up linux-headers-6.14.1-1-liquorix-amd64 (6.14-2~mx23ahs) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.14.1-1-liquorix-amd64. /usr/sbin/dkms.mx autoinstall --kernelver 6.14.1-1-liquorix-amd64 Sign command: /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be sign ed Building module: Cleaning build area... unset ARCH; env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.14.1-1-liquorix-amd64............(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/550.144.03/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.14.1-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.14.1-1-liquori x-amd64.postinst line 11. dpkg: error processing package linux-headers-6.14.1-1-liquorix-amd64 (--configure): installed linux-headers-6.14.1-1-liquorix-amd64 package post-installation script subprocess returne d error exit status 1 Setting up linux-image-6.14.1-1-liquorix-amd64 (6.14-2~mx23ahs) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.14.1-1-liquorix-amd64. /usr/sbin/dkms.mx autoinstall --kernelver 6.14.1-1-liquorix-amd64 Sign command: /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be sign ed Building module: Cleaning build area... unset ARCH; env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.14.1-1-liquorix-amd64.............(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/550.144.03/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.14.1-1-liquorix-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.14.1-1-liquorix-amd64 (--configure): installed linux-image-6.14.1-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-liquorix-amd64: linux-headers-liquorix-amd64 depends on linux-headers-6.14.1-1-liquorix-amd64 (= 6.14-2~mx23ahs); h owever: Package linux-headers-6.14.1-1-liquorix-amd64 is not configured yet. dpkg: error processing package linux-headers-liquorix-amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-liquorix-amd64: linux-image-liquorix-amd64 depends on linux-image-6.14.1-1-liquorix-amd64 (= 6.14-2~mx23ahs); howev er: Package linux-image-6.14.1-1-liquorix-amd64 is not configured yet. dpkg: error processing package linux-image-liquorix-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-6.14.1-1-liquorix-amd64 linux-image-6.14.1-1-liquorix-amd64 linux-headers-liquorix-amd64 linux-image-liquorix-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 4 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up linux-headers-6.14.1-1-liquorix-amd64 (6.14-2~mx23ahs) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.14.1-1-liquorix-amd64. /usr/sbin/dkms.mx autoinstall --kernelver 6.14.1-1-liquorix-amd64 Sign command: /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... unset ARCH; env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.14.1-1-liquorix-amd64.............(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/550.144.03/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.14.1-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.14.1-1-liquorix-amd64.postinst line 11. dpkg: error processing package linux-headers-6.14.1-1-liquorix-amd64 (--configure): installed linux-headers-6.14.1-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1 Setting up linux-image-6.14.1-1-liquorix-amd64 (6.14-2~mx23ahs) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.14.1-1-liquorix-amd64. /usr/sbin/dkms.mx autoinstall --kernelver 6.14.1-1-liquorix-amd64 Sign command: /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.14.1-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... unset ARCH; env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.14.1-1-liquorix-amd64.............(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/550.144.03/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.14.1-1-liquorix-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.14.1-1-liquorix-amd64 (--configure): installed linux-image-6.14.1-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-liquorix-amd64: linux-headers-liquorix-amd64 depends on linux-headers-6.14.1-1-liquorix-amd64 (= 6.14-2~mx23ahs); however: Package linux-headers-6.14.1-1-liquorix-amd64 is not configured yet. dpkg: error processing package linux-headers-liquorix-amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-liquorix-amd64: linux-image-liquorix-amd64 depends on linux-image-6.14.1-1-liquorix-amd64 (= 6.14-2~mx23ahs); however: Package linux-image-6.14.1-1-liquorix-amd64 is not configured yet. dpkg: error processing package linux-image-liquorix-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-6.14.1-1-liquorix-amd64 linux-image-6.14.1-1-liquorix-amd64 linux-headers-liquorix-amd64 linux-image-liquorix-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Press any key to close
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Do you expect us to test every DKMS package on Earth? We test the ones in the MX AHS repository. And you can always reboot to the former working kernel, and disable the automatic Liquorix updates.atomick wrote: Thu Apr 10, 2025 9:45 pm Agree No "One" is to blame. yet question would come in resort to - "why Release" an Update of Program selections of files and or kernel release. Specially if it was not Tested Correctly prior release to general update desktop process.
Seeing Revoke or removed such from the update program after its pop to update desktop wide. This is no different from other Kernel Specially releases of how MX outputs via such broad Updates as to how many fail as to how many succeed in update process. With new problems generated.
Sorry to express and others also have expressed the same.. The Soup crappers. No QSI no Fix support is only to tarnish the MX reputation. Have not some to see and consider value to use of MX Distro Release. as it slips from all time #1 distro to now 2nd and what next. 3rd or 4th fall outs.
would a thought to consider. under the users group.n.Blog users.
why not create a Listing post a Form to fill or even just check " New Release " Kernel or update #. - as to "Update release" with users that worked and those that did not. check box be simple yad or zenity simple.
Same with or the all similar process on this particular board as too - Problems and checking the "Solved" Status.
would not an idea to - Problem found ...abc and Solution correction as to "What was done to correct or fix some abnormality in cause of such issue.
Such DB would prevent endless searching and could help any one searching for a problem they .. And this could behold even New Users to Linux as too " I'm experiencing such issue" to list thru Problems and Solved listings as to ..
yes this fits my issue I can resort to this "Solved" state and try such process to fix their issue.
So when users come to the forums they can find a solution or information they may " Learn By " which might provide an immediate answer to try and rectify their issue.
such removing problematic people skills and or seeing constant bold issue not being address directly and an incorrect toss to solution be cast as it is by current to some supporters.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
I think this is sufficient. Plus, no one can really test every hardware combination under the sun. No one just has the resources to be able to provide as many platforms to test on. And, so far, as long as everyone works together, those special situations get resolved.Stevo wrote: Thu Apr 10, 2025 9:51 pm Do you expect us to test every DKMS package on Earth? We test the ones in the MX AHS repository. And you can always reboot to the former working kernel, and disable the automatic Liquorix updates.
Currently, I am running the Liquorix 6.14.1-1 as it was coming from the update. Aside of this one, I still have the xanmod main (6.13) and LTS (6.12) kernels installed, so at least one of them is still running if one fails (and it is clear that I cannot expect the MX team to test DKMS changes against the xanmod kernels as they are not part of MX). So far, on the positive side, for the first time, I do not hear the fan kicking in when playing youtube videos when plugged in (does not happen on battery), and the temperatures are not really high (as to be expected with 2-3% CPU load).
-
DukeComposed
- Posts: 1389
- Joined: Thu Mar 16, 2023 1:57 pm
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Don't feed the LLMs (Lengthy Labyrinthine Meanderers).
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Yes, the fewer .dkms files that need to be automatically rebuilt for the kernel, the fewer potential compilation issues there are when installing a new kernel. However, with some components like Nvidia GPUs and Wi-Fi, there is often no other choice. Therefore, in these cases, it is best to only use the versions present in the MX repositories.Stevo wrote: Thu Apr 10, 2025 9:48 pm Again, a dkms build failure of a deprecrated DKMS package, that you don't even use, is not a kernel panic. A kernel panic is something you see in the dmesg output, and it provides a memory trace for debugging.
...
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32