There’s already a /dev/tee. Does it need to be /dev/tee0?
I’m not aure what you want to do here but generally you’d use the mknod command to create such a device.
Yes, it has to be /dev/tee0. I know that mknod would be correct. All I wanted to achieve is, that Kodi finds that node on startup. It doesn’t use it afterwards, because of some bootloader changes. So that touch/chmod is just to keep Kodi happy.
1 Like
It seems we’re now able to reproduce that green screen issue using an old testbuild. So no further action is needed right now. We’ll keep you informed!
6 Likes
Is it OK to update the “OSMC Update Available” popup even though using this 4.9 kernel version?
/Söder
Yes.
1 Like
A new update has been pushed with an updated kernel and Kodi updated to v18.9.
What does that mean? Is that the update I wrote about, or that I should do it via ssh?
/Söder
The changes are covered in the original post on this thread. Note that it’s not an exhaustive list.
Updating via My OSMC is supported. You don’t need to use SSH.
You likely only got the Kodi update and not the kernel update as I uploaded that a little after your post. You can check again for updates shortly or wait for the update prompt again.
@tanio99 I hate to do this to you 
but your depth formula for 3D subtitles seems to have gone wrong somewhere along the line. I was playing a bit of The Avengers today, and the subs are generally too close to the screen (too far away from the viewer).
pgs or other subtitles?
PGS.
Ok, I’ll have a look at it tomorrow.
Alas, very broken with my Marantz NR1711. I get no picture at all . Update appeared to go ok and then blank screen. I tried the usual things, switching inputs etc, no display. I connected directly to the TV and I did get a display. Back to the AVR and no display at all.
Also, when connected to the TV, I noticed the Vero is struggling really badly with thumbnails, my database is on a Synology NAS. My LE Pi’s recently upgraded to 18.9, and all the database info has been staying in sync across Pi’s and the Vero. With this new update, even when the Vero seems to have refreshed thumbnails, going in and out of the TV shows or Movies is really painful, very laggy, previously it was very slick.
I guess the priority would be the blank screen via the AVR. Without a functioning display I could do with some advice per terminal commands I might run to help diagnose.
I can’t think of any changes that would cause this.
Some logs would be helpful to see if something’s running in the background and doing this.
Usually a slow interface is a result of hotplugging the HDMI from one device to another without a full HDMI chain refresh, which causes a resolution mismatch. A reboot may fix this lag.
The current update introduces a 100ms delay in PHY toggling, as we suspected a timing issue with your AVR. This can be adjusted as an environment variable. The easiest way to do this would be to edit /usr/bin/mediacenter and append the Kodi startup line with the phydelay environment variable.
I.e. changing:
sudo -u osmc MALLOC_MMAP_THRESHOLD_=8192 LIRC_SOCKET_PATH=/var/run/lirc/lircd $KODI --standalone -fs; CODE="$?"
to
sudo -u osmc MALLOC_MMAP_THRESHOLD_=8192 phydelay=X LIRC_SOCKET_PATH=/var/run/lirc/lircd $KODI --standalone -fs; CODE="$?"
But ideally, it would be good to see some logs first.
Sam,
Despite all the good work, i installed the last update and none of my 4k test files and movies will play anymore,
This is the screen that pops up.
Lg chess demo gives the same
The world in hdr 4k gives the same
Dolby atmos trailer leaf 1080 works
Here are the logs
1 Like
Thanks for the report.
We’ll check it out.
I can certainly see an issue
[ 201.583276] [0]timeout_process decoder timeout
[ 201.584250] [0]VH265: output first frame
[ 201.584263] video first pts = 1
[ 201.584437] DI bypass all 3840x2160-0x501000.
[ 201.638295] hdmitx: video: Colorimetry: bt2020nc
[ 201.638304] hdmitx: video: HDR data: EOTF: HDR10
[ 201.638339] hdmitx: video: Master display colours:
Primary one 0.2650,0.6900, two 0.1500,0.0600, three 0.6800,0.3200
White 0.3127,0.3290, Luminance max/min: 1000,0.0000
[ 201.638347] hdmitx: video: Max content luminance: 0, Max frame average luminance: 0
[ 201.807296] [0]timeout_process decoder timeout
[ 202.023305] [0]timeout_process decoder timeout
[ 202.239262] [0]timeout_process decoder timeout
[ 202.459255] [0]timeout_process decoder timeout
[ 202.683259] [0]timeout_process decoder timeout
[ 202.899249] [0]timeout_process decoder timeout
[ 203.119247] [0]timeout_process decoder timeout
[ 203.335251] [0]timeout_process decoder timeout
[ 203.555247] [0]timeout_process decoder timeout
[ 203.779246] [0]timeout_process decoder timeout
[ 203.995253] [0]timeout_process decoder timeout
[ 204.215247] [0]timeout_process decoder timeout
[ 204.439249] [0]timeout_process decoder timeout
[ 204.659257] [0]timeout_process decoder timeout
[ 204.883248] [0]timeout_process decoder timeout
[ 205.107268] [0]timeout_process decoder timeout
[ 205.323272] [0]timeout_process decoder timeout
[ 205.539299] [0]timeout_process decoder timeout
[ 205.755266] [0]timeout_process decoder timeout
[ 205.971270] [0]timeout_process decoder timeout
[ 206.195272] [0]timeout_process decoder timeout
[ 206.415261] [0]timeout_process decoder timeout
[ 206.639264] [0]timeout_process decoder timeout
[ 206.855260] [0]timeout_process decoder timeout
[ 207.079334] [0]timeout_process decoder timeout
[ 207.303319] [0]timeout_process decoder timeout
[ 207.531279] [0]timeout_process decoder timeout
[ 207.751249] [0]timeout_process decoder timeout
[ 207.975250] [0]timeout_process decoder timeout
[ 208.195255] [0]timeout_process decoder timeout
[ 208.415256] [0]timeout_process decoder timeout
[ 208.635245] [0]timeout_process decoder timeout
[ 208.859256] [0]timeout_process decoder timeout
[ 209.079258] [0]timeout_process decoder timeout
[ 209.299257] [0]timeout_process decoder timeout
[ 209.519248] [0]timeout_process decoder timeout
[ 209.739249] [0]timeout_process decoder timeout
[ 209.963246] [0]timeout_process decoder timeout
[ 210.187250] [0]timeout_process decoder timeout
[ 210.407246] [0]timeout_process decoder timeout
[ 210.627247] [0]timeout_process decoder timeout
[ 210.847245] [0]timeout_process decoder timeout
[ 211.067259] [0]timeout_process decoder timeout
[ 211.287247] [0]timeout_process decoder timeout
[ 211.507246] [0]timeout_process decoder timeout
[ 211.679316] [0]vdec requested to be disconnected
[ 211.679376] [0]vh265_work_implement: force exit end
[ 211.680320] PPMGRVPP: info: task: quit
Hi,
Same issue/symptoms for me…
Regards
Weasel
1 Like
Noted. That’s why these are still test builds
Cheers
Sam
2 Likes
Something ghastly seems to have happened to my Vero since updating this evening. Wired Ethernet no longer seems to work correctly. And 3D movies that were playing perfectly in the last build are suddenly playing with lots of on-screen corruption.
Here are some logs for 3D playback:
https://paste.osmc.tv/metadakora
EDIT: like other users, I’m also seeing issues with 4K playback.
1 Like
I cut the power to my Marantz AVR and now have a display from the Vero.
However, the network side of the Vero is now so flaky I can’t do any meaningful testing. In spite of re-boots, the experience of browsing my TV library is pretty painful. I would post a log but the Log Uploader under My OSMC is crawling away with the spinning circle, and I have to turn in now. Will check in the morning to see if the log upload has worked.
I just powered up my other 4.9 Vero (on .113-25) and that’s as slick as ever at browsing the database.
EDIT: left overnight, the log uploader is not working. Via the GUI it gets to “combining and writing logs” and then the spinning circle just spins. I tried via the command line and it appeared to be hanging, so I had to quit out of that. If there is anything I can run from the terminal to help diagnose, please let me know.