On Tue, 2007-11-13 at 06:30 -0800, [EMAIL PROTECTED] wrote: > >You do not need any i386 libs on the server side. But your NFS > >exported root is fully i386. > > That's the way I thought (hoped) it would work. I figured the whole > of the > i386 stuff would be contained within the ltsp directory itself. > > > Can you connect a working linux computer on the system; go on a > > virtual text console and launch 'X :1 -query a.b.c.d' where a.b.c.d > is > > the LTSP server IP address. > > I'm not entirely sure what I'm supposed to see when I do this. > > I just ssh-ed into another computer on my network and here is what I > got when > I ran that command. (My LTSP server is 192.168.0.2) > > X :1 -query 192.168.0.2 > > X Window System Version 1.3.0 > Release Date: 19 April 2007 > X Protocol Version 11, Revision 0, Release 1.3 > Build Operating System: Fedora Core 7 Red Hat, Inc. > Current Operating System: Linux mutt.melvilletheatre.net > 2.6.22.9-91.fc7 #1 SMP > Thu Sep 27 23:10:59 EDT 2007 i686 Build Date: 11 June 2007 > Build ID: xorg-x11-server 1.3.0.0-9.fc7 > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.1.log", Time: Mon Nov 12 16:42:36 2007 > (==) Using config file: "/etc/X11/xorg.conf" > (II) Module already built-in > (II) Module already built-in > (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. > (EE) AIGLX: Screen 0 is not DRI capable > > It seemed to hang here. After I hit ctrl-c, I got this: > > FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing. > > And that's all there was. > > Incidentally, the Gnome display on the computer that I ssh-ed into to > do that > disappeared and went to the grey screen with an X in the middle until > I hit > ctrl-c. > > > If it does not work, you have a problem with your server (firewall > or > > something), but not with LTSP. If it does work, it's an LTSP > problem, > > your clients are not configured properly. > > So... what do you think? I have a working Centos 5/i386 setup using > this very > same model of terminal, and I was using this exact terminal on this > computer > under Fedora 7/i386. I'm reasonably sure that I have this new x86_64 > setup the > same as I had it before. I'm probably missing something.
You've got the answer, that (so far) this is nothing to do with ltsp. Do the X -query: You get a normal login screen on the server Solve your server running XDMCP. It all does work, XDMCP and LDM on 32 and 64 hosts. ltsp cannot work until your remote login works James ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _____________________________________________________________________ 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
