My switch to the 5.10 kernel with update 2020-12-30

Feedback
, ,
2

  1. Ok tried to reboot and could not boot the new kernel, because the systemd-boot-manager(0.9-1) package still created a wrong config:
    (fallback version is similar, just different ramdisk)

    • bootctl list
         title: Manjaro Linux 5.10 (manjarolinux5.10.conf)
      id: manjarolinux5.10.conf
  source: /efi/loader/entries/manjarolinux5.10.conf
   linux: /10eef4bb59134395bc85dfb713b67a70/vmlinuz-5.10-x86_64
  initrd: /10eef4bb59134395bc85dfb713b67a70/amd-ucode.img
          /10eef4bb59134395bc85dfb713b67a70/intel-ucode.img
          /initramfs-5.10-x86_64.img (No such file or directory)
 options: root=UUID=da54bb75-506a-4659-996c-f9bfcf94b2b7 rw cryptdevice=UUID=2d2d4f8f-d805-48f1-8ebb-dcf6ff0f77bd:luks2 apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1 add_efi_memmap intel_iommu=on modeset=1 nvidia-drm.modeset=1
    • manjarolinux5.10.conf:
      title	Manjaro Linux 5.10
linux	/10eef4bb59134395bc85dfb713b67a70/vmlinuz-5.10-x86_64
initrd	/10eef4bb59134395bc85dfb713b67a70/amd-ucode.img
initrd	/10eef4bb59134395bc85dfb713b67a70/intel-ucode.img
initrd	/initramfs-5.10-x86_64.img
options	root=UUID=da54bb75-506a-4659-996c-f9bfcf94b2b7 rw cryptdevice=UUID=2d2d4f8f-d805-48f1-8ebb-dcf6ff0f77bd:luks2 apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1 add_efi_memmap intel_iommu=on modeset=1 nvidia-drm.modeset=1
    1. :warning: As can be seen it still generates an invalid entry for the kernel’s ramdisk, because it is located in same directory as the kernel instead of the root of the filesystem…
      A bug report to the package maintainer in past was closed without fixing this, and thus still present…
      I will try to report this to him in same issue with a link to this post.
    2. :warning: It still generates a wrong root= option for my full-disk LUKS root file-system setup.
      Reported at: Wrong configs generated when using LUKS2 (#8) · Issues · dalto / systemd-boot Manager for Manjaro · GitLab
    3. It still generates a cryptdevice= option which is not used, will need to check if it causes problems, because the functionality is handled by the /etc/crypttab inside the ramdisk.
      See :woman_teacher:[HowTo] Boot without a password for encrypted root partition

  2. So I will need to create a config manually again:
    (fallback version is similar, just different ramdisk)

    • sed ‘s|5.9|5.10|g’ manjaro5.9.conf > manjaro5.10.conf
      manjaro5.10.conf:
      #/loader/entries/manjaro5.10.conf
title		Manjaro Linux
version		5.10
machine-id	10eef4bb59134395bc85dfb713b67a70
architecture	x64
linux		/10eef4bb59134395bc85dfb713b67a70/vmlinuz-5.10-x86_64
initrd		/10eef4bb59134395bc85dfb713b67a70/intel-ucode.img
initrd		/10eef4bb59134395bc85dfb713b67a70/initramfs-5.10-x86_64.img
#options	resume=/dev/mapper/luksSWAP root=UUID=dfd082e3-5928-4dd9-95f5-50bc074a5faa bootsplash.bootfile=bootsplash-themes/xxxxx/bootsplash
options		root=/dev/mapper/Linux-ManjaroArchitect ro apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1 add_efi_memmap intel_iommu=on modeset=1 nvidia-drm.modeset=1 bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash
    • sed ‘s|5.9|5.10|g’ manjaro5.9-fallback.conf > manjaro5.10-fallback.conf
      manjaro5.10-fallback.conf:
      #/loader/entries/manjaro5.10-fallback.conf
title		Manjaro Linux
version		5.10-fallback
machine-id	10eef4bb59134395bc85dfb713b67a70
architecture	x64
linux		/10eef4bb59134395bc85dfb713b67a70/vmlinuz-5.10-x86_64
initrd		/10eef4bb59134395bc85dfb713b67a70/intel-ucode.img
initrd		/10eef4bb59134395bc85dfb713b67a70/initramfs-5.10-x86_64-fallback.img
options		root=/dev/mapper/Linux-ManjaroArchitect ro apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1 add_efi_memmap intel_iommu=on modeset=1 nvidia-drm.modeset=1 bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash

Time to try to boot in new kernel again…

1 Like