RPi 3B+ with 'Bullseye' can't rotate screen?

fribse

@sdetweil That would be odd, as it works with previous versions of Raspberry Pi OS?

fribse

@BKeyport That is worth a try, didn’t think of that!

fribse

@fribse Hmm, can’t make this work. I can get it to work on a RPi4, but not on a RPi3 with the ‘Screenconfiguration’ app.

It’s really annoying, I would like to have screencast and remote-control modules enabled, so that Home Assistant can integrate to it, through the remote-control module, but that doesn’t work on Buster (the integration fails to set up), it fails because of some weird problem in the integration combined with the screencast, which the author can’t reproduce, which is very odd, as I can show it every time.

I can get the integration to work on Bullseye together with the remote-control module and the screencast, but not on a RPi3, only on a RPi4, and even rotate the screen, but I don’t want to place a very hot and overly powerfull RPi4 behind the magicmirror.

Damned if I do, and damned if I don’t.

fribse

@fribse Ok, so now I’ve gotten a second RPi3b+. Apparently the monitor doesn’t like the way that Bullseye rotate the screen (by using the ‘Screen orientation’ in the GUI).
So how do I rotate the screen in ‘the old way’ which works fine on the monitor.
My guess is that it’s modifying the refresh rate beyond the capabilities of the monitor.
It’s usually running on 60Hz, and I tried changing it to 50Hz, but that didn’t change anything.

So what do I do now? I would really like to use the bullseye, as I can’t get Home Assistant to control the mirror if I have screencast installed on the mirror under Buster.

N6NG

@fribse I use a RPi3 B+ and Bullseye and I do the rotate in the boot/config.txt and it works ok for me.

karsten13

@fribse

I have no solution for your problem but if you use the WebUI to change screen settings in bullseye the changes are made here:

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 you could play with the xrandr command, may this helps …

fribse

@N6NG Ok, and what are you writing in the config for it to work? That would be a big help for me :-)

kayakbabe

@fribse it’s not in the mirror config. you have to change the rasperrypi’s actual configuration

fribse

@kayakbabe Yes, I’m referring to /boot/config.txt, not Magicmirror/config/config.yaml :-)

N6NG

@fribse It is in the boot/config.txt file itself. Not in the MagicMirror/config/config.js file.
Just cd /boot and sudo nano config.txt and either find the display_rotate=0 and change it to display_rotate=1
or add the line display_rotate=1 I added it under the #config_hdmi_boost=4 line but I suspect you could add it just about anywhere…
Dennis N6NG