Black screen after last OSMC upgrade of Vero4k

clude · 4 November 2022 09:48

Hello community ,

Last night I’ve upgraded my Vero 4k (it already received the September Bullseye upgrade successfully before).

I’ve forced the update scan from the interface, it downloaded the upgrade then a popup asked me to restart the Vero in order to apply the upgrade
Since then I’ve got nothing at screen

What I tried (with the same HDMI cable):

connect another screen (ViewSonic VG2448) → OSMC/Kodi is working fine and I can navigate through the menu
connect the screen which seems to malfunction HANNS G HH251) to another computer → and it’s working well

Journalctl show the following when I connect the screen to Kodi (cf below).

The following lines are red:

cectx c810023c.aocec: [hdmitx_notify_callback] unsupported notify:3
hdmitx: s-val 2199 h_total 2080

The following are yellow:

[RX]-up_phy_addr = 2
hdmitx: Bitdepth is set to 10 bits but display does not support deep colour

Nov 04 10:41:17 osmc-GoldenB kernel: hdmitx: system: irq 2 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: plugin
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: EDID Parser:
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 768 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 770 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 774 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: [RX]-up_phy_addr = 2
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: get dtd0 vic: 3
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: get dtd1 vic: 5
Nov 04 10:41:18 osmc-GoldenB kernel: Can't find timing exact match for 1920 x 1080 x 60
Nov 04 10:41:18 osmc-GoldenB kernel: DTD changed timings for VIC 16
Nov 04 10:41:18 osmc-GoldenB kernel: edid: vic: 16
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.pixel_freq: 148500
Nov 04 10:41:18 osmc-GoldenB kernel: edid: tmds_clk: 148500
Nov 04 10:41:18 osmc-GoldenB kernel: edid: hdmitx_vinfo.video_clk: 148500000
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.h_freq: 67500
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.v_freq: 60000
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.h_blank: 280
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.h_front: 88
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.h_sync: 44
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.v_blank: 45
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.v_front: 4
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.v_sync: 5
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.hsync_polarity: 1
Nov 04 10:41:18 osmc-GoldenB kernel: edid: timing.vsync_polarity: 1
Nov 04 10:41:18 osmc-GoldenB kernel: Backup tmds clock 138500
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: get dtd2 vic: 16
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: get dtd3 vic: 20
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: get dtd4 vic: 31
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 16 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 788 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 787 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 784 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 783 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 780 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 779 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: vic 775 added to vesa modes
Nov 04 10:41:18 osmc-GoldenB kernel: edid: reset VIC 16, 1920x1080p60hz to default timings
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: get dtd5 vic: 16
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: get PMT vic: 16
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: find IEEEOUT
Nov 04 10:41:18 osmc-GoldenB kernel: cectx c810023c.aocec: [hdmitx_notify_callback] unsupported notify:3
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: blk0 raw data
                                     00 ff ff ff ff ff ff 00 22 64 11 22 f8 05 00 00
                                     20 13 01 03 80 36 1e 78 ea cf 55 a2 56 4c 9d 23
                                     12 50 54 bf ef 80 d1 c0 b3 00 a9 40 95 00 90 40
                                     81 80 81 40 71 4f 1a 36 80 a0 70 38 1f 40 30 20
                                     35 00 1f 31 21 00 00 1b 00 00 00 fc 00 48 48 32
                                     35 31 0a 20 20 20 20 20 20 20 00 00 00 fd 00 38
                                     4b 18 50 0e 00 0a 20 20 20 20 20 20 00 00 00 ff
                                     00 39 33 32 52 4e 33 51 41 30 31 35 32 38 01 6a
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: edid: blk1 raw data
                                     02 03 22 f1 4d 9f 14 13 12 1e 16 01 90 04 05 07
                                     03 0e 23 09 07 07 83 01 00 00 67 03 0c 00 20 00
                                     28 de 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 1f 31
                                     21 00 00 18 01 1d 80 18 71 1c 16 20 58 2c 25 00
                                     1f 31 21 00 00 9e 02 3a 80 18 71 38 2d 40 58 2c
                                     45 00 1f 31 21 00 00 1e 01 1d 80 d0 72 1c 16 20
                                     10 2c 25 80 1f 31 21 00 00 9e 02 3a 80 d0 72 38
                                     2d 40 10 2c 45 80 1f 31 21 00 00 1e 00 00 00 21
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: update physical size: 540 300
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: auto - get current mode: 1080p60hz vmode_e 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: stream colourdepth was 8 in para 000000000b78d319 (1920x1080p60hz)
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: display colourdepth was 10 in cur_param 0x0a951000 (VIC: 16)
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: update physical size: 540 300
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: hdev->para now = para at 0x0a95cb88
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hdmitx: display colourdepth is 10 in cur_param 0x0a951000 (VIC: 16)
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Bitdepth is set to 10 bits but display does not support deep colour
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: Stream colourdepth is 8 in para 0x0a95cb88 (1920x1080p60hz - VIC: 16)
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: already init VIC = 0  Now VIC = 16
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: params found at 0x0a951000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: cur_param = param at 0x0a951000 colourdepth 10 colourspace 1
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: pixel freq 138500, tmds clock 173125, MaxClock1 1110000, HF_IEEEOUI 0x000000, MaxClock2 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: div40: 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: irq 80000001 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: E: ddc w1b 0x54 0x20 0x00
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: frac_rate = 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hpll_clk_out was 5540000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: config HPLL = 5540000 frac_rate = 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: HPLL: 0xc00002e6 0x800cb355
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: config HPLL done
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: set_hpll_od3_clk_div[687] div = 6
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: j = 4  vid_clk_div = 1
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: set enc for VIC: 16
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: s-val 2199 h_total 2080
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom timing: h_total 2080 v_total 1111
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006df8: 0x000000ff
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006df8: 0x000000ff
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006e00: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006e00: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006d5c: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006d5c: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006e34: 0x00004040
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006e34: 0x00004040
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006e38: 0x00000018
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006e38: 0x00000018
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006e5c: 0x0000081f
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006e5c: 0x0000081f
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006eb8: 0x00000456
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006eb8: 0x00000456
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006e90: 0x00000070
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006e90: 0x00000070
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006e8c: 0x000007ef
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006e8c: 0x000007ef
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006e98: 0x0000001c
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006e98: 0x0000001c
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006ebc: 0x00000453
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006ebc: 0x00000453
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006e9c: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006e9c: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006ea0: 0x00000020
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006ea0: 0x00000020
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006ea4: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006ea4: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006ea8: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006ea8: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006eac: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006eac: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006eb0: 0x00000005
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006eb0: 0x00000005
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: Custom reg: 0x2006d5c: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: 0x2006d5c: 0x00000000
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: PHY Setting Done
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw:  config hdmitx IP vic = 16 cd:5 cs: 1
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: Sink is HDMI device
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: set audio type 1 channels 1 + 1
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: tx_aud_src = 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: Audio Type: PCM  Audio Channels: 2, Speaker layout: 0x0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: Audio Output Channels set to: 0:0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: fs = 2, cd = 4, tmds_clk = 138500
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: aud_n_para = 6272
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: set channel status, sample rate 2
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: [0x10e3] = 0x1f
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: audio: Audio Type: PCM
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: VIC: 16 (16) 1920x1080p60hz
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: Video output
                                             Bit depth: 12-bit, Colourspace: YUV422
                                             Colour range RGB: limited, YCC: limited
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: Gamut
                                             Colorimetry BT709
                                             Transfer SDR
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: video: PLL clock: 0xc00002e6, Vid clock div 0x000a739c
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: system: update rx hdr info 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: set audio type 1 channels 1 + 1
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: tx_aud_src = 0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: Audio Type: PCM  Audio Channels: 2, Speaker layout: 0x0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: Audio Output Channels set to: 0:0
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: fs = 2, cd = 4, tmds_clk = 138500
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: aud_n_para = 6272
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: set channel status, sample rate 2
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: hw: [0x10e3] = 0x1f
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: audio: Audio Type: PCM
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000104]: 0x00000001
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000180]: 0x000000ff
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000181]: 0x000000ff
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000182]: 0x00000003
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000183]: 0x00000007
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000184]: 0x0000003f
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000185]: 0x00000002
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000187]: 0x000000ff
Nov 04 10:41:18 osmc-GoldenB kernel: hdmitx: [0x10000188]: 0x00000003

