The touchscreen monitor that we use is obsolete, and its replacement has the wrong aspect ratio after boot. Both the old monitor and its replacement are 16:9. On the old monitor, xrandr reports “default connected 1280x720+0+0 0mm x 0mm”, the correct aspect ratio. The new monitor reports “default connected 1280x1024+0+0 0mm x 0mm”, a 5:4 aspect ratio which causes everything to be compressed vertically. If I edit the uEnv file to force “HDMI-A-1:1280x720@60e”, the monitor does not turn on at all after boot. Also tried 24 fps. Also tried a bunch of other smaller resolutions.
Is there anything else I should look at to try to force a resolution? Is this just the limitation of the monitor itself? Thanks for any help.
We have a very old image running kernel 3.8 which we were able to get mostly working by changing from the fbdev driver to the modesetting driver and then forcing a resolution using xrandr. However, opening some of the applications causes the BBB to freeze and become unresponsive. We are in the process of upgrading our image to 6.18, but selecting the modesetting driver there does not allow for the window manager to open at all (though you can still ssh just fine). Has anyone else won a similar battle?
1 Like
Hey There,
I was dealing with the many already allocated LCD pins on a specific branch years and years ago. It was a little after 3.8.x kernels. I think 4.1.x or 4.14.x kernels.
It was a complicated piece of source code to me but the fellows that put it together were called groupgets.
Now with kernels that are in the LTS phase or mainline phase, I am out but I have hints before I require more time dedicated to this matter.
- DTS for the HDMI may provide clues
- Maybe the core source for the xrandr has changed
That is all I got for now. I will look into it hopefully sometimes soon.
So, just to put me “on the bridge here:”
- BBB
- HDMI
- Needs an OS with GUI
The more you can give, the easier it will be on random people like me pitching in.