This device appears to be a Nova-T Stick variant.
- Microtune MT2060 tuner
- Dibcom DiB7700P DVB-T demodulator & USB 2.0 controller
|USB ID||Model no.||Version||Tuner||Supported from|
Making it work
August 21, 2008 - New firmware file fixing the last cause for i2c errors and disconnects and providing a new, more modular i2c request formatting.
You will need the dvb-usb-dib0700-1.20.fw firmware file in /lib/firmware or the relevant place for your distribution.
You may need to change the name of the file to dvb-usb-dib0700-1.10.fw or create a link until the driver code reflects that change.
For archival purposes: dvb-usb-dib0700-1.10.fw firmware file
August 29,2008 - Issues with Firmware 1.20. Some issues have been found with the latest version of the firmware. Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch.
November 15,2008 - Issues with Firmware 1.20.
- The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers
dvb-usb-dib0700-1.20.fw firmware fileis now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed. The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect.
- The mercurial drivers have been changed so they now load 1.20 firmware. To revert to 1.10 firmware you need to rename your firmware file to dvb-usb-dib0700-1.20.fw or provide a link of that name.
- To avoid spurious remote control signals with 1.20 firmware, you need to edit /etc/modprobe.d/options or from Ubuntu onwards /etc/modprobe.d/options.confand add:
options dvb_usb disable-rc-polling=1
November 28,2008 - i2c errors. Changes were made to the remote control drivers on November 16,2008 to correct the repeat key problem. The card is generally stable for dual tuner reception and remote control function with Firmware 1.20.
November 10,2009 - mt2060 I2C write failed. Possible regression of a driver bug raised against Ubuntu running 2.6.27-14 and 2.6.31-2.17 causing mt2060 I2C errors in MythTV useage with firmware 1.20. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397696 Recommend check the kernel extensions listed here for Low Noise Activation and rc_polling are loaded with correct config file name for your distribution, EIT listings information is turned off until a suitable delay (500ms-1000ms)is added to a single card (not both) and the card has correctly been added to the database as two tuners (no additional NULL entries) in the mythtv recordcard table.
Status on 25 January 2008
dvb_usb_dib0700 38152 0 dib7000p 23560 2 dvb_usb_dib0700 dib7000m 22404 1 dvb_usb_dib0700 dvb_usb 27020 1 dvb_usb_dib0700 dvb_core 82388 2 dvb_usb dib3000mc 20232 1 dvb_usb_dib0700 dibx000_common 11780 3 dib7000p,dib7000m,dib3000mc dib0070 15236 2 dvb_usb_dib0700
Sample kernel output
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 myTV.t' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'Hauppauge myTV.t' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge myTV.t) DVB: registering frontend 0 (DiBcom 7000PC)... DiB0070: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input4 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Hauppauge myTV.t successfully initialized and connected. usbcore: registered new interface driver dvb_usb_dib0700
Specific to the model
The myTV.t is not supplied with a remote control. However using a remote sourced individually is reported to be working.