# DevTerm OS CM4 64bit image files

**URL:** <https://forum.clockworkpi.com/t/devterm-os-cm4-64bit-image-files/8786>\
**Category:** Firmware and Apps\
**Tags:** firmware\
**Created:** [August 1, 2022, 8:55pm UTC](https://forum.clockworkpi.com/t/devterm-os-cm4-64bit-image-files/8786 "2022-08-01T20:55:13Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![xordspar0](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/xordspar0/32/14995_2.png) [@xordspar0](https://forum.clockworkpi.com/u/xordspar0)\
**Post date:** [October 13, 2023, 8:44pm UTC](https://forum.clockworkpi.com/t/devterm-os-cm4-64bit-image-files/8786/13 "2023-10-13T20:44:05Z")

</div>

I’ve been thinking for a while that I’d like to get Debian Bookworm on my DevTerm. Now that [the latest Raspberry Pi OS version](https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os/) is out and it’s based on Debian Bookworm, I’m looking forward to a Bookworm-based image! I think I’ll try following the instructions to build my own image as well.

Update: so far I haven’t really gotten it working! I can boot Raspberry OS lite with Clockwork’s build of the 5.15 kernel, but as soon as I install a graphical environment, it fails to boot, presumably because of ~~kernel modules with the wrong version~~ I actually have no idea why.

I also tried to patch and build my own 6.1 kernel based on the Raspberry Pi kernel at github.com/raspberrypi/linux. While I was able to manually apply the DevTerm patches and get it to build, I haven’t gotten my kernel to boot yet.

Update (2023-11-10): I actually have been having success running the stock RP OS Bookworm lite image with the DevTerm’s kernel and device trees. I just need to be careful to not allow kernel upgrades that will mess up my boot partition. I also tried:

1. Moving the DevTerm kernel from kernel8.img to kernel-devterm-5.10.img, and modifying config.txt to point to that kernel image. That way, I can let Debian update its kernel without causing trouble. I haven’t gotten this to work, however. I can’t boot past the bootloader when I do this.
2. My custom-patched 6.1 kernel. Still won’t boot though.

To debug both of these problems, I have an I/O board coming in the mail that I will use to flash the bootloader firmware and enable UART logging in the bootloader. `enable_uart=true` in config.txt works great for getting kernel logs over UART, but I need the bootloader logs as well since my kernel isn’t even booting yet.

Update (2023-11-17): After enabling UART logs, I was able to see that my patched 6.1 kernel does boot, it just doesn’t have working drivers for the screen or keyboard.

---

_[View the full topic](https://forum.clockworkpi.com/t/devterm-os-cm4-64bit-image-files/8786)._