Unable to uninstall kernel linux-6.17 after installed linux-6.18

Hi team!!! Hope everything fine overthere…

As title says , i’m unable to uninstall kernel linux-6.17 (which has been marked as EOL ) after install linux-6.18…

I’m getting this error message:

error: failed to prepare transaction (could not satisfy dependencies) :: removing linux617 breaks dependency ‘linux617’ required by linux-meta

Here i let my “inxi --full --admin --filter --width” output:

System:
  Kernel: 6.18.2-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
    root=UUID=cc0092ed-8fae-4f26-aee0-4fcc21f7f9ce rw rootflags=subvol=@ quiet
    splash apparmor=1 security=apparmor udev.log_priority=3
  Desktop: GNOME v: 49.2 tk: GTK v: 3.24.51 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 49.2 Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ASUS EXPERTBOOK B3604CMA_B3604CMA
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: B3604CMA v: 1.0 serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: ASUSTeK (Licensed by AMI
    LLC.) v: B3604CMA.307 date: 12/12/2024
Battery:
  ID-1: BAT0 charge: 39.6 Wh (77.9%) condition: 50.9/50 Wh (101.7%)
    power: 18.4 W volts: 13.09 min: 11.88 model: C490-42 type: Unknown
    serial: <filter> charging: status: charging control: start: N/A end: 80%
    cycles: 29
  Device-1: ps-controller-battery-a0:5a:5d:55:08:45 model: N/A serial: N/A
    charge: N/A status: full