clude · 4 November 2022 13:57

Following commands does not seems to change anything

echo 422now | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
422now
echo 8bitnow | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
8bitnow

qpkorr · 4 November 2022 14:03

Not sure if it’s appropriate to add my case here - but I was just about to start a thread with the exact same title…

My situation is a bit different - I guess I had the bullseye update to do (over 600 packages), and after update, on boot I see some text, then the blue screen with the OSMC logo, then my screen goes blank. My screen is a very peculiar beast (from 2004 or so) that only supports 1080p60hz (and I’ve had support from you guys before, eg Interlaced output to progressive-only display?). Plugging into a more modern computer monitor, everything seems fine.

In case it’s relevant, I too have the message in journalctl:
cectx c810023c.aocec: [hdmitx_notify_callback] unsupported notify:3
and also
kernel: Can't find timing exact match for 1920 x 1080 x 60

and whilst running grab-logs, I got the message:

Grabbing log edid-decode ...
An error occurred while grabbing edid-decode:
 FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/edid-decode'

but I’ve no idea if any or all of these messages are relevant!

Thanks for any tips you guys can provide! (and apologies to @clude if my issue isn’t related!)

LarryBeans · 4 November 2022 16:06

I may be in the same boat, black screened after the latest update. I had changed the disp_cap settings but otherwise not done anything crazy. The black screens happen on a modern HP monitor and two older (2014) Samsung TVs. I had never previously had these issues with Vero and it happened for the first time immediately after installing the October update.

