From owner-freebsd-questions@FreeBSD.ORG Sun Jul 13 17:56:57 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFBC61065678 for ; Sun, 13 Jul 2008 17:56:57 +0000 (UTC) (envelope-from LukeD@pobox.com) Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com [208.72.237.25]) by mx1.freebsd.org (Postfix) with ESMTP id AF21F8FC0C for ; Sun, 13 Jul 2008 17:56:57 +0000 (UTC) (envelope-from LukeD@pobox.com) Received: from localhost.localdomain (localhost [127.0.0.1]) by a-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id 9083D2A08B; Sun, 13 Jul 2008 13:56:56 -0400 (EDT) Received: from lukas.is-a-geek.org (pool-71-113-98-220.sttlwa.dsl-w.verizon.net [71.113.98.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 95A2C2A08A; Sun, 13 Jul 2008 13:56:53 -0400 (EDT) Date: Sun, 13 Jul 2008 10:56:48 -0700 (PDT) From: Luke Dean X-X-Sender: lukas@border.lukas.is-a-geek.org To: Neil Short In-Reply-To: <447397.28597.qm@web56515.mail.re3.yahoo.com> Message-ID: <20080713104939.U26523@border.lukas.is-a-geek.org> References: <447397.28597.qm@web56515.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Pobox-Relay-ID: 1558F3BE-5105-11DD-8598-3113EBD4C077-96347044!a-sasl-quonix.pobox.com Cc: freebsd-questions@freebsd.org Subject: Re: aterm whacked? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Luke Dean List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2008 17:56:58 -0000 On Sat, 12 Jul 2008, Neil Short wrote: > I just mem-wiped my laptop and am in the process of installing > everything after. > > I have several issues (linux-firefox with linux-flash plugin crashes on > sites with flash), not the least of which is aterm doesn't seem to > behave very well. > > When I run aterm I get: > > $ aterm > aterm has encountered the following problem interacting with X Windows : > Request: 64, Error: 8(BadMatch (invalid parameter attributes)) > in resource: 0x140000D > aterm has encountered the following problem interacting with X Windows : > Request: 64, Error: 8(BadMatch (invalid parameter attributes)) > in resource: 0x140000D > aterm has encountered the following problem interacting with X Windows : > Request: 64, Error: 8(BadMatch (invalid parameter attributes)) > in resource: 0x140000D > > .... etc. > > Transparency doesn't work right either - which I see is the greatest > attraction to aterm. > > Any ideas? I had this problem with an old Sony Vaio about a year ago. Xorg detected that the correct video driver to use was "neomagic". Whatever automatic configuration method I was using at the time decided that I should be running with 32-bit color depth in xorg.conf. It turns out that the neomagic driver doesn't support color depth greater than 24-bits... This misconfiguration worked well enough until something like aterm tried to use transparency, then it would complain about the "BadMatch", referring to the color depth that the driver supported versus the color depth that X was configured for, presumably. I found two solutions. One was to edit the "Screen" section of xorg.conf to remove the entry with DefaultDepth 32. The other was to edit xorg.conf to use the vesa driver instead of the neomagic driver.