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

From LinuxTVWiki
Jump to navigation Jump to search
m (Trivial spacing fix.)
(Remote control support status update.)
Line 65: Line 65:
=== Remote control support ===
=== Remote control support ===


At least the 70001 version has an IR sensor. Though as of 11 August 2007 there is no support for the sensor in v4l-dvb, it is known to work with Hauppauge's 45-button remote control and will handle signals from similar remote controls.
Supported in v4l-dvb as of 18 August 2007. The 70001 version has an IR sensor, and the 70009 version is listed by Wikipedia as having one. It works with Hauppauge's 45-button remote control and will handle signals from similar remote controls.


[http://www.linuxtv.org/pipermail/linux-dvb/2007-August/019479.html This patch] implements support for the IR sensor; if you have problems with a flood of "unknown key" messages in the kernel log, you'll also need [http://www.linuxtv.org/pipermail/linux-dvb/2007-August/019493.html this patch] (it is not cleanly applicable to recent trees, but it is an easy one-liner to do by hand).
If you have problems with a flood of "unknown key" messages in the kernel log, you'll also need [http://www.linuxtv.org/pipermail/linux-dvb/2007-August/019493.html this patch] (it is not cleanly applicable to recent trees, but it is an easy one-liner to do by hand).


{{Note|The IR support patch still hasn't made it into the tree, and has not yet received any [http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb feedback] (as of 13 August 2007), and the log-flood patch should currently be regarded as a [http://www.linuxtv.org/pipermail/linux-dvb/2007-August/019796.html temporary workaround].}}
{{Note|The log-flood patch should currently be regarded as a [http://www.linuxtv.org/pipermail/linux-dvb/2007-August/019796.html temporary workaround].}}


==External Links==
==External Links==

Revision as of 00:42, 19 August 2007

WinTV-Nova-T-Stick

A DVB-T USB device from Hauppauge.

Note: Currently, the Nova-T Stick (70009) is known to suffer from I2C errors. Updating to current Hg drivers and using new firmware should cure this.


Features

  • Microtune MT2060 tuner
  • Dibcom DiB7700 DVB-T demodulator & USB 2.0 controller
  • IR receiver (not currently supported)

Identification

USB ID Model no. Version Tuner Supported from
Device Box
2040:7050 70001 Model 294 SL-294-V2.0-UK DiB7700M 2.6.19
2040:7060 70009 Model 1132 DiB7700P 2.6.20
  • One model number is above the MAC address on the label on the underside of the device.
  • The other model number and the version information are on the base of the box, below the bar code.
Note: see Peter's Aug 9/2007 note regarding boxes in the discussion page

Making it work

Firmware

You will need the dvb-usb-dib0700-03-pre1.fw firmware file in /lib/firmware or the relevant place for your distribution.

Drivers

Status on 11 August 2007

Just use Mercurial by following the How_to_install_DVB_device_drivers instructions.

Sample kernel output

This is for the 70001 version, using the driver in Linux 2.6.22.1.

usb 1-10: new high speed USB device using ehci_hcd and address 8
usb 1-10: configuration #1 chosen from 1 choice
dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw'
dib0700: firmware started successfully.
dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T Stick).
DVB: registering frontend 2 (DiBcom 7000MA/MB/PA/PB/MC)...
MT2060: successfully identified (IF1 = 1220)
dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected.

Remote control support

Supported in v4l-dvb as of 18 August 2007. The 70001 version has an IR sensor, and the 70009 version is listed by Wikipedia as having one. It works with Hauppauge's 45-button remote control and will handle signals from similar remote controls.

If you have problems with a flood of "unknown key" messages in the kernel log, you'll also need this patch (it is not cleanly applicable to recent trees, but it is an easy one-liner to do by hand).

Note: The log-flood patch should currently be regarded as a temporary workaround.

External Links