From owner-freebsd-ia32@FreeBSD.ORG  Thu May 12 04:39:00 2005
Return-Path: <owner-freebsd-ia32@FreeBSD.ORG>
Delivered-To: freebsd-ia32@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 280A016A4CE; Thu, 12 May 2005 04:39:00 +0000 (GMT)
Received: from ms-smtp-01-eri0.southeast.rr.com
	(ms-smtp-01-lbl.southeast.rr.com [24.25.9.100])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 57E4B43D90; Thu, 12 May 2005 04:38:59 +0000 (GMT)
	(envelope-from jason@ec.rr.com)
Received: from [192.168.1.100] (cpe-065-184-196-020.ec.res.rr.com
	[65.184.196.20])j4C4ctLv001695;	Thu, 12 May 2005 00:38:56 -0400 (EDT)
Message-ID: <4282E0C4.9050901@ec.rr.com>
Date: Thu, 12 May 2005 00:51:16 -0400
From: jason henson <jason@ec.rr.com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050426)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sean Davis <dive-d@endersgame.net>
References: <20050511003146.GA28025@endersgame.net>
	<428179C3.3090900@ec.rr.com> <20050511103034.GC28269@endersgame.net>
In-Reply-To: <20050511103034.GC28269@endersgame.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Symantec AntiVirus Scan Engine
cc: freebsd-ia32@freebsd.org
cc: freebsd-questions@freebsd.org
Subject: Re: FreeBSD/i386 lockups with Xorg & Radeon cards
X-BeenThere: freebsd-ia32@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: FreeBSD on the IA-32 platform <freebsd-ia32.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ia32>,
	<mailto:freebsd-ia32-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ia32>
List-Post: <mailto:freebsd-ia32@freebsd.org>
List-Help: <mailto:freebsd-ia32-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ia32>,
	<mailto:freebsd-ia32-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2005 04:39:00 -0000


>>>      
>>>
>>Do you have an nforce chipset on the motherboard?  I do and I have never 
>>had any version of x to work with dri on a radeon.  So disable dri if it 
>>is on and try again. 
>>    
>>
>
>No. Both motherboards are VIA chipsets, one is an ASUS and one is an ASRock.
>(although I've been told that ASRock is a low-budget division of ASUS, dunno
>whether that's true or not.)
>
>  
>
>>Also are you getting any error messages?  You can check /var/run for the 
>>x logs from the last running of x. 
>>    
>>
>
>Nope. Just locks the machine.
>
>  
>
>>Does x lock after the startx command, or randomly later on while you are 
>>using x?
>>    
>>
>
>It locks as soon as the X server starts. I can start it with X -configure,
>xorgcfg, or just plain `X', it doesn't matter - as soon as it starts trying
>to initialize the display, it locks up.
>
>-Sean
>
>  
>
Sounds like a driver problem.  Are you loading dri.  Post a copy of 
xorg.conf.