<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Good news! <div class="moz-forward-container"> Richard Doyle from the LTSP mail list posted that I can add acpi=force to the end of the append command in /var/lib/tftpboot/ltsp/<arch>/pxelinux.cfg/default. I did this on my Edubuntu and Lubuntu LTSP servers, and all clients tested then shut down fully. The only remaining problem, which seems to this newbie like a bug rather than a feature, is what Richard Doyle points out (I have not it confirmed here, but his other info was dead-on-center): running ltsp-update-image will restore the original /var/lib/tftpboot/ltsp/<arch>/pxelinux.cfg/default, so this and any other edits are wiped out. And I still have a related secondary question: Since acpi=force indicates that ACPI has to run on the client and not just on the server, how can I verify that ACPI is indeed running on the client? Someone suggested looking at the output of dmesg on the client for results that contain "ACPI," but it seems to me that this will just report the boot messages from the server, not the client. A big thank-you to all who contributed to solving the original primary problem. Special thanks to Richard Doyle from the LTSP mail list and Steve Yorvyk from this list. <div class="moz-cite-prefix">On 9/5/2012 5:56 PM, John Hupp wrote: </div> <blockquote cite="mid:5047CA7A.6000909@prpcompany.com" type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> VERY intriguing. Anyone know how to set an equivalent parameter for LTSP clients? [Marco Muller posted to the LTSP a solution that did not work for him. See <a moz-do-not-send="true" href="http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg40651.html">http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg40651.html</a>, but he reports that he edited /var/lib/tftpboot/ltsp/amd64/pxelinux.cfg/default to add append ro initrd=initrd.img root=/dev/nbd0 init=/sbin/init-ltsp quiet splash acpi=force plymouth:force-splash vt.handoff=7 nbdroot=:ltsp_amd64 and nobody posted a reply.] And in connection with that configuration question (OK, I'm really showing my newbie stripes here), how do I verify whether ACPI is running? <div class="moz-cite-prefix">On 9/3/2012 4:15 PM, Yorvyk wrote: </div> <blockquote cite="mid:50450FC7.2050201@googlemail.com" type="cite">On 03/09/12 17:07, Yorvyk wrote: <blockquote type="cite"> Some reading matter that may be of help: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://forums.fedoraforum.org/archive/index.php/t-306.html">http://forums.fedoraforum.org/archive/index.php/t-306.html</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.mail-archive.com/eug-lug@efn.org/msg16221.html">http://www.mail-archive.com/eug-lug@efn.org/msg16221.html</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.lesswatts.org/projects/acpi/">http://www.lesswatts.org/projects/acpi/</a> I have a couple of machines that exhibit this problem and will be trying the various suggestions from the above this evening. </blockquote> In my case the problem was rectified by adding 'acpi=force' to the boot params. -- Steve </blockquote> </blockquote> </div> </body> </html>