From owner-freebsd-x11@FreeBSD.ORG Mon May 4 21:41:14 2009 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E42B61065673 for ; Mon, 4 May 2009 21:41:14 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx04.pub.collaborativefusion.com (mx04.pub.collaborativefusion.com [206.210.72.84]) by mx1.freebsd.org (Postfix) with ESMTP id AA39A8FC16 for ; Mon, 4 May 2009 21:41:14 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from [192.168.2.164] ([206.210.89.202]) by mx04.pub.collaborativefusion.com (StrongMail Enterprise 4.1.1.4(4.1.1.4-47689)); Mon, 04 May 2009 17:39:03 -0400 X-VirtualServerGroup: Default X-MailingID: 00000::00000::00000::00000::::16 X-SMHeaderMap: mid="X-MailingID" X-Destination-ID: freebsd-x11@freebsd.org X-SMFBL: ZnJlZWJzZC14MTFAZnJlZWJzZC5vcmc= Message-ID: <49FF60F9.6010303@comcast.net> Date: Mon, 04 May 2009 17:41:13 -0400 From: Steve Polyack User-Agent: Thunderbird 2.0.0.21 (X11/20090327) MIME-Version: 1.0 To: Robert Noland References: <49FF28BC.5080304@comcast.net> <1241460816.1788.22.camel@balrog.2hip.net> <49FF387F.1080203@comcast.net> <1241464053.1788.32.camel@balrog.2hip.net> <49FF4857.4070904@comcast.net> <1241467827.1788.43.camel@balrog.2hip.net> <49FF51BC.5050104@comcast.net> <1241470167.1788.45.camel@balrog.2hip.net> In-Reply-To: <1241470167.1788.45.camel@balrog.2hip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-x11 , freebsd-stable Subject: Re: Radeon 9250 DRM in 7.2-RELEASE X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2009 21:41:15 -0000 Robert Noland wrote: > ok, how about this one... If this doesn't do it, then we need to start > digging... > > robert. > > No change when using this patch either. I've also updated to the latest BIOS and have ensured that the onboard Intel adapter is as disabled as it can get. I can provide you some photos of the screen behavior if you think it may help. Thanks again so far!