Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: difficulty getting Nova-T working with dvbtune



(It's clear that you can't receive the Berlin DVB-T channels;)

Please don't expect the driver to tune to any transmitter after 
initialisation, this is a feature for developers here, it's nowhere 
specified and just a hidden 'test-feature'. Don't count on it.

It's up to the application to tune. Try to create a channel list for any 
zap program you like to use, the simple tzap in the DVB/apps/szap 
directory will do fine, all other programs which can handle OFDM 
frontends should do as well.

Some applications get mislead because they don't clear outstanding 
events from the event queue after opening the device. The NEWSTRUCT 
driver does this for you, so even buggy applications should not run in 
troubles, the old driver did not. Please use the NEWSTRUCT branch, there 
are many other problems fixed, too.

Holger



Glyn Davies wrote:
> Hi there folks,
> 
> I've been lurking around for a while, and finally got around to getting a Nova-T card.
> 
> As expected under Windows the picture is great, but the software is terrible so I am now
> trying to get the card working under Linux.
> 
> I have downloaded the driver (from Henning Holtschneider's web site - thanks btw) and compiled up.
> 
> Everything seems to work, I've traced the tuner being detected, etc.  However when I attempt to tune
> I get:
> 
> tuning DVB-T to 505833000
> Getting frontend event
> Received failure event
> 
> On startup (installing the modules) it seems the module attempts to tune to a frequency:
> 
> Jun 30 11:35:17 tv kernel: i2c-core.o: i2c core module
> Jun 30 11:35:17 tv kernel: Linux video capture interface: v1.00
> Jun 30 11:35:18 tv kernel: i2c-core.o: driver VES1893 DVB demodulator registered.
> Jun 30 11:35:18 tv kernel: i2c-core.o: driver VES1820 DVB demodulator registered.
> Jun 30 11:35:18 tv kernel: i2c-core.o: driver L64781 DVB demodulator registered.
> Jun 30 11:35:18 tv kernel: init_SP8870:
> Jun 30 11:35:18 tv kernel: i2c-core.o: driver SP8870 DVB demodulator registered.
> Jun 30 11:35:18 tv kernel: i2c-core.o: driver tda8083 DVB demodulator registered.
> Jun 30 11:35:18 tv kernel: i2c-core.o: driver stv0299 DVB demodulator registered.
> Jun 30 11:35:18 tv kernel: i2c-core.o: driver i2c TV tuner driver registered.
> Jun 30 11:35:18 tv kernel: saa7146_core.o: saa7146(1): bus:2, rev:1, mem:0xd18f0000.
> Jun 30 11:35:18 tv kernel: i2c-core.o: client [L64781] registered to adapter [saa7146(1)](pos. 0).
> Jun 30 11:35:18 tv kernel: L64781: attaching L64781 @ 0x55 (adap cf8f71a0)
> Jun 30 11:35:18 tv kernel: SP8870: no SP8870 found ...
> Jun 30 11:35:18 tv kernel: tuner: chip found @ 0x61
> Jun 30 11:35:18 tv kernel: i2c-core.o: client [i2c tv tuner chip] registered to adapter [saa7146(1)](pos. 1).
> Jun 30 11:35:18 tv kernel: i2c-core.o: adapter saa7146(1) registered as adapter 0.
> Jun 30 11:35:18 tv kernel: tuner: type set to 42 (TSA5060)
> Jun 30 11:35:18 tv kernel: dvb: 1 dvb(s) found!
> Jun 30 11:35:18 tv kernel: tuner: tv freq set to 730000000      // Repeated a number of times
> Jun 30 11:35:18 tv kernel: buffer == 0x11 0xf4 0x88 0x00        // 
> 
> Which is hardcoded into the module.  I've changed those to make it attempt to tune to my local transmitter
> (crystal palace) and had similar results.
> 
> Adding some debug into the module when the 'failure event' is set appears that the initial tuning being done
> by the module causes this to happen - ie before I've ever asked it to tune to anything.
> 
> Anyone got any clues here, as I can't see what I'm doing wrong...
> 
> Cheers,
> 
> Glyn
> 
> 




-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.



Home | Main Index | Thread Index