Black screen after last OSMC upgrade of Vero4k

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

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

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.

@grahamh I’ve forced:

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

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

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

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

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

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.

@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.

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.

2 Likes

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 :slight_smile:
Not sure if it’s saying I might have some success with 640x480 - but I think I’d rather wait for your fix!

I’ve merged these fixes – but won’t be able to make them available until next weekend as I’m currently travelling. Once I’ve done so, I’ll update this thread with a test builds.

Cheers

Sam

1 Like

Hello @sam_nazarko,

Did you have the time to make the test build?

Thank you :slight_smile:

2 Likes

I’ll make these changes available shortly – but I’m waiting to merge a couple of extra fixes before doing so.

I’ll let you know when these changes are available. I’m anticipating the end of the week.

Sorry for the delay.

Sam

2 Likes

Thanks for your patience. The issue is hopefully now addressed.

To test this update:

  1. Login via the command line
  2. Run the following command to add the staging repository:
    echo 'deb http://apt.osmc.tv bullseye-devel main' | sudo tee /etc/apt/sources.list.d/osmc-devel.list
  3. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
  4. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you remove /etc/apt/sources.list.d/osmc-devel.list after updating.

This will deactivate the staging repository. You can do so with the following command:
sudo rm /etc/apt/sources.list.d/osmc-devel.list.

Please note that we will automatically disable this update channel after 14 days on your device in case you forget to do so to ensure that your system reverts to the stable update channel.

Does not seems to work :frowning: (I’ve sent the logs link by IM to @sam_nazarko and @grahamh).

