Not able to install different kernel versions (Manjaro Stable KDE)

Support Kernel
1

Hello,

I’m currently running Manjaro Stable Versions released 2024-jul-29, It’s a rollback from 2024-aug-08 once my system crashed too much often with that last release. In general it crashed with less frequency.

When that happen in general I also start o check updates combined with different kernels in order to find a better stable combination but for any reason, after rollback, Manjaro Kernel APP is not able to install any other kernel version. Besides I click on install it runs the bar and show the message DONE, but nothing change, the flag INSTALLED is not added and boot list is not changed as well, even after reboot.

While I’m waiting for the next stable release to see if stability was improved, maybe kwin issue or other, I’d like to test different kernels in the meantime.

Is there any procedure I shoulddo in order to fix Manjaro Kernel APP?

kernel list
kernel list979×1109 109 KB

Below my system information.

System:
  Kernel: 6.9.10-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.9-x86_64
    root=UUID=84e0bfca-0d47-4324-b85a-614ea38dc5f9 rw rootflags=subvol=@ quiet
    splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.4.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: MACHINIST model: E5-MR9A v: V1.0
    serial: <superuser required> uuid: <superuser required>
    UEFI: American Megatrends v: 5.11 date: 10/25/2022
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 31.19 GiB used: 2.68 GiB (8.6%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 256 GiB note: check slots: 4 modules: 4
    EC: Multi-bit ECC max-module-size: 64 GiB note: est.
  Device-1: DIMM_A1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1 min: 1.14 max: 1.26 width (bits): data: 72
    total: 72 manufacturer: Hynix Semiconductor part-no: HMA41GR7AFR4N-UH
    serial: <filter>
  Device-2: DIMM_B1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1 min: 1.14 max: 1.26 width (bits): data: 72
    total: 72 manufacturer: Hynix Semiconductor part-no: HMA41GR7AFR4N-UH
    serial: <filter>
  Device-3: DIMM_C1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1 min: 1.14 max: 1.26 width (bits): data: 72
    total: 72 manufacturer: Hynix Semiconductor part-no: HMA41GR7AFR4N-UH
    serial: <filter>
  Device-4: DIMM_D1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1 min: 1.14 max: 1.26 width (bits): data: 72
    total: 72 manufacturer: Hynix Semiconductor part-no: HMA41GR7AFR4N-UH
    serial: <filter>
CPU:
  Info: model: Intel Xeon E5-2667 v4 bits: 64 type: MT MCP arch: Broadwell
    level: v3 note: check built: 2015-18 process: Intel 14nm family: 6
    model-id: 0x4F (79) stepping: 1 microcode: 0xB000040
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB L3: 25 MiB
    desc: 1x25 MiB
  Speed (MHz): avg: 1656 high: 3600 min/max: 1200/3600 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 1200 2: 1309 3: 1200
    4: 1200 5: 1200 6: 1200 7: 1200 8: 1200 9: 1200 10: 3600 11: 3600 12: 3600
    13: 1200 14: 1200 15: 1200 16: 1200 bogomips: 102218
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon
    avx avx2 bmi1 bmi2 bts cat_l3 cdp_l3 clflush cmov constant_tsc cpuid
    cpuid_fault cqm cqm_llc cqm_mbm_local cqm_mbm_total cqm_occup_llc cx16 cx8
    dca de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fxsr hle ht ibpb ibrs ida intel_ppin intel_pt
    invpcid lahf_lm lm mca mce md_clear mmx monitor movbe msr mtrr nonstop_tsc
    nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt
    pse pse36 pti pts rdrand rdseed rdt_a rdtscp rep_good rtm sdbg sep smap
    smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xsave xsaveopt xtopology xtpr
  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
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  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: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-1 code: Navi-1x
    process: TSMC n7 (7nm) built: 2019-20 pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: DP-2 empty: DP-1,DP-3,HDMI-A-1 bus-ID: 05:00.0
    chip-ID: 1002:731f class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.1
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: DP-2 res: 2560x1440 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
    drv: radeonsi inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.3-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 5700 XT (radeonsi
    navi10 LLVM 18.1.8 DRM 3.57 6.9.10-1-MANJARO) device-ID: 1002:731f
    memory: 7.81 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 6 device: 0 type: discrete-gpu name: AMD
    Radeon RX 5700 XT (RADV NAVI10) driver: mesa radv v: 24.1.3-manjaro1.1
    device-ID: 1002:731f surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:ab38
    class-ID: 0403
  API: ALSA v: k6.9.10-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.2.1 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-4: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 08:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp8s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: virbr0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  Info: services: NetworkManager
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.73 TiB used: 1.7 TiB (62.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WD Blue SN570 500GB size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 234100WD temp: 30.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: A-Data model: LEGEND 850 Lite
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: V0922A0 temp: 29.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD20PURZ-85GU6Y0
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 0A80 scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 123.45 GiB (26.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
    label: N/A uuid: 84e0bfca-0d47-4324-b85a-614ea38dc5f9
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:3 label: N/A
    uuid: 21D8-DE05
  ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 123.45 GiB (26.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
    label: N/A uuid: 84e0bfca-0d47-4324-b85a-614ea38dc5f9
  ID-4: /home/<filter>/Games raw-size: 465.76 GiB size: 457.38 GiB (98.20%)
    used: 141.37 GiB (30.9%) fs: ext4 dev: /dev/nvme0n1p1 maj-min: 259:1
    label: GAMES uuid: b5780269-0438-4193-9b38-7df4aaf9b229
  ID-5: /home/<filter>/HDD-2TB raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
    used: 1.44 TiB (80.5%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: 2TB-EXT4
    uuid: b9d4d0f9-d1ce-425d-8fe4-e2f830005289
  ID-6: /swap raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 123.45 GiB (26.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
    label: N/A uuid: 84e0bfca-0d47-4324-b85a-614ea38dc5f9
  ID-7: /var/cache raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 123.45 GiB (26.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
    label: N/A uuid: 84e0bfca-0d47-4324-b85a-614ea38dc5f9
  ID-8: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 123.45 GiB (26.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
    label: N/A uuid: 84e0bfca-0d47-4324-b85a-614ea38dc5f9
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 512 MiB used: 12.1 MiB (2.4%) priority: -2
    file: /swap/swapfile
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8008
    class-ID: 0900
  Hub-3: 2-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8000
    class-ID: 0900
  Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 15 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-1:2 info: SINO WEALTH Gaming KB type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 258a:002a class-ID: 0300
  Device-2: 3-2:3 info: [Maxxter] USB GAMING MOUSE type: mouse,keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s)
    lanes: 1 mode: 1.0 power: 100mA chip-ID: 18f8:0fc0 class-ID: 0301
  Hub-6: 4-0:1 info: super-speed hub ports: 6 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 26.0 C mobo: N/A gpu: amdgpu temp: 36.0 C
    mem: 38.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 850
Info:
  Processes: 330 Power: uptime: 13m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.46 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: 1625 pm: pacman pkgs: 1581 libs: 465 tools: pamac pm: flatpak
    pkgs: 44 Compilers: clang: 18.1.8 gcc: 14.1.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.26 running-in: konsole inxi: 3.3.35
3

From the stable update post:

:warning: Linux 6.9 is EOL 18

Linux 6.9 is EOL 18
and will - at some point - be removed from the repo

Switch to the latest LTS kernel, which you already have installed. (Or install 6.10.X.)

1 Like
4

Installing a new kernel with mhwd-kernel in the terminal may provide more feedback. See the Manjaro wiki for usage details.

5

To install kernel version in this way the terminal forces me to update my system, is there I way to fix the kernel app? in that way I can keep current versions and avoid the issues related to system crashing.

6

That’s probably the reason why the GUI is not installing anything.

The packages always have to be up to date when you want to add another package. This also true for the application packages.

2 Likes
7

Why would you want a different (newer, more up to date) kernel
while apparently being reluctant to update the rest of the system?

… there is a way to circumvent this (there always is):

fetch the kernel with:
pacman -Sw ...
it will end up in the pacman cache:
/var/cache/pacman/pkg/...
install it using
pacman -U /var/cache/pacman/pkg/...

mkinitcpio -P
should generate … that
make it known to Grub by
update-grub
or
grub-mkconfig -o /boot/grub/grub.cfg

1 Like
8

because as I mention my system became unstable, crashing, so it’s not clear to me what is contributing more to the crashes, if it’s the kernel or if it’s all the others packages update.

9

Thank you, probably, it would be better to receive an error message warning to update the system rather then DONE. but make sense, i will wait the next release to check the update again.

10

you are using 6.9.10-1 per your inxi output
but manjaro settings manager shows you running 6.9.12-1
why not use the also installed LTS kernel? …

Or use the method I outlined above.

11

I have the impression that the kernel 6.9 provides me less crashes then the 6.6, why I would change it?

As i mention, my intention was to be able to install different kernels like the 6.10 and 6.11 to test them.

Since I migrate full time to linux, the live is harder to keep the system stable, and Manjato is currently the best distro option that offers rollback combined with different kernel options, and all out of the box with standard installation, so let me take advantage of those tools :slight_smile:

12

You may do whatever you want.

I have never had a problem with stability - not in the last 25+ years :wink:

for one: because it’s an impression
and you may be chasing an XY problem.

… other distros provide backup and roll back solutions as well
but they are less frequently needed - because they are not constantly changing - they are not “rolling”. :wink:

2 Likes
13

You are luckier then me. I have around 4 years using linux with some suffering. I already change hardware twice in this meantime but always facing issues. Learning how to live with them and rollback out of the box is mandatory for my case, thanks Manjaro.

Could you name them?

I only knows OpenSUSE Tumbleweed witch is rolling release distro and Nobara witch is “semi-rolling” release distro, but I had issues with both.

With opensuse, after fresh install, the secong boot time increase to more them 2 minutes. No explanation for that, so moved to Nobara, maybe I back to test it again with Plasma 6.

With Nobara, trying to rollback my system due to an issue with Lutrix my system failed boot and no support from Nobara community was able to revive my system. so I back to Manjaro witch is product with much higher maturity.

14

If you have problems with stability, you should stay away from distros that are constantly changing
like Arch
like Manjaro
like Suse Tumbleweed
…

But I have used Arch for many years - never had a problem.
To be very honest:
with Manjaro I frequently had them - make of that what you will

I started with Debian back in the days (before 2000) and I currently use Mint.
(the most up to date among the fixed release distos, I figured
all the frequent updating just didn’t add any value for me anymore, it just used up time and bandwidth)

15

Manjaro Stable is a very good compromise. I’m very interest also to used OpenSUSE Slowroll when the project is officially released anytime I hope soon. It will be very close to Manjaro Stable, holding some packages from Tumbleweed.

But instability is the linux nature for desktop, to many hardware and software complexity to be combined with money and resources constrains to test all combinations.

So rollback software that effectively works and small patient is enough to keep using linux. BTRFS + Timeshift / Snapper + GRUB is so forgiving.

16

I tend to disagree - from experience.
The compromise creates problems that the original does not have - and with which many “unsuspecting and inexperienced” users come to struggle.
Likely you included … :sunglasses:
may that day never come for you!

A strongly voiced opinion not based in fact, my friend. :wink:

Good luck with using BTRFS without actually knowing how it works!
Seriously! :+1:

2 Likes
17

That’s a long winded way of doing this:

pacman -S ...
18

or this … :sunglasses: of course
may not work as intended when the system isn’t up to date (was what I thought …)
And it wasn’t my intention to provide an easy to follow cheat sheet :smiley:

1 Like
19

Indeed, if the package has been updated since the local database was last updated, then it’ll need an update. Same goes for the long winded approach though.

2 Likes
20

Taking car as an example, Imagine if people should learn how Hybrid engines works in order to by and drive a car. We need to rely o good engineers from the manufacturers and as final users take advantage of technology not needing to learn everything. Besides so many volunteers, with Linux, isn’t different. Probably more then 300 people works only for the kernel, so…

I don’t have afraid or concerns to use the technologies Manjaro or other distro incorporate without knowing them deeply. I just use rollback and keep my personal back-up up to date :slight_smile:

Thank you for the small talk and suggestions

21

That is all well and good.

But analogies are just that - and they may or may not apply and have their limits.

You’ll hopefully never experience the difference.

BTRFS can be very tricky - especially to unsuspecting persons unaware of the technology behind it.

All the best!
Be well!

1 Like