Helipil0t Posted May 2, 2020 Posted May 2, 2020 So I have armbian installed on a tinkerboard and have had absolutely no issues with it until I bought a new Samsung 7000 series TV (2019). For some reason this TV does not recognize the signal coming from the tinkerboard. For the life of me I cannot figure out how to get this to work. I notice a few references online about being able to force a resolution but nothing related to the rockchip boards. Is there an equivalent way to force a display resolution as in this article? https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output I'm running 4.19.21-rockchip 5.76 I've also tried kernel 5.4.28 as well and it's the same issue. Just for kicks I loaded Lakka on there and it works just fine so I know the board itself is working properly. I don't even know where to begin. I was hoping someone could chime in and point me in the right direction.
Werner Posted May 2, 2020 Posted May 2, 2020 Quote 4.19.21-rockchip 5.76 Your system is outdated. If you have a spare sd card you can give both legacy (4.4.x) and dev (5.6.x) a shot and see if the issue persists:https://www.armbian.com/tinkerboard/ Quote Is there an equivalent way to force a display resolution as in this article? Try https://docs.armbian.com/User-Guide_Fine-Tuning/#screen-resolution-within-xorg-thx-maxlinux2000
Helipil0t Posted May 2, 2020 Author Posted May 2, 2020 11 hours ago, Werner said: Your system is outdated. If you have a spare sd card you can give both legacy (4.4.x) and dev (5.6.x) a shot and see if the issue persists:https://www.armbian.com/tinkerboard/ Try https://docs.armbian.com/User-Guide_Fine-Tuning/#screen-resolution-within-xorg-thx-maxlinux2000 I appreciate the reply. So I've tried the latest Armbian_20.02.7_Tinkerboard_buster_current_5.4.28_minimal.img and the issue persists. I'll try the latest nightly dev build which looks to be Armbian_20.02.7_Tinkerboard_bullseye_current_5.4.28 later tonight and see how that goes and report back. As Far as the screen-resolution guide you've pointed me to. I can't even get started as using xrandr doesn't seem to work. Again I haven't tried this with the latest so I'll try again later tonight and see how it goes. I was happily running ROTT1.1 (RetroPie on the Tinkerboard) which is using that 4.19.21 version. The end goal is to get this running RetroPie again. The first fight in a long battle ahead of me it would seem. xrandr --listmonitors Can't open display Why just the Samsung TV I wonder? I've hooked this thing up to many TVs from 720p to 4k resolutions using all kinds of refresh rates.
Werner Posted May 2, 2020 Posted May 2, 2020 As pointed out give 4.4.x a chance too. It looks oldage but in this special case it is not. The sources are heavily customised for Rockchip devices and it is still maintained upstream as LTS kernel. No idea why xrandr fails with TV connected, sorry. Try to find something useful in various log files like syslog or X.org.log when connecting/disconnecting the TV.
Myy Posted May 3, 2020 Posted May 3, 2020 This might be due to the lack of some YUV configurations support in the Rockchip DRM drivers used in mainline kernels. I'll try some new HDMI patches next week, against mainline kernels, see if that resolve these kind of situations. 1
Myy Posted May 9, 2020 Posted May 9, 2020 If you know how to recompile armbian kernels ( sudo ./compile.sh docker EXPERT="yes" ), could you test this : https://github.com/armbian/build/pull/1887 And see if that works with your TV ?
Recommended Posts