Mailing List archive

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

[linux-dvb] Re: DST & Twinhan-Card



Stefan Schenk wrote:


This might be also of interest for the list

I was playing around with the values Jamie was talking about ...
without success.
There must be some other differences between DVB-T in Australia and
Germany ....

Stefan

-----Ursprüngliche Nachricht-----
Von: Jamie Honan [mailto:jhonan@optushome.com.au] Gesendet: Sonntag, 14. November 2004 23:38
An: Stefan Schenk
Betreff: Re: DST & Twinhan-Card


On Sun, Nov 14, 2004 at 12:14:37PM +0100, Stefan Schenk wrote:

Hello Jamie,


as i saw on the dvb-mailing-list you did a lot of great work, making the Twinhan-cards working under linux. I have a very strange problem here. I use a DVB-T card from the german company HAMA which is

said to be a 100% clone of Twinhans VisionDTV. I can load the drivers and everything looks perfect. The problem is, that i get a very bad signal in (vdr's femon-plugin shows someting between 15% and 30%) and therefore the picture is very very bad.
When i start the card with the same antenna in the same room under
windows i get a full signal and a perfect picture.

Do you have any idee whats wrong with my system or my card ?

Thanks a lot

I have exactly the same problem on my Twinhan VisionDTV here in Australia. The MythTV setup program reports ~23% signal strength, I get 2/5 channels ok (ABC and SBS), but everything else is totally unwatchable. The same card works reasonably under Windoze (>80% signal strength, HDTV is unwatchable and channel 10 gets a glitch every minute or so). This is running under Knoppmyth with the 2.4 kernel. I also have a Teac STB which works well on all channels (but not enough singnal for HDTV). I'm about to try loading Suse 9.1 on a fresh drive with 2.4 kernel and a fresh CVS checkout of the dvb drivers. If that doesn't work, I'll sell the Twinhan card on ebay and buy a DVico FusionHDTV (unless somebody suggests a better DVB-T card).


Hmm. Everything looks good as far as module loading goes.

I guess there's a lot more undocumented registers etc.

One thing you could try, the guy who got it going was in Australia,
which has 7Mhz bandwidth. You are either 8 or 6. Most apps try
BANDWIDTH_AUTO, which I notice sets 7 MHz.

You could try playing round with this in the code.
I haven't a copy of the latest versions but look for code
like this:

case BANDWIDTH_6_MHZ:
val[6] = 6;
break;


case BANDWIDTH_7_MHZ:
case BANDWIDTH_AUTO:
val[6] = 7;
break;


case BANDWIDTH_8_MHZ:
val[6] = 8;
break;

and try moving BANDWIDTH_AUTO to 8Mhz.
(actually I see two spots)

You might also try 0 for Auto and see what happens.

Let me or the list know.
Jamie




Home | Main Index | Thread Index