• Content Count

  • Joined

  • Last visited

Everything posted by CluelessLee

  1. Hi Myy, Thank you for taking the time to respond. I have attached the dmesg file. There is an update which I hope will help you, it doesn't me :-( I performed a fresh install of Focal server and plugged in the screen. I installed openbox etc using and when I tried to run openbox using startx It didnt and timed out I then noticed in /var/log/Xorg.0.log the message Screen(s) found, but none have a usable configuration. I plugged in another monitor and it worked fine. Does this shed any light on it? I am able to set a resolution o
  2. I logged an issue a little while ago with Armbian running on the Tinkerboard that the screen when rotated 90 degrees couldn't draw the screen at any speed. I have been playing with a few alternatives incl going back to the original tinkeros. All have issues so I was delighted to see the FOCAL port. I am using the recommended Waveshare 7" touchscreen that you advertise on the home page as tested 3rd party hardware. Both the desktop and the server versions of Focal come up with the error Configure crtc 0 failed setting mode when I manually set the supported resolution of 1024 x 60
  3. I would prefer to run this in Buster, as I am trying to make this as lightweight as possible. Is there a similar setting in Buster that I could try with? Thanks Lee
  4. Hi Igor, Thank you for your response. Apologies for the delay, I had to flash the OS onto my tinkerboard again. I would say it has made a slight improvement but it's still very slow when rotating 90 degrees left. I have tried 2 different monitors. Any other suggestions would be very much appreciated. Thanks Lee
  5. Hi first post here. I had been wrestling with TinkerOS but discovered Armbian and so far am super impressed with this one caveat. I too am experiencing the same issue, a web page's performance when running with a normal view is significantly quicker than when its rotated using xrandr I have tried the current buster build and used buster_legacy_4.4.213. Both appear to have the same issue, but I am very open to having got something wrong. The monitor(s) I have tested with all worked with a similar script when using TinkerOS. All help would be gratefully received.