<emOne>
It is indeed weird. Xrandr shows the selected and preferred mode as 1080i @ 60 hz
<emOne>
In display settings it shows the selected mode as 1920x1080@30hz
<emOne>
At least it is clear now that it isn't the AVR that is causing problems
<narmstrong>
yesh the state shows 1920x1080i@60Hz is selected
<narmstrong>
something is wrong in the UI, what desktop are you using ?
<emOne>
I am using armbian
<emOne>
But I have tried using libreelec
<emOne>
And it does the exact same thing
<emOne>
Libreelec also shows that 1920x1080x30hz is selected inside Kodi
<emOne>
But I suspect that it is also running in 1080i@60hz
yann has joined #linux-amlogic
<emOne>
narmstrong: the TV does support 1080i@60hz according to the manual
<narmstrong>
Yeah so the UI reports the wrong mode
<narmstrong>
Xrandr is ok, and seems the right mode is set on the HDMI
<emOne>
Yes it seems that way
<emOne>
But that doesn't explain why that mode is buggy
<emOne>
And why all the modes hijack all hdmi inputs
<emOne>
Either the dtb is bad or something in the kernel driver is a bit flimsy
<narmstrong>
never had such report
<l-as>
your hardware could just be faulty, no?
emOne has quit [Ping timeout: 264 seconds]
emOne has joined #linux-amlogic
<emOne>
I-as no it isn't faulty. Everything else works fine. When I use the same s905x3 box with a 4.9 kernel I have no display problems
<emOne>
narmstrong: well I am glad that I am the first to report this issue
<emOne>
I-as: I can single out the kernel and dtb
<emOne>
I don't know if it is possible that the dtb could cause this weird behaviour
<emOne>
And I know that with a different OS but the same kernel I also get this buggy behavior
<emOne>
l-as: ^
<l-as>
<emOne "And I know that with a different"> what is the kernel that does not work?
<l-as>
ah, mainline
<l-as>
you could try asking on armbian forums if someone is using the same setup, since it doesn't seem that unusual
<l-as>
I still wouldn't rule out faulty hardware honestly, since it could be that the 4.9 kernel just doesn't trigger the bug
emOne has quit [Ping timeout: 240 seconds]
trem has joined #linux-amlogic
Anessen97_0 has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 260 seconds]
Darkmatter66 has joined #linux-amlogic
emOne has joined #linux-amlogic
<emOne>
l-as: i am currently testing it in 5.8.5
<emOne>
It was the same in 5.7.16
<emOne>
In 4.9 it is fine
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 240 seconds]
<narmstrong>
implementation between 4.9 and mainline is totally different, but honestly I don't know how an HDMI signal can fsck up your AVR
emOne has quit [Read error: Connection reset by peer]
emOne has joined #linux-amlogic
<emOne>
Neither do I but it is pretty impressive
<emOne>
I suppose as long as it doesn't happen with other brands it isn't really a top priority
<emOne>
Pioneer doesn't make Avrs or TVs anymore either AFAIK
buzzmarshall has joined #linux-amlogic
emOne has quit [Ping timeout: 265 seconds]
Barada has quit [Quit: Barada]
vagrantc has joined #linux-amlogic
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 240 seconds]
emOne has joined #linux-amlogic
<emOne>
Perhaps it is a problem with the dtb
<emOne>
Is that a possibility?
<emOne>
Maybe i2c is not set up properly inside the dtb?
<emOne>
I2c is supposed to be responsible for DDC, which is responsible for getting the edid of the display
yann has quit [Ping timeout: 256 seconds]
emOne has quit [Ping timeout: 246 seconds]
Tonymac32 has joined #linux-amlogic
emOne has joined #linux-amlogic
<emOne>
I should add. When it hijacks the other HDMI ports the display just flickers on all the other ports. It isn't like I am getting a nice constant image. I am going to diagnose the issue tonight and see what exactly in the HDMI protocol is causing this
yann has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 260 seconds]
vicencb has quit [Quit: Leaving.]
jakogut_ is now known as jakogut
jakogut has quit [Disconnected by services]
zkrx has quit [Remote host closed the connection]
jakogut__ has joined #linux-amlogic
drieschel has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
<emOne>
narmstrong: I just realised that you're the one who does the drivers for video decoding
<emOne>
Just wanted to say great work :)
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
<narmstrong>
emOne: indeed, thx, but I’m not the main author of the driver !
<narmstrong>
Maxime did all the hard work
drieschel has quit [Quit: drieschel]
drieschel has joined #linux-amlogic
drieschel has quit [Client Quit]
sputnik_ has quit [Ping timeout: 240 seconds]
drieschel has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
vicencb has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
drieschel has quit [Quit: drieschel]
sputnik_ has quit [Ping timeout: 260 seconds]
jakogut__ is now known as jakogut
cmeerw has quit [Ping timeout: 272 seconds]
warpme_ has quit [Quit: Connection closed for inactivity]