Hauppauge WinTV-Duet Dual DVB-T Receiver


Hi all,

I’m currently running OSMC on a Pi2 with a Hauppauge WinTV-Duet Dual DVB-T Receiver, and to get it to work, I have to do the following:

cd /lib/firmware
sudo wget http://linuxtv.org/downloads/firmware/dvb-usb-dib0700-1.20.fw

sudo nano /etc/modprobe.d/options.conf

options dvb_usb disable-rc-polling=1
options dvb_usb_dib0700 force_lna_activation=1

At which point it works great - my question is, will the same work if I move over to a Vero 4K(+) or will my tuner not be supported?




Can you tell us the VID/PID of the device?


FYI: Hauppauge wintv dualhd on Vero 4k+ - just one tuner


He might not even get one tuner to work.
Hauppage internals often vary; even if they keep the same product name.

lsusb would allow us to see if the device is similar.


Hi Sam,
The device is Bus 001 Device 006: ID 2040:5200 Hauppauge
On my RPi, both tuners function - it’s much older than the HD capable dual tuner that Hauppauge now manufacture.


Any confirmation on this? I don’t want to break my currently working setup whilst stepping up to another device…


Not sure. I will be updating DVB drivers to 4.21 soon; so things should work well then.

Just keep an eye on this thread


I’ve decided to take the risk anyway; I can’t see why it should stop working as it does at the moment. I’m assuming that you can SSH into a Vero in the same fashion that you do with an RPi! If I get to it before you do, I’ll let you know :slight_smile:


So… The device appears to TVHeadEnd once the firmware is loaded as above, but it fails to scan on the Vero 4K+ after adding the relevant muxes. On the Pi I had this behaviour until I added the /etc/modprobe.d/options.conf - is this ignored on the Vero, or do I need to make the alterations elsewhere? Happy to perform any requested tests etc!


It should be the same.
What changes did you need to make?



I had to add these lines (which are the only ones in there now:


Have you tried them on Vero? This is unclear


I’ve done exactly as I would do on an RPi (that works). On the Vero, scans don’t start - they all immediately go to PEND and don’t progress. I’ve added the firmware for the stick (as it’s missing - this is the case on all Linux distros by default), and added the necessary lines to the modprobe.d conf file.

It could be kernel related, it’s rather old on the Vero. I found reference to a minimum of 4.10 but can’t be sure about that as it was in French!


Ok — might be an idea to wait for the DVB updates for now



Just so that this issue is a little better annotated; once the firmware and modprobe.d changes are made, both of the tuners appear on the Vero, but fail to scan the muxes.


The same stick plugged into (any) of my Pi’s 1/2/3 running OSMC with the same alterations and configuration, scan and discover upwards of 200 channels in total.


Thanks for the data point.
When v18 is out of the door, I’ll look at moving to the 4.21 DVB stack.