[linux-dvb] Mantis 2033 dvb-tuning problems

Mårten Gustafsson reklam at holisticode.se
Thu Oct 23 15:13:14 CEST 2008


I tried your patch, and it "improve" things a bit. Kaffeine is able to scan
a few channels now without any entries in /var/log/messages. w_scan finds a
few frequencies, but no services. Scan results are different between scans.
w_scan works "better" if timeout settings are increased.

The channels found by Kaffeine are not viewable, there is something moving,
but I guess the driver is unable to descramble the signal. 

My system is an Ubuntu 8.10 amd64. The network is ComHem and the CI is from
Conax. I also have the AzureWave AD-CP300.

Since this is an improvement I agree with you, Manu should apply the patch.


-----Ursprungligt meddelande-----

On Wed, 15 Oct 2008, Hans Bergersen wrote:

> Hi,

> I have got a Twinhan vp-2033 based card. I run Ubuntu 8.04. I have 
> downloaded the driver from http://jusst.de/hg/mantis and it compiled 
> just fine. But when i try to tune a channel the tuning fails. It is 
> a newer card with the tda10023 tuner but when the driver loads it 
> uses the tda10021. What do I have to do to make it use the right 
> tuner? Can i give some options when compiling or when loading the 
> module?
> Any ideas?

Try the attached patch which fixes this for my Azurewave AD-CP300 (at 
least last time I compiled it).

I've sent it to Manu and he was going to apply it, but it hasn't shown 
up on http://jusst.de/hg/mantis/ yet...

  Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se      |     nikke at acc.umu.se
  "I don't believe it. There are no respected plastic surgeons." - Logan
-------------- next part --------------

Fix tda10021 to not claim tda10023.

Previously mantis_frontend_init() relied on the PCI ID alone, this
causes trouble when a card has a different chip depending on
the manufacturing date. This match makes it work with newer
Azurewave AD-CP300 cards while (hopefully) maintaining compatibility
with older cards.

More information about the linux-dvb mailing list