I tried this (`rpi-update next`) again, and again got blocked by initramfs-tools failing, due to a missing /boot/config-6.12.14-v8+ file.
After `rpi-update next`, the initramfs.image is still the previous kernel's initramfs.
There's a chicken-and-egg situation here:The workaround of copying the old config seems to work, but is that really the proper solution?
Even after that, I run into a different issue:It seems like you're missing out on a whole category of test systems by not having `rpi-update next` install the config and the vmlinuz file.
I honestly mostly just wanted to check if the `powerz` sensors driver has been enabled. I guess I should request it on the bug tracker instead of here?
After `rpi-update next`, the initramfs.image is still the previous kernel's initramfs.
There's a chicken-and-egg situation here:
- I can't create an initramfs until there's a config-$(uname -r) file
- I can't get the config until I boot the kernel
- I can't boot until I build an initramfs
- I can't build an initramfs until I get the config
Code:
root@pi5:~# update-initramfs -u -k 6.12.14-v8+update-initramfs: Generating /boot/initrd.img-6.12.14-v8+grep: /boot/config-6.12.14-v8+: No such file or directoryW: lz4 compression (CONFIG_RD_LZ4) not supported by kernel, using gzipgrep: /boot/config-6.12.14-v8+: No such file or directoryE: gzip compression (CONFIG_RD_GZIP) not supported by kernelupdate-initramfs: failed for /boot/initrd.img-6.12.14-v8+ with 1.Even after that, I run into a different issue:
Code:
root@pi5:~# update-initramfs -u -k 6.12.14-v8+update-initramfs: Generating /boot/initrd.img-6.12.14-v8+ERROR: Unsupported initramfs version (6.12.14-v8+)I honestly mostly just wanted to check if the `powerz` sensors driver has been enabled. I guess I should request it on the bug tracker instead of here?
Statistics: Posted by UnicodeFiend — Wed Feb 19, 2025 3:40 am