there’s 2 kernels in 1 package kenel8 for the cm4 and kernel_2712 for the cm5. you need to also grab the newer firmware package and change out that too.
1 Like
you will also need to edit the config.txt for the cm5
Yep, already saw that, and will copy over the overlays and edit the config.txt.
Thanks, I’ll report back soon!
you will need the complete kernel package, i’ve have to edit the panel driver to work with the new timing coming from the rp1 chip.
Yes of course that as well, sorry for the confusion, my last answer was only related to your last message 
I noticed a few problems with the installer from the December update when using on DevTerm:
- File system resize doesn’t happen automatically post install, have to trigger it manually via raspi-config
- Upon updating via apt update/upgrade, and after reboot, the system doesn’t seem to boot up properly anymore–two different symptoms–first attempt, the system booted into desktop but at wrong resolution–tried installing again and updating, this time I noticed the boot screen would just go all white–moved the card to a another machine and noticed that in /boot/config.txt, the CM4 entries were all commented out and the CM5 entries were uncommented. Not a build expert so not sure what’s happening here.
@Rex I know you don’t have a DevTerm anymore (since I bought yours haha). Happy to test out new images if needed. Can also logs if that will help if you get to this. Know that there aren’t that many DevTerm users so may not be a priority.
1 Like
the newest image is still just a test for the CM5 the last kernel for it reset the config.txt all you have to comment out is the lines that have uconsole listed and uncomment devterm. the rest you can leave uncommented.
I must of forgot to run the script on it to get it to auto-expand on first boot i’ll fix it on the next release i put out.
the cm4 will ignore everything in the [pi5] section.
2 Likes
Hi, is there a way to get a hold of older bookworm images (pre-CM5)? Tried the latest and the 4g doesn’t seem to work. Couldn’t get the USB0 enabled in the 6.6.66y image. I have 2 SD Cards and the older bullseye fresh install works with 4g and enabled usb0 so I’m thinking based on the earlier message on this thread that maybe it’s only affecting the latest image? Thanks in advance!
Did it work for you before on bookworm? What are you doing to enable the 4g card? Have you tried uconsole-4g enable to enable the 4g card? Nothing changed on the CM4 side the way things work. 4g on the CM5 might need some tweaking.
If you still want to try an older image, I would have this one: ClockworkPi-CM4-Bookworm-6.6.31.img.xz - Google Drive
How to resolve kernel compile errors?
I understand to the point where the compile versions are different.
└─[$] cat /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log [9:02:48]
DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.2 for kernel 6.6.69-v8-16k+ (aarch64)
2025年 1月 13日 月曜日 08:58:41 JST
make: ディレクトリ '/usr/src/linux-headers-6.6.69-v8-16k+' に入ります
warning: the compiler differs from the one used to build the kernel
The kernel was built by: aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0
You are using: gcc (Debian 12.2.0-14) 12.2.0
What system type are you compiling on?
The kernel was compiled using the exact one that comes in the bookworm image.
What command are you using to build the DKMS package?
I usedsudo apt install
what package is it?
do you have all the dependencies installed?
sudo apt install bc bison flex libssl-dev make libc6-dev libncurses5-dev
should install everything you need.
aarch64-linux-gnu-gcc vs. gcc – are you building it from your x64 host?
If not (and you’re building on uC/DT), double check if aarch64-linux-gnu-* in your PATH
Try this:
To configure DKMS to use the aarch64-linux-gnu- prefix for cross-compilation, you need to modify the DKMS configuration. Add this to /etc/dkms/framework.conf:
Copy
CROSS_COMPILE="aarch64-linux-gnu-"
This will make DKMS use the specified prefix for all compiler tools (gcc, ld, etc.) when building kernel modules.
1 Like
it’s clockworkpi-kernel (6.6.69-v8-16k+)
I installed them.
I added those, but the result was the same
Configuring clockworkpi-kernel (6.6.69-v8-16k+) ...
/etc/kernel/postinst.d/dkms:.
dkms: running auto installation service for kernel 6.6.69-v8-16k+.
Sign command: /lib/modules/6.6.69-v8-16k+/build/scripts/sign-file
Binary /lib/modules/6.6.69-v8-16k+/build/scripts/sign-file not found, modules won't be signed
Building module:...
Cleaning build area...
make -j4 KERNELRELEASE=6.6.69-v8-16k+ -C /lib/modules/6.6.69-v8-16k+/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build.... (bad exit status: 2)
Bad return status for module build on kernel: 6.6.69-v8-16k+ (aarch64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information.
One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.6.69-v8-16k+ failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: Error processing package clockworkpi-kernel (--configure)
: : installed clockworkpi-kernel
installed clockworkpi-kernel package post-installation script subprocess return
ed error exit status 1
An error occurred while processing
clockworkpi-kernel
E: Sub-process /usr/bin/dpkg returned an error code (1)
I just updated the kernel. It’s 6.6.70. It should fix the post-installation error you’re getting.
1 Like