From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-desktop+bounces-1969-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1QEVjt-0000GV-0W
for garchives@archives.gentoo.org; Tue, 26 Apr 2011 00:02:49 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 5FD701C0B9
for <garchives@archives.gentoo.org>; Tue, 26 Apr 2011 00:02:48 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by pigeon.gentoo.org (Postfix) with ESMTP id 7E34C1C012
for <gentoo-desktop@lists.gentoo.org>; Mon, 25 Apr 2011 23:11:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp.gentoo.org (Postfix) with ESMTP id D005A1B403D
for <gentoo-desktop@lists.gentoo.org>; Mon, 25 Apr 2011 23:11:12 +0000 (UTC)
X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org
X-Spam-Score: -2.526
X-Spam-Level:
X-Spam-Status: No, score=-2.526 required=5.5 tests=[AWL=0.073,
BAYES_00=-2.599]
Received: from smtp.gentoo.org ([127.0.0.1])
by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id LZBjKlz0LU7q for <gentoo-desktop@lists.gentoo.org>;
Mon, 25 Apr 2011 23:11:06 +0000 (UTC)
Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])
by smtp.gentoo.org (Postfix) with ESMTP id 597481B4036
for <gentoo-desktop@gentoo.org>; Mon, 25 Apr 2011 23:11:03 +0000 (UTC)
Received: from list by lo.gmane.org with local (Exim 4.69)
(envelope-from <glgd-gentoo-desktop@m.gmane.org>)
id 1QEUvk-0002YX-9r
for gentoo-desktop@gentoo.org; Tue, 26 Apr 2011 01:11:00 +0200
Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-desktop@gentoo.org>; Tue, 26 Apr 2011 01:11:00 +0200
Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-desktop@gentoo.org>; Tue, 26 Apr 2011 01:11:00 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-desktop@lists.gentoo.org
From: Duncan <1i5t5.duncan@cox.net>
Subject: [gentoo-desktop] Re: OpenGL Issue -- "failed to create drawable" (pyglet, python)
[SOLVED]
Date: Mon, 25 Apr 2011 23:10:49 +0000 (UTC)
Message-ID: <pan.2011.04.25.23.10.49@cox.net>
References: <4DB4C84A.4080207@aim.com> <pan.2011.04.25.03.34.37@cox.net>
<pan.2011.04.25.12.18.27@cox.net> <4DB5CDCF.8060002@aim.com>
Precedence: bulk
List-Post: <mailto:gentoo-desktop@lists.gentoo.org>
List-Help: <mailto:gentoo-desktop+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-desktop+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-desktop+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-desktop.gentoo.org>
X-BeenThere: gentoo-desktop@lists.gentoo.org
Reply-to: gentoo-desktop@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net
User-Agent: Pan/0.134 (Wait for Me; GIT 9383aac branch-testing)
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt:
X-Archives-Hash: 7cfe36f178581545150228464f19ba79
Corey Richardson posted on Mon, 25 Apr 2011 15:38:55 -0400 as excerpted:
> As for Gallium saying it's a i965 card, I think it was reading the last
> option in eselect with it set. Not positive, but that's the only thing =
I
> could come up with (I had both i915 and i965 set to gallium in eselect.
> After changing that to classic, here's the new glxinfo I get:
>=20
> OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string:
> Mesa DRI Mobile Intel=C2=AE GM45 Express Chipset OpenGL version string:=
2.1
> Mesa 7.10.1 OpenGL shading language version string: 1.20
>=20
> Looks better, AND it solves the pyglet problem! Thank you Duncan.
>=20
> Now that I think about gallium using i965, it doesn't seem as odd when
> you consider that the DRI2 driver is i965. I find that very strange, an=
y
> ideas what that could be? Didn't really find anything online, perhaps m=
y
> google-foo is lacking.
I expect it's simply not knowing about the eselect mesa bit, and having=20
something set wrong, originally. It would have been interesting to see=20
what the xorg log said before we started experimenting, as I suspect that=
=20
we fixed it in two stages, either setting something else wrong before we=20
found the first problem so fixing it didn't solve the entire problem, or=20
having two misconfigured settings in the first place and it took getting=20
them both correct to fix the problem.
FWIW, if you haven't already done so, you will probably want to enable=20
eselect's tab-completion option, among others. eselect bashcomp list wil=
l=20
give you a *BIG* list (199 items long, here) of bash-completion command=20
options you can activate if you use them on the command line. Each login=
=20
user can run eselect bashcomp and set their own prefs, so root doesn't=20
have to have the same set of active bash-completions as your normal user,=
=20
as someone (significant-other, whatever) else with a login on your=20
computer, etc.
Tab-completion for commands like eselect make them **MUCH** easier to use=
=20
effectively, just as tab-completion for filesystem paths makes them both=20
much easier to use effectively, AND much easier to use without error. If=
=20
you tab-complete an rm command, you're MUCH less likely to typo and rm th=
e=20
wrong thing, and MUCH more likely to catch it if you do typo, due to the=20
completion giving you something unexpected, before you actually do the=20
removal!
With eselect tab completion enabled, it too becomes much easier to use=20
effectively and without error. =3D:^)
--=20
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman