From owner-freebsd-hackers Thu Nov 22 7: 5:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 9BDC637B405 for ; Thu, 22 Nov 2001 07:05:19 -0800 (PST) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id fAMF5I796001; Thu, 22 Nov 2001 09:05:18 -0600 (CST) (envelope-from tinguely) Date: Thu, 22 Nov 2001 09:05:18 -0600 (CST) From: mark tinguely Message-Id: <200111221505.fAMF5I796001@web.cs.ndsu.nodak.edu> To: freebsd-hackers@FreeBSD.ORG, step@acm.org Subject: Re: meteor driver problems In-Reply-To: <20011122115948.A25406@step.cg.tuwien.ac.at> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > i've been experiencing weird problems with the Meteor device driver.. > on two machines of the seven we've installed, the METEOR_CAP_SINGLE > ioctl locks up the process once in a while (every few hours). [deletion] the original metoer card's PCI chipset had a known and uncorrectable hardware incompatibility with PCI 2.0 chipsets that caused lockup. Matrox had to change the components on the next generation of cards and at the time Matrox was not too generous with documentation, so the multimedia developers switched to the Brooktree 848 video capture chipset based cards. My guess every computer that you used to test the card uses the PCI 2.x chipset (a safe guess since it has been a long time since a manufacturer used a PCI 1.x chipset). --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message