I have added a few working/testing images and kernels with the *.deb files to install in the mega folder if you want for different OSs.
Google Drive link for the main image if Mega doesnāt work for you.
Hereās my Github with the rpi-6.12.y branch if youād like to compile yourself. All the ClockworkPi drivers are pre-marked to compile in bcm2711_defconfig or bcm2712_defconfig. Also the APT repo with kernels and hardware scripts for ClockworkPi devices
I was going to ask you Rex to do this one as its my favourite Linux distro thank you brother. Now all i need is Batocera if you can get that running Uconsole.
Awesome work @Rex! Iām using it right now and it feels very snappy on the CM4. Havenāt run into any problems so far, installation was a breeze. Thank you so much!
Iām having the same issue with this Ubuntu image that was reported for initramfs. I looked at this solution:
However, my initramfs.conf file already has the āMODULES=mostā line. I couldnāt figure out how to solve it. The kernel seems to have been updated, but the error persists after attempting another āapt upgradeā. I just restarted my uConsole and it booted up correctly though.
EDIT: the error message is not the same as in the Bookworm image, so hereās the error for Ubuntu:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following upgrades have been deferred due to phasing:
gnome-shell gnome-shell-common
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up flash-kernel (3.107ubuntu13~24.04.2) ...
Using DTB: bcm2711-rpi-cm4.dtb
flash-kernel: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
update-initramfs: Generating /boot/initrd.img-6.12.28-v8-16k+
Using DTB: bcm2711-rpi-cm4.dtb
Installing /usr/lib/linux-image-6.12.28-v8-16k+/broadcom/bcm2711-rpi-cm4.dtb into /boot/dtbs/6.12.28-v8-16k+/./bcm2711-r
pi-cm4.dtb
Taking backup of bcm2711-rpi-cm4.dtb.
Installing new bcm2711-rpi-cm4.dtb.
Ignoring old or unknown version 6.12.28-v8-16k+ (latest is )
Processing triggers for flash-kernel (3.107ubuntu13~24.04.2) ...
Using DTB: bcm2711-rpi-cm4.dtb
Couldn't find DTB bcm2711-rpi-cm4.dtb on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image- /lib/firmware
//device-tree/
Installing into /boot/dtbs//./bcm2711-rpi-cm4.dtb
cp: cannot stat '': No such file or directory
dpkg: error processing package flash-kernel (--configure):
installed flash-kernel package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
flash-kernel
E: Sub-process /usr/bin/dpkg returned an error code (1)
Did you force update the kernel? I thought I mark it on hold, Iāll have to go back and check.
The only systems that can get automatic kernel updates are the Debian builds. Ubuntu has deviated far enough away from Debian that my kernel package canāt be use to update it.
Iām looking through my command history and I seem to have done āapt upgradeā only. Would it help to manually downgrade the clockworkpi-kernel package using the .deb file for the previous version?
Iāve imaged an SD card with the Ubuntu Preinstalled Image and it doesnāt seem to be happy. Booting the uConsole results in a black screen. If I plug a display in, I can see that the bootloader on the pi is first unhappy with the config.txt, it needs me to add os_check=0 in order to boot. After I shut down and edit that file and reboot, the bootloader seems to just loop, claiming FAT read errors, but doesnāt complain about the config.txt anymore. It seems like there probably isnāt a FAT read error if it can validate the config.txt, but Iām a little out of my depth.
Is this a known issue? Or maybe Iām doing something wrong, getting the image onto the SD card with rufus and now trying rpi imager.
ETA: After lots of restarting and waiting it seems like the ubuntu image is booting⦠Iām not sure why the pi thinks the SD card canāt be read at first. I guess maybe it does the same thing with the CM4 and I just havenāt ever been impatient enough to notice?
ETA2: Seems stabler now, after first full boot it seems like it āfigured outā how to boot from the SD card. All of this is such a black box to me
OH EMM GEE how did I miss this post? Thanks @Rex, this is going on a spare SD card immediately, possibly becoming my daily driver. God tier stuff, thank you!
Is there a fix for (or could it be related to overheating) my CM5 UConsole crashing during lite use and causing the screen lights to remain on but wont allow the system to be shut down or reset using the power button?