CPU:
  Info: model: Intel Core Ultra 5 125U bits: 64 type: MST AMCP
    arch: Meteor Lake level: v3 note: check built: 2023+ process: Intel 4 (7nm)
    family: 6 model-id: 0xAA (170) stepping: 4 microcode: 0x25
  Topology: cpus: 1x dies: 1 clusters: 5 cores: 12 threads: 14 mt: 2 tpc: 2
    st: 10 smt: enabled cache: L1: 1.2 MiB desc: d-10x32 KiB, 2x48 KiB; i-12x64
    KiB L2: 10 MiB desc: 5x2 MiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 400 min/max: 400/4300:3600:2100 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
    bogomips: 75264
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection 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: old_microcode status: Not affected
  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: Enhanced / Automatic IBRS; IBPB: conditional;
    PBRSB-eIBRS: Not affected; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Meteor Lake-P [Intel Graphics] vendor: ASUSTeK driver: i915
    v: kernel alternate: xe arch: Xe-LPG process: Intel 4 (7nm+) built: 2023+
    ports: active: HDMI-A-1,eDP-1 empty: DP-1, DP-2, DP-3, DP-4
    bus-ID: 0000:00:02.0 chip-ID: 8086:7d45 class-ID: 0300
  Device-2: BillionPixels USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-7:3 chip-ID: 322e:2338
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: HDMI-A-1 model: MSI MP243X serial: <filter> built: 2025
    res: 1920x1080 dpi: 92 gamma: 1.2 size: 530x290mm (20.87x11.42")
    diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  Monitor-2: eDP-1 model: ChiMei InnoLux 0x1614 built: 2021 res: 1920x1200
    dpi: 142 gamma: 1.2 size: 344x215mm (13.54x8.46") diag: 406mm (16")
    ratio: 16:10 modes: 1920x1200
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (MTL)
    device-ID: 8086:7d45 memory: 29.94 GiB unified: yes display-ID: :0.0
  API: Vulkan v: 1.4.335 layers: 2 device: 0 type: integrated-gpu
    name: Intel Graphics (MTL) driver: mesa intel v: 25.3.1-arch1.2
    device-ID: 8086:7d45 surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo gpu: gputop, intel_gpu_top,
    lsgpu x11: xprop,xrandr
Audio:
  Device-1: Intel Meteor Lake-P HD Audio vendor: ASUSTeK
    driver: sof-audio-pci-intel-mtl
    alternate: snd_sof_pci_intel_mtl,snd_hda_intel bus-ID: 0000:00:1f.3
    chip-ID: 8086:7e28 class-ID: 0401
  Device-2: Sony DualShock 4 [CUH-ZCT2x]
    driver: playstation,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-6.4:8 chip-ID: 054c:09cc class-ID: 0300
  API: ALSA v: k6.18.2-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Meteor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 0000:00:14.3 chip-ID: 8086:7e40 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Device-2: Intel Ethernet I219-LM driver: e1000e v: kernel port: N/A
    bus-ID: 0000:00:1f.6 chip-ID: 8086:550b class-ID: 0200
  IF: eno2 state: down mac: <filter>
  IF-ID-1: br-539e74b62cc9 state: down mac: <filter>
  IF-ID-2: br-74374c568f83 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IF-ID-3: br-ac9ab113a6b3 state: down mac: <filter>
  IF-ID-4: br-acaf46c64379 state: down mac: <filter>
  IF-ID-5: br-e1c6b159770a state: down mac: <filter>
  IF-ID-6: br-f6f4693bad50 state: down mac: <filter>
  IF-ID-7: docker0 state: down mac: <filter>
  IF-ID-8: veth04e7206 state: up speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-9: veth3c32528 state: up speed: 10000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, sshd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:9 chip-ID: 8087:0026
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller Intel
    driver: vmd v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:7d0b rev:
    class-ID: 0104
Drives:
  Local Storage: total: 476.94 GiB used: 237.2 GiB (49.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Solidgm model: SSDPFKNU512GZ
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 002C temp: 18.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 80 GiB size: 80 GiB (100.00%) used: 32.48 GiB (40.6%)
    fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-2: /boot/efi raw-size: 512.7 MiB size: 511.6 MiB (99.80%)
    used: 648 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-3: /home raw-size: 40 GiB size: 40 GiB (100.00%) used: 11.67 GiB (29.2%)
    fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-4: /var/log raw-size: 80 GiB size: 80 GiB (100.00%)
    used: 32.48 GiB (40.6%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p9 maj-min: 259:9
Sensors:
  System Temperatures: cpu: 34.5 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.66 GiB used: 4.19 GiB (13.7%)
  Processes: 439 Power: uptime: 8m states: freeze,mem,disk suspend: s2idle
    avail: deep wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend,
    test_resume image: 12.25 GiB services: gsd-power, power-profiles-daemon,
    upowerd Init: systemd v: 258 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1563 libs: 363 tools: gnome-software,pamac
    pm: flatpak pkgs: 0 Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Zsh v: 5.9

Happy Hollidays!!!

Thanks in advance!!!

This just means that you need to remove linux-meta along with linux6.17.

1 Like

But, suposely , that must be done by system management tool automatically…i’ve been doing this since i installed Manjaro by first time around 7 years ago. And i never got this error

AFAIK, you cannot install or remove the linux-meta package via Manjaro-Settings-Manager.

Yes - the linux-meta package - one of @philm’s inventions to free the user of the worries of kernel maintenance.

It is used to ensure you are not using an unsupported kernel - and it automagically appear.

To get rid of it you can remove it - and since you don’t use Nvidia the following will do

sudo pacman -R linux-meta linux617
1 Like

As @jrichard326 suggests, linux-meta needs to be uninstalled first – make sure to install either of kernels 6.18 (LTS) or 6.12 (LTS) before rebooting. Having both of these kernels installed is currently the most viable option.

Regards.

Done…solved …thanks to everyone, specially to @jrichard326 …so, for now and on everytime i install new kernel gonna need to uninstall old one manually?

Yep, you are right but what i mean it’s that i never got this error before while installing new kernels and removing old ones using Manjaro Settings Manager

You are likely correct - the linux-meta package is not that old - I think it was created due to some incidents relating to Nvidia driver; when the kernel was removed from the rope - thus the Nvida kernel driver would get removed too - this created some hard to explain and hard to guide the user to resolve.

You can sill install a new kernel and remove the old one in the same roll - just remember to restart your system or strange events may occur.

sudo mhwd-kernel -i linux618 rmc

Only on the event that you forget - then you know why the linux-meta is there once again.

A piece of advice: just stick to LTS kernels, like 6.18 and you will have to change again in 2 years. Otherwise - every 3 months.

3 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.