How can I change TS050 orientation in VIM3L?

Let me review, if I overlooked any other changes. Before xorg conf solution, I played with overlay file, /etc/rc.local and khadas_init.sh.

I am using the Ubuntu focal from fenix build.

~$ cat /etc/fenix-release
BOARD=VIM3
VENDOR=Amlogic
VERSION=1.0.4
ARCH=arm64
INITRD_ARCH=arm64
INSTALL_TYPE=EMMC
IMAGE_VERSION=V1.0.4-210330
################ GIT VERSION ################
UBOOT_GIT_VERSION=khadas-vims-v1.0.4-release
LINUX_GIT_VERSION=khadas-vims-v1.0.4-release
FENIX_GIT_VERSION=v1.0.4
#############################################

~$ DISPLAY=:0 xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1088 x 1088, current 1920 x 1088, maximum 1920 x 1920
default connected 1920x1088+0+0 0mm x 0mm
1088x1920 0.00
1920x1088 0.00*

A snippet from my Xorg.0.log

[ 13.171] (II) LoadModule: “modesetting”
[ 13.171] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 13.173] (II) Module modesetting: vendor=“X.Org Foundation”
[ 13.173] compiled for 1.20.9, module version = 1.20.9
[ 13.173] Module class: X.Org Video Driver
[ 13.173] ABI class: X.Org Video Driver, version 24.1
[ 13.173] (II) LoadModule: “fbdev”
[ 13.173] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 13.174] (II) Module fbdev: vendor=“X.Org Foundation”
[ 13.174] compiled for 1.20.1, module version = 0.5.0
[ 13.174] Module class: X.Org Video Driver
[ 13.174] ABI class: X.Org Video Driver, version 24.0
[ 13.174] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 13.174] (II) FBDEV: driver for framebuffer: fbdev
[ 13.184] (WW) Falling back to old probe method for modesetting
[ 13.184] (EE) open /dev/dri/card0: No such file or directory
[ 13.184] (WW) Falling back to old probe method for fbdev
[ 13.184] (II) Loading sub module “fbdevhw”
[ 13.184] (II) LoadModule: “fbdevhw”
[ 13.184] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 13.187] (II) Module fbdevhw: vendor=“X.Org Foundation”
[ 13.187] compiled for 1.20.9, module version = 0.0.2
[ 13.187] ABI class: X.Org Video Driver, version 24.1
[ 13.187] (II) FBDEV(0): using default device
[ 13.187] (II) FBDEV(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
[ 13.187] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[ 13.187] (==) FBDEV(0): RGB weight 888
[ 13.187] (==) FBDEV(0): Default visual is TrueColor
[ 13.188] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 13.188] (II) FBDEV(0): hardware: OSD FB (video memory: 77312kB)
[ 13.188] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 13.188] () FBDEV(0): Option “Rotate” “CW”
[ 13.188] (
) FBDEV(0): rotating screen clockwise
[ 13.188] (II) FBDEV(0): checking modes against framebuffer device…
[ 13.188] (II) FBDEV(0): checking modes against monitor…
[ 13.188] (II) FBDEV(0): Virtual size is 1088x1920 (pitch 1088)
[ 13.188] () FBDEV(0): Built-in mode “current”
[ 13.188] (==) FBDEV(0): DPI set to (96, 96)
[ 13.188] (II) Loading sub module “fb”
[ 13.188] (II) LoadModule: “fb”
[ 13.189] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 13.190] (II) Module fb: vendor=“X.Org Foundation”
[ 13.190] compiled for 1.20.9, module version = 1.0.0
[ 13.190] ABI class: X.Org ANSI C Emulation, version 0.4
[ 13.190] (
) FBDEV(0): using shadow framebuffer
[ 13.190] (II) Loading sub module “shadow”
[ 13.190] (II) LoadModule: “shadow”
[ 13.191] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 13.192] (II) Module shadow: vendor=“X.Org Foundation”
[ 13.192] compiled for 1.20.9, module version = 1.1.0
[ 13.192] ABI class: X.Org ANSI C Emulation, version 0.4
[ 13.192] (II) UnloadModule: “modesetting”
[ 13.192] (II) Unloading modesetting
[ 13.214] (II) FBDEV(0): display rotated; disabling DGA
[ 13.214] (II) FBDEV(0): using driver rotation; disabling XRandR
[ 13.214] (==) FBDEV(0): Backing store enabled
[ 13.215] (==) FBDEV(0): DPMS enabled


1 Like

I haven’t see any difference from the xorg log file.

I use the default gnome desktop, and after add the configuration file, after login the default mode is 1088x1920, and I have to execute xrandr --output "default" --mode "1920x1088" to set the mode to 1920x1088, after that the display is correct.

I wasn’t paying attention that you were trying on the GNOME desktop. I can reproduce the issue on the GNOME desktop as well.
My suspicion is either the gnome settings daemon or the org.gnome.Mutter.DisplayConfig changing the settings. Will be investigating this further.

The screen rotates fine on a freshly built XFCE desktop eliminating the possibility that I may have modified some script.

Meanwhile could you please try the following using autostart file .config/autostart/rotate-ts050.desktop

[Desktop Entry]
Type=Application
Name=TS050 in Landscape Mode
Exec=xrandr --output "default" --mode "1920x1088"
Terminal=false
X-GNOME-Autostart-enabled=true
3 Likes

Yes, that’s my solution. :wink:

2 Likes

@numbqq @Frank any update of the TS050 in mainline ?

Still have no luck to make it work with mainline kernel .

@numbqq I am encountering this error with eMMC images as well, Its the v200530 image and after I did sudo apt update && apt upgrade I seem to be having a torn screen like I had previously (but that was in SD/USB image, this is eMMC image)

this is the plymouth boot splash I guess, it seems to be fine when booting up for a couple of seconds, then immediately after entering tty, it is shows a torn screen… :confused:

I guess you use the server image, right? We have fixed this issue and will release new image this week.

And you can try to upgrade the package manually:

$ wget https://dl.khadas.com/test/linux-board-package-focal-vim3_1.0.4_arm64.deb
$ sudo dpkg -i linux-board-package-focal-vim3_1.0.4_arm64.deb
$ sudo reboot
1 Like

yep, I will update it and get back to you :slightly_smiling_face:

Update: it now works alright

1 Like

@numbqq when can we get an update on the fenix 4.9 images ?
I had an unforseen incident, and had to reflash my VIM3 back to v200530, and now I have the same issue as before with TS050 screen torn

Already updated. Please follow this docs to update to latest V1.0.5 version.

2 Likes

ah yes, its working fine again, sorry for the alarm,
thanks for the update :slightly_smiling_face: