You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the last couple updates, if I attach an external monitor, it only works at 24 Hertz if it's a TV, and when you unplug it the built-in screen on the deck splits into multiple sideways screens with glitches. I fixed that somehow but have a new issue. Now I can only make the orientation correct if I invert them. Bazite seems to be under the impression that my screen is tall vertically and so to make it look right this is what I have to do please see screenshot.
What did you expect to happen?
I expected to have my screen display properly in 1280x800 rather than 800x1280.
Output of rpm-ostree status
Version: 41.20250216
Hardware
Steam deck OLED 1tb
Extra information or context
Gaming mode works fine no issues.
The text was updated successfully, but these errors were encountered:
iirc, this is a hardware issue. My OneXFly has the same "issue", that because screens need to be plugged in and manufactured, they use vertical screens in gamerdecks and rotate the screen via the OS. As such, there is nothing that can be done on the bazzite end.
Describe the bug
After the last couple updates, if I attach an external monitor, it only works at 24 Hertz if it's a TV, and when you unplug it the built-in screen on the deck splits into multiple sideways screens with glitches. I fixed that somehow but have a new issue. Now I can only make the orientation correct if I invert them. Bazite seems to be under the impression that my screen is tall vertically and so to make it look right this is what I have to do please see screenshot.
What did you expect to happen?
I expected to have my screen display properly in 1280x800 rather than 800x1280.
Output of
rpm-ostree status
Hardware
Steam deck OLED 1tb
Extra information or context
Gaming mode works fine no issues.
The text was updated successfully, but these errors were encountered: