mkinitcpio-37-1 upgrade error

[mcloaked]

By the way I had a page of php errors when I submit a post to this thread - apologies for the repeated posts earlier in this thread - I was trying to work around the php errors and didn't realise each time I tried to edit the post that it had already -posted the reply.

[mcloaked]

I also note that the linked 'issue' from gitlab was closed with a commit from a few weeks ago, so presume the changes offered as a solution in the source were already in the 37-1 release - so this will need a new and different commit to fix the issue for archlinuxarm.

[mtnflyr]

I tried the steps offered by user phperrer on a RPi4 running armv7.

After upgrading mkinitcpio to version 37-1 edited the file /usr/lib/initcpio/install/kms by commenting out the line

[code] add_checked_modules_from_symbol 'drm_privacy_screen_register' '=drivers/platform' [/code]

The following command is then successful.

[code] mkinitcpio -p linux-rpi [/code]

I don't understand what it means or what else could be affected, but thought posting my experience might help in finding a solution.

[mcloaked]

That same line is in the file /usr/lib/initcpio/install/kms on the main arch linux repo for mkinitcpio, and that does not seem to be a problem on those systems, but just on archlinuxarm. So I wonder what the difference is that causes archlinuxarm to break building the initrd with mkinitcpio 37-1 ?

I also just tested with 37.1-1 and on my rock64 system it still gives the error lines:

==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly

So I have downgraded back to 36.1 until this issue is resolved fully - though I didn't try to remove the line in the file suggested as in the first line of this post. I also don't know if removing that line may cause any issue in the future, or whether that change on the rock64 would resolve it, as it did on the rpi.

[mcloaked]

I guess the upstream changes discussed in
make_clickable_callback(MAGIC_URL_FULL, '
', 'https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/merge_requests/269', '', ' class="postlink"')

and
make_clickable_callback(MAGIC_URL_FULL, '
', 'https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues/218', '', ' class="postlink"')

maybe not been fully debugged? Has anyone worked through whether the commits in the current version need to be amended?

[mcloaked]

Also worth keeping an eye on discussion atmake_clickable_callback(MAGIC_URL_FULL, ' ', 'https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues/220', '', ' class="postlink"')

[mtnflyr]

I can confirm that on the RPi4 ARMv7 the 37-1-1 update did not change anything for me.

Commenting out the line in [code]/usr/lib/initcpio/install/kms[/code] still results in [code]mkinitcpio -p linux-rpi[/code] completing successfully just as before.

[phperrer]

Looking at it some more and reading the actual code, it unpacks all kernel modules in "/lib/modules/*/kernel/drivers/platform" and literally greps the resulting binary dump for the "drm_privacy_screen_register" string.

On my amd64 machine it finds two entries:
/lib/modules/6.6.4-arch1-1/kernel/drivers/platform/chrome/chromeos_privacy_screen.ko.zst
/lib/modules/6.6.4-arch1-1/kernel/drivers/platform/x86/thinkpad_acpi.ko.zst

On ARM it doesn't find any. I don't quite understand Linux's build system well enough to figure out why at least the chrome one isn't being built because it's enabled:

$ zgrep CHROMEOS_PRIVACY_SCREEN /proc/config.gz
CONFIG_CHROMEOS_PRIVACY_SCREEN=y

Then again even on amd64 the two modules are not even later included in the final initramfs image so why is it even looking for them?

$ lsinitcpio /boot/initramfs-linux.img | grep -E 'chromeos_privacy_screen|thinkpad_acpi'
<nope>

Clearly somebody much smarter than me has to have a look at this because apparently I know nothing about this Linux thing.

[mcloaked]

I do hope that this can be resolved before long - this bug report from the main arch linux bugtracker is directly relevant:
make_clickable_callback(MAGIC_URL_FULL, '
', 'https://bugs.archlinux.org/task/72964', '', ' class="postlink"')

[mcloaked]

With systemd packages now showing up as updates this would normally rebuild the initrd with pacman -Syu - I guess --ignore mkinitcpio will allow the rest to update without issues.