I have just acquired a Vero 4k and wanting to see if i can get my Hauppauge WinTV-DualHD usb tuner working. It seems there is a bit of work going on around tv tuners so it may not be supported yet?
I have it plugged into a power hub and out of the box on OSMC oct build, I can see the usb device detected, but there appears to be no DVB action. Running ‘dmesg | grep dvb’ returns nothing and there is no /dev/dvb folder
I installed tvheadend from the app store, which populated a number of firmware files in /lib/firmware. Including dvb-demod-si2168-b40-01.fw which I think is the one i require. Dmesg doesn’t log any mention of trying to download firmware either.
[ 4.028434] usb 1-2.5.5: New USB device found, idVendor=2040, idProduct=0265
[ 4.028446] usb 1-2.5.5: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 4.028452] usb 1-2.5.5: Product: dualHD
[ 4.028457] usb 1-2.5.5: Manufacturer: HCW
[ 4.028461] usb 1-2.5.5: SerialNumber: 0013942601
so it must be the model
Model 01590: Dual tuner for DVB-C, DVB-T and DVB-T2, has IEC connector, USB device ID 2040:0265.
Drivers
The Model 01590 device is supported since Kernel 4.7 (see commit https://git.linuxtv.org/media_tree.git/commit/drivers/media/usb/em28xx?id=11a2a949d05e9d2d9823f0c45fa476743d9e462b).
Looks like support for this has only been added as late as 4.11 for some models. We are indeed working on adding more tuner support; but currently we are aiming for 4.4 adapter support.
Until we move to a newer kernel; or there are suitable backports, the tuner won’t work at this time.
Hi, just checking, because this is the only thing that’s keeping my Vero 4K order on hold.
Do you have an estimate, when might support for Hauppauge dualHD be added?
EDIT: 8 days, no answer. I guess that’s all folks. Nevermind, maybe I’ll check back in a year or two.
I’m just about to test a kernel Sam’s sent me with added DVB support. I don’t have a Hauppauge but we seem to be getting some movement. I’d check back in days/weeks rather than years.
Sorry – must have missed this. I had a few tabs open and wanted to post a reply when I could tell you the fixes were actually merged, but Chrome sometimes crashes and as such, individual threads don’t get updated. Bugs / issues are tracked more directly via JIRA.
DVB-T2 improvements are done now. I haven’t the foggiest if that means your specific tuner will be supported. If you give me the VID/PID of your device, I can tell you. I know that Hauppage devices vary a fair bit.
I’m curious about the latest DVB-T2 improvements mentioned in the previous two posts. Are these already available in the Jan 2018 release or still in testing? Any updates on support for the Silicon Labs Si2168-40 demodulator or the Silicon Labs Si2157-30 tuner? As you know, support for those would most likely fix the OP’s stick as well as mine (and potentially a lot of others as well).
Thanks for the update. I’d be interested in the details.
Eventually almost all of these issues should be fixed with the 4.9 kernel upgrade planned for later this year. I wonder if it would be a good idea to go all-in now and solely focus on getting that out of the door, now that the Stretch upgrade is done. Might mean a bigger pay-off than individual DVB improvements.
Yep, I know, AMLogic… THE main issue of most SoCs, proper up-to-date kernel support. AMLogic’s own 4.9 kernel doesn’t seem to have received any updates over the past 9 months and mainlining S905X support still has a long way to go.
At least things are progressing which is already way better than what can be said about other SoCs (port and forget).
That’s (kind of) close I presume you depend on upstream to get that final feature integrated as it shouldn’t be trivial. Hopefully AMLogic still goes that extra length, despite the linux-meson project doing their work.
Anyhow, we’re getting off-topic here and I don’t want to hijack the thread, despite the interesting topic.