From owner-freebsd-multimedia  Fri May  9 14:40:17 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA00299
          for multimedia-outgoing; Fri, 9 May 1997 14:40:17 -0700 (PDT)
Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA00292
          for <multimedia@freebsd.org>; Fri, 9 May 1997 14:40:12 -0700 (PDT)
Received: from rztsun.rz.tu-harburg.de (rztsun.rz.tu-harburg.de [134.28.200.14])
	by agora.rdrop.com (8.8.5/8.8.5) with SMTP id OAA07752
	for <multimedia@freebsd.org>; Fri, 9 May 1997 14:29:00 -0700 (PDT)
Message-Id: <XFMail.970509232824.aussem@mavhh.aut.tu-harburg.de>
X-Mailer: XFMail 1.0 [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Mime-Version: 1.0
In-Reply-To: <19970508161741.28673@ct.picker.com>
Date: Fri, 09 May 1997 23:21:02 +0200 (MET DST)
From: Ralph Thomas Aussem <aussem@tu-harburg.d400.de>
To: Randall Hopper <rhh@ct.picker.com>
Subject: Re: Problems with bt848 in FreeBSD 2.2.1
Cc: multimedia@freebsd.org, Richard Tobin <richard@cogsci.ed.ac.uk>,
        Ralph-Thomas Aussem <aussem@tu-harburg.d400.de>
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi Randall,

[..]
There really isn't much in fxtv that's tuner-type/-mode specific, so my
>first guess is it might be driver-related.  But to try and nail it down,
>try these things:
>
>    1) In fxtv when you can hear the audio, play with the appearance 
>       controls (Input->Appearance) and see if that changes anything.
If I change the appearance the display changes to. If I change tuner/video
the video signal changes. So the control functions seems to work.

>   
>    2) Try running in a different color depth ("startx -- -bpp 8" 
>       [or 16, etc.]) and see if that makes a difference.
No difference

>
>    3) Startup fxtv with startup debugs on "fxtv -debug startup"
>       If the selected video mode says it supports direct video,
>       run with it disabled ("fxtv -disableDirectV").
I doesn't help. fxtv reports without -disableDirectV that direct video isn't 
supported.

>
>    4) If the previous doesn't work, or if it didn't say you were using
>       direct video anyway, put a printf at the top of the
>       TVSCREENNewFrameHdlr routine to see if its getting called.
I will try this. 

At the moment I have the main problem that the computer freezes 
after some seconds  I started fxtv.. So testing is very dangerous :-(

Bye
Ralph