[Unstable Update] January 2024 Edition

anon51566685 · 15 January 2024 18:20

Why would anything be needed in 6.7 for code that is new in 6.8?

Yochanan · 15 January 2024 18:32

I’ve just applied that MR with mkinitcpio 37.1-3.

EDIT: I didn’t realize 37.2 was going to be released so fast. 37.2-1 is now available.

ydar · 15 January 2024 21:08

after updating mkinitcpio, I now see these errors (for all installed kernels):

==> ERROR: file not found: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-modeset.ko.xz'
==> ERROR: file not found: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia.ko.xz'
==> ERROR: file not found: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-drm.ko.xz'
==> ERROR: file not found: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-uvm.ko.xz'
xz: /tmp/mkinitcpio.ByP9Tk/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-modeset.ko.xz: No such file or directory
xz: /tmp/mkinitcpio.ByP9Tk/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia.ko.xz: No such file or directory
xz: /tmp/mkinitcpio.ByP9Tk/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-drm.ko.xz: No such file or directory
xz: /tmp/mkinitcpio.ByP9Tk/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-uvm.ko.xz: No such file or directory
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.7-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.

Are these safe to ignore, or is there something I need to do?

Yochanan · 15 January 2024 21:23

That’s not normal, what did you do?

ydar · 15 January 2024 21:36

Could it be related to disabling the fallback images?

Yochanan · 15 January 2024 21:37

Maybe? Only one way to find out.

By the way, was that output with 37.1-3, 37.2-1 or both?

ydar · 15 January 2024 22:04

For 37.2-1.

I still have the fallback image disabled. I decided to see if there were more updates, there were, but this time no errors but warnings.

warning: could not get file information for usr/lib/modules/extramodules-5.15-MANJARO/nvidia-drm.ko.xz
warning: could not get file information for usr/lib/modules/extramodules-5.15-MANJARO/nvidia-modeset.ko.xz
warning: could not get file information for usr/lib/modules/extramodules-5.15-MANJARO/nvidia-uvm.ko.xz
warning: could not get file information for usr/lib/modules/extramodules-5.15-MANJARO/nvidia.ko.xz
warning: could not get file information for usr/lib/modules/extramodules-6.6-MANJARO/nvidia-drm.ko.xz
warning: could not get file information for usr/lib/modules/extramodules-6.6-MANJARO/nvidia-modeset.ko.xz
warning: could not get file information for usr/lib/modules/extramodules-6.6-MANJARO/nvidia-uvm.ko.xz
warning: could not get file information for usr/lib/modules/extramodules-6.6-MANJARO/nvidia.ko.xz

I decided to reinstall nvidia driver, now those warnings are gone except this one: WARNING: errors were encountered during the build. The image may not be complete. for each kernel.

==> Building image from preset: /etc/mkinitcpio.d/linux67.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.7-x86_64 -g /boot/initramfs-6.7-x86_64.img --microcode /boot/amd-ucode.img
==> Starting build: '6.7.0-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
cp: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia.ko.xz' and '/tmp/mkinitcpio.Ro0QLa/root/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia.ko.xz' are the same file
cp: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-drm.ko' and '/tmp/mkinitcpio.Ro0QLa/root/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-drm.ko' are the same file
cp: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-uvm.ko.xz' and '/tmp/mkinitcpio.Ro0QLa/root/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-uvm.ko.xz' are the same file
xz: /tmp/mkinitcpio.Ro0QLa/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-modeset.ko: File exists
xz: /tmp/mkinitcpio.Ro0QLa/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia.ko: File exists
xz: /tmp/mkinitcpio.Ro0QLa/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-uvm.ko: File exists
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.7-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.

Edit:

Sorry I forgot, I had enabled early kms for nvidia (was experimenting but I don’t need it), I will disable and see if it makes a difference.

Now I only get the WARNING: errors were encountered during the build. The image may not be complete. for kernel 5.15 but not 6.6 and 6.7 (which reminds me I need to uninstall 6.6).

