Manjaro sway install error: crc32c_intel not supported anymore

embediver · 2 June 2025 14:02

I just ran into a error installing Manjaro sway regarding mkinitcpio.

I had to use the latest unstable image for wayland to work on the StarBook Mk VII. (manjaro-sway-25.0.0-unstable-250601-linux614.iso)

Unfortunately Calamares fails to install, here is the relevant log section:

2025-06-02 - 14:27:03 [1]:     ERROR: Installation failed: "External command finished with errors." 
2025-06-02 - 14:27:03 [6]:     .. - message: "External command finished with errors." 
2025-06-02 - 14:27:03 [6]:     .. - details: Command <i>mkinitcpio</i> finished with exit code 1.
Output:
==> Building image from preset: /etc/mkinitcpio.d/linux614.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.14-x86_64 -g /boot/initramfs-6.14-x86_64.img
==> Starting build: '6.14.9-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [kms]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
  -> Running build hook: [filesystems]
==> ERROR: module not found: 'crc32c_intel'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.14-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Running post hooks
  -> Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!
==> Post processing done
==> Building image from preset: /etc/mkinitcpio.d/linux614.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.14-x86_64 -g /boot/initramfs-6.14-x86_64-fallback.img -S autodetect
==> Starting build: '6.14.9-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
  -> Running build hook: [filesystems]
==> ERROR: module not found: 'crc32c_intel'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.14-x86_64-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Running post hooks
  -> Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!
==> Post processing done
2025-06-02 - 14:27:03 [6]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)

Someone on AW had the same problem: topic id=304822 Link to thread

The suggested fix is to remove crc32c_intel from the mkinitcpio.conf MODULES but I don’t know how I have to conduct this for it to work with the Calamares installation process.
It also seems that the crc32_intel module is included through the filesystems hook.
I tried to replace that in /etc/mkinitcpio.conf before running Calamares but that seems to have no effect.

Mod edit: Added the link I believe you refer to. If this is not the correct one, please let us know either via reply or PM (or edit your post to remove it).
_{Also fixed a couple of typos.}

Nachlese · 2 June 2025 15:06

Do you know that you need it?

The reason for the error message is likely that you have it explicitly mentioned in your:
/etc/mkinitcpio.conf

grep ^MODULES /etc/mkinitcpio.conf

The function may not be a module anymore, but built in.
But I don’t know that - it’s just speculation as of now.
I didn’t look at the linux614 (yet) - it is present in linux612 and lower.

megavolt · 2 June 2025 15:46

The module crc32c_intel is removed on newer kernels. crc32c is used now as builtin module, since crc32c_intel is now integrated. Therefore: remove the entry.

Nachlese · 2 June 2025 16:18

Adding to what @megavolt said:

as I understand, this is during installation - and the Calamares installer does “choke” on it, doesn’t complete

Before starting the installation, edit the file (even though you are on a live system), remove the entry, save.
It will reflect the change for the duration of this one boot.

embediver · 2 June 2025 17:01

Yeah, I thought that too and tried that.
The crc32c_intel wasn’t included in the config in the first place but the filesystem hook was so I removed that (and included btrfs by hand instead).
But I still see the Running build hook: [filesystem] log line with the error afterwards.

I suspected that Calamares mounted the filesystem separately for the installation and thus won’t see the change.
Any Idea?

Nachlese · 2 June 2025 17:08

Ok, so my ignorance of how the installer works has been demonstrated.
No more ideas from me.

kysh · 2 June 2025 18:59

I believe you were still somehow right though missing a part but OP misread your directions which were to remove the crc32c_intel (the part you missed was to replace crc32c_intel with crc32c if its present or to add it if its not).

@embediver you can put it on a line on its own at the top of the file

A snippet of the beginning from mine

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(usbhid xhci_hcd)
MODULES=(crc32c)

In any case DO NOT REMOVE the filesystem hook. I would advise to leave the HOOKS= line alone at installation unless you have a very specific reason like encryption in mind to do so.

You can see more on this issue here

Nachlese · 2 June 2025 19:36

From what I remember from installing to real hardware, MODULES was always empty, since there was no need to explicitly load any modules in early boot (initrd).

Of course, if there is a module named/mentioned which does not actually exist, that would cause an error.

As I like to see things for myself, I’m downloading that ISO right now and will test install it in a VM …
I tried Sway before, but it wouldn’t really work in my VM.
I “blamed” it on Wayland back then - but I don’t really know.

It kinda works, with graphics glitches.
There is only modules pertaining to this being run in a VM in MODULES in /etc/mkinitcpio.conf.
no crc32c_intel

But the installation fails at the same point with the same error as for @embediver

Even basic investigating proves difficult because I’m totally unfamiliar with the sway environment and because the terminal output is laggy and glitchy in my VM.

Perhaps in TTY, but:
I don’t know where the want for crc32c_intel during installation may come from.

linux-aarhus · 3 June 2025 04:03

I think something is not up-to-date on your system?

ensure your iso-profiles repo is up-to-date
make sure you manjaro-tools-git is up-to-date

I vaguely recall the crc module being added to mkinitcpio by the installer when you select btrfs as the file system.

A calamares module is responsible for this action - a corresponding merge request has been created.