From owner-freebsd-stable@FreeBSD.ORG Sun Apr 6 01:21:17 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4776637B401 for ; Sun, 6 Apr 2003 01:21:17 -0800 (PST) Received: from sunfire.lclark.edu (lclark.edu [149.175.1.5]) by mx1.FreeBSD.org (Postfix) with SMTP id B965D43FBF for ; Sun, 6 Apr 2003 01:21:16 -0800 (PST) (envelope-from eta@lclark.edu) Received: from [149.175.30.191] ([149.175.30.191]) by sunfire.lclark.edu (SAVSMTP 3.0.1.45) with SMTP id M2003040601203509507 ; Sun, 06 Apr 2003 01:20:35 -0800 From: Eric Anholt To: Paul Boehmer In-Reply-To: <1047947841.613.10.camel@leguin> References: <20030313113235.Y77941@netfoo.net> <1047947841.613.10.camel@leguin> Content-Type: text/plain Organization: Message-Id: <1049621139.613.6.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 06 Apr 2003 01:25:39 -0800 Content-Transfer-Encoding: 7bit cc: freebsd-stable@FreeBSD.ORG Subject: Re: XFree86 4.3.0 Matrox/MultiHead (Long!) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Apr 2003 09:21:17 -0000 On Mon, 2003-03-17 at 16:37, Eric Anholt wrote: > On Thu, 2003-03-13 at 09:10, Paul Boehmer wrote: > > I have a test box that had been running X 4.2 in a multihead config for a > > while now (1 Nvidia TNT2 AGP, and 2 Matrox Millennium/Mystique PCI Cards). > > I upgraded yesterday to 4.3.0 only to find out that any attempts to run X > > result in a complete console lockup (still have access via ssh). Since > > the box was running 5.0, I loaded 4.8-RC from scratch this morning only to > > find the same problem. > > > > Using a 4.2.x standby XF86Config, X works fine when running a single card > > (either TNT or Matrox). I get console lockups when attempting to run > > multiple cards. > > > > I experience the same problem when attempting to run xf86cfg. > > Just a heads up on this one: It's a problem in the generic int10 > module. Linux folks haven't noticed it because by they use a > linux-specific int10 module by default. One of the XFree86 developers > has reproduced it, hopefully it will be fixed soon. It should be fixed now in XFree86 CVS and in the ports tree, XFree86-Server-4.3.0_3 -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org