Summary

==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.147-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img --microcode /boot/amd-ucode.img
==> Starting build: '6.6.12-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux67.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.7-x86_64 -g /boot/initramfs-6.7-x86_64.img --microcode /boot/amd-ucode.img
==> Starting build: '6.7.0-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.7-x86_64.img'
==> Image generation successful

I do not use dkms.

Furthermore, rebooting into 5.15 fails [FAILED] Failed to start Load Kernel Modules., but as expected 6.6 and 6.7 both work

Yochanan · 15 January 2024 22:09

Odd. By the way, I use DKMS modules so I can update and test before I package the precompiled modules. Does the same happen with nvidia-dkms?

cscs · 15 January 2024 22:26

Works fine here with or without the fallbacks enabled.

(note: kernels 6.6 and 6.7, but 6.7 is custom and not a manjaro kernel)

Delor3an91 · 15 January 2024 22:59

Hi Everybody,

Same things appear with last linux67, nvidia, mkinitcpio updates on testing branch and make my GNOME desktop unreachable. Only swithching with alt+F2 give me useful CLI. I tried to boot linux66 with no success either so I presume it’s a mkinitcpio problem.

EDIT : nvidia modules with ko.xz extensions are missing, there is only .ko files which may be the cause for this.
After switching to unstable branch kernel linux66 is able to reach GNOME desktop but linux67 still don’t.

Wish You well

philm · 15 January 2024 23:29

Hmm, maybe due to the nature of synlinks this happens now. ARCH installs extramodules differently and only with precompiled ones.

Our nvidia package looks like this:

pacman -Fl linux67-nvidia
linux67-nvidia usr/
linux67-nvidia usr/lib/
linux67-nvidia usr/lib/modules/
linux67-nvidia usr/lib/modules/extramodules-6.7-MANJARO/
linux67-nvidia usr/lib/modules/extramodules-6.7-MANJARO/nvidia-drm.ko.xz
linux67-nvidia usr/lib/modules/extramodules-6.7-MANJARO/nvidia-modeset.ko.xz
linux67-nvidia usr/lib/modules/extramodules-6.7-MANJARO/nvidia-peermem.ko.xz
linux67-nvidia usr/lib/modules/extramodules-6.7-MANJARO/nvidia-uvm.ko.xz
linux67-nvidia usr/lib/modules/extramodules-6.7-MANJARO/nvidia.ko.xz
linux67-nvidia usr/share/
linux67-nvidia usr/share/licenses/
linux67-nvidia usr/share/licenses/linux67-nvidia/
linux67-nvidia usr/share/licenses/linux67-nvidia/LICENSE

Arch has it like that:

    usr/
    usr/lib/
    usr/lib/modules/
    usr/lib/modules/6.7.0-arch3-1/
    usr/lib/modules/6.7.0-arch3-1/extramodules/
    usr/lib/modules/6.7.0-arch3-1/extramodules/nvidia-drm.ko.xz
    usr/lib/modules/6.7.0-arch3-1/extramodules/nvidia-modeset.ko.xz
    usr/lib/modules/6.7.0-arch3-1/extramodules/nvidia-peermem.ko.xz
    usr/lib/modules/6.7.0-arch3-1/extramodules/nvidia-uvm.ko.xz
    usr/lib/modules/6.7.0-arch3-1/extramodules/nvidia.ko.xz
    usr/share/
    usr/share/licenses/
    usr/share/licenses/nvidia/
    usr/share/licenses/nvidia/LICENSE

We might have a general symlink to the modules, which then might create the issue as symlinks are now not copied as files. Have to test more.

ls -lasih /usr/lib/modules/6.7.0-2-MANJARO
5253587    0 lrwxrwxrwx  1 root root   27 15. Jan 07:36 extramodules -> ../extramodules-6.7-MANJARO

so it might not include all the extramodules on how we provide it.

Delor3an91 · 16 January 2024 01:00

Hi @philm ,

I looked in those extramodules folders when runing
mkinitcpio -P and it extract xz archives into ko files. Maybe is it related with the fact that I used the modules decompress=(yes) into my mkinitcpio.conf but before that last three updates I had no error of that kind.

Wish You well

Yochanan · 16 January 2024 02:20

I’ve pulled mkinitcpio 37.2-1 and reverted back to 37.1 for now. Everyone here I’m sure knows the routine.

cscs · 16 January 2024 02:33

Ignore and continue using 37.2-1 because no problems occurred?

(and -Syuu for the rest of yous)

Yochanan · 16 January 2024 02:38

Yes, that’s fine. @philm is probably going to add a patch for 37.2.

philm · 16 January 2024 03:00

cp: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia.ko.xz' and '/tmp/mkinitcpio.Ro0QLa/root/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia.ko.xz' are the same file
cp: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-drm.ko' and '/tmp/mkinitcpio.Ro0QLa/root/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-drm.ko' are the same file
cp: '/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-uvm.ko.xz' and '/tmp/mkinitcpio.Ro0QLa/root/lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-uvm.ko.xz' are the same file
xz: /tmp/mkinitcpio.Ro0QLa/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-modeset.ko: File exists
xz: /tmp/mkinitcpio.Ro0QLa/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia.ko: File exists
xz: /tmp/mkinitcpio.Ro0QLa/root//lib/modules/6.7.0-2-MANJARO/extramodules/nvidia-uvm.ko: File exists

This is not a regular path, but includes a symlink on our end as shown here:

ls -lasih /usr/lib/modules/6.7.0-2-MANJARO
5253587    0 lrwxrwxrwx  1 root root   27 15. Jan 07:36 extramodules -> ../extramodules-6.7-MANJARO

This patch creates a regression on our end for that folder. Arch has a regular folder structure. We simply didn’t adopt that yet. I’ll try to patch it. Else I’ve to rebuild all kernels and change how we do extramodules in general.

philm · 16 January 2024 03:26

@ydar and @Delor3an91 can you test mkinitcpio 37.2-1.1 and also provide me the output of sudo lsinitcpio /boot/initramfs-6.7-x86_64.img | grep extra with 37.1-4 and 37.2-1.1.

ydar · 16 January 2024 04:47

I ran: sudo lsinitcpio /boot/initramfs-6.7-x86_64.img | grep extra
There was no output for either version.

Did a bit of experimenting, re-installed 5.15

I still get the same error ==> WARNING: errors were encountered during the build. The image may not be complete. for 5.15.
I uninstalled 6.6 - even though there were no errors here.
Installed 6.1 - there are no errors,
6.7 - no errors

sudo mkinitcpio -p linux515

Summary

==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.147-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.

I just noticed I still had the kms hook. I removed it and now 5.15 builds successfully.

Summary

==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.147-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> 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

Interesting that the kms hook with nothing to do caused problems for the 5.15 kernel but not 6.1, 6.6, or 6.7.

philm · 16 January 2024 04:51

You will get the errors when you have nvidia modules enabled in /etc/mkinitcpio.conf. Also provide a full output of sudo mkinitcpio -p linux515. @ydar

medmedin · 16 January 2024 08:36

Me also, I need kernel 5.4 installed on one particular machine (intel CPU), but since November I started to get theses messages

WARNING: errors were encountered during the build. The image may not be complete.

error: command failed to execute correctly

It appears only with old 5.4 but not with latest ones.

( 6/10) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: '5.4.267-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.4-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: '5.4.267-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
  -> Running build hook: [filesystems]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.4-x86_64-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux67.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.7-x86_64 -g /boot/initramfs-6.7-x86_64.img --microcode /boot/intel-ucode.img
==> Starting build: '6.7.0-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.7-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux67.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.7-x86_64 -g /boot/initramfs-6.7-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.7.0-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.7-x86_64-fallback.img'
==> Image generation successful
error: command failed to execute correctly
( 7/10) Refreshing PackageKit...