Hi,
I am trying to setup a DVB-T2 USB stick on my Vero4K but without any luck yet.
Here are the full logs: http://paste.osmc.io/yubobiheca
The device ID with lsusb:
Bus 001 Device 005: ID 2040:0264 Hauppauge
Then I followed this link https://linuxtv.org/wiki/index.php/Hauppauge_WinTV-soloHD
to install the firmware dvb-demod-si2168-b40-01.fw to /lib/firmware.
But dmesg still only reports that it is aware of new USB hardware but no firmware seems to be loaded:
[ 3.911409] usb 1-2.3: New USB device found, idVendor=2040, idProduct=0264
[ 3.911422] usb 1-2.3: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 3.911427] usb 1-2.3: Product: soloHD
[ 3.911432] usb 1-2.3: Manufacturer: HCW
[ 3.911436] usb 1-2.3: SerialNumber: 0011545127
...
Your device should work as soon as Sam found the time and the means to backport these drivers, which he’s already looking into. The only extra bit needed to support your device (which is basically the same as mine) would be to add its USB ID (from the commit you mentioned). The drivers themselves should be the same.
At least Sam will now have access to at least two testers as soon as he gets the code backported from the 4.4 kernel
Hey @olli, did you already install the latest OSMC update and check whether your DVB device now works as expected? It should be detected properly now. Unfortunately mux scanning doesn’t yet work for my (more or less identical) device, so I’m interested to hear whether it works for yours.
Hi, my vero now runs with version 2017.05-2 and it seems to download the required firmware:
dmesg
...
[ 17.697108] si2168 2-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 17.915062] si2168 2-0064: firmware version: B 4.0.11
[ 17.920923] si2157 3-0060: found a 'Silicon Labs Si2157-A30'
[ 17.969018] si2157 3-0060: firmware version: 3.0.5
However, after configuring the device in tvheadend I was not able to find any channels. Probably this is the same problem you have @brevilo ?
After disabling tvheadend server I ran a locally compiled w_scan and get this:
./w_scan -ft -c DE
w_scan version 20170107 (compiled for DVB API 5.10)
using settings for GERMANY
DVB aerial
DVB-T Europe
scan type TERRESTRIAL, channellist 4
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
WARNING: YOU ARE USING OUTDATED DVB DRIVERS.
/dev/dvb/adapter0/frontend0 -> "Silicon Labs Si2168" doesnt support TERRESTRIAL -> SEARCH NEXT ONE.
main:4007: FATAL: ***** NO USEABLE TERRESTRIAL CARD FOUND. *****
Please check wether dvb driver is loaded and
verify that no dvb application (i.e. vdr) is running.
Now, I am running out of ideas.
Suggestions, anyone?
What’s the exact error message? When you run the network scan in the Tvheadend web interface you can pull up the system log by clicking on the double-up-arrow in the lower right corner.
WARNING: YOU ARE USING OUTDATED DVB DRIVERS.
/dev/dvb/adapter0/frontend0 -> "Silicon Labs Si2168" doesnt support TERRESTRIAL -> SEARCH NEXT ONE.
main:4007: FATAL: ***** NO USEABLE TERRESTRIAL CARD FOUND. *****
That might actually be misleading and might also be due to a failed ioctl call. I’d have to look at the code to verify that though. But it’s good to have another pointer for investigation.
Is there anything we can do to speed up the support for this device? It would be really great. It was actually the main reason why I bought the vero4k…
@olli There’s a patched Tvheadend version available you want to try. I doubt that it’ll fix the issue for your device (as it didn’t for mine) but it’s definitely worth a try.
