[PROBLEM] 9.0.1/RPi 3b+: RPi 7" display can't be rotated

[Iacov]

hi

until yesterday I used 8.3.9 (I think that was the latest bullseye release?) and it worked flawless with my raspberry pi 3b+ and RPi 7" display

I have installed 9.0.1 via the RPi imager and with the current release I face the issue that I can't rotate the display anymore

I'm no native speaker but I try to explain the besri can

- when first booting the fresh install, everything is upside down (like it was with a fresh moode 8 install too)
- I then headed to settings/system, activated the local display and set the rotation to 180 degrees
- when rebooting, the display is at first rotated correctly (by 180°) but in the middle of the boot sequence it turns back to 0°/upside down and stays this way

I have checked the boot log - it looks unsuspicous to me
I have checked /boot/firmware/config and the display rotation is correctly set to 2
I have tried switching from kernel to firmware mode... the display stays correctly rotated then, but the GUI does not start 

is there a way to check the list of entries that are displayed while booting? I'd like to find the line at which the display gets rotated in the wrong direction again

besides my "report"... is there a way to fix my issue?

[Iacov]

i seem to have found a workaround here

it appears to be a bookworm thing? but i don't know why
i just added to /boot/firmware/cmdline.txt (at the end of the first line, not in a separate line)

Code:

video=DSI-1:800x480@60,rotate=180

this seems to keep the orientation correct without any further changes (to clarify, the option to rotate for 180° is still set in settings..i will test if it makes any difference)

i don't know why it is needed and if it is something that i should keep that way? should i rather wait for a moode update that accounts for the issue?

edit: touch orientation is still not correc though, will investigate

[Tim Curtis]

It looks like none of the Pi Touch specific settings in Peripheral Config work with Bookworm KMS video driver. There are fixes for two of the three settings.

Brightness:    Add "dtoverlay=rpi-backlight" to [all] section in config.txt
Rotate screen: Add "video=DSI-1:800x480@60,rotate=180" to end of cmdline.txt
Pixel aspect:  No solution. Circles will look oval, squares oblong because square pixels apparently can't be configured in the frame buffer as they could in the old Firmware mode BCM2835 video driver.

It seems every major OS bump causes a lot of configuration issues with  these DSI/SPI displays. At this point it's clear that the direction in Bookworm is toward HDMI displays. 

I tested the two fixes listed above and they work with the default KMS video driver. There is an option in System Config named "Integrated audio" that allows the old Firmware mode driver to be used instead of the KMS driver but this is meant specifically as a hack for a Headphone-only audio config and not for reverting to the BCM driver for displays which is absolutely not supported!

I'll plan to implement these two fixes and a fix for pixel aspect ratio if one is discovered.

[taku82162]

Hi,
Thanks to everyone who developed this great software.
Please excuse my poor English.

I encountered a similar problem.
I will post what I have tried.

I also installed 9.0.1 onto my Pi-4B 1.4 8GB with RPi 7" display using the RPi imager.
I set "Rotate screen" to "180 Deg", and the screen rotated correctly immediately after startup, but the screen became upside down during startup.

I did the same thing by adding 
  "video=DSI-1:800x480@60,rotate=180"
 to the end of /boot/firmware/cmdline.txt, and it started to display normally, but the touch operation was not correct.

I modified /boot/firmware/config.txt using this URL as a reference.

Code:

dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch,invx,invy  # <- add this line.
MAX_framebuffers=2
#display_auto_detect=1  # <- comment out this line.

After modifying cmdline.txt and config.txt as above, the display and touch operation became normal.

If you do not set "Rotate screen" to "180 Deg" and modify cmdline.txt and config.txt as above, the display will be correct from the middle of startup and touch operation will also be normal.

I hope this reply is helpful.

[Tim Curtis]

Hi,
Thanks to everyone who developed this great software.
Please excuse my poor English.

I encountered a similar problem.
I will post what I have tried.

I also installed 9.0.1 onto my Pi-4B 1.4 8GB with RPi 7" display using the RPi imager.
I set "Rotate screen" to "180 Deg", and the screen rotated correctly immediately after startup, but the screen became upside down during startup.

I did the same thing by adding 
  "video=DSI-1:800x480@60,rotate=180"
 to the end of /boot/firmware/cmdline.txt, and it started to display normally, but the touch operation was not correct.

I modified /boot/firmware/config.txt using this URL as a reference.

Code:

dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch,invx,invy  # <- add this line.
MAX_framebuffers=2
#display_auto_detect=1  # <- comment out this line.

After modifying cmdline.txt and config.txt as above, the display and touch operation became normal.

If you do not set "Rotate screen" to "180 Deg" and modify cmdline.txt and config.txt as above, the display will be correct from the middle of startup and touch operation will also be normal.

I hope this reply is helpful.

Yes very helpful.
I'll plan to include the addition configs in the fix for screen rotation.

[Iacov]

Hi,
Thanks to everyone who developed this great software.
Please excuse my poor English.

I encountered a similar problem.
I will post what I have tried.

I also installed 9.0.1 onto my Pi-4B 1.4 8GB with RPi 7" display using the RPi imager.
I set "Rotate screen" to "180 Deg", and the screen rotated correctly immediately after startup, but the screen became upside down during startup.

I did the same thing by adding 
  "video=DSI-1:800x480@60,rotate=180"
 to the end of /boot/firmware/cmdline.txt, and it started to display normally, but the touch operation was not correct.

I modified /boot/firmware/config.txt using this URL as a reference.

Code:

dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch,invx,invy  # <- add this line.
MAX_framebuffers=2
#display_auto_detect=1  # <- comment out this line.

After modifying cmdline.txt and config.txt as above, the display and touch operation became normal.

If you do not set "Rotate screen" to "180 Deg" and modify cmdline.txt and config.txt as above, the display will be correct from the middle of startup and touch operation will also be normal.

I hope this reply is helpful.

Yes very helpful.
I'll plan to include the addition configs in the fix for screen rotation.

thank you very much you two!
i will try the workaround mentioned by @taku82162 and report back

and thank you for your hard work @Tim Curtis!

edit: the workaround works, but funny detail, the mouse cursor is "inverted"...e.g. when i touch the "m" in the upper right corner, i get the correct options menu, but the mouse cursor is in the bottom left corner

[TheOldPresbyope]

@Tim Curtis

Seems the RPF folk described most of this in their official documentation.

Go to Raspberry Pi Touch Display and scroll down to Rotate screen without a desktop and the following Rotate touch input.


Regards,
Kent

[Tim Curtis]

Yes they have documented these things but it's geared for fresh configs and not migrating from the previous Bullseye way of doing things. Thats left up to the users or project devs to figure out what things can stay as-is and what needs a new configuration. When doing an entire OS migration there is only so much project bandwidth. Some things will necessarily end up being be discovered "in the field".

[TheOldPresbyope]

Sorry, that post wasn’t intended to mean to be anything more than a confirmation of the proposed changes above by way of a reference to official docs. I wasn’t aware of it either until I finally had time to look earlier today.

As I read the RPi forum and the RPi GitHub issues I get the unsettled feeling that even those within the inner sanctum are still figuring this stuff out. 

Regards,
Kent

[Iacov]

with "things still in progress"...should i rather install 9.0.1 and apply the workaround or should i wait till an update?