public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: timf <timf@iinet.net.au>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Kworld DVB-T 210 - dvb tuning problem
Date: Fri, 07 Mar 2008 21:51:21 +0900	[thread overview]
Message-ID: <1204894281.10536.8.camel@ubuntu> (raw)

Hi Hartmut,
I noticed you had a bit to do with implementing this card.

With a fresh install of ubuntu 7.10 (kernel i386 2.6.22-14-generic),
the card is auto recognised as: Kworld DVB-T 210 (card=114)

However, tda1004 firmware does not load.
Used download-firmware, placed dvb-fe-tda10046.fw
into /lib/firmware/2.6.22-14-generic

Rebooted.

Now, again card is recognised, firmware recognised as version 20.
Here is the strange part:
- using dvb-utils scan, each time I run that I get a different result in
channels.
- I try to scan with Kaffeine - nothing
- I try to scan with Me-tv - nothing
- I try to scan with tvtime - all channels obtained ( no audio).

Now, after reboot, if I first start tvtime (analog tv), view a channel,
turn tvtime off, and then :
- if I place a previously good channels.dvb in Kaffeine - it plays all
channels.
- if I place a previously good channels.conf in Me-tv - it plays all
channels. 

Would it be correct to say that the "switch" is not working for DVB
after boot?

I have studied the code, but I need your help to point me in the right
direction.

Thanks,
Tim


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

             reply	other threads:[~2008-03-07 12:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 12:51 timf [this message]
     [not found] <1204893775.10536.4.camel@ubuntu>
     [not found] ` <47D1A65B.3080900@t-online.de>
2008-03-14  7:41   ` [linux-dvb] Kworld DVB-T 210 - dvb tuning problem timf
2008-03-17 21:22     ` Hartmut Hackmann
2008-03-18 14:40       ` timf
2008-03-18 22:56         ` Hartmut Hackmann
2008-03-19  4:03           ` timf
2008-03-19 23:18             ` Hartmut Hackmann
     [not found]         ` <1213744559.11684.4.camel@asus.lounge>
2008-06-18  2:12           ` timf
2008-06-18  2:51             ` timf
  -- strict thread matches above, loose matches on Subject: below --
2008-03-14 12:52 Steve Moreau
2008-04-10 16:22 timf
2008-04-10 22:08 ` Hartmut Hackmann
2008-04-10 23:30   ` hermann pitton
2008-04-11 17:54     ` timf
2008-04-11 22:14       ` Hartmut Hackmann
2008-04-13  6:00         ` timf
2008-04-13  7:59           ` timf
2008-04-13 15:54             ` timf
2008-04-13 17:08               ` timf
2008-04-13 18:56                 ` Hartmut Hackmann
2008-04-13 19:25                   ` timf
2008-04-13 20:23                     ` Hartmut Hackmann
2008-04-13 21:08                       ` timf
2008-04-13 21:41                         ` Hartmut Hackmann
2008-04-13 22:11                           ` timf
2008-04-13 22:35                             ` timf
2008-04-13 22:53                             ` Hartmut Hackmann
2008-04-14 14:10                               ` timf
2008-04-15  0:42                                 ` hermann pitton
2008-04-11 21:23     ` Hartmut Hackmann
2008-04-12 11:30       ` hermann pitton
2008-04-12 12:00         ` timf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1204894281.10536.8.camel@ubuntu \
    --to=timf@iinet.net.au \
    --cc=linux-dvb@linuxtv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox