narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
vicencb has quit [Quit: Leaving.]
sputnik__ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
Linnaea has quit [Ping timeout: 246 seconds]
Linnaea has joined #linux-amlogic
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 265 seconds]
vagrantc has joined #linux-amlogic
random_yanek has joined #linux-amlogic
buzzmarshall has quit [Remote host closed the connection]
yann has joined #linux-amlogic
Barada has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
Darkmatter66 has joined #linux-amlogic
Darkmatter66_ has quit [Ping timeout: 256 seconds]
cmeerw has joined #linux-amlogic
ldevulder_ is now known as ldevulder
<narmstrong> emOne: it's the right place
<narmstrong> emOne: but honestly I don't see what's going wrong
<narmstrong> emOne: can you give more details on the mode detected ?
<emOne> narmstrong it selects 1080p@30hz
<emOne> My TV doesn't support that Mode
<narmstrong> this is weird, can you share the TV's EDID ?
<emOne> This is what it looks like under that mode
<emOne> Sure. How can I get the edid?
<emOne> There is something strange going on. Even if I switch it to a supported mode like 1080p@60 there are sometimes occasional flickers
<emOne> My TV is connected through an AVR
<emOne> A sattelite receiver is connected to the input HDMI 1
<emOne> My s905x3 box is connected to HDMI 3
<emOne> When I turn in the s905x3 box it hijacks the other HDMI inputs
<emOne> Meaning if I switch the receiver to HDMI1 to the switched on satellite receiver all I see on the TV is the s905x3 box
<emOne> No matter what mode I have selected
<emOne> When I turn on*
<emOne> When I switch off the s905x3 box all other HDMI inputs start working again
<emOne> Hold on I will try to get the edid. I need to Flash the mainline armbian image to my sd card
<emOne> The exact same thing happens on libreelec BTW with the mainline kernel
Barada has quit [Quit: Barada]
Barada has joined #linux-amlogic
vicencb has joined #linux-amlogic
yann has quit [Ping timeout: 256 seconds]
<emOne> Hold on I am uploading the raw edid now
emOne has quit [Read error: Connection reset by peer]
Anessen97_0 has quit [Ping timeout: 260 seconds]
emOne has joined #linux-amlogic
<emOne> narmstrong: xrandr doesn't even show 1080p@30fps as an option
<emOne> narmstrong: OK I think I have figured it out
<emOne> When I select 1080p@30hz in armbian xrandr shows that I have selected 1080i@60hz
<emOne> Or rather when I select 1920x1080@30hz
<emOne> Which gives me the crazy screen flickering
<emOne> Does that make sense?
<narmstrong> emOne: it's weird
<narmstrong> what happens when you connect it to the TV directly ?
<emOne> Good question
<emOne> I will try
<narmstrong> indeed, 1080p30 is not supported
<narmstrong> the native is 1920x1080i@60Hz, does this one work ?
<narmstrong> beware, AVRs alters the EDID and can do weird stuff
<emOne> How do I select a 1080i mode in armbian?
<emOne> OK hold on. I disconnected the box
<emOne> I will connect it to the TV. It is an older 50 inch plasma
<emOne> So it is heavy and a bit tricky to get to the back
<emOne> Once connected I will also get the edid again incase it was altered by the AVR
<narmstrong> it should be selected at boot
<narmstrong> can you cat /sys/kernel/debug/dri/0/state or /sys/kernel/debug/dri/1/state ?
<emOne> I will. I am reflashing the image to the SD card
<emOne> Because I have manually altered modes
<emOne> OK I connected the box directly to the display
<emOne> And it is doing the exact same thing
<emOne> The screen is flickering
<emOne> Can I switch modes to run that cat command?
<emOne> So I can actually see what I am doing
Barada has quit [Quit: Barada]
Barada has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 256 seconds]
<emOne> That is the output of the cat you asked for
<emOne> Also the edid when directly connected to the TV https://mega.nz/file/rAwVQCha#ZR1HTMZvdSYIKD7yjsQReZ6u87yOPAFUzvFWSwcWDw8
<emOne> Have you managed to decode the edid?
<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]
_whitelogger has joined #linux-amlogic
trem has quit [Quit: Leaving]