From owner-freebsd-current Fri Dec 3 22:37:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 23EEE14BF6 for ; Fri, 3 Dec 1999 22:37:17 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA62241; Fri, 3 Dec 1999 23:35:15 -0700 (MST) (envelope-from ken) Message-Id: <199912040635.XAA62241@panzer.kdm.org> Subject: Re: Bktr driver In-Reply-To: from Kenneth Culver at "Dec 3, 1999 11:56:18 pm" To: culverk@culverk.student.umd.edu (Kenneth Culver) Date: Fri, 3 Dec 1999 23:35:15 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Culver wrote... > It seems that the bktr driver is still broken. I have looked through the > code for the driver, and have yet to find the problem. here is a dmesg > output with the error that seems to be causeing my problem: > > bktr0: irq 9 at device 17.0 on pci0 > bktr0: Hauppauge Model 61291 D110 > Warning - Unknown Hauppauge Tuner 0xa > Hauppauge WinCast/TV, Philips NTSC tuner, remote control. > > The problem with the driver can be found at: > > www.wam.umd.edu/~culverk/fxtv.jpg > > I am positive that this problem is not with X or fxtv, I have already > talked to the X people about this problem. You should probably look at the -multimedia list. Chris Csanady reported that his problems went away when he backed bktr_core.c from version 1.102 to version 1.101. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message