Hauppauge WinTV-NOVA-T-500
This is a dual tuner DVB-T PCI card from Hauppauge. In actuality, its a USB device, also known as Bristol, with the host USB controller and USB dual-tuner (two DiB3000P and two MT2060) on a single PCI card. There aren't any real USB plugs or sockets involved. One Low Noise Amplifier (LNA) is present for both channels, but needs to be manually activated (see below).
See DiBcom USB2.0 DVB-T devices (based on the DiB0700) for further technical details.
This card requires Linux 2.6.19 or higher, as it requires the dib0700 driver. See this page for information.
You will find the model name and number on the box, under the bar code. Known to work cards have the following:
- WinTV-NOVA-T-500 model 289 SL-289-V2.0-UK
- List incomplete, please add
A new version appears to have been released (in the UK at least) which doesn't work with the normal Nova-T 500 driver. The card is labeled with the 'Diversity' feature stickers and the actual model number on the board is Nova-TD 500. The card has two aerial connectors. It uses a DiB0710 PCI controller which was never sold for Mass-Production. Support for this controller is not planned for now, sorry. A Linux driver would be a waste of effort given the low shipment volume.
Dibcom end of lifed the silicon. Message 1 Message 2
You will find the model name and number on the box, under the bar code. Known NOT to work cards have the following:
- On the box: WinTV-NOVA-T-500 model 289 SL-289-V2.1-UK - On the card: WinTV-NOVA-TD-500 DVB-T 68109 LF rev C1B5 - The box also has a sticker stating it is the diversity option and only suitable for intel cards. "When i put it in my athlon based XP box it blue screened as soon as i tried to load the drivers. I brought mine from Amazon.co.uk and there was no mention that this card was any different or wouldn't work with non-intel processors."
- List incomplete, please add
Issues
Disconnects
Some cards suffer from a serious problem. The USB DVB-T tuners seem to occasionally "disconnect" and reconnect during a tuning operation. In Linux 2.6.21 and earlier, this causes the kernel to oops requiring a reboot. With an old series of patches 1 2 3 (not needed anymore) then you won't get a kernel oops - instead, your Linux DVB application will just stop working. Exiting and restarting your application (more accurately, closing all the LinuxDVB devices and then waiting a second) should make everything work again.
Someone has 2 of these, which are different revisions of the board. This one is rock solid:
$ lspci 00:13.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) 00:13.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) 00:13.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
This one has the random USB disconnects problem:
$ lspci 00:13.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 00:13.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 00:13.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65)
Note that USB controller chip is a different revision number.
There are now patches that should fix this. See below.
Scanning
Scanning (or tuning with any AUTO parameters) is known to be broken in kernel 2.6.20, and probably earlier kernels too. Fixed in kernel 2.6.21; try [this patch] for older kernels.
Remote control
Grey top, black bottom.
There is a patch that makes the system recognize the remote system and provides full key codes, see below.
Making it work
Firmware
You will need the dvb-usb-dib0700-01.fw firmware file in
/lib/firmware
or the relevant place for your distribution.
Patches
Status on July 30, 2007
In order to fix the disconnects and get proper remote control support, you should apply the following patches in that order to the v4l-dvb tree:
* MT1060_IF1_freq_set.diff - 2.3K
* Sets the MT2060 IF1 frequency according to the calibration values stored in the EEPROM. It is supposed to enhance the signal quality
* Olivier Danet
* Post: http://linuxtv.org/pipermail/linux-dvb/2006-December/014926.html
* dibcom2.diff - 1.2K
* fix disconnects for NOVA-T-500 and NOVA-TD
* Jose Alberto Reguero
* Post: http://linuxtv.org/pipermail/linux-dvb/2007-July/019284.html
* nova-td_remote.diff - 2.6K
* Add remote keymap for the Hauppauge Nova-TD Stick
* Janne Grunau
* Post: http://linuxtv.org/pipermail/linux-dvb/2007-July/019349.html
* nova-t500_remote.diff - 760B
* Add remote control support for the Hauppauge Nova-T 500
* Janne Grunau
* Post: http://linuxtv.org/pipermail/linux-dvb/2007-July/019349.html
YMMV... Please report on the list.
Thanks for work by Patrick Boettcher, Olivier Danet, Janne Grunau, Jose Alberto Reguero and probably others.
On-board amplifier
You may want/need to turn on the on-board amplifier:
sudo gedit /etc/modprobe.d/options
Add:
options dvb-usb-dib0700 force_lna_activation=1
Sample kernel output
[ 31.101203] dib0700: loaded with support for 3 different device-types [ 31.138278] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [ 31.138318] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 31.138453] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 31.215273] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22 [ 31.216086] PCI: Setting latency timer of device 0000:00:1b.0 to 64 [ 31.223706] DVB: registering frontend 0 (DiBcom 3000MC/P)... [ 31.256177] MT2060: successfully identified (IF1 = 1245) [ 31.742377] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 31.742552] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 31.745816] DVB: registering frontend 1 (DiBcom 3000MC/P)... [ 31.748246] MT2060: successfully identified (IF1 = 1251) [ 32.244378] input: IR-receiver inside an USB DVB receiver as /class/input/input4 [ 32.244403] dvb-usb: schedule remote query interval to 150 msecs. [ 32.244406] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. [ 32.244430] usbcore: registered new interface driver dvb_usb_dib0700