clude · 4 November 2022 17:38

@LarryBeans @qpkorr ,

Thank you for both your reply.

@qpkorr the error '/usr/bin/edid-decode' is not a big deal in my opinion and you can solved that error by installing the missing program sudo apt-get install edid-decode

@LarryBeans @qpkorr
I then tried your solution (and rebooted) but without success. Indeed the disp_cap does not show all the mode the screen is capable.

cp /sys/class/amhdmitx/amhdmitx0/disp_cap /home/osmc/.kodi/userdata/disp_cap
chown osmc:osmc ~/.kodi/userdata/disp_cap
chmod 755 ~/.kodi/userdata/disp_cap

osmc:~/.kodi/userdata$ pwd
/home/osmc/.kodi/userdata
osmc:~/.kodi/userdata$ ll disp_cap
-rwxr-xr-x 1 osmc osmc 199 Nov  4 18:21 disp_cap
osmc:~/.kodi/userdata$ cat disp_cap
480p60hz
576p50hz
720p50hz
720p60hz
1080p50hz
1080p60hz*
640x480p60hz
800x600p60hz
1024x768p60hz
1152x864p75hz
1280x960p60hz
1280x1024p60hz
1440x900p60hz
1400x1050p60hz
1600x1200p60hz
1680x1050p60hz
1920x1080p60hz
1920x1080p50hz
1920x1080i60hz
1920x1080i50hz

cat /sys/class/amhdmitx/amhdmitx0/disp_cap
480p60hz
576p50hz
720p50hz
720p60hz
1080p50hz
1080p60hz*
640x480p60hz
800x600p60hz
1024x768p60hz
1152x864p75hz
1280x960p60hz
1280x1024p60hz
1440x900p60hz
1400x1050p60hz
1600x1200p60hz
1680x1050p60hz

According to the documentation documentation of my screen is capable of these modes:

qpkorr · 5 November 2022 10:24

Thanks @clude - in particular for finding the package for edid-decode. I agree it’s probably no big deal that grab-logs can’t find it - I only thought it possible that the rest of the system might seek to use it, and its absence could actually be causing my issue.

Re disp_cap - yes, I’ve been fiddling with that in the past (Interlaced output to progressive-only display? - #5 by qpkorr ) - and when I reduced mine to just 1080p60hz, everything worked, until now.

Re an earlier tip above, I did also trying blowing away my .kodi directory and rebooting, but that didn’t help (in case unsupported plugins were the issue).

grahamh · 5 November 2022 10:38

OK, you guys have guessed right on the edid-decode thing. It was introduced mainly for RPi since the old methods of listing display caps has gone. What I’m reading is the problem is with PC monitors and not TV screens, even though those monitors claim to support 1080p60.

We’ll need full logs from everyone.

clude · 5 November 2022 11:27

@grahamh I’ve sent you the log by private message.

sam_nazarko · 5 November 2022 12:23

The edid-decode package is used to receive EDID information on the Raspberry Pi. On Vero at the time of writing, we don’t implement Direct Render Management, so our EDID is exposed and collected by logs in a different way.

clude · 5 November 2022 12:49

Tried the following:

mv .kodi bakkodi
reboot

But did not change anything (blank screen).
I’ve confirmed with another screen that kodi started correctly.

qpkorr · 5 November 2022 13:15

Thanks Sam. Updated version of my logs https://paste.osmc.tv/cabazigana

clude · 10 November 2022 07:42

@sam_nazarko @grahamh do you have any lead I could dig?

grahamh · 10 November 2022 10:01

Sorry for the delay. Your EDID has four separate definitions for 1080p60! I suspect the one Vero picks is only relevant to the VGA input but we’ve no way of knowing that.

As a workaround, you should be able to set the resolution to 1080p50 or 720p60 (on a different monitor) so you can at least get a GUI picture. Can you confirm that works? I’ll have to think about the best way of working round this quirk without upsetting other users with PC monitors.

clude · 10 November 2022 11:29

@grahamh I’ve forced:

720p60 ok
1080p50 ok
1080p59 NOK
1080p60 nok

I should have tried harder what was already written in the forum.

grahamh · 10 November 2022 11:32

Thanks for confirming. You should not have to do without 1080p60 so we will get this fixed for you.

clude · 10 November 2022 11:35

@grahamh I then tried to play a movie. But once started my screen getting blank again. When I stop it I recover the screen

Do not hesitate to contact me, I will do my best to help you.

grahamh · 10 November 2022 11:40

If the movie is 30 or 60Hz that’s expected. You would have to whitelist just 1080p50 to see the movie but it might not play smoothly.

clude · 10 November 2022 12:53

@grahamh it’s a lot to process and I havn’t understood everything but I’ve found a nice How To to start with [HowTo] Guide to the Kodi whitelist function and related settings

Now I try to understand the following:

Your EDID has four separate definitions for 1080p60! I suspect the one Vero picks is only relevant to the VGA input but we’ve no way of knowing that.

 cat /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid | edid-decode | grep 1080

gives me

    DMT 0x52:  1920x1080   60.000 Hz  16:9    67.500 kHz 148.500 MHz
    DTD 1:  1920x1080   59.934 Hz  16:9    66.587 kHz 138.500 MHz (543 mm x 305 mm)
    VIC  31:  1920x1080   50.000 Hz  16:9    56.250 kHz 148.500 MHz (native)
    VIC  20:  1920x1080i  50.000 Hz  16:9    28.125 kHz  74.250 MHz
    VIC  16:  1920x1080   60.000 Hz  16:9    67.500 kHz 148.500 MHz (native)
    VIC   5:  1920x1080i  60.000 Hz  16:9    33.750 kHz  74.250 MHz
    DTD 3:  1920x1080i  60.000 Hz  16:9    33.750 kHz  74.250 MHz (543 mm x 305 mm)
    DTD 4:  1920x1080   60.000 Hz  16:9    67.500 kHz 148.500 MHz (543 mm x 305 mm)
    DTD 5:  1920x1080i  50.000 Hz  16:9    28.125 kHz  74.250 MHz (543 mm x 305 mm)
    DTD 6:  1920x1080   50.000 Hz  16:9    56.250 kHz 148.500 MHz (543 mm x 305 mm)

Shouldn’t Kodi select by default the «native» configuration with the higher frequency? This is most probably what it’s doing and that’s why I have to force a lower frequency. That means I still have a lot of reading to do in order to understand.
This problem occured after the last upgrade. Do you know what changed on that perimeter?

thank you for your time.

grahamh · 10 November 2022 13:10

At the moment we assume the timing in ‘DTD 1’ is the correct (‘native’) mode. But for some reason that’s not working. The other three lines for 1080p60 are the standard CTA timings that TVs support. I haven’t come across a display that supports that timing for 1920x1080 before (if you are interested, it’s called ‘reduced blanking’).

The reason it’s popped up now is we made some changes to support monitors with 1920x1200 which needs Vero to read and rely on that DTD 1.

I’ve got a fix which should also solve @qpkorr’s issue, but it will need some changes to kernel code.

qpkorr · 10 November 2022 15:21

Thanks @grahamh ! I’d offer the output of
cat /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid | edid-decode | grep 1080
also - but it looks like you’ve already got it in the debug logs
Not sure if it’s saying I might have some success with 640x480 - but I think I’d rather wait for your fix!