RPi 5 update produces a config.txt-pacnew file problem

[pudge]

The latest update includes an update on the linux-rpi-16k kernel which produces a config.txt-pacnew file
The config.txt-pacnew file does not contain the following line

initramfs initramfs-linux.img followkernel

So if the user overwrites config.txt with config.txt-pacnew file, RPi will no longer boot.
It won't even boot far enough to get a TTY Console window. Just a kernel panic then lock up.

Can someone look into this?

Pudge

[graysky]

Thanks for reporting. I thought the auto_initramfs=1 would take care of that. I just want to confirm that that line is not working, ie you have hit a boot error not just speculating that it won't work.

[pudge]

@graysky

Thanks for the quick response,

I haven't checked yet if RPi 4b is affected or not. Going to do that right now.

EDIT:
A quick test tells me this doesn't affect RPi 4b

Pudge

[graysky]

linux-rpi-16k is only for RPi5 not 4. Did your 5 not boot with the pkg provided file?

[pudge]

Here is what happened.

I support RPi 5 images (and others) that are available here

make_clickable_callback(MAGIC_URL_FULL, '
', 'https://github.com/endeavouros-arm/images/releases', '', ' class="postlink"')

After the RPi 5 image is burned to a micro SD or USB 3 SSD at first boot
it auto launches a script that queries for the pertinent info including a choice
of DE. During this process of installing the DE I noticed that linux-rpi-16k
had an update and a warning about /boot/config.txt.pacnew file.

I used pacdiff/meld to compare config.txt.pacnew to config.txt
I decided to overwrite config.txt with config.txt.pacnew
After that it would no longer boot.

Investigation showed the problem to be that config.txt.pacnew did not have
initramfs initramfs-linux.img followkernel
adding this to the overwritten config.txt fixed the problem.

Pudge

[codicodi]

I think I encountered the same problem, and my RPI5 system actually failed to boot after an upgrade. I didn't get a pacnew file however, as my config.txt is unmodified.

Docs for config.txt seem to explain what happened: auto_initramfs option places strict requirements on how initramfs file is named:

[url]https://www.raspberrypi.com/documentation/computers/config_txt.html#auto_initramfs[/url]
[code]If auto_initramfs is set to 1, the firmware looks for an initramfs file to match the kernel. The file must be in the same location as the kernel image, and the name is derived from the name of the kernel by replacing the kernel prefix with initramfs, and removing any extension such as .img, e.g. kernel8.img requires initramfs8. You can make use of auto_initramfs with custom kernel names provided the names begin with kernel and initramfs respectively and everything else matches (except for the absence of the file extension on the initramfs). Otherwise, an explicit initramfs statement is required.[/code]

In our case the kernel file is kernel8.img so it requires initramfs8, while we have initramfs-linux.img. So we need either to change back to explicit initramfs statement or change default_image in the mkinitcpio preset file.

[graysky]

Ah, thanks for pointing that out. Fixed.

[solskogen]

I think you forgot to commit that fix

[graysky]

thanksmake_clickable_callback(MAGIC_URL_FULL, '
', 'https://github.com/archlinuxarm/PKGBUILDs/commit/e561eae38e376e0c8a2206c502d327412d776056', '', ' class="postlink"')make_clickable_callback(MAGIC_URL_FULL, '
', 'https://github.com/archlinuxarm/PKGBUILDs/commit/1b75a50316b985b4adcc2f324b42ff3e0cc4a27f', '', ' class="postlink"')