From owner-freebsd-multimedia  Fri May  9 14:55:45 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA00858
          for multimedia-outgoing; Fri, 9 May 1997 14:55:45 -0700 (PDT)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA00853
          for <multimedia@FreeBSD.ORG>; Fri, 9 May 1997 14:55:43 -0700 (PDT)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
	by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id OAA04245;
	Fri, 9 May 1997 14:55:30 -0700 (PDT)
Message-Id: <199705092155.OAA04245@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Ralph Thomas Aussem <aussem@tu-harburg.d400.de>
cc: Randall Hopper <rhh@ct.picker.com>, multimedia@FreeBSD.ORG,
        Richard Tobin <richard@cogsci.ed.ac.uk>
Subject: Re: Problems with bt848 in FreeBSD 2.2.1 
In-reply-to: Your message of "Fri, 09 May 1997 23:21:02 +0200."
             <XFMail.970509232824.aussem@mavhh.aut.tu-harburg.de> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 09 May 1997 14:55:29 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-multimedia@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

What is your CPU and PCI chipset? 

	Tnks,
	Amancio



>From The Desk Of Ralph Thomas Aussem :
> 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
>