09-20-2021, 06:09 AM
(09-18-2021, 11:04 AM)jlucas Wrote: I'm using X11 on Arch Linux.
The commands I posted are the ones I use on my script to rotate the screen.
I tested them right before I posted and they were working. Then I noticed you mentioned fbturbo - which I hadn't heard of before - so I searched for it in the repos and noticed it wasn't installed.
So I installed xf86-video-fbturbo-git and rebooted. And now xrandr gives me an error similar to yours (only difference is the "Major opcode of failed request" is 140 instead of 139, whatever that means).
As for the monitor name, mine was showing the right names, but after installing fbturbo it also listed it as "default".
Searching a bit for the error, it seems fbturbo really doesn't support xrandr rotation (https://github.com/ssvb/xf86-video-fbtur...-146012185).
It should be possible to have a fixed orientation other than the default with fbturbo, but apparently it reduces performance (https://github.com/ssvb/xf86-video-fbtur...t-45969823).
So if you can live without that driver, then it should work.
Do you have an explanation on how to use X11 on Phosh?
Because I thought the Purism team made it Wayland-only.
I never liked the whole Wayland lock-in, because why are we replacing something that has been fully functional for 24 years with something that is still far from functional 12 years after its development started?
Looks a lot like the more effort we put to make something better, the worse results we're getting in the end.
Not just with Linux, this is the case with pretty much everything in the current year.
母語は日本語ですが、英語も喋れます(ry