Page 1 of 1
Kernel Update Issue
Posted: Sat Apr 12, 2025 7:51 pm
by rej
Hi-
Today's update was stalled at 82%, while I assume involved kernels - "depmod" or something.
Long ago, as I did not want kernels to update and had uninstalled:
Code: Select all
linux-image-amd64 meta-package
linux-headers-amd64
And this is likely why the update issue stalled.
Went to reinstall them to get past this and Synaptic dialogue box popped up:
Code: Select all
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
E: _cache->open() failed, cannot continue.
Ran it and it stuck at:
Code: Select all
rj@mx23-rj:~
$ sudo dpkg --configure -a
[sudo] password for rj:
Setting up rtl8821cu-dkms (5.12.0+git20250219-1~mx23+1) ...
Removing old rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms.mx remove -m rtl8821cu -v 5.12.0 --all
Deleting module rtl8821cu-5.12.0 completely from the DKMS tree.
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms.mx add -m rtl8821cu -v 5.12.0
Building for 6.1.0-12-amd64
/usr/sbin/dkms.mx status -m rtl8821cu -v 5.12.0 -k 6.1.0-12-amd64
Building initial module for 6.1.0-12-amd64
/usr/sbin/dkms.mx build -m rtl8821cu -v 5.12.0 -k 6.1.0-12-amd64 -k 6.1.0-12-amd64 -k 6.1.0-11-amd64 -k 6.1.0-10-amd64 -a x86_64
Could it be fixed by manually installing those files uninstalled files through terminal, and if so, how?
I tried "sudo apt install linux-image-amd64 meta-package", which responded with:
"E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem."
Is there any way to fix this?
Re: Kernel Update Issue
Posted: Sat Apr 12, 2025 8:02 pm
by dolphin_oracle
the update probably didn't stall. we updated a bunch of dkms packages so that they won't build on 6.14 and up, because they are included in the 6.14 kernel. but the update could take a while, depeding on hardware.
if you don't need those drivers, remove them wit mx-cleanup, which will remove any unused wifi dkms packages.
Re: Kernel Update Issue
Posted: Sat Apr 12, 2025 8:28 pm
by Tallguy43
I am having the same issue with my update. I had the installation pause at about 73% for a long time. Like earlier poster I interrupted the install.
dpkg --configure -a produces the following dialog.
S****@mxS****~
$ sudo dpkg --configure -a
[sudo] password for S****:
Setting up rtl8821cu-dkms (5.12.0+git20250219-1~mx23+1) ...
Removing old rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms.mx remove -m rtl8821cu -v 5.12.0 --all
Deleting module rtl8821cu-5.12.0 completely from the DKMS tree.
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms.mx add -m rtl8821cu -v 5.12.0
Building for 6.1.0-31-amd64 6.1.0-33-amd64
/usr/sbin/dkms.mx status -m rtl8821cu -v 5.12.0 -k 6.1.0-31-amd64
Building initial module for 6.1.0-31-amd64
/usr/sbin/dkms.mx build -m rtl8821cu -v 5.12.0 -k 6.1.0-31-amd64 -k 6.1.0-31-amd64 -k 6.1.0-33-amd64 -k 6.1.0-32-amd64 -a x86_64
I attempted to use Mx Cleanup to remove rtl8821cu and got prompted to repeat "dpkg --configure -a"
My system runs without any apparent errors but I assume that dpkg is broken.
-----------------------------------------------------------
Code: Select all
System:
Kernel: 6.1.0-31-amd64 [6.1.128-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-31-amd64 root=UUID=<filter> ro quiet nomodeset splash
init=/lib/systemd/systemd
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto Jan 12 2025 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Dell product: Latitude 7390 v: N/A serial: <superuser required> Chassis:
type: 10 serial: <superuser required>
Mobo: Dell model: 0MXW44 v: A07 serial: <superuser required> UEFI: Dell v: 1.41.0
date: 11/06/2024
Re: Kernel Update Issue
Posted: Sat Apr 12, 2025 8:41 pm
by dolphin_oracle
so building the dkms packages for three kenrels is going to take a while.
run the dpkg --configure -a command and let it finish.
Re: Kernel Update Issue
Posted: Sat Apr 12, 2025 9:06 pm
by Tallguy43
How long would you guess? Running this in terminal does not give any feedback as to progress. Are we talking minutes? hours?
Re: Kernel Update Issue
Posted: Sat Apr 12, 2025 9:13 pm
by siamhie
Tallguy43 wrote: Sat Apr 12, 2025 9:06 pm
How long would you guess? Running this in terminal does not give any feedback as to progress. Are we talking minutes? hours?
As long as it takes to make sure it works.
Re: Kernel Update Issue
Posted: Sat Apr 12, 2025 9:32 pm
by rej
dolphin_oracle wrote: Sat Apr 12, 2025 8:41 pm
so building the dkms packages for three kenrels is going to take a while.
run the dpkg --configure -a command and let it finish.
Hi Dolphin -
You are right - guess this computer is pretty slow.
Thank you!
Re: Kernel Update Issue
Posted: Sat Apr 12, 2025 9:59 pm
by Tallguy43
Dolphin, Siamhie
My problem finally resolved by letting "dpkg --configure -a" run for a lengthy period of time. I wasn't watching closely, but I'd guess a little over an hour.
Thanks for the feedback!
Scott
Re: Kernel Update Issue
Posted: Sun Apr 13, 2025 10:55 am
by Stevo
Use MX Cleanup to remove unused wifi drivers to really speed that up.
Re: Kernel Update Issue
Posted: Sun Apr 13, 2025 10:57 am
by Eadwine Rose
I did that for the first time, and boy did that make a massive difference! Should have done that a long time ago, so yeah, can recommend!
Re: Kernel Update Issue
Posted: Sun Apr 13, 2025 11:04 am
by Stevo
Eadwine Rose wrote: Sun Apr 13, 2025 10:57 am
I did that for the first time, and boy did that make a massive difference! Should have done that a long time ago, so yeah, can recommend!
But...but....didn't you have to put in your password and push a couple buttons?
Re: Kernel Update Issue
Posted: Sun Apr 13, 2025 12:19 pm
by Eadwine Rose
I didn't even trust that the drivers that would be removed were unused. I have trust issues (gee).
Re: Kernel Update Issue
Posted: Sun Apr 13, 2025 4:19 pm
by b3ta
Stevo wrote: Sun Apr 13, 2025 11:04 am
But...but....didn't you have to put in your password and push a couple buttons?
Having just suffered through a kernel update that took so long on our ancient Netflix laptop that my wife went to bed, I tried running
mx-cleanup, but it failed, as it wouldn't accept my password for the privilege enhancement. Since I have more than one user on my system, I was presented with a choice of which user to run the actual Wi-Fi driver remove command as, but none was accepted (details below).
If anyone comes up against not being able to run a GUI program as root, here is the simplest solution I have found, which you have to run from an xterm:
Code: Select all
sudo XAUTHORITY=$XAUTHORITY DISPLAY=$DISPLAY {PROGRAM}
That sets the two critical environment variables for the program to be allowed by X to handle GUI I/O.
As an aside, after the kernel update that machine once again sees and talks to its built-in Wi-Fi card. There were frayed nerves at having no Netflix and no Spotify for a few days, so now it's happy wife...
For those who can/want to look into the polkit issue, this is what I got:
Code: Select all
==== AUTHENTICATING FOR org.mxlinux.pkexec.mx-cleanup.helper-terminal ====
MX Cleanup
Multiple identities can be used for authentication:
1. user1
2. ,,, (user2)
3. user3,,, (user3)
4. user4,,, (user4)
Choose identity to authenticate as (1-4): 1
Password:
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized
This incident has been reported.
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
Press any key to close
It took me a while, but I did eventually find the "any key", but I shudder for when I log in again as root: all those emails...
For those building a data base:
Code: Select all
System:
Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.12-1-liquorix-amd64
root=UUID=<filter> ro threadirqs resume=UUID=<filter> resume_offset=1466368 noapic nolapic
init=/lib/systemd/systemd
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: AVL_MXE-23.2-20240405_x64 Enlightened April 5 2024 base: Debian
GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: Dell product: Latitude E6510 v: 0001 serial: <superuser required> Chassis:
type: 9 serial: <superuser required>
Mobo: Dell model: 0N5KHN v: A03 serial: <superuser required> BIOS: Dell v: A17 date: 05/12/2017
Battery:
ID-1: BAT0 charge: 42.1 Wh (100.0%) condition: 42.1/86.6 Wh (48.6%) volts: 12.3 min: 11.1
model: Samsung SDI DELL MP4949B type: Li-ion serial: <filter> status: full
CPU:
Info: model: Intel Core i7 Q 840 bits: 64 arch: Nehalem gen: core 1 level: v2 built: 2008-10
process: Intel 45nm family: 6 model-id: 0x1E (30) stepping: 5 microcode: 0xA
Topology: cpus: 1x cores: 1 smt: disabled cache: L1: 64 KiB desc: d-1x32 KiB; i-1x32 KiB
L2: 256 KiB desc: 1x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): 1627 min/max: 1199/1867 boost: enabled scaling: driver: acpi-cpufreq
governor: performance core: 1: 1627 bogomips: 3724
Flags: 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 status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, RSB filling, PBRSB-eIBRS:
Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GT218M [NVS 3100M] vendor: Dell Latitude E6510 driver: nvidia v: 340.108
non-free: series: 340.xx status: legacy (EOL) last: release: 340.108 kernel: 5.4 xorg: 1.20
arch: Tesla process: 40-80nm built: 2006-13 pcie: gen: 2 speed: 5 GT/s lanes: 16
bus-ID: 01:00.0 chip-ID: 10de:0a6c class-ID: 0300
Device-2: Ricoh HD Webcam type: USB driver: uvcvideo bus-ID: 1-1.4:3 chip-ID: 05ca:1814
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: 1368x768 s-dpi: 96 s-size: 362x204mm (14.25x8.03") s-diag: 416mm (16.36")
Monitor-1: DP-3 size-res: N/A modes: N/A
Monitor-2: VGA-0 pos: primary res: 1368x768 hz: 60 modes: N/A
API: OpenGL v: 3.3.0 NVIDIA 340.108 renderer: NVS 3100M/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell Latitude E6510
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403
Device-2: NVIDIA High Definition Audio vendor: Dell Latitude E6510 driver: snd_hda_intel
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0be3 class-ID: 0403
API: ALSA v: k6.6.12-1-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: Intel 82577LM Gigabit Network vendor: Dell Latitude E6510 driver: e1000e v: kernel
port: 8040 bus-ID: 00:19.0 chip-ID: 8086:10ea class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:422b class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
Device-3: Dell F3607gw v2 Mobile Broadband Module type: USB driver: cdc_acm,cdc_ether,cdc_wdm
bus-ID: 2-1.6:4 chip-ID: 413c:8184 class-ID: 0202 serial: <filter>
IF: wwx028037ec0200 state: down mac: <filter>
Bluetooth:
Device-1: Dell DW375 Bluetooth Module type: USB driver: btusb v: 0.8 bus-ID: 2-1.7:5
chip-ID: 413c:8187 class-ID: fe01 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 4 state: up address: <filter> bt-v: 2.0 lmp-v: 3.0
sub-v: 4203 hci-v: 3.0 rev: 205
Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
Local Storage: total: 111.8 GiB used: 49.89 GiB (44.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WDS120G2G0A-00JH30 size: 111.8 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 0000
scheme: MBR
Partition:
ID-1: / raw-size: 111.79 GiB size: 109.48 GiB (97.93%) used: 49.89 GiB (45.6%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 10.7 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 58.0 C mobo: N/A sodimm: SODIMM C gpu: nvidia temp: 52 C
Fan Speeds (RPM): cpu: 2397
Repos:
Packages: 2679 pm: dpkg pkgs: 2674 libs: 1503 tools: apt,apt-get,aptitude,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 5
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/mx.list
1: deb http://it.mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://it.mxrepo.com/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.sources
1: deb https://repo.protonvpn.com/debian stable main
Info:
Processes: 292 Uptime: 1h 17m wakeups: 2 Memory: 7.7 GiB used: 1.43 GiB (18.5%) Init: systemd
v: 252 target: graphical (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: BIOS (legacy, CSM, MBR)