From owner-freebsd-questions@FreeBSD.ORG Wed Jul 16 01:36:12 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 D5E5B1065682 for ; Wed, 16 Jul 2008 01:36:12 +0000 (UTC) (envelope-from neshort@yahoo.com) Received: from web56504.mail.re3.yahoo.com (web56504.mail.re3.yahoo.com [66.196.97.33]) by mx1.freebsd.org (Postfix) with SMTP id 7EC3B8FC18 for ; Wed, 16 Jul 2008 01:36:12 +0000 (UTC) (envelope-from neshort@yahoo.com) Received: (qmail 63613 invoked by uid 60001); 16 Jul 2008 01:36:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=Dl3SF41FU1hm8+E8lqhxRJjbe4kjtwhTWBwgylFy+SpQ8TnxauckHb48q7BYR8JCBvIUGchwo3LxuairSe3+vENKdHba7616cD5xGAg/Q3hcVX1F+RMLXVfPdyDs9eMB/pAL9o06xcAziCz2j9odfwbCuGHXlBoQwFOVTMGuE+I=; Received: from [97.112.207.18] by web56504.mail.re3.yahoo.com via HTTP; Tue, 15 Jul 2008 18:36:11 PDT X-Mailer: YahooMailWebService/0.7.218 Date: Tue, 15 Jul 2008 18:36:11 -0700 (PDT) From: Neil Short To: freebsd-questions@freebsd.org In-Reply-To: <20080713104939.U26523@border.lukas.is-a-geek.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <567402.62256.qm@web56504.mail.re3.yahoo.com> Cc: Luke Dean Subject: Re: aterm whacked? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: neshort@yahoo.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 01:36:12 -0000 That's it! I have an ATI Radion on this box. The screen res is 1280x800 which is not supported by vesa. I dug up my old backup xorg.conf file and realized I had set "ati" as the driver and was full of good experiences with it. I had just forgotten. Also, for the record, this fix also fixed my linux-firefox/linux-flashplugin issue. much appreciation. ====== If not us, who? And if not now, when? Ronald Reagan --- On Sun, 7/13/08, Luke Dean wrote: > From: Luke Dean > Subject: Re: aterm whacked? > To: "Neil Short" > Cc: freebsd-questions@freebsd.org > Date: Sunday, July 13, 2008, 11:56 AM > 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.