From owner-freebsd-questions@FreeBSD.ORG  Mon Jan  3 07:34:01 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4EEA016A4CE
	for <freebsd-questions@freebsd.org>;
	Mon,  3 Jan 2005 07:34:01 +0000 (GMT)
Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7C78143D2F
	for <freebsd-questions@freebsd.org>;
	Mon,  3 Jan 2005 07:33:59 +0000 (GMT)
	(envelope-from dave@horsfall.org)
Received: from localhost (dave@localhost)
	by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id j037XvO13295
	for <freebsd-questions@freebsd.org>;
	Mon, 3 Jan 2005 18:33:57 +1100 (EST)
Date: Mon, 3 Jan 2005 18:33:57 +1100 (EST)
From: Dave Horsfall <dave@horsfall.org>
To: freebsd-questions@freebsd.org
In-Reply-To: <41D8EF18.5010504@taborandtashell.net>
Message-ID: <Pine.BSI.4.61.0501031831130.12968@dave.horsfall.org>
References: <41D8EF18.5010504@taborandtashell.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: Upgraded to Xorg 6.8.1 and some icons broke in Window Maker
 0.91.0
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2005 07:34:01 -0000

On Sun, 2 Jan 2005, Tabor Kelly wrote:

> Of note: I have an Intel i810 video chipset and Xorg 6.8.1 "broke" the 
> driver for it, but I set NoAccel in my xorg.conf file and that was 
> supposed to take care of it (now X at least starts). Does anyone think 
> this could be related to my specific hardware?

Could be; grab the latest Xorg from CVS, as a fix to the 810 driver 
(6.8.1_1) was committed yesterday.

-- Dave