Anders Bruun Olsen wrote: > Tanner Bachman wrote: >> I currently have about 35 terminals connected to an LTSP server and >> everything runs fine. I setup a cronjob to shutdown all the terminals at >> 8:00PM each night. The cronjob runs a shell script that essesentially runs >> the following command: ltspinfo --shutdown -h xxx.xxx.xxx.xxx All the >> terminals power off and the world stays round. However, yesterday I added >> another terminal to the mix. This terminal is based around the VIA >> EPIA-M10000-LVDS mini-ITX motherboard. I built the system and set it up >> normally on the LTSP server and it boots right up and runs fine...and then >> later that night the server powered it down along with all the other >> terminals. This morning I tried to boot the new terminal up and it exits >> the PXE boot before even trying to contact the DHCP server. I poked around >> in the BIOS and everything is set properly, but what finally did the trick >> was removing power (physically unplugging the system) and then plugging it >> in again. I have tested this several times today by manually running the >> ltspinfo command on that terminal and each time it refuses to boot afterward >> unless it's unplugged first. Obviously it's jamming up the network >> interface and locking out the ROM option. I'm just curious as to whether or >> not anyone else has had an issue like this before. I know that I haven't >> with any other computers on the network and they are not all the same. For >> reference, this board uses the VIA CLE266/VT8235 Chipset and the LAN >> interface is controlled by the VIA VT6103 chip. Any thoughts would be much >> appreciated. > > I have about 30 terminals based on Epia ME6000 exhibiting this exact > problem. I have yet to find any other solution to it than not shutting > them down properly but instead just instructing users to hold the > powerbutton until they shut off. That obviosly isn't a solution for you > and a poor one for me, so if anybody has a real solution for this > problem it would be great! > This might be waaay off base, but have you tried running ether-wake, or some other Wake-On-LAN tool, to try to wake the client up?
Petre ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _____________________________________________________________________ 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
