From owner-freebsd-multimedia Fri Jan 4 6:25:16 2002 Delivered-To: freebsd-multimedia@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id B279837B417 for ; Fri, 4 Jan 2002 06:25:12 -0800 (PST) Received: from colt.ncptiddische.net (ppp-309.wobline.de [212.68.71.30]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id g04EP9g04750; Fri, 4 Jan 2002 15:25:10 +0100 Received: from tisys.org (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id g04EPiX16960; Fri, 4 Jan 2002 15:25:45 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id g04EO4F75212; Fri, 4 Jan 2002 15:24:04 +0100 (CET) (envelope-from nils) Date: Fri, 4 Jan 2002 15:24:04 +0100 From: Nils Holland To: Randall Hopper Cc: Roger Hardiman , freebsd-multimedia@FreeBSD.ORG Subject: Re: bktr / fxtv problem -fixed!- Message-ID: <20020104152404.A75193@tisys.org> References: <20020101134607.A151@tisys.org> <20011230170550.A33828@tisys.org> <20020101104922.C19839@nc.rr.com> <20020102140143.A370@tisys.org> <20020104143305.A14137@tisys.org> <20020104084838.A7545@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020104084838.A7545@nc.rr.com>; from aa8vb@nc.rr.com on Fri, Jan 04, 2002 at 08:48:38AM -0500 X-Operating-System: FreeBSD jodie.ncptiddische.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE X-Machine-Uptime: 3:17PM up 5:38, 1 user, load averages: 0.17, 0.09, 0.30 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Jan 04, 2002 at 08:48:38AM -0500, Randall Hopper stood up and spoke: > > What would be interesting to see is if, when you start fxtv with your > PAL/BDGHI X resource setting, if you then switched to NTSC/M manually via > the format menu, and then switched back to PAL/BDGHI, are you in the same > bad state as you were originally? And when you quit and restart fxtv, does > that "clear up" this bad state. Well, this problem is more weird that you and I could ever think. Actually, what I had just done did not fix the problem. Something else did, and I'm in the process of finding out why. Here's the story: When I thought I successfully got fxtv to work, I was also doing a "make clean" in /usr/ports just at the same time. While this make clean operating was running, fxtv worked fine, once the operation completed, I was back at the old problems! So I ran "make clean" in /usr/ports again, and the problem was fixed for another ten minutes! I also noticed that receiving teletext with alevt would also only work while my "make clean" was running. So, for you as the author of fxtv, I can confirm that what I had been seeing is really not a problem with your software (which I like very much, by the way!). Instead, I highly guess that it's a problem with my KT133 / 686B chipset. It's really strange - when the hard disk is working, I can watch TV and teletext, but when the hard disk is idle, I can't! I've reported this problem to FreeBSD's IDE / ATA / 686b bug guru Soren Schmidt. I asked him if he has a clue what the hard disk thing might have to do with my TV watching. In the mean time, my only solution is to run a script that constantly cleans /usr/ports. As long as the script runs, I can watch TV just fine. As I said, this is really weird, and I wonder if anyone's seen that before ;-) Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message