RaspbianOS bullseye arm64

DevTerm
1

Recently I found Raspbian rolled out new OS and they also released arm64 image.

It boots but immediately shutdown when it goes to graphical.target (of systemd)
I guess it is graphic driver related problem.

Could please clockworkpi team provides some way or guide to adopt new RaspianOS on DevTerm?

2 Likes
2

Silence, both here and at DevTerm/Code/kernel at main · clockworkpi/DevTerm · GitHub , is the worst thing that can happen to the DevTerm. It runs the risk of this device joining the masses of other RPI carriers doomed to stick at a single software version, forever falling further out of date.

What can we do to upstream the DevTerm software so that we don’t fall into that trap? Does the clockworkpi team need help?

5 Likes
3

I copied patches from A06 onto Raspbian kernel source (rpi-5.10.y branch) of arm64
And build it

$  make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- bcmrpi3_defconfig
$ ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make -j4 \
    CXXFLAGS="-march=armv8-a+crc -mtune=cortex-a53" \
    CFLAGS="-march=armv8-a+crc -mtune=cortex-a53" \
    bindeb-pkg

# I've mounted distribution-image of arm64 on /mnt/p1

$ cp arch/arm64/boot/Image /mnt/p1/boot/kernel8.img
$ cp arch/arm64/boot/dts/overlays/*.dtbo /mnt/p1/boot/overlays/
$ cp arch/arm64/boot/dts/broadcom/*.dtb /mnt/p1/boot/

cmdline.txt and config.txt are same with official document.

Devterm boots successfully but no display, no wifi.
HDMI display works if removes line of ‘dtoverlay=vc4-kms-v3d’

1 Like