If we knew when it would be fixed, it would be fixed already.
Helpful!
YW. But seriously, it’s almost like asking how long it will take to find a needle in a haystack as far as I can see watching devs that are cleverer than me. It is being worked on.
I notice 720p has improved on 4.9 compared to 3.14 kernel. It looks a lot clearer now on 4k screen. Is it just me? Or was there a real improvement done?
I’m having some trouble updating, this is the SSH output when I follow the instructions above:
osmc@Vero:~$ sudo apt-get update && sudo apt-get dist-upgrade && reboot
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.debian.org/debian buster InRelease
Hit:3 http://ftp.debian.org/debian buster-updates InRelease
Hit:4 http://ftp.fau.de/osmc/osmc/apt buster InRelease
Hit:5 http://ftp.fau.de/osmc/osmc/apt videoimprovevero49 InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I’m on version 2020.06-1 currently - 3D has worked for me in the past, so I believe this is one of the test firmwares. Thanks for your help.
Please run grab-logs -a
(with a small a this time) and post the URL.
Please show the output from these commands:
dpkg -l vero364-kernel-osmc
dpkg -l "vero364-image*"
apt-cache depends vero364-kernel-osmc
See below, thanks for your help:
osmc@Vero:~$ dpkg -l vero364-kernel-osmc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=========================-============-============-================================================================
ii vero364-kernel-osmc:arm64 3.9.177 arm64 Kernel meta package bringing in the latest OSMC kernel for this
lines 1-6/6 (END)
osmc@Vero:~$ dpkg -l "vero364-image*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================-============-============-=====================================================
un vero364-image <none> <none> (no description available)
un vero364-image-4.9 <none> <none> (no description available)
ii vero364-image-4.9.113-20-osmc:arm64 20 arm64 Linux kernel binary image for version 4.9.113-20-osmc
un vero364-image-4.9.113-20-osmc-dbg <none> <none> (no description available)
ii vero364-image-4.9.113-22-osmc:arm64 22 arm64 Linux kernel binary image for version 4.9.113-22-osmc
un vero364-image-4.9.113-22-osmc-dbg <none> <none> (no description available)
osmc@Vero:~$ apt-cache depends vero364-kernel-osmc
vero364-kernel-osmc:arm64
Depends: vero364-image-4.9.113-22-osmc:arm64
For some reason, you’re still stuck on version 3.9.177 of package vero364-kernel-osmc. It should be 3.9.182.
Try these commands:
sudo apt-get update
sudo apt-get install --reinstall vero364-kernel-osmc
Thanks, it says reinstallation not possible, it cannot be downloaded. Output is below:
osmc@Vero:~$ sudo apt-get update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:2 http://ftp.debian.org/debian buster InRelease
Get:3 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]
Hit:4 http://ftp.fau.de/osmc/osmc/apt buster InRelease
Hit:5 http://ftp.fau.de/osmc/osmc/apt videoimprovevero49 InRelease
Get:6 http://security.debian.org buster/updates/main armhf Packages [250 kB]
Get:7 http://security.debian.org buster/updates/main arm64 Packages [249 kB]
Get:8 http://security.debian.org buster/updates/main Translation-en [140 kB]
Fetched 756 kB in 3s (284 kB/s)
Reading package lists... Done
osmc@Vero:~$ sudo apt-get install --reinstall vero364-kernel-osmc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reinstallation of vero364-kernel-osmc:arm64 is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Let’s try a few more things:
apt-mark showhold
apt-cache policy vero364-kernel-osmc
md5sum /var/lib/apt/lists/apt.osmc.tv_dists*
Thanks, see below:
osmc@Vero:~$ apt-mark showhold
osmc@Vero:~$ apt-cache policy vero364-kernel-osmc
vero364-kernel-osmc:arm64:
Installed: 3.9.177
Candidate: 3.9.177
Version table:
*** 3.9.177 100
100 /var/lib/dpkg/status
osmc@Vero:~$ md5sum /var/lib/apt/lists/apt.osmc.tv_dists*
0c0f4c3de5f0bdc0e28409e770d3b744 /var/lib/apt/lists/apt.osmc.tv_dists_buster_InRelease
d41d8cd98f00b204e9800998ecf8427e /var/lib/apt/lists/apt.osmc.tv_dists_buster_main_binary-arm64_Packages
d41d8cd98f00b204e9800998ecf8427e /var/lib/apt/lists/apt.osmc.tv_dists_buster_main_binary-armhf_Packages
d167105f0e6f49f3701b22defabac5e3 /var/lib/apt/lists/apt.osmc.tv_dists_videoimprovevero49_InRelease
d41d8cd98f00b204e9800998ecf8427e /var/lib/apt/lists/apt.osmc.tv_dists_videoimprovevero49_main_binary-arm64_Packages
d41d8cd98f00b204e9800998ecf8427e /var/lib/apt/lists/apt.osmc.tv_dists_videoimprovevero49_main_binary-armhf_Packages
Four of those files have the same MD5 value. That’s the MD5 of an empty file. I suspect there’ll be more empty files in that directory, so please take a look.
If all the empty files are restricted to apt.osmc.tv_dists*, run this:
sudo rm -f /var/lib/apt/lists/apt.osmc.tv_dists*
If there are other empty files in that directory, run this instead
sudo rm -rf /var/lib/apt/lists/*
Then run the usual
sudo apt-get update
sudo apt-get dist-upgrade
Thanks! This worked, and my 3D files have resumed working as well.
Great! Out of interest were there any other zero-length files?
I think so, but I wasn’t sure, so I just used the second command. Thanks again.
Had the green screen as well when I skipped 10 sec back or so, needed to restart the system to get it fixed, only Kodi wasn’t enough.
I think we’ve worked out the cause of the green screen now. Some users reported occurrences for several months, but if I have things right, the issue should only have started occurring from August.
If this is indeed the case, it’s caused by a race when loading firmware as requested by the kernel decoder module. The TA doesn’t guarantee to service this request in time before Kodi starts requesting frames.
There are a few ways of fixing this.
Regarding the green screen issue: guys, can you tell me which media types showed that issue? I’m only able to reproduce it with 4k h.265 videos.