From owner-freebsd-multimedia Thu May 8 13:27:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17481 for multimedia-outgoing; Thu, 8 May 1997 13:27:16 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA17474 for ; Thu, 8 May 1997 13:27:14 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Thu, 8 May 1997 16:18:24 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA08472; Thu, 8 May 97 16:18:20 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id QAA11989; Thu, 8 May 1997 16:17:41 -0400 Message-Id: <19970508161741.28673@ct.picker.com> Date: Thu, 8 May 1997 16:17:41 -0400 From: Randall Hopper To: Ralph-Thomas Aussem Cc: Richard Tobin , multimedia@freebsd.org Subject: Re: Problems with bt848 in FreeBSD 2.2.1 References: <3371A9A1.41C67EA6@mavhh.aut.tu-harburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <3371A9A1.41C67EA6@mavhh.aut.tu-harburg.de>; from Ralph-Thomas Aussem on Thu, May 08, 1997 at 12:23:29PM +0200 Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ralph-Thomas Aussem: |Hi Randall, |I've just installed the bt848 driver from april 24. Now I have |the following problem: | |If I start fxtv (version 0.42) I can hear the tv sound |but I don't see anything. I have patch fxtv to use PAL, |cable and weurope frequencies (the X11 application defaults |doesn't work. fxtv doesn't find it in /usr/X11/lib/X11/app-defaults). |With xrtv I can switch the channels but I don't see any picture. | |Do you have a hint for me ? I've rolled in a few things for PAL along with a PAL-related patch from Richard Tobin , but as I don't have access to a PAL signal or a WinTV, I'm not sure how much I can help. As far as I know, no-one's really beat on the PAL side of the system yet. Maybe Richard or someone else on the list in Europe can give some advice. 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. 2) Try running in a different color depth ("startx -- -bpp 8" [or 16, etc.]) and see if that makes a 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"). 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. Hope this helps you track it down. Randall