linux-rpi 6.1.27-1 (Rpi 2 v7) not building initramfs

[pezz]

Just updated my Pi2 and mkinitcpio is not building the initramfs image:

$this->bbcode_second_pass_code('', '
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating linux-rpi initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-rpi.preset: 'default'
==> WARNING: No kernel version specified. Skipping image 'default'')
I also noticed /etc/mkinitcpio.d/linux-rpi.preset is different to what's in Github, this line:

$this->bbcode_second_pass_code('', 'ALL_kver=""')
The repo has:

$this->bbcode_second_pass_code('', 'ALL_kver="%KERNVER%"')
But changing that line doesn't make it build. Specifying the new kernel version doesn't work either:

$this->bbcode_second_pass_code('', '# mkinitcpio -P -k 6.1.27-1-rpi-ARCH
==> Building image from preset: /etc/mkinitcpio.d/linux-rpi.preset: 'default'
==> WARNING: No kernel version specified. Skipping image 'default'')
Cheers.

[solskogen]

I've edited /etc/mkinitcpio.d/linux-rpi.preset so that it reads

$this->bbcode_second_pass_code('', 'ALL_kver="6.1.27-1-rpi-ARCH"
')

Now mkinitpcio -P works.

[pezz]

Nice, that works great.

I suppose "%KERNVER%" is meant to be populated during the package build but something happened this time?

I dunno, hopefully don't have to do it with every upgrade.

Cheers for that.

[solskogen]

This should not happen, so @graysky will probably fix it shortly

[graysky]

Thanks for reporting, fixed in 6.1.27-2

[pezz]

Thanks heaps graysky, just waiting for this to hit the repos.

[solskogen]

As it haven't hit the mirrors I guess (and hope) that a major rebuild is happening with newest gcc/binutils and glibc toolchain

[tomty89]

Hi graysky. I think it's still wrong? It should be $this->bbcode_second_pass_code('', '$(<version)') instead of $this->bbcode_second_pass_code('', '$(version)')?

[tiagoboldt]

I use RAID1 with mdadm and after rebooting, the md module was no longer available, meaning I am now unable to boot. I've managed to boot a live system and chroot into my arch installation and rebuild the kernel with the instructions above, ensuring that the mdadm configuration was on the mkinitcpio HOOKS, but to no avail.

Could there be some relation to this issue? I'll try to update the kernel on the chroot environment to see if that helps soon, but working out of the live environment is slow as I do not have easy access to this server.

[graysky]

Yes, it should. Fixed in 6.1.27-3, thanks for pointing that out.