OK, also restart the vero at least twice while everything else is on too I find.
For my problem in general, restarting the vero doesn’t necessarily do anything, sometimes I can play these files a few times, others I just can’t. Seems random. Sometimes I can play one of them but not the other.
The 4+ is now also on 21.2 so can’t switch back to kodi 20.2 to check other things.
Can anyone give me some ssh commands I can check my installation with? did the obvious apt-get and dist-upgrade last night. (and quite often).
Did you try updating via the staging repository?
HI sam no - I dont know how to do that, or whats in it at the moment.
yes I can - would you like me to put it somewhere.
Would you like to wait a bit or do you know how to use SSH?
I’d suggest waiting a little for the next update
Sam
yep ssh is easy - I just dont know linux commands. I really need the commands to check my installation first though I think.
So I can do it fine - I just need others to tell me what to type.
- Login via the command line
- 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 - Run the following commands to update:
sudo apt-get update && sudo apt-get dist-upgrade && reboot - 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.
Seems to have stalled part way through the upgrade:
The following NEW packages will be installed:
vero564-image-4.9.269-83-osmc:arm64
The following packages will be upgraded:
armv7-network-osmc libamcodec-osmc mediacenter-skin-osmc vero5-mediacenter-osmc vero564-kernel-osmc:arm64
5 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 128 MB of archives.
After this operation, 84.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 Index of /osmc/osmc/apt bullseye-devel/main armhf armv7-network-osmc armhf 1.9.10 [3956 B]
Get:2 Index of /osmc/osmc/apt bullseye-devel/main armhf libamcodec-osmc armhf 2.4.0-1 [98.5 kB]
Get:3 Index of /osmc/osmc/apt bullseye-devel/main armhf mediacenter-skin-osmc all 21.2.1-2 [9888 kB]
Get:4 Index of /osmc/osmc/apt bullseye-devel/main armhf vero5-mediacenter-osmc armhf 21.2.0-4 [94.4 MB]
Get:5 Index of /osmc/osmc/apt bullseye-devel/main arm64 vero564-image-4.9.269-83-osmc arm64 4.9.269-83-osmc [23.9 MB]
Get:6 Index of /osmc/osmc/apt bullseye-devel/main arm64 vero564-kernel-osmc arm64 3.9.325 [1084 B]
Fetched 128 MB in 36s (3515 kB/s)
(Reading database … 45272 files and directories currently installed.)
Preparing to unpack …/0-armv7-network-osmc_1.9.10_armhf.deb …
Unpacking armv7-network-osmc (1.9.10) over (1.9.9) …
Preparing to unpack …/1-libamcodec-osmc_2.4.0-1_armhf.deb …
Unpacking libamcodec-osmc (2.4.0-1) over (2.3.0-1) …
Preparing to unpack …/2-mediacenter-skin-osmc_21.2.1-2_all.deb …
Unpacking mediacenter-skin-osmc (21.2.1-2) over (21.2.0-9) …
Preparing to unpack …/3-vero5-mediacenter-osmc_21.2.0-4_armhf.deb …
Unpacking vero5-mediacenter-osmc (21.2.0-4) over (21.2.0-1) …
Selecting previously unselected package vero564-image-4.9.269-83-osmc:arm64.
Preparing to unpack …/4-vero564-image-4.9.269-83-osmc_4.9.269-83-osmc_arm64.deb …
Unpacking vero564-image-4.9.269-83-osmc:arm64 (4.9.269-83-osmc) …
Preparing to unpack …/5-vero564-kernel-osmc_3.9.325_arm64.deb …
Unpacking vero564-kernel-osmc:arm64 (3.9.325) over (3.9.322) …
Setting up armv7-network-osmc (1.9.10) …
Progress: [ 52%] [##################################################…]
yep, looks like it’s stalled. what do I do now.
When the network package is updating as long as you don’t press enter the connection will come alive.
Otherwise you can just log in again as a separate session.
I logged back in and reupdated, seems like it was all done. Will check and report.
No change. It Played guardians a couple of times but not dune, then wouldn’t play anything. Changed TV type from PAL to ntsc in denon and both played a few times then would not. Changed it back to PAL and would still not play. Played another 4K non HDR10+ title then managed to play guardians once then no go again. Seems no rhyme nor reason to it.
Say what? Is that Denon doing some sort of video processing?
1 Like
Well it can do. Denons for decades have had this. It sets what the tv will accept. In any case ip (up) scaling on off or anywhere in between makes no difference but what may have happened was a change in the hdmi system that allowed it to play a few times then stop again.
I’m assuming there’s nothing in the debug logs. I can’t even find where its trying to play the titles!
So I guess I must be the only one with this problem?
Please, I’ve asked a few times now:
- was there anything in the logs
- what are the commands to check my osmc installation
Ta
We haven’t heard from @prisoner881 recently but it’s certainly not a universal problem. Having said that, his seems a bit different if switching output to SDR doesn’t help.
If there was anything obvious you would have heard.
There’s no automatic checking function.
I have some suspicions as to what’s happening but haven’t had time to dig into it. Can you upload somewhere enough of that Guardians or Dune to show the issue?
Edit: I just re-read the thread and see you have the same issue with vero 4k+ and 21.2. I can’t think what changed on 4k+ in March that would be relevant but we’ll check.
Cheers Grahamh. I can upload a little guardians to somewhere yes.
For the 4K+ when I dug it out it was still running 20.2 and was working fine, then I updated it to the latest and it too started doing the exact same thing as the V. I could perform a clean install on it and see if any change.
moved into a new thread.