Should I for security reasons? My sys is working fine, so no hardware issues, my blue tooth comes on at boot up, but we are far of the road no none will get on, not sure when it started, just noticed 1 day. Also, not wanting to brake anything.
That depends on what you are on. Non-LTS kernel are not supported for a very long time, so you will have to upgrade relatively regularly.
If you are on a long-term supported (LTS) kernel, you will get bug and security fixes for several months or even years and Manjaro provides them for a pretty long time. No new features though. Therefore, you will be fine without upgrading for a while. You have to apply updates with Pamac or pacman of course.
Just be sure that you are a on supported kernel and you will get the security updates.
The most recent LTS kernel at the moment is Linux 5.15 and according to kernel.org, upstream support will end in October 2023. It is pretty rare that Manjaro drops kernels before that.
I am on a older kernel, it is below 4.19 I think. The app doesn’t open kernel anymore, a min ago it was opening fine. Hmmm, stoped responding I guess.
What’s the output of uname -r or mhwd-kernel -li?
5.13.13-1-MANJARO
5.13 has been EOL for some time. If you don’t want/need to track the newest stable releases you should install an LTS kernel, 5.10 or 5.15, or both.
1 Like
Ok, how do I bring the app up with the kernels so I can download the newer one?
The GUI way is through Manjaro Settings Manager or you can use:
sudo mhwd-kernel -i <kernel_version>
So to install 5.15 it would be sudo mhwd-kernel -i linux515
You can list kernels available for installation with mhwd-kernel -l
Hmmm, hope everything is still ok.
[edward78@nicholas ~]$ sudo mhwd-kernel -i linux515
[sudo] password for edward78:
:: Synchronizing package databases…
core 160.3 KiB 321 KiB/s 00:01 [######################] 100%
extra 1829.8 KiB 1694 KiB/s 00:01 [######################] 100%
community 7.5 MiB 4.71 MiB/s 00:02 [######################] 100%
multilib 166.4 KiB 2.23 MiB/s 00:00 [######################] 100%
resolving dependencies…
looking for conflicting packages…
Packages (1) linux515-5.15.85-1
Total Download Size: 100.23 MiB
Total Installed Size: 104.73 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages…
linux515-5.15.85… 100.2 MiB 9.88 MiB/s 00:10 [######################] 100%
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
:: Processing package changes…
(1/1) installing linux515 [######################] 100%
Optional dependencies for linux515
wireless-regdb: to set the correct wireless channels of your country
[installed]
:: Running post-transaction hooks…
(1/4) Arming ConditionNeedsUpdate…
(2/4) Updating module dependencies…
(3/4) Updating linux initcpios…
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: ‘default’
→ -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.85-1-MANJARO
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [autodetect]
→ Running build hook: [modconf]
→ Running build hook: [block]
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [resume]
→ Running build hook: [filesystems]
→ Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: ‘fallback’
→ -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.85-1-MANJARO
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [modconf]
→ Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [resume]
→ Running build hook: [filesystems]
→ Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
(4/4) Updating Grub-Bootmenu
Generating grub configuration file …
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.13-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.13-x86_64.img
Found initrd fallback image: /boot/initramfs-5.13-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings …
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[edward78@nicholas ~]$
If you cannot find it in menu use this command:
manjaro-settings-manager -m msm_kernel
Thanks, upgraded through CLI, hope nothing is broken on next boot.
Cool, just made a launcher to it.