Hi Everyone, I have three old Dell Dimension L800CXE computers laying around and I thought that they would make great LTSP terminals for training purposes. I have a whole company (about 60 terminals) running off of an LTSP server and I love it. The problem is that the Dell systems have an Intel i810 video chip and even though they connect to the xserver just fine, they lock up completely after about a minute of clicking around. I've tried various X_MODE and X_VIDEORAM and XSERVER settings in LTS.CONF, but I just can't get it to work. I was wondering if anyone else has had this problem before and perhaps knows a workaround or solution. I have gone through the LTSP Wiki and tried the various suggestions, but nothing seems to work. I'm running LTSP v4.2 on Fedora Core 5.
Thanks, Tanner ----- Original Message ----- From: [EMAIL PROTECTED] To: [email protected] Sent: Monday, August 27, 2007 12:07:09 PM (GMT-0700) America/Phoenix Subject: Ltsp-discuss Digest, Vol 15, Issue 30 Send Ltsp-discuss mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/ltsp-discuss or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Ltsp-discuss digest..." Today's Topics: 1. Re: I need to remote reboot a LTSP 5 client (Scott Balneaves) 2. Re: I need to remote reboot a LTSP 5 client (Jean-Michel Dault) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Aug 2007 13:22:02 -0500 From: Scott Balneaves <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] I need to remote reboot a LTSP 5 client To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sherwood Botsford wrote: > Why are you reluctant to run ssh? The biggest problem with running sshd on the thin client is mainly a performance issue: if you've got 1ghz clients with goodly amount of ram, yeah, it's a great solution. Problem is, we've got a lot of people running some really low end hardware, who, understandably, want all the bells and whistles, but have some acheingly bad hardware. Just a few weeks ago, I bumped into a fellow who's got a few hundred machines with, like, 200 Mhz processors and 16 megs (!) of ram. They worked, barely, on an older ltsp version with a 2.4 kernel, but now don't under ltsp5, due to 2.6 kernels being much bigger, and the size of the initramfs. Of course, he wanted sound, localdevs, graphics, and any other bling going that he could. We couldn't make it work for him, and the last time I talked, he was going to have to see about finding more ram for the boxes. > Method 2: > On the server create a new file system. Can be quite small. > Let it be mountable rw by all clients. Mount it as > "remote_commands" In this directory, create a directory for each > client, with the name of the cleint. > > On the client, create a cron job that periodically checks for the > contents of /remote_commands/`hostname`/ > If it finds a script there, it copies the script to /tmp, deletes > the script from the server, then executes it. (Or the last line > of the script can delete the script. I like this method, however, only thing I'd change would be to replace cron with a small inotify util. It would be small, with a low memory consumption. Scott -- Scott L. Balneaves | "Eternity is a very long time, Systems Department | especially towards the end." Legal Aid Manitoba | -- Woody Allen ------------------------------ Message: 2 Date: Mon, 27 Aug 2007 14:46:34 -0400 From: Jean-Michel Dault <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] I need to remote reboot a LTSP 5 client To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 Le lundi 27 ao?t 2007 ? 13:22 -0500, Scott Balneaves a ?crit : > The biggest problem with running sshd on the thin client is mainly > a performance issue: if you've got 1ghz clients with goodly amount > of ram, yeah, it's a great solution. Problem is, we've got a lot > of people running some really low end hardware, who, understandably, > want all the bells and whistles, but have some acheingly bad hardware. Don't forget that you can run ssh under inetd/xinetd, which means that, until there's a connection, you don't use any resources. Many LTSP services could benefit from inetd/xinetd: - printing - reboot - local applications - ltspfs - etc. The main disadvantage of running xinetd is that it adds a small delay, but for all these services, it's not a problem. -- Jean-Michel Dault <[EMAIL PROTECTED]> R?volution Linux inc. ------------------------------ ------------------------------------------------------------------------- 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 End of Ltsp-discuss Digest, Vol 15, Issue 30 ******************************************** ------------------------------------------------------------------------- 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
