From owner-freebsd-stable@FreeBSD.ORG Tue Aug 26 21:39:57 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 8410D16A4BF; Tue, 26 Aug 2003 21:39:57 -0700 (PDT) Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id C49AC43FE3; Tue, 26 Aug 2003 21:39:56 -0700 (PDT) (envelope-from welchsm@earthlink.net) Received: from misspiggy.psp.pas.earthlink.net ([207.217.78.246]) by swan.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19rs63-0005WU-00; Tue, 26 Aug 2003 21:39:51 -0700 Received: from [207.217.78.15] by EarthlinkWAM via HTTP; Tue Aug 26 21:39:51 PDT 2003 Message-ID: <245001.1061959191108.JavaMail.nobody@misspiggy.psp.pas.earthlink.net> Date: Tue, 26 Aug 2003 21:38:30 -0500 (GMT) From: Sean Welch To: Glenn Johnson Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Web Access Mail version 3.0 cc: freebsd-stable@freebsd.org cc: Vulpes Velox cc: freebsd-current@freebsd.org Subject: Re: Radeon 7500 w/ DRI locking on restart of X X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sean_Welch@alum.wofford.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2003 04:39:57 -0000 I sent an earlier message which seems to have disappeared into the void. I tried the forcepcimode under the 5.1 install on my laptop (RELEASE with upgraded ports tree) and found that it behaved as you said yours does. I can't get it to hang no matter what I do now -- though the performance is a little less than half what it was with the AGP. I haven't had a chance to try that option on my desktops. If it works there I'll be mighty happy! Your other message about the newest version of X having this fixed is very interesting; I track both XFree86 and DRI CVS daily. The only problem is that I have nearly 2 GB of programs built on top of X, so that is not nearly as easy to upgrade... Maybe it is time for me to finally blow away that install of 4.7-RELEASE and try it out. Sean -------Original Message------- From: Glenn Johnson Sent: 08/26/03 09:14 PM To: Sean_Welch@alum.wofford.org Subject: Re: Radeon 7500 w/ DRI locking on restart of X > > On Tue, Aug 26, 2003 at 03:31:29PM -0500, Sean Welch wrote: > I have precisely the same symptoms as what Glenn listed. > > I have now tried the forcepcimode option on the laptop and > unfortunately experienced what appears to be the opposite effect to > what Glenn noted. I get a black screen with lots of disk activity. > I can log in remotely (at least that seemed to work every time) and > a top listing shows X taking up more and more CPU cycles. It seems > to be scribbling to the disk making temporary files as well because > eventually I couldn't edit the XF86Config file any longer -- I was > getting a "no space left on device" error. I ended up taking out all > options short of disabling DRI altogether and eventually discovered > the only way I could run with DRI switches on and forcepcimode set > to true was to unload the agp module from kernel space. This got it > started just fine but there was no DRI. It seems that X is getting > confused and somehow PCI and AGP modes are duking it out... Does it work on your desktops? I do not have agp in the kernel config. When X starts it loads both the radeon and agp modules, or maybe the radeon module is loading the agp module. Either way, both radeon.ko and agp.ko get loaded up. Here is some info about my hardware: - The motherboard is an Abit IS7 (P4c w/865PE chipset) - The graphics card is an ATI Radeon 9100 Here is the device section of my XF86Config (sans comments): Section "Device" Identifier "Card0" Driver "ati" VendorName "ATI Technologies Inc" BoardName "Radeon R200 QM [Radeon 9100]" BusID "PCI:1:0:0" Option "DDCMode" "true" Option "ForcePCIMode" "true" EndSection Finally, here are the first few lines of glxinfo: name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 -- Glenn Johnson >