For some time, DVB support on Vero 4K hasn’t been in the shape that we want it to be. There are two reasons for this:
The Vero 4K kernel version is older than desired (a SoC vendor limitation currently).
The Vero 4K kernel is 64-bit (Aarch64), but the userland is 32-bit. This creates some issues with DVB FE ioctls
The most popular adapter on the Vero 4K is the OSMC branded DVB-T2 dongle. I’ve backported support for the second tuner which handles DVB-T2 and DVB-C in this commit.
This can be tested by running the following commands:
There is a second kernel available for testing. This uses the media_build tree to backport all DVB tuner support from Linux 4.9. Ideally, this is the approach we would like to use, but there seems to be issues with this, at least with the OSMC tuner. For those with a non OSMC tuner, or using a different DVB system, please try this kernel instead:
If you use the second kernel, I’d suggest stopping TVHeadend (sudo systemctl stop tvheadend) temporarily, and using this version of w_scan which has been patched against the new kernel headers which have been adjusted for 64-bit → 32-bit pointers.
great to see these improvements! I do have a non-OSMC tuner (a Terratec Cinnergy S2 USB Box, more details) which worked fined with a Raspberry Pi but not with the Vero 4k.
I’ll try your test build for this device soon, but I didn’t understand your last comment about the w_scanto be used. Does tvheadendonly fail to do the initial scan but should work afterwards with the scan results from your patched w_scan?
First of all thanks for providing the beta kernels!
I’ve installed the first one, uname shows me “3.14.29-62-osmc” and lsmod indicates the kernel driver to be loaded. Running a scan in either TVH or with w_scan (TVH disabled) doesn’t recognize any (known) muxes.
Apart from that, dmesg doesn’t contain any reference to loading the firmware for the MN88473 and when I plug in the dongle after Vero has been booted it crashes.
Any hints on how I can fix / improve the initialization of the dongle? Does it make any difference which of the USB ports to be used?
New OSMC DVB-T2 arrived today (delayed by snow)! Plugged in and set up. Did not show DVB-T2 adapter - only DVB-C and two DVB-T adapters. Ran code shows by @sam_nazarko. Rebooted and now tvheadend only shows one device - Realtek RTL2832 (DVB-T) #0 : DVB-T #0.
uname -a
Linux OSMCVero 3.14.29-62-osmc #1 SMP Mon Mar 5 17:00:37 UTC 2018 aarch64 GNU/Linux
You will never get anything listed as ‘DVB-T2’. All adapters report as DVB-T even if they do T2. The OSMC stick has two DVB-T tuners - one does just DVB-T, the other DVB-T and DVB-T2. It’s the second one (panasonic) which is giving trouble.
There is only one adapter - one item plugged into USB but it only shows one DVB-T entry. It did show two Realtek and one Panasonic entry earlier before I ran sudo dpkg -i vero3-image.deb a second time. That could be my mistake!
I can confirm what graham mentioned, at least when the dongle is already plugged in during boot time.
Did anyone successfully plug the OSMC dongle into an already running Vero 4K without making it crash?
Apart from not working hot-plug, the problem is mainly about not loading the required firmware to the dongle. According to previous experience this is necessary to actually receive something with the stick, even though it already shows up in TVH without having the firmware loaded.