You are not logged in.
Pages: 1
Hi,
I would like to install the linux-lts kernel next to the linux kernel.
I'm not sure of myself and before doing something stupid I prefer to ask for confirmation. I am in UEFI with systemd-boot manager.
I recovered using pacman the lts kernel and the 3 lts images (vmlinuz, initramfs and initramfs falback) are in /boot/.
Do I just have to create in the / boot/loader/entries/ directory a second configuration file cloned to the existing one but with the lts references?
armand@Desktop-living boot]$ ls /boot/
EFI amd-ucode.img b89d5bdf20d14d6db1eb02f5e1a1a291 initramfs-linux-fallback.img initramfs-linux.img loader vmlinuz-linux
[armand@Desktop-living ~]$ ls /boot/EFI/
BOOT Linux systemd
[armand@Desktop-living ~]$ ls /boot/EFI/BOOT/
BOOTX64.EFI
[armand@Desktop-living ~]$ ls -a /boot/EFI/Linux
. ..
[armand@Desktop-living ~]$ ls /boot/EFI/systemd/
systemd-bootx64.efi
[armand@Desktop-living ~]$
[armand@Desktop-living ~]$ ls -a /boot/b89d5bdf20d14d6db1eb02f5e1a1a291
. ..
[armand@Desktop-living ~]$ ls -a /boot/loader/
. .. entries loader.conf random-seed
[armand@Desktop-living ~]$ nano /boot/loader/loader.conf
GNU nano 5.8 /boot/loader/loader.confGNU nano
timeout 10
#console-mode keep
default 2021-08-05_22-36-41
[armand@Desktop-living ~]$ ls -a /boot/loader/entries/
. .. 2021-08-05_22-36-41.conf
[armand@Desktop-living ~]$ nano /boot/loader/entries/2021-08-05_22-36-41.conf
GNU nano 5.8 /boot/loader//entries/2021-08-05_22-36-41.conf
# Created by: archinstall
# Created on: 2021-08-05_22-36-41
title Arch Linux
linux /vmlinuz-linux
initrd /amd-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=976b9a9a-c31f-445a-beea-625abd22e242 rw intel_pstate=no_hwp
[armand@Desktop-living ~]$ sudo pacman -S linux-lts
resolving dependencies...
looking for conflicting packages...
Packages (1) linux-lts-5.10.56-1
Total Download Size: 74.50 MiB
Total Installed Size: 79.29 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
linux-lts-5.10.56-1-x86_64 MiB 3.77 MiB/s 00:20 [##############################################################] 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 linux-lts [##############################################################] 100%
Optional dependencies for linux-lts
crda: to set the correct wireless channels of your country
linux-firmware: firmware images needed for some devices [installed]
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
-> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 5.10.56-1-lts
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keymap]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
-> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 5.10.56-1-lts
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keymap]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful
[armand@Desktop-living ~]$ ls /boot/
EFI amd-ucode.img b89d5bdf20d14d6db1eb02f5e1a1a291 initramfs-linux-fallback.img initramfs-linux-lts-fallback.img initramfs-linux-lts.img initramfs-linux.img loader vmlinuz-linux vmlinuz-linux-lts
[armand@Desktop-living ~]$
Last edited by Breizh29 (2021-08-18 02:53:23)
Offline
Do I just have to create in the / boot/loader/entries/ directory a second configuration file cloned to the existing one but with the lts references?
Pretty much, yes.
Offline
Breizh29 wrote:Do I just have to create in the / boot/loader/entries/ directory a second configuration file cloned to the existing one but with the lts references?
Pretty much, yes.
It worries me! something is missing?
Offline
V1del wrote:Breizh29 wrote:Do I just have to create in the / boot/loader/entries/ directory a second configuration file cloned to the existing one but with the lts references?
Pretty much, yes.
It worries me! something is missing?
You're looking for a problem that doesn't exist. You asked how to add the LTS kernel to your bootloader's options, described the correct way, which was confirmed. What else do you want? An insurance contract? You won't get that here.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Pages: 1