<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
(Forgot to reply to list.)<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0" height="86" width="427">
<tbody>
<tr>
<td valign="top"><br>
</td>
<td valign="top"><br>
</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE"><br>
</th>
<td><br>
</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE"><br>
</th>
<td><br>
</td>
</tr>
</tbody>
</table>
<br>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 10/18/2010 01:56 PM, Gough, Erik S wrote:
<blockquote
cite="mid:BA470D5E3C77CA43B5291073FB0680CB334EBF358F@VPEXCH08.purdue.lcl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am receiving the following error when I
try and open a structure running chimera with Mesa 7.0 on
Debian 5.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">X Error of failed request:
GLXBadRenderRequest<o:p></o:p></p>
<p class="MsoNormal"> Major opcode of failed request: 148
(GLX)<o:p></o:p></p>
<p class="MsoNormal"> Minor opcode of failed request: 1
(X_GLXRender)<o:p></o:p></p>
<p class="MsoNormal"> Serial number of failed request: 5334<o:p></o:p></p>
<p class="MsoNormal"> Current serial number in output stream:
5336<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am assuming that this is related to
running an older version of the Mesa driver, but I do not have
root on the system and the administrators are hesitant of
upgrading the Mesa package in /usr/lib to anything beyond the
stable release. The servers do not have access to any
hardware based video so doing an updated hardware based driver
install won’t help either. I am limited to what I can do and
only have access to my home directory. Would it be possible
for me to compile a newer version of the Mesa driver in my
home directory and then compile chimera to use that version of
the driver instead of the default in /usr/lib? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!</p>
</div>
</blockquote>
<br>
If the Debian 5 system is a server, I would remote mount my home
directory on my workstation with the hardware graphics driver, and
run chimera locally. Or you might be able to copy libGL.so from
your workstation to a directory in your home directory on the server
and set the LD_LIBRARY_PATH environment variable to that directory.<br>
<br>
If the Debian 5 system is supposed to be a workstation, I would be
very tempted to reboot it with a Ubuntu Live CD and when done,
reboot it back to Debian 5, or maybe the administrators would be
willing to make it a dual-boot system. Your idea, of compiling a
software-only version of Mesa, should work if you set the
LD_LIBRARY_PATH environment variable appropriately.<br>
<br>
In the LD_LIBRARY_PATH cases above you would need to start chimera
from the command line after setting up the environment or start
chimera after editing the CHIMERA/bin/chimera shell script.<br>
<br>
Hope this helps,<br>
<br>
Greg<br>
<br>
</body>
</html>