sudo apt-get update && sudo apt-get dist-upgrade && reboot
Hit:1 http://ftp.debian.org/debian bullseye InRelease
Get:2 http://ftp.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:3 http://security.debian.org bullseye-security InRelease [48.4 kB]
Hit:4 http://ftp.fau.de/osmc/osmc/apt bullseye InRelease           
Get:5 http://ftp.fau.de/osmc/osmc/apt bullseye-devel InRelease [4710 B]
Get:6 http://security.debian.org bullseye-security/main armhf Packages [200 kB]
Get:7 http://security.debian.org bullseye-security/main arm64 Packages [200 kB]
Get:8 http://security.debian.org bullseye-security/main Translation-en [132 kB]
Get:9 http://ftp.fau.de/osmc/osmc/apt bullseye-devel/main armhf Packages [25.0 kB]
Get:10 http://ftp.fau.de/osmc/osmc/apt bullseye-devel/main arm64 Packages [30.1 kB]
Fetched 684 kB in 3s (263 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  armv7-libass-osmc armv7-libnfs-osmc dh-python gnupg-agent libapt-inst2.0 libbind9-140 libbind9-161 libcdio13 libcdio18 libcryptsetup4 libdevmapper-event1.02.1 libdns1104 libdns1110 libdns162 libenca0 libevent-2.0-5 libevent-2.1-6 libfdk-aac1 libffi6 libgeoip1 libhogweed4
  libicu57 libicu63 libidn11 libip4tc0 libip6tc0 libiptc0 libisc1100 libisc1105 libisc160 libisccc140 libisccc161 libisccfg140 libisccfg163 libiso9660-8 libjson-c3 liblvm2app2.2 liblwres141 liblwres161 libmpdec2 libncurses5 libnettle6 libnfs12 libntfs-3g871 libprocps6 libprocps7
  libpython2-stdlib libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3.5-minimal libpython3.5-stdlib libpython3.7 libpython3.7-minimal libpython3.7-stdlib libreadline7 libssl1.0.2 libunistring0 libwebpmux2 python-pkg-resources python-six python2 python2-minimal
  python2.7 python2.7-minimal python3-distutils python3-lib2to3 python3.5 python3.5-minimal python3.7 python3.7-minimal wireless-firmware-osmc
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  libgssapi-krb5-2 libk5crypto3 libkrb5-3 libkrb5support0 libntfs-3g883 libxml2 ntfs-3g vero3-mediacenter-osmc
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 95.6 MB/96.7 MB of archives.
After this operation, 6144 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://security.debian.org bullseye-security/main armhf libk5crypto3 armhf 1.18.3-6+deb11u3 [110 kB]
Get:2 http://security.debian.org bullseye-security/main armhf libkrb5support0 armhf 1.18.3-6+deb11u3 [62.6 kB]
Get:3 http://security.debian.org bullseye-security/main armhf libkrb5-3 armhf 1.18.3-6+deb11u3 [319 kB]
Get:4 http://security.debian.org bullseye-security/main armhf libgssapi-krb5-2 armhf 1.18.3-6+deb11u3 [143 kB]
Get:5 http://ftp.fau.de/osmc/osmc/apt bullseye-devel/main armhf vero3-mediacenter-osmc armhf 19.5.0-11 [94.9 MB]
74% [5 vero3-mediacenter-osmc 66.9 MB/94.9 MB 71%]                                                                                                                                                                                                                           10.9 MB/s 2s^Fetched 95.6 MB in 10s (9130 kB/s)                                                                                                                                                                                                                                                       
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_TIME = "fr_FR.UTF-8",
	LC_MONETARY = "fr_FR.UTF-8",
	LC_ADDRESS = "fr_FR.UTF-8",
	LC_TELEPHONE = "fr_FR.UTF-8",
	LC_NAME = "fr_FR.UTF-8",
	LC_MEASUREMENT = "fr_FR.UTF-8",
	LC_IDENTIFICATION = "fr_FR.UTF-8",
	LC_NUMERIC = "fr_FR.UTF-8",
	LC_PAPER = "fr_FR.UTF-8",
	LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
(Reading database ... 40981 files and directories currently installed.)
Preparing to unpack .../libk5crypto3_1.18.3-6+deb11u3_armhf.deb ...
Unpacking libk5crypto3:armhf (1.18.3-6+deb11u3) over (1.18.3-6+deb11u2) ...
Setting up libk5crypto3:armhf (1.18.3-6+deb11u3) ...
(Reading database ... 40981 files and directories currently installed.)
Preparing to unpack .../libkrb5support0_1.18.3-6+deb11u3_armhf.deb ...
Unpacking libkrb5support0:armhf (1.18.3-6+deb11u3) over (1.18.3-6+deb11u2) ...
Setting up libkrb5support0:armhf (1.18.3-6+deb11u3) ...
(Reading database ... 40981 files and directories currently installed.)
Preparing to unpack .../libkrb5-3_1.18.3-6+deb11u3_armhf.deb ...
Unpacking libkrb5-3:armhf (1.18.3-6+deb11u3) over (1.18.3-6+deb11u2) ...
Setting up libkrb5-3:armhf (1.18.3-6+deb11u3) ...
(Reading database ... 40981 files and directories currently installed.)
Preparing to unpack .../libgssapi-krb5-2_1.18.3-6+deb11u3_armhf.deb ...
Unpacking libgssapi-krb5-2:armhf (1.18.3-6+deb11u3) over (1.18.3-6+deb11u2) ...
Setting up libgssapi-krb5-2:armhf (1.18.3-6+deb11u3) ...
(Reading database ... 40981 files and directories currently installed.)
Preparing to unpack .../libxml2_2.9.10+dfsg-6.7+deb11u3_armhf.deb ...
Unpacking libxml2:armhf (2.9.10+dfsg-6.7+deb11u3) over (2.9.10+dfsg-6.7+deb11u2) ...
Preparing to unpack .../vero3-mediacenter-osmc_19.5.0-11_armhf.deb ...
Unpacking vero3-mediacenter-osmc (19.5.0-11) over (19.5.0-8) ...
Preparing to unpack .../ntfs-3g_1%3a2017.3.23AR.3-4+deb11u3_armhf.deb ...
Unpacking ntfs-3g (1:2017.3.23AR.3-4+deb11u3) over (1:2017.3.23AR.3-4+deb11u2) ...
Preparing to unpack .../libntfs-3g883_1%3a2017.3.23AR.3-4+deb11u3_armhf.deb ...
Unpacking libntfs-3g883 (1:2017.3.23AR.3-4+deb11u3) over (1:2017.3.23AR.3-4+deb11u2) ...
Setting up libntfs-3g883 (1:2017.3.23AR.3-4+deb11u3) ...
Setting up ntfs-3g (1:2017.3.23AR.3-4+deb11u3) ...
Setting up libxml2:armhf (2.9.10+dfsg-6.7+deb11u3) ...
Setting up vero3-mediacenter-osmc (19.5.0-11) ...
Processing triggers for libc-bin (2.31-113) ...
Processing triggers for mailcap (3.69) ...

It doesn’t look like you updated to the new kernel. Try checking for updates again.

You were right tried the update upgrade and now screen is back. Thank you very much for your time and hard work.

I guess the development will be included in the next upgrade (like december)?

sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  armv7-libass-osmc armv7-libnfs-osmc dh-python gnupg-agent libapt-inst2.0 libbind9-140 libbind9-161 libcdio13 libcdio18 libcryptsetup4
  libdevmapper-event1.02.1 libdns1104 libdns1110 libdns162 libenca0 libevent-2.0-5 libevent-2.1-6 libfdk-aac1 libffi6 libgeoip1 libhogweed4
  libicu57 libicu63 libidn11 libip4tc0 libip6tc0 libiptc0 libisc1100 libisc1105 libisc160 libisccc140 libisccc161 libisccfg140 libisccfg163
  libiso9660-8 libjson-c3 liblvm2app2.2 liblwres141 liblwres161 libmpdec2 libncurses5 libnettle6 libnfs12 libntfs-3g871 libprocps6 libprocps7
  libpython2-stdlib libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3.5-minimal libpython3.5-stdlib libpython3.7
  libpython3.7-minimal libpython3.7-stdlib libreadline7 libssl1.0.2 libunistring0 libwebpmux2 python-pkg-resources python-six python2
  python2-minimal python2.7 python2.7-minimal python3-distutils python3-lib2to3 python3.5 python3.5-minimal python3.7 python3.7-minimal
  wireless-firmware-osmc
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  vero364-image-4.9.269-17-osmc:arm64
The following packages will be upgraded:
  vero364-kernel-osmc:arm64
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.8 MB of archives.
After this operation, 83.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.fau.de/osmc/osmc/apt bullseye-devel/main arm64 vero364-image-4.9.269-17-osmc arm64 4.9.269-17-osmc [23.8 MB]
Get:2 http://ftp.fau.de/osmc/osmc/apt bullseye-devel/main arm64 vero364-kernel-osmc arm64 3.9.254 [1080 B]
Fetched 23.8 MB in 2s (9781 kB/s)              
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_TIME = "fr_FR.UTF-8",
	LC_MONETARY = "fr_FR.UTF-8",
	LC_ADDRESS = "fr_FR.UTF-8",
	LC_TELEPHONE = "fr_FR.UTF-8",
	LC_NAME = "fr_FR.UTF-8",
	LC_MEASUREMENT = "fr_FR.UTF-8",
	LC_IDENTIFICATION = "fr_FR.UTF-8",
	LC_NUMERIC = "fr_FR.UTF-8",
	LC_PAPER = "fr_FR.UTF-8",
	LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
Selecting previously unselected package vero364-image-4.9.269-17-osmc:arm64.
(Reading database ... 40981 files and directories currently installed.)
Preparing to unpack .../vero364-image-4.9.269-17-osmc_4.9.269-17-osmc_arm64.deb Progress: [ 11%] [#####...............................................] 
Unpacking vero364-image-4.9.269-17-osmc:arm64 (4.9.269-17-osmc) ...

Preparing to unpack .../vero364-kernel-osmc_3.9.254_arm64.deb ............................................................................................................................................................................................................................
Unpacking vero364-kernel-osmc:arm64 (3.9.254) over (3.9.253) ...
Setting up vero364-image-4.9.269-17-osmc:arm64 (4.9.269-17-osmc) ...
11+1 records in
11+1 records out
12318720 bytes (12 MB, 12 MiB) copied, 0.362673 s, 34.0 MB/s
0+1 records in
0+1 records out
116736 bytes (117 kB, 114 KiB) copied, 0.0100764 s, 11.6 MB/s
Setting up vero364-kernel-osmc:arm64 (3.9.254) ...

Great – thanks for confirming.

We’ll include the change in the next update but don’t have a firm schedule just yet.

Sam

Thank you - yep, working for me too.
The volume controls on the RF remote are no longer controlling my AVR via CEC - perhaps that’s a side effect of the update (which caused the screen issues) but the CEC Adapter was listed as enabled and I couldn’t immediately see what was wrong with the settings. Will look some more and post separately if required.
Also - was a little surprised that ‘reboot’ didn’t just work for me:
#: john@o1mc:~ ; reboot
Failed to set wall message, ignoring: Interactive authentication required.
Failed to reboot system via logind: Interactive authentication required.
Failed to open initctl fifo: Permission denied
Failed to talk to init daemon.
#: john@o1mc:~ ; sudo reboot
Connection to o1mc closed by remote host.
Connection to o1mc closed.

Perhaps I’m not in the right group?
#: john@o1mc:~ ; groups
john adm disk lp dialout cdrom sudo audio video osmc

Anyway, main problem fixed - thanks so much guys!

FYI - I tried turning off Vero and AVR for ten minutes to fix CEC, as suggested in some places, but no luck. However, reverting to default settings for CEC then adjusting to my setup solved the problems (at least after a reboot). The HDMI settings were quite different after I reset them to default - not sure what was going on there - but all fixed.

1 Like