Page 1 of 1
Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Mar 05, 2025 1:16 am
by argonaut459
Hi,
due to the nvidia issues I - somehow - paused my updates of kernel. Now the issues seem to be fixed, according to blog post. Wanted to enable auto update again, getting this error.
Code: Select all
OK:1 https://mirror.23m.com/mx-packages/mx/repo bookworm InRelease
OK:2 http://deb.debian.org/debian bookworm-updates InRelease
OK:3 http://security.debian.org/debian-security bookworm-security InRelease
OK:4 http://deb.debian.org/debian bookworm InRelease
Ign:5 https://repo.vivaldi.com/stable/deb stable InRelease
OK:6 https://repo.vivaldi.com/stable/deb stable Release
Paketlisten werden gelesen…
Paketlisten werden gelesen…
Abhängigkeitsbaum wird aufgebaut…
Statusinformationen werden eingelesen…
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
libgdk-pixbuf-xlib-2.0-0 libgdk-pixbuf2.0-0
Verwenden Sie »apt autoremove«, um sie zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
linux-headers-6.1.0-31-amd64 linux-headers-6.1.0-31-common
linux-image-6.1.0-31-amd64
Vorgeschlagene Pakete:
linux-doc-6.1 debian-kernel-handbook
Empfohlene Pakete:
apparmor
Die folgenden NEUEN Pakete werden installiert:
linux-headers-6.1.0-31-amd64 linux-headers-6.1.0-31-common
linux-image-6.1.0-31-amd64
Die folgenden zurückgehaltenen Pakete werden verändert:
linux-headers-amd64 linux-image-amd64
Die folgenden Pakete werden aktualisiert (Upgrade):
linux-headers-amd64 linux-image-amd64
2 aktualisiert, 3 neu installiert, 0 zu entfernen und 2 nicht aktualisiert.
E: Der Status gehaltener Pakete wurde geändert und -y wurde ohne --allow-change-held-packages verwendet.
update dkms modules for kernel: 6.1.0-28-amd64
see log at /var/log/rebuild-dkms.log
dkms: running auto installation service for kernel 6.1.0-28-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-28-amd64
dkms: autoinstall for kernel: 6.1.0-28-amd64.
Can't remember how I disable updates of AHS and normal kernel - but it was easy - just a click somewhere. Maybe I deactivated the "update packages" in MXPI for normal Debian and AHS.
I don't need AHS kernels, so the other kernel I got installed can be removed afterwards.
But how do I use
--allow-change-held-packages
?
Thanks for the help, of again fixing my stupid mistakes.
Code: Select all
System:
Kernel: 6.1.0-28-amd64 [6.1.119-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-28-amd64 root=UUID=<filter> ro quiet splash
resume=UUID=<filter> resume_offset=206848
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel, plank wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: MX-23.5_ahs_x64 Libretto January 21 2024 base: Debian GNU/Linux
12 (bookworm)
Machine:
Type: Desktop Mobo: MSI model: Z97A GAMING 6 (MS-7917) v: 2.0 serial: <superuser required>
UEFI: American Megatrends v: 10.2 date: 08/11/2015
CPU:
Info: model: Intel Core i5-4690K 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: 0x28
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: 3500 min/max: 800/3500 scaling: driver: intel_cpufreq governor: ondemand
cores: 1: 3500 2: 3500 3: 3500 4: 3500 bogomips: 27998
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 mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: eVga.com. driver: nvidia v: 535.216.03
non-free: 530.xx+ status: current (as of 2023-03) arch: Maxwell code: GMxxx process: TSMC 28nm
built: 2014-19 pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 02:00.0
chip-ID: 10de:13c2 class-ID: 0300
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: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
Monitor-1: DVI-I-1 res: 1920x1080 hz: 60 dpi: 92 size: 531x298mm (20.91x11.73")
diag: 609mm (23.97") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 535.216.03 renderer: NVIDIA GeForce GTX 970/PCIe/SSE2
direct-render: Yes
Audio:
Device-1: Intel 9 Series Family HD Audio vendor: Micro-Star MSI 9 driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403
Device-2: NVIDIA GM204 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 02:00.1 chip-ID: 10de:0fbb
class-ID: 0403
API: ALSA v: k6.1.0-28-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: Qualcomm Atheros Killer E220x Gigabit Ethernet vendor: Micro-Star MSI driver: alx
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 04:00.0 chip-ID: 1969:e091
class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 2.73 TiB used: 340.2 GiB (12.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 033 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ABB0
scheme: MBR
Partition:
ID-1: / raw-size: 65.19 GiB size: 63.61 GiB (97.58%) used: 55.46 GiB (87.2%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 866.07 GiB size: 851.4 GiB (98.31%) used: 284.74 GiB (33.4%) fs: ext4
dev: /dev/sda3 maj-min: 8:3
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 37.3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
ID-2: swap-2 type: zram size: 15.65 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
ID-3: swap-3 type: zram size: 15.65 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram1
ID-4: swap-4 type: zram size: 15.65 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram2
ID-5: swap-5 type: zram size: 15.65 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram3
Sensors:
System Temperatures: cpu: 37.0 C mobo: N/A gpu: nvidia temp: 59 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
Packages: 2350 pm: dpkg pkgs: 2324 libs: 1191 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 26
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 https://mirror.23m.com/mx-packages/mx/repo/ bookworm main non-free
2: deb https://mirror.23m.com/mx-packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
Processes: 224 Uptime: 10m wakeups: 1 Memory: 31.29 GiB used: 2.8 GiB (8.9%) 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: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Mar 05, 2025 1:22 am
by Stevo
Just reinstall the "Debian 64-bit kernel" in MXPI to get the Bookworm automatic updates again. But 6.1.0-31 is the latest, and you have it.
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Mar 05, 2025 1:27 am
by argonaut459
You mean the one that called DEBIAN 64bit?
that's the one that caused the error.
Or how do I activate the debian AHS ones? Maybe they are a good idea after all? newer = better ??
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Mar 05, 2025 4:41 am
by CatManDan
by installing one of the Debian kernels below. 6.12.17 would be the latest version. You should then find this entry in your GRUB on startup.
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Mar 05, 2025 5:33 am
by argonaut459
CatManDan wrote: ↑Wed Mar 05, 2025 4:41 am
by installing one of the Debian kernels below. 6.12.17 would be the latest version. You should then find this entry in your GRUB on startup.
And than, it'll auto update this kernel?
perfect, will do
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Mar 05, 2025 7:57 am
by j2mcgreg
Rather than updating your kernel just because you can, you should first be asking yourself: Is my system working well as is? As I say in my signature, In Linux newer isn't always better. The best solution is the one that works.
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Mar 05, 2025 10:21 am
by Stevo
If you use MXPI to install the Liquorix kernel, it'll auto-update. The backported upstream MX AHS Debian kernels do not auto-update.
You may be able to figure out some way to do that in Debian backports, but I would not bother. Remember that updating kernels does not remove older kernels...unless you autoremove them, which is also not recommended.
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Fri Apr 11, 2025 4:13 am
by argonaut459
some time passed, and still not able to get rid of these "witheld" packages.
In MXPI I only got one checkmark in Kernels - a liqourix kernel. If I say deinstall, it fails and states this in console:
Code: Select all
Paketlisten werden gelesen…
Abhängigkeitsbaum wird aufgebaut…
Statusinformationen werden eingelesen…
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:
Die folgenden Pakete haben unerfüllte Abhängigkeiten:
linux-headers-liquorix-amd64 : Hängt ab von: linux-headers-6.11.10-1-liquorix-amd64 (= 6.11-15~mx23ahs) soll aber nicht installiert werden
linux-image-liquorix-amd64 : Hängt ab von: linux-image-6.11.10-1-liquorix-amd64 (= 6.11-15~mx23ahs) soll aber nicht installiert werden
E: Fehler: Unterbrechungen durch pkgProblemResolver::Resolve hervorgerufen; dies könnte durch zurückgehaltene Pakete verursacht worden sein.
inxi states that I'm currently using
Code: Select all
System:
Kernel: 6.12.17-amd64 [6.12.17-1~mx23ahs]
trying to install standart debian kernel from MXPI
Code: Select all
Installieren
linux-headers-6.1.0-32-amd64 (6.1.129-1)
linux-headers-6.1.0-32-common (6.1.129-1)
linux-headers-amd64 [6.1.119-1] => (6.1.129-1)
linux-image-6.1.0-32-amd64 (6.1.129-1)
linux-image-amd64 [6.1.119-1] => (6.1.129-1)
results in
Code: Select all
OK:1 https://mirror.23m.com/mx-packages/mx/repo bookworm InRelease
OK:2 http://security.debian.org/debian-security bookworm-security InRelease
OK:3 http://deb.debian.org/debian bookworm-updates InRelease
OK:4 http://deb.debian.org/debian bookworm InRelease
Ign:5 https://repo.vivaldi.com/stable/deb stable InRelease
OK:6 https://repo.vivaldi.com/stable/deb stable Release
Paketlisten werden gelesen…
Paketlisten werden gelesen…
Abhängigkeitsbaum wird aufgebaut…
Statusinformationen werden eingelesen…
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
libgdk-pixbuf-xlib-2.0-0 libgdk-pixbuf2.0-0 linux-headers-6.1.0-28-amd64
linux-headers-6.1.0-28-common linux-image-6.1.0-28-amd64 lp-solve
Verwenden Sie »apt autoremove«, um sie zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
linux-headers-6.1.0-32-amd64 linux-headers-6.1.0-32-common
linux-image-6.1.0-32-amd64
Vorgeschlagene Pakete:
linux-doc-6.1 debian-kernel-handbook
Empfohlene Pakete:
apparmor
Die folgenden NEUEN Pakete werden installiert:
linux-headers-6.1.0-32-amd64 linux-headers-6.1.0-32-common
linux-image-6.1.0-32-amd64
Die folgenden zurückgehaltenen Pakete werden verändert:
linux-headers-amd64 linux-image-amd64
Die folgenden Pakete werden aktualisiert (Upgrade):
linux-headers-amd64 linux-image-amd64
2 aktualisiert, 3 neu installiert, 0 zu entfernen und 11 nicht aktualisiert.
E: Der Status gehaltener Pakete wurde geändert und -y wurde ohne --allow-change-held-packages verwendet.
update dkms modules for kernel: 6.12.17-amd64
see log at /var/log/rebuild-dkms.log
dkms: running auto installation service for kernel 6.12.17-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.12.17-amd64
readelf: Warning: Section '.comment' was not dumped because it does not exist
readelf: Warning: Section '.comment' was not dumped because it does not exist
dkms: autoinstall for kernel: 6.12.17-amd64.
Seems I really really messed up my system again, just cause I feared issues with the Nvidia card and newer kernels *sigh*
Really appreciate all your help
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Fri Apr 11, 2025 10:36 am
by CharlesV
Go into mx Boot Options and look at the kernels you have available there. You can boot to a different kernel as well.
Once you are on a kernel you want to be running, then you can go into MX Cleanup and use the List and select kernels to remove. ( this will do a better job of removing kernels from what I have seen.)
I would leave at least three kernels on board - the one your running, and two others. I usually leave the LAST one that I know ran good, and then the stock LTS kernel ( 6.1.0.32 in my case atm.)
You may want to do a cache and apt cleanup. (also MX Cleanup - or stacer ) And also... if you have not already done it... a timeshift so you can restore if it all goes south ;-/
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Apr 16, 2025 7:45 am
by argonaut459
CharlesV wrote: ↑Fri Apr 11, 2025 10:36 am
Go into mx Boot Options and look at the kernels you have available there. You can boot to a different kernel as well.
Once you are on a kernel you want to be running, then you can go into MX Cleanup and use the List and select kernels to remove. ( this will do a better job of removing kernels from what I have seen.)
I would leave at least three kernels on board - the one your running, and two others. I usually leave the LAST one that I know ran good, and then the stock LTS kernel ( 6.1.0.32 in my case atm.)
You may want to do a cache and apt cleanup. (also MX Cleanup - or stacer ) And also... if you have not already done it... a timeshift so you can restore if it all goes south ;-/
Running MX Cleanup, and selecting 6.11. liquorix kernel results in this error
Code: Select all
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:
Die folgenden Pakete haben unerfüllte Abhängigkeiten:
linux-headers-liquorix-amd64 : Hängt ab von: linux-headers-6.11.10-1-liquorix-amd64 (= 6.11-15~mx23ahs) soll aber nicht installiert werden
linux-image-liquorix-amd64 : Hängt ab von: linux-image-6.11.10-1-liquorix-amd64 (= 6.11-15~mx23ahs) soll aber nicht installiert werden
E: Fehler: Unterbrechungen durch pkgProblemResolver::Resolve hervorgerufen; dies könnte durch zurückgehaltene Pakete verursacht worden sein.
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
libgdk-pixbuf-xlib-2.0-0 libgdk-pixbuf2.0-0 lp-solve
Verwenden Sie »apt autoremove«, um sie zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 28 nicht aktualisiert.
Schließen mit beliebiger Taste
pkgProblemResolver::Resolve
As the message states, probably caused by the withheld packages. I haven't found yet how to not withhold them
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Apr 16, 2025 8:22 am
by j2mcgreg
It looks like you installed the Liquorix 6.11.xxx kernel image but you didn't install the corresponding (and required) Liquorix 6.11.xxx headers package. You should search under the Enabled Repos tab of MXPI for this package, install it, and then reboot. If you see improved performance in your computer, you should keep it. Otherwise you can now remove the kernel with Cleanup.
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Apr 16, 2025 8:26 am
by argonaut459
Just to be sure:
select it and click the "re-install" / install button. Will try it, when I'm back home tonight.
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Wed Apr 16, 2025 8:40 am
by j2mcgreg
argonaut459 wrote: ↑Wed Apr 16, 2025 8:26 am
Just to be sure:
select it and click the "re-install" / install button. Will try it, when I'm back home tonight.
No, what you need is this last one listed:
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Sat Apr 26, 2025 2:03 pm
by argonaut459
6.11.10 header is already installed. Shall I re-install it?
Re: Update Kernel issue, after halting kernel updates due to nvidia issues
Posted: Sat Apr 26, 2025 2:31 pm
by j2mcgreg
I fear that you may be in a "too many cooks" scenario where all of us are offering you advice, but none of us have the advantage of looking over you shoulder at your actual machine, I think that your best next moves would be to back up your data and then do a reinstall so that you have a fresh perspective. You can find the MX 23.6 releases here:
https://mxlinux.org/blog/mx-23-6-now-available/