Hauppauge WinTV-NOVA-T-500: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
(Added Freq setting patch from Olivier Danet)
m (removed the "no fix for disconnects" statement)
Line 1: Line 1:
This is a Hauppauge Dual-tuner PCI card. It's actually a USB device, with the host USB controller and USB dual-tuner on a single PCI card. There aren't any real USB plugs or sockets involved. See [[DVB_USB#DiBcom_USB2.0_DVB-T_devices_.28based_on_the_DiB0700.29 | DVB_USB]] for further details
This is a Hauppauge Dual-tuner PCI card. It's actually a USB device, with the host USB controller and USB dual-tuner on a single PCI card. There aren't any real USB plugs or sockets involved. See [[DVB_USB#DiBcom_USB2.0_DVB-T_devices_.28based_on_the_DiB0700.29 | DVB_USB]] for further details


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. If you apply all these patches [http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=8f4baced069c3fa0a9eeec6716d1928557df0cec;style=raw 1] [http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=45d23e0b79726e71f0a37dc6644a297a55403ec7;style=raw 2] [http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=1a4739838a8e4f09ff151d7dcb502ebb864f2e04;style=raw 3] then you won't get a kernel oops - instead, your LinuxDVB 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. There is currently (May 2007) no known fix for the underlying USB disconnect problem.
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. If you apply all these patches [http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=8f4baced069c3fa0a9eeec6716d1928557df0cec;style=raw 1] [http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=45d23e0b79726e71f0a37dc6644a297a55403ec7;style=raw 2] [http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=1a4739838a8e4f09ff151d7dcb502ebb864f2e04;style=raw 3] then you won't get a kernel oops - instead, your LinuxDVB 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.


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 [[http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=4e0f277a01f1;style=gitweb this patch]] for older kernels.
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 [[http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=4e0f277a01f1;style=gitweb this patch]] for older kernels.

Revision as of 13:04, 30 July 2007

This is a Hauppauge Dual-tuner PCI card. It's actually a USB device, with the host USB controller and USB dual-tuner on a single PCI card. There aren't any real USB plugs or sockets involved. See DVB_USB for further details

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. If you apply all these patches 1 2 3 then you won't get a kernel oops - instead, your LinuxDVB 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.

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.


I've got 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.



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,,,

thanks for work by Olivier Danet, Janne Grunau and Jose Alberto Reguero.

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
Retrieved from "https://www.linuxtv.org/wiki/index.php?title=Hauppauge_WinTV-NOVA-T-500&oldid=10404"