Web lists-archives.com

Hauppauge USB 2.0 DVB-T WinTV-Nova-T-Stick Lite

Dear folks @ V4L List,

I just write this, to mention some words on how to install and use the 

Hauppauge USB 2.0 DVB-T WinTV-Nova-T-Stick Lite.  

As usual, 
I found several infos on the net, but nothing was complete, and sometimes 
referring Hauppauge WinTV-Nova-T, thus it's not sure 
if this works all fine also for the "Lite" version. It was the cheapest dvb-t 
stick I was able to find, something like 20Euro.

And here is, how it works (Suse 11.1 distribution): 

After booting up linux and plugging the t-sick to some USB port, 



	Bus 002 Device 005: ID 2040:7060 Hauppauge Nova-T Stick 2



should show something like:

	dib0700: loaded with support for 7 different device-types                                                                                                                                   
	dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware                                                                                                        
	firmware: requesting dvb-usb-dib0700-1.10.fw                                                                                                                                                
	dvb-usb: did not find the firmware file. (dvb-usb-dib0700-1.10.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)                                          
	usbcore: registered new interface driver dvb_usb_dib0700  

This is, assuming v4l is installed, the firmware is missing. The latest working version on the net I found is the file:


now, the stick needs a file named 


as reported above.
Thus the latest firmware file needs to be renamed, and copied into the 



	cp Desktop/dvb-usb-dib0700-1.20.fw /lib/firmware/dvb-usb-dib0700-1.10.fw

now, I removed the stick and plugged it again to the USB port. 


shows now:

	dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware
	firmware: requesting dvb-usb-dib0700-1.10.fw
	dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.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 0 (DiBcom 7000PC)...
	MT2060: successfully identified (IF1 = 1220)
	input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:02.1/usb2/2-9/2-9.2/input/input5
	dvb-usb: schedule remote query interval to 150 msecs.
	dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected.
	usb 2-9.2: New USB device found, idVendor=2040, idProduct=7060
	usb 2-9.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
	usb 2-9.2: Product: Nova-T Stick
	usb 2-9.2: Manufacturer: Hauppauge
	usb 2-9.2: SerialNumber: 4028655835

This is, the firmware has been loaded and the driver strated. 
There are now new device enties seen with 

	ls /dev/dvb/adapter0/

	demux0     dvr0       frontend0  net0

thus, the device driver is installed, and the application can access the USB stick via these named pipes.
(I assume, the sometimes reported 


device entry is used togehter with some older version of the v4l driver software, I'm not sure at this point..)

Having said this, clearly some palyer/toos may not work. 
just to mention Xine, mplayer and kaffeine are.  And here is what needs to be done:

First, the default installation of Kaffeine is not supporting mpeg streams. Even if all codec are istalled,
Kaffeine can not find them correctly. The simplest way (I found) to fix this is to resinstall Kaffeine from some 
packman repository, not from Suse directly. This seems to be due to legal issues with suse, for what reason ever,
this problem disappears after installation of Kaffeine from Packman. 

After launching Kaffeine, a message appears like "no device found". This is, 
Kaffeine needs to be told explicitely, that the device 

	dvbt 0:0 

should be used. The device can be selected from the Kaffeine configuration menu. 

Kaffeine has a build in scanner for to determine the frequencies used from some sender.
Using Kaffeine to check for channels, the konsole output looks like:

	Not able to lock to the signal on the given frequency
	Frontend closed
	dvbsi: Cant tune DVB
	Using DVB device 0:0 "DiBcom 7000PC"
	tuning DVB-T to 578000000 Hz
	inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
	Transponders: 22/57
	it's dvb 2!	
	Reading SDT: pid=17
	RTL Television: sid=16405
	RTL2: sid=16406
	Super RTL: sid=16411
	VOX: sid=16418	
	Reading PAT: pid=0
	Reading PMT: pid=336
	Reading PMT: pid=352
	Reading PMT: pid=368
	Reading PMT: pid=544
	Frontend closed

This means, that sometimes there is no sender found, and the later text 
indicated four sender found on one frequency. (this is usual, because 
of compression usage: four tv-channels share one frequency).

Now, in the Rhein/Main area in the south near of Frankfurt am Main, something like 22 dvb-t sender are found.
These are listed in the kaffeine konfiguration window and can be seletcted and added to the ones actually 
used by kaffeine. 

Similar: xine

to find the channels, xine needs a configuration file, usually named channels.conf, loos like:


one line of ascii code for each channel. 
This file can be created using the v4l tool:

	scan /usr/share/dvb/dvb-t/de-Frankfurt

utilizing some default file for Frankfurt area. The prints someting like: 

scanning /usr/share/dvb/dvb-t/de-Frankfurt
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
0x0000 0x401d: pmt_pid 0x01d0 BetaDigital -- TELE 5 (running)
0x0000 0x4024: pmt_pid 0x0240 MEDIA BROADCAST -- Eurosport (running)
0x0000 0x402a: pmt_pid 0x02a0 MEDIA BROADCAST -- Bibel TV (running)
0x0000 0x4b00: pmt_pid 0x0b00 MEDIA BROADCAST -- rheinmaintv (running)

than, dumps the channels.conf lines on the konsole window...
Thus better to use:

scan /usr/share/dvb/dvb-t/de-Frankfurt > channels.conf

and pipe the stdout directly to the right filename (Cut and paste from the console output should work also).
Xine searches for this file in the 


directory, thus the file channels.conf needs to be created or copied in(to) this directory. 


PS.: Just for sake of completeness,

	modprobe -l |grep  dib




Armin Nückel
63303 Dreieich
Oisterwijkerstr. 49
mobil: +49(0)1728667251

video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe