SteMMo Posted October 30, 2019 Posted October 30, 2019 Hello all, I downloaded the Armbian Buster OS desktop version. I need to run it with a vertical display - portrait mode. The OS starts correctly and I see the desktop in landscape mode but when I try to rotate left the display, it does not rotate and return to landscape mode. The display is a large NBT monitor 1920x1080 that I need to rotate to 1080x1920. Any idea? Regards
Igor Posted October 30, 2019 Posted October 30, 2019 54 minutes ago, SteMMo said: Armbian Buster OS desktop version. You forget to mention the most important detail. Which kernel version? We provide 4.4, 4.19 and 5.3.
SteMMo Posted October 30, 2019 Author Posted October 30, 2019 I opened the Xorg log and I noted that on the first list of available resolution is present the frequency values: [ 158.884] (--) modeset(0): HDMI max TMDS frequency 600000KHz [ 158.884] (II) modeset(0): Printing probed modes for output HDMI-1 [ 158.884] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 158.884] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) [ 158.884] (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) [ 158.884] (II) modeset(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e) [ 158.884] (II) modeset(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e ) whilst in the next lists the frequencies are zero-ed: [ 160.568] (II) modeset(0): EDID vendor "NBT", prod id 0 [ 160.568] (II) modeset(0): Using EDID range info for horizontal sync [ 160.568] (II) modeset(0): Using EDID range info for vertical refresh [ 160.568] (II) modeset(0): Printing DDC gathered Modelines: [ 160.568] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 160.568] (II) modeset(0): Modeline "1366x768"x0.0 85.50 1366 1436 1579 1792 768 771 774 798 +hsync +vsync (47.7 kHz e) [ 160.568] (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) [ 160.568] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Is it meaningful?
Igor Posted October 30, 2019 Posted October 30, 2019 Not sure about this kernel, but it works on development version with 5.3.y / Ubuntu 19.10 ... http://ix.io/20lc You can try to upgrade your 4.19.y to 5.3.y kernel with armbian-config -> system -> alternative kernels ... or build your own image https://github.com/armbian/build (branch = arm64). It's development version - no free end user support.
SteMMo Posted October 30, 2019 Author Posted October 30, 2019 Updated to 5.3.7 5.98.191029. Rotating the display for a while I see the desktop in portrait mode but then it returns to landscape mode And no other resolution is settable !!
SteMMo Posted October 30, 2019 Author Posted October 30, 2019 Same behavior with 5.3.8: - no rotation - no other resolutions
Igor Posted October 30, 2019 Posted October 30, 2019 59 minutes ago, SteMMo said: but then it returns to landscape mode This is normal. It only probes, then you have to confirm this change. Keep in mind that I used Ubuntu 19.10 user space for doing those tests ... it could be related.
Igor Posted October 30, 2019 Posted October 30, 2019 Just now, SteMMo said: How can i confirm the change, please? I used utility from XFCE desktop settings, not via CLI. I suspect that it throws you back if you use xrand ... just speculating. Rotation works for me on both monitors so I can't really debug.
SteMMo Posted October 30, 2019 Author Posted October 30, 2019 I have no way to confirm the change: when I see the portrait mode it is for half a second, then it switches to landscape.
Igor Posted October 30, 2019 Posted October 30, 2019 6 minutes ago, SteMMo said: I have no way to confirm the change: when I see the portrait mode it is for half a second, then it switches to landscape. Another cheap try is to check with identical image which I am doing those tests: https://dl.armbian.com/tinkerboard/nightly/Armbian_5.98_Tinkerboard_Ubuntu_eoan_current_5.3.7_desktop.img.gz
SteMMo Posted October 31, 2019 Author Posted October 31, 2019 I wrote your image. Nothing to do .. same behavior, no rotations Is it possible that the display information are incompatible ? Is there anything in the Xorg log? I don't see anything interesting ..
SteMMo Posted October 31, 2019 Author Posted October 31, 2019 I'm comparing two xorg log: Display NTB 75": [ 491.878] (II) modeset(0): Allocate new frame buffer 1080x1920 stride [ 492.474] (II) modeset(0): Allocate new frame buffer 320x200 stride [ 492.542] (II) modeset(0): EDID vendor "NBT", prod id 0 [ 492.542] (II) modeset(0): Using hsync ranges from config file [ 492.542] (II) modeset(0): Using vrefresh ranges from config file [ 492.542] (II) modeset(0): Printing DDC gathered Modelines: [ 492.542] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 492.542] (II) modeset(0): Modeline "1366x768"x0.0 85.50 1366 1436 1579 1792 768 771 774 798 +hsync +vsync (47.7 kHz e) No rotation, '320x200' ?? Which config file ? Display TVL : [ 16.667] (II) modeset(0): Allocate new frame buffer 1080x1920 stride [ 19.814] (II) modeset(0): EDID vendor "TVL", prod id 6432 [ 19.814] (II) modeset(0): Using EDID range info for horizontal sync [ 19.814] (II) modeset(0): Using EDID range info for vertical refresh [ 19.814] (II) modeset(0): Printing DDC gathered Modelines: [ 19.814] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 19.814] (II) modeset(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) Rotation ok and uses EDID info..
SteMMo Posted October 31, 2019 Author Posted October 31, 2019 With your image in the Xorg log I see: [ 47.733] (II) modeset(0): Allocate new frame buffer 1080x1920 stride [ 48.253] (II) modeset(0): Allocate new frame buffer 320x200 stride [ 48.314] (II) modeset(0): EDID vendor "NBT", prod id 0 [ 48.315] (II) modeset(0): Using hsync ranges from config file [ 48.315] (II) modeset(0): Using vrefresh ranges from config file [ 48.315] (II) modeset(0): Printing DDC gathered Modelines: [ 48.315] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) .. [ 48.397] (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) [ 48.398] (--) modeset(0): HDMI max TMDS frequency 600000KHz [ 48.426] (II) modeset(0): Allocate new frame buffer 1920x1080 stride [ 48.557] (II) modeset(0): EDID vendor "NBT", prod id 0 [ 48.557] (II) modeset(0): Using hsync ranges from config file [ 48.557] (II) modeset(0): Using vrefresh ranges from config file [ 48.557] (II) modeset(0): Printing DDC gathered Modelines: [ 48.557] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) .. [ 48.558] (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) [ 48.558] (--) modeset(0): HDMI max TMDS frequency 600000KHz [ 97.626] (II) modeset(0): Allocate new frame buffer 1280x720 stride [ 97.961] (II) modeset(0): Allocate new frame buffer 320x200 stride [ 98.176] (II) modeset(0): EDID vendor "NBT", prod id 0 So there is a quickly sequence of changes 1080x1920 (required) --> 320x200 --> 1920x1080 Why??
Igor Posted October 31, 2019 Posted October 31, 2019 24 minutes ago, SteMMo said: Why?? No idea. I know this won't help you, but there are lots of other people with the same problem. Read, perhaps you get some clues.
SteMMo Posted November 5, 2019 Author Posted November 5, 2019 Just tested with Raspberry 4. Is is able to rotate the display.
Igor Posted November 5, 2019 Posted November 5, 2019 2 hours ago, SteMMo said: Just tested with Raspberry 4. Is is able to rotate the display. This means bug is deep in the video driver as it can be extracted from other topics.
Recommended Posts