<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, 7 Jun 2018 at 03:46, Nicolas Thierry-Mieg <<a href="mailto:Nicolas.Thierry-Mieg@univ-grenoble-alpes.fr">Nicolas.Thierry-Mieg@univ-grenoble-alpes.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On 06/07/2018 05:48 AM, John Adegbile wrote:<br>
> I finally got to try out the solution posted. Unfortunately, it did not <br>
> work for me though. The error I now get is:<br>
> <br>
> 22.409] (II) LoadModule: "glx"<br>
> [ 22.409] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so<br>
> [ 22.409] (EE) Failed to load <br>
> /usr/lib64/xorg/modules/extensions/libglx.so: libGL.so.1: cannot open <br>
> shared object file: No such file or directory<br>
> [ 22.409] (II) UnloadModule: "glx"<br>
> [ 22.409] (II) Unloading glx<br>
> [ 22.409] (EE) Failed to load module "glx" (loader failed, 7)<br>
> <br>
<br>
that's strange. At least X is trying to load the correct libglx.so. <br>
Don't you have mesa-libGL installed?<br>
sudo yum install mesa-libGL<br>
<br>
If that doesn't fix it, what's your output for<br>
find /usr -name libGL.so.1<br>
_______________________________________________<br>
elrepo mailing list<br>
<a href="mailto:elrepo@lists.elrepo.org" target="_blank">elrepo@lists.elrepo.org</a><br>
<a href="http://lists.elrepo.org/mailman/listinfo/elrepo" rel="noreferrer" target="_blank">http://lists.elrepo.org/mailman/listinfo/elrepo</a></blockquote><div><br></div><div>Thanks for all your help with this!</div><div><br></div><div>As you suspected, I did not have mesa-libGL installed. I installed this, rebooted, and..........I still can't get to an x windows session!!! The last 3 messages I see during the startup before the machine hangs is:</div><div><br></div><div>[ok] Started gnome display manager</div><div>[ok] Started System Logging Service<br></div><div>[ok] Started Virtualization daemon<br></div><div><br></div><div>There are no x related errors in the Xorg.logs.</div><div><br></div><div>I'm not quite sure what to do now...</div></div></div>