Hi All,

I'm once again trying to get a picture from my WinTV Nova USB device, but I'm not convinced its looking at the USB port

Is there any way I can say that /dev/dvb/adapter0 is on USB ?

I tried the tzap program and it says it locks on BBC One, how do I display this picture ?

Thanks,

Karl.

Pb with Hauppauge Nova T USB 2, under Linux kernel 2.6.13.2 or 2.6.17.7 tested too :

udev service first recognize my card and makes directories : /dev/dvb/adapter0/dvr0, frontend0, demux0, et net0 but juste after (I think when entering KDE level 5) udev scan again my plugs and disconnect my Nova T nodes

Files samples : " dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 32). dvb-usb: MAC address: 00:0d:fe:02:ca:13 dvb-usb: schedule remote query interval to 100 msecs. dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully initialized and connected. usbcore: registered new driver dvb_usb_nova_t_usb2 dvb-usb: bulk message failed: -110 (2/0) dvb-usb: bulk message failed: -110 (2/0) dvb-usb: bulk message failed: -110 (2/0) dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully deinitialized and disconnected. dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge WinTV-NOVA-T usb2). dvb-usb: MAC address: 00:0d:fe:02:ca:13 dib3000: Found a DiBcom 3000P. DVB: registering frontend 0 (DiBcom 3000P/M-C DVB-T)... dvb-usb: schedule remote query interval to 100 msecs. dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully initialized and connected.

Aug 22 22:40:33 pcnew udev[2668]: configured rule in '/etc/udev/rules.d/dvb.rules' at line 1 applied, 'dvb0.dvr0' becomes '%c' <30>Aug 22 22:40:33 udev[2668]: creating device node '/dev/dvb/adapter0/dvr0' Aug 22 22:40:33 pcnew udev[2753]: removing device node '/dev/dvb/adapter0/dvr0' Aug 22 22:40:33 pcnew udev[2667]: configured rule in '/etc/udev/rules.d/dvb.rules' at line 1 applied, 'dvb0.demux0' becomes '%c' <30>Aug 22 22:40:33 udev[2667]: creating device node '/dev/dvb/adapter0/demux0' Aug 22 22:40:33 pcnew udev[2741]: removing device node '/dev/dvb/adapter0/frontend0' Aug 22 22:40:33 pcnew udev[2746]: removing device node '/dev/dvb/adapter0/net0' Aug 22 22:40:33 pcnew udev[2761]: removing device node '/dev/dvb/adapter0/demux0' "

1. tzap M6

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 714000000 Hz status 00 | signal ff3f | snr 0001 | ber 001fffff | unc 0000ffff | status 00 | signal ff3f | snr 0001 | ber 001fffff | unc 0000ffff | status 00 | signal ff3f | snr 0001 | ber 001fffff | unc 0000ffff | ...

1. scandvb -c

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x0000 dumping lists (0 services) Done.

1.

Who could take me out off hell ?

What happens if you plug it in after boot and run 'udevstart'?

I've had similar problems with PCI hardware on Gentoo, if the dvb drivers were compiled as modules, udev was not creating the relevant dev entries. To solve this I compiled a kernel with the drivers built in, despite other probelms the tuner appears to be working.

More relevant to your situation is perhaps:

<cant post a link, search google for "MythTV UK DVB-T Guide">

In the section Kernel 2.6.11-rc3 + DVB-t + UDEV (Project Utopia) it tells you have to configure udev to make /dev/dvb.


While i'd like to give it a go its working atm so dont count on it, will reply again if i do.

Regards