[linux-dvb] MSI TV @nywhere a/d support
Greg 'groggy' Lehey
grog at lemis.com
Fri Jan 12 06:47:21 CET 2007
On Friday, 12 January 2007 at 0:35:53 +0100, hermann pitton wrote:
> Am Donnerstag, den 11.01.2007, 22:14 +1030 schrieb Trevor Glen:
>> Peter D. wrote:
>>>> In looking at the latest mercurial code, this card isn't detected
>>>> automatically. What do I have to do to get that to happen? (or, please,
>>>> correct me if I am wrong)
>>> Don't know, but that model does work. Hopefully an expert will jump in and
>>> offer a solution.
>> Any other thoughts out there people?
> That might depend on if your au-Adelaide (?) initial scan file is
> already tda10046 safe. It needs correct values. Other frontends are
> more tolerant and this can break it for you.
I'm not sure I understand this. A couple of questions:
- By the "original scan file", do you mean the channels.conf file
described at http://www.linuxtv.org/wiki/index.php/Zap ? If so,
what might be wrong with it, in particular the au-Adelaide file?
I've had no trouble with it with the DVICO Fusion cards.
- What's "tda10046 safe"? In particular, what values do you think
might be incorrect? How would one go about establishing what's
> Usually, if using "scan" from mercurial dvb-apps, it is best to set
> all to AUTO there except freq. and bandwidth.
Is this version significantly different from the one described at
> This works fine for me on all 8MHz transponders, but my single 7MHz
> one won't do it that way. Might differ for you. I think people had
> already success also with 7MHz stuff.
It would appear that transponders in Adelaide are all 7 MHz.
> Another known pitfall with the tda10046 is that in Australia
> reportedly offsets of 167000Hz are in use. You might try with
> modified scan files with such positive and negative offsets.
Where would this be?
On Friday, 12 January 2007 at 15:38:01 +1100, Peter D. wrote:
> On Friday 12 January 2007 10:35, hermann pitton wrote:
>> That might depend on if your au-Adelaide (?) initial scan file is
>> already tda10046 safe. It needs correct values. Other frontends are more
>> tolerant and this can break it for you.
> I forgot about that. I have two tuner cards and they differ in their
> capabilities when presented with wrong configuration files. Be warned that
> there are many places that such a config file can be lurking - especially
> if you are playing with multiple applications.
> I'm in Melbourne if you are interested in my configuration of Kaffeine.
I'd certainly be interested in what differences you have in the
> Do you want any information about the remote?
I'd certainly be interested.
This card (if it's the one I'm thinking of) looks like being the
cheapest locally available DVB-T card, so it would be nice to get good
support for it.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20070112/b75d0d90/attachment.pgp
More information about the linux-dvb