[linux-dvb] Hauppauge WinTV Nova-T USB Stick

Paul McEnery pmcenery at gmail.com
Sat Apr 28 09:35:45 CEST 2007


Just bought a Hauppauge WinTV Nova-T stick and plugged it into Ubuntu
Fiesty (2.6.20). All I had to do was download the firmware and place
it in the correct directory. After plugging in, I get the following
messages:


[10323.652000] usb 5-5: USB disconnect, address 3
[10323.652000] dvb-usb: Hauppauge Nova-T Stick successfully
deinitialized and disconnected.
[10331.668000] usb 5-6: new high speed USB device using ehci_hcd and address 4
[10331.800000] usb 5-6: configuration #1 chosen from 1 choice
[10331.800000] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold
state, will try to load a firmware
[10331.832000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw'
[10332.008000] dib0700: firmware started successfully.
[10332.512000] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
[10332.512000] dvb-usb: will pass the complete MPEG2 transport stream
to the software demuxer.
[10332.512000] DVB: registering new adapter (Hauppauge Nova-T Stick).
[10332.704000] **WARNING** I2C adapter driver [DiBX000 tuner I2C bus]
forgot to specify physical device; fix it!

[10332.728000] DVB: registering frontend 0 (DiBcom 7000PC)...
[10332.728000] MT2060: successfully identified (IF1 = 1220)
[10333.192000] dvb-usb: Hauppauge Nova-T Stick successfully
initialized and connected.



Noticed the warning message, but decided to see if I was able to scan:

$ scan uk-<somewhere>
scanning uk-<somewhere>
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 754167000 0 2 9 1 0 0 0
>>> tune to: 754167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 754167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
(tuning failed)
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.


After a failed scan, I noticed the following output in dmesg:

[10416.900000] mt2060 I2C read failed
[10416.908000] mt2060 I2C read failed
[10416.916000] mt2060 I2C read failed
[10416.924000] mt2060 I2C read failed
[10416.932000] mt2060 I2C read failed
[10416.940000] mt2060 I2C read failed
[10416.948000] mt2060 I2C read failed
[10416.956000] mt2060 I2C read failed
[10416.964000] mt2060 I2C read failed
[10416.972000] mt2060 I2C read failed


I found a couple of other threads with similar problems, but none
seemed to have a solution:

http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015250.html
http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015287.html
http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015368.html


Does anyone know if there is a solution to this?



More information about the linux-dvb mailing list