So my sources.list should be like this:
deb Index of /debian buster main contrib non-free
deb Index of /debian buster-updates main contrib non-free
deb http://security.debian.org/ buster-updates main contrib non-free
deb http://apt.osmc.tv buster main
deb http://apt.osmc.tv buster-devel main
Yes
http://paste.osmc.tv/reruliyono.xml
I can’t make head nor tail of this
I also have an issue with my Vero OSMC not uploading logs… Am I supposed to be able to upload from My OSMC? I get a successful upload message pointing to https://past.osmc.tv/
I just turned on debug logging for this.
http://paste.osmc.tv/qacuhiwodu.xml
Was this log from the time that the Addon’s where migrated? Because there is nothing like that written in the logfile. If it was in the past and you want to figure out only possible way might be to look at the disabled addons.
The first log was.
I enabled debug logging and restarted.
Then get the message it is migrating (on the splash screen) and then the popup message saying addon couldn’t be migrated but not saying which addon
Then I turned off logging.
I have also gone through the list of addons and uninstalled every disabled one that had an uninstall button
I just updated to Kodi 19 on my Vero 4K, so far everything works, except one strange network issue.
When pinging external domains everything works fine, but when pinging internal hostnames they don’t resolve.
I am connected to LAN with an external USB 1Gbit adapter. After the update my SMB shares won’t connect: “No route to host” error, so I sshed to the Vero and tried to ping the hosts:
osmc@osmc:~$ ping fileserver
ping: bad address ‘fileserver’
or
osmc@osmc:~$ nslookup fileserver
Server: 192.168.169.4
Address: 192.168.169.4#53
External:
osmc@osmc:~$ ping google.de
PING google.de (142.250.185.195): 56 data bytes
64 bytes from 142.250.185.195: seq=0 ttl=118 time=15.344 ms…
I then switched from manual network setting (which uses my internal Windows DNS server) to DHCP (which uses my router’s DNS), but the result stays the same.
/etc/resolv.conf shows the correct nameserver.
Pinging the internal hosts also works.
I now switched the SMB shares from hostname to IP address as a workaround.
Any idea, what may cause this? Any other things, I may try?
Thanks in advance,
Marc
So 192.168.169.4 is your Windows DNS Server?
I would suggest to install tcpdump and check if the packets go out/in from the Vero if you do a lookup (tcpdump -n -i any udp port 53)
@fzinken I did and crosschecked with another Debian VM I am running (DHCP).
It seems that the search name was missing (the VM got it from DHCP, Vero did not).
Vero (DHCP) requests “fileserver”, which gives an error, the Debian VM requests fileserver.fritz.box (fritz.box is the router), which the router resolves.
After switching the Vero back to manual configuration and entering the same data as before (Windows DNS), DNS resolve now works. Seems some config file has been rewritten be MyOSMC which fixes the problem.
Thanks for your help!
Marc
I think the myOSMC service is crashing randomly. I haven’t been able to capture a of log of it yet (the random part is driving my crazy), but my symptom is that if I try and open myOSMC I often get a message saying the service is unavailable and to try again later. Trying again later never seems to help, but if I reboot the Vero 4K+ then it’s fine again for awhile.
I’ve been seeing that as well, on a plain, clean new installation, with the only add-on being the Aeon Nox: SiLVO skin. I re-installed, this time without adding the Aeon Nox: SiLVO skin and the issue has not come back. Coincidence?
Is it normal that I still see “OSMC November 2020 2020.11-1” in My OSMC?
I feel like I remember seeing this report, but now I can’t find it, so:
Unable to change skins. I’m using Arctic Horizon, and if I try and change to either the OSMC skin or Estuary, it just bounces me back to Arctic Horizon. Not sure how I was able to switch to Arctic Horizon in the first place, but I guess it’s a good thing I really like the skin.
'-)
Yes.
Randomly my resolution is changed from 1080p to 1024x768.
Executing dmesg in the terminal I get this errors:
[47469.587978] cectx c810023c.aocec: cec unsupported cmd:0xa6, halflg:0x0
[47469.735764] cectx c810023c.aocec: cec unsupported cmd:0x84, halflg:0x0
[47469.874207] cectx c810023c.aocec: cec unsupported cmd:0x84, halflg:0x0
[47470.026014] cectx c810023c.aocec: cec unsupported cmd:0x90, halflg:0x0
[47470.449472] cectx c810023c.aocec: cec unsupported cmd:0x84, halflg:0x0
[47471.083910] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47472.099189] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47472.235728] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47472.499534] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47473.079238] cectx c810023c.aocec: cec unsupported cmd:0x84, halflg:0x0
[47473.558129] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47474.006142] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47474.229212] cectx c810023c.aocec: cec unsupported cmd:0x84, halflg:0x0
[47474.794124] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47476.698177] cectx c810023c.aocec: cec unsupported cmd:0x84, halflg:0x0
[47476.856068] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47477.170608] cectx c810023c.aocec: cec unsupported cmd:0xa7, halflg:0x0
[47479.136969] cectx c810023c.aocec: cec unsupported cmd:0x84, halflg:0x0
[47479.294974] cectx c810023c.aocec: cec unsupported cmd:0x87, halflg:0x0
[47479.610557] cectx c810023c.aocec: cec unsupported cmd:0xa7, halflg:0x0
My AVR is a Denon X3700H.
Hello Guys,
I’m the new guy and i have a question.
If I’m installing the beta version like sam listed above will i get, after the “official” version hits the store, also the beta releases?
I really would like to watch my HDR files ( i have a Espon LS10000 projector which is capable of playing 4K files but only in SDR (but the projector is calibrated to REC2020)).
So i do need the HDR SDR function 
If you follow the above steps you will get Beta versions till you remove deb http://apt.osmc.tv buster-devel main from /etc/apt/sources.list.
After you remove that line you will get the next stable release automatically when it is published.
The skin change works after 3, 4, 5 or more times. Sometimes a reboot helps.
This is odd. Presumably it means REC2020 primaries and, possibly, a BT2100 tonecurve. Did you calibrate it yourself?
If you are feeding it with REC709 material (and you will be because that’s all it claims to support) you will be getting wrong colours.
If you want to discuss this it would be better to start a new thread. It has little to do with this testing release. Vero has always converted HDR to SDR - we’re just doing it a bit differently now.
I’m using an HD Fury Linker to trick the player into playing rec2020 to the epson. Works perfect with my Panasonic player when playing UHDs.