On Wednesday 14 December 2005 22:14, you wrote: > Please try to upgrade to CVS or use a recent kernel. There was only > limited support for the Nova-T USB2 in the dvb-dibusb-drivers. I am now running a 2.6.14 kernel on the system in question and I get the same thing happening! Annoyingly, something (which I have yet to track down) is forcing the dvb-dibusb modules to load before hotplug has started which is why it was failing to load the firmware earlier on... If I leave it unplugged until the system has booted up, the firmware loads correctly. I even have a working remote now, though, although the keymapping is wrong so only a few buttons work... Using tzap on the USB device I get: $ tzap -r -a 1 "BBC ONE" using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' reading channels from file '/home/laz/.tzap/channels.conf' tuning to 722166670 Hz video pid 0x0258, audio pid 0x0259 status 1b | signal 073b | snr 0000 | ber 001fffff | unc 0000ffff | FE_HAS_LOCK status 1f | signal 073a | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK With tzap running like this, I can do cat /dev/dvb/adaptor1/dvr0 into a file and get a playable transport stream, so I think the 'signal 0000' is along the same lines as the 'snr ffff', i.e. the numbers don't actually mean anything yet! Femon on the working PCI card whiles vdr is using it gives: $ femon -a 0 using '/dev/dvb/adapter0/frontend0' FE: Conexant CX22702 DVB-T (TERRESTRIAL) status 1f | signal 0039 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0039 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0039 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0039 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0039 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK Running vdr using just the USB device and then using femon shows that there is no lock under those conditions. This all brings me back to the thought that it is down to vdr not being able to tune the USB device for some reason. I've just found a macro in the vdr source to add a 5 s timout to get a lock. Didn't help me when I enabled it, though. :( Cheers, Laz
