On Mon, Nov 05, 2007 at 11:29:51AM +0100, Hans Ekbrand wrote: > Hello ltsp-discuss! > > I am returning to this list after a long break. I met with a > particular problem which I couldn't resolve by myself, so now I am > turning to you. > > I was installing a scientific/statistical application, R, onto the LTSP > server using a LTSP-client. (This is on LTSP 4.2) > > The installation failed due to: > > "RGL: GLX extension missing on server" > > I have put output of glxinfo, glxgears -info and xdpyinfo near the end of > this letter. > > I added > > Load "dri" > Load "glx" > Load "GLcore" > > to the modules section of xorg.conf, but it didn't help. > > This client has an old non 3D graphics card (Matrox 2064W > [Millenium]), but software-rendering 3D is all I need. > > I have three questions to the list:
And now I have spent some time debugging this. Here is the answers (and at the end some debugging tips). > 1. I was looking for a log file from X, but didn't find any. Where is it > supposed to be (in LTSP 4.2)? It is in /tmp/mnt/xorg.log The location of the logfile is determined by /etc/screen.d/startx (in the ltsp tree). > 2. Can it be a lack of memory problem? The X server runs at > [EMAIL PROTECTED], but I don't know how much memory the card has (since I > don't find the log-file from X)? No, DRI complained about lack of memory, but for software rendering DRI was not needed. > 3. What might be missing from my /opt/ltsp/i386/ tree that causes > software-rendering 3D to not work? Nothing (because /opt/ltsp/i386/usr/X11R6/lib/modules/extensions/libglx.so was already there). Some tips for the archive: 1. To get the glx module loaded use a customized XF86Config for that (class of) thin clients. 2. When debugging X, note that there is *no point* in editing /tmp/XF86Config.2, since that file is rebuilt everytime X is restarted. (the rebuild is done by /opt/ltsp/i386/etc/screen.d/startx which in turn calls /opt/ltsp/i386/etc/build_x4_cfg). 3. When creating a customized XF86Config, use a temporary writable nfs-mount to get a copy of the /tmp/XF86Config.2 from the thin client. I used the directory for swapfiles for this purpose: # mkdir tmpmount # mount -o nolock -t nfs ip.of.server:/var/opt/ltsp/swapfiles tmpmount # cp /tmp/XF86Config.2 tmpmount/ Then from the server-side edit /var/opt/ltsp/swapfiles/XF86Config.2 and save as /opt/ltsp/i386/etc/XF86Config.custom or something like that. Add an entry in lts.conf so the scripts that build the /tmp/XF86Config.2 will copy the static customized file instead of building a new: XF86CONFIG_FILE = XF86Config.custom in the section of that (class of) thin client(s). -- Hans Ekbrand ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
