pi@pi4:~ $ cat /usr/share/dispsetup.sh
#!/bin/sh
if ! grep -q 'Raspberry Pi' /proc/device-tree/model || (grep -q okay /proc/device-tree/soc/v3d@7ec00000/status 2> /dev/null || grep -q okay /proc/device-tree/soc/firmwarekms@7e600000/status 2> /dev/null || grep -q okay /proc/device-tree/v3dbus/v3d@7ec04000/status 2> /dev/null) ; then
if xrandr --output HDMI-1 --primary --mode 1920x1080 --rate 60.000 --pos 0x0 --rotate normal --output HDMI-2 --off --dryrun ; then
xrandr --output HDMI-1 --primary --mode 1920x1080 --rate 60.000 --pos 0x0 --rotate normal --output HDMI-2 --off
fi
fi
if [ -e /usr/share/tssetup.sh ] ; then
. /usr/share/tssetup.sh
fi
exit 0

So editing this script should work for command line.

it works in the WebUI preferences -> screen configuration

command line: xrandr --output HDMI-1 --rotate right (got it not working over ssh)

So I took the 64 bit image as well, seems fine so far.

Only thing I am not trying to get working is rotating the display.

display_rotate=1

added to boot/config doesnt seem to work anymore. Anyone got it working?

wondering what is wrong w install

I am away from my pi devices til middle of march.
😱

Meanwhile I digged into pi specific setup.

Real bad is that they removed /opt/vc and integrated the pi specific stuff into the normal file system under /lib and /usr.

With a docker setup I could formerly just mount /opt/vc into the container which is impossible now.

E.g. for getting vcgencmd working in the container I have to mount
now

      - /lib/aarch64-linux-gnu/libvchiq_arm.so:/lib/aarch64-linux-gnu/libvchiq_arm.so.0:ro
      - /lib/aarch64-linux-gnu/libvcos.so:/lib/aarch64-linux-gnu/libvcos.so.0:ro
      - /usr/bin/vcgencmd:/usr/bin/vcgencmd

after using ldd to know which libraries are used.

Other possibility would be to install the pi specific libraries into the docker image which will explode size.

This will have also impact to hardware releated modules which hardcoded the /opt/vc/ path in their js code (e.g. mmm-systemtemperature).

Just for the fun of it, I’m installing it on the test box…

Seems your script has issues with it…

Also, with this - Rasp Imager got an update, too - It’s got lots of config changes now, so make sure you check out the gear icon when writing!

Off topic: Did not expect that motioneye with raspicam (running in docker buster image) is working.

my pi4 is now running with 64bit, mm runs out of the box (docker setup as always).