<html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-forward-container"> <div class="moz-cite-prefix">On 12/3/2012 9:43 AM, Valerio Pachera wrote: </div> <blockquote cite="mid:CAHS0cb-VbvbO24RbhS7W=YpUZFMC2V-iUjcWqXcW75C3zqxkaw@mail.gmail.com" type="cite"> <pre wrap="">Hi, I have a class room with "recent" pc. I have trouble with them: they boot by network but do not always complete to load ldm. Sometime I get a black screen, sometime the preloader just hang up, and sometime it works... I'm testing now on one of the class room client and I get the above problems. Using another old pc I have (a pentium 4), I do not get the above problem. I also tried to use fat client configuration but nothing changes. The pc has an intel 82g33/g31 express integrated graphic controlloer and atheros comunication ar8121/ar8113/ar8114 network card. Cpu is a core duo. I tested pc ram and it's ok. When I get black screen or it hangs on the preloader, the last message on /var/log/syslog of the server is size of exported file device is 12345678 When it work, ather the 'size' message I see disconnect request received child exited with 0 Any advice is wellcome </pre> </blockquote> I wish I had a solution. I've been troubleshooting the *very same* problem, except that I'm running Lubuntu Quantal. Perhaps we can share some useful information. Are you also on Quantal, or something older? I'm using the LTSP-PNP setup with a single NIC rather than the standard LTSP5 setup with two NIC's. You? I'm using the default network-manager configuration to configure my NIC rather than the older approach with /etc/network/interfaces. You? I have not compiled any information yet about the chipsets, etc., from different clients that work or don't work. You? I was thinking about reinstalling Lubuntu Quantal to see if this happens on a fresh installation, perhaps on a test server. Have you tried that? My posts from another list (most recent posts on top): -------------------- Since the client syslogs always end with "ntpd[1314]: Listening on routing socket on fd #24 for interface updates" after a block of other ntpd items, I thought I would just disable ntpd on the client to see if that was the sticking point. I remember reading somewhere that if ntpd is not active, the system just uses the BIOS time. So I added ntpd to the RM_SYSTEM_SERVICES statement in lts.conf, but after a server reboot and a client boot ntpd appeared in the logs as before. So I also added ntpd to the RM_THIN_SYSTEM_SERVICES statement, but that did not prevent ntpd from running either. Are RM_SYSTEM_SERVICES and RM_THIN_SYSTEM_SERVICES ineffective for certain common services, or is there a dependency that prevents removal, or is this another bit of bad behavior? Perhaps also entering the picture is NTP Bug # 999725 (<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/999725">https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/999725</a>, which reports that in Ubuntu Precise, ntp is being started before DNS resolution is available. The bug is currently marked Expired due to inactivity. That bug is reminiscent of other startup timing/dependency sorts of problems that have cropped up when network-manager is used to configure the networking rather than the older scheme with /etc/network/interfaces. I am currently using network-manager with the experimental statement in /etc/dnsmasq.d/network-manager which replaces the "bind-interfaces" line with a "bind-dynamic" line. That solved a client boot error "PXE-E32: TFTP open timeout" on the only client that currently boots successfully. Ideas for troubleshooting or a work-around? ------------------- I finally got it set up so that client syslog messages forward to the server. I thought that this would somehow point me rather directly to the problem with some sort of a failure message. But that is not the case. The log simply ends ..... I hope someone else will be able to read something important from it or from the server syslog comparison between good and bad client boots (below in the previous message). Client syslog could not be attached due to a list size limit, but is downloadable from <a href="http://www.prpcompany.com/ltspclientlog.gz">http://www.prpcompany.com/ltspclientlog.gz</a> On 12/1/2012 5:11 PM, John Hupp wrote: > I have not been able to figure out how to send client syslog messages to the server, but I just compared the server syslog file from a case where the client got to a logon screen against a case where the client went from the splash screen to a blank, black screen. > > The logs are essentially the same to the point where I inserted a dash line, and the good-boot log continues with an ldminfod entry. (See below) > > The man page of ldminfod says: > > DESCRIPTION > > ldminfod will output the login sessions and locales available. it is > usually run from an inetd(8) instance. it is used by ldm(1) to remotely > determine available login and locale settings. > > EXAMPLE > > add the following lines to /etc/inetd.conf(5): > > 9571 stream tcp nowait nobody /usr/sbin/tcpd > /usr/sbin/ldminfod > > (I think /usr/sbin/ldiminfod is on the same line as 9571.) > > On the LTSP server, /etc/inetd.conf only has one line that is not commented out: > 9571 stream top nowait nobody /usr/sbin/ldminfod > > Does this add anything to help someone see what's going on? > > ----------------------------------- > > Excerpt from good boot syslog: > > Dec 1 16:34:10 Lubuntu1 dnsmasq-dhcp[880]: PXE(eth1) 00:50:da:64:39:4e proxy > Dec 1 16:34:13 Lubuntu1 dnsmasq-dhcp[880]: PXE(eth1) 192.168.1.135 00:50:da:64:39:4e /ltsp/i386/pxelinux.0 > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: error 0 TFTP Aborted received from 192.168.1.135 > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: failed sending /var/lib/tftpboot/ltsp/i386/pxelinux.0 to 192.168.1.135 > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: sent /var/lib/tftpboot/ltsp/i386/pxelinux.0 to 192.168.1.135 > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/44454c4c-43b4-1033-8050-b6c04f313031 not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/01-00-50-da-64-39-4e not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A80187 not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A8018 not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A801 not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A80 not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A8 not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0 not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C not found > Dec 1 16:34:14 Lubuntu1 dnsmasq-tftp[880]: sent /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default to 192.168.1.135 > Dec 1 16:34:15 Lubuntu1 dnsmasq-tftp[880]: sent /var/lib/tftpboot/ltsp/i386/vmlinuz-3.5.0-19-generic to 192.168.1.135 > Dec 1 16:34:21 Lubuntu1 dnsmasq-tftp[880]: sent /var/lib/tftpboot/ltsp/i386/initrd.img-3.5.0-19-generic to 192.168.1.135 > Dec 1 16:34:29 Lubuntu1 nbd_server[1613]: connect from 192.168.1.135, assigned file is /opt/ltsp/images/i386.img > Dec 1 16:34:29 Lubuntu1 nbd_server[1613]: Can't open authorization file /etc/ltsp/nbd-server.allow (No such file or directory). > Dec 1 16:34:29 Lubuntu1 nbd_server[1613]: Authorized client > Dec 1 16:34:29 Lubuntu1 nbd_server[1970]: Starting to serve > Dec 1 16:34:29 Lubuntu1 nbd_server[1970]: Size of exported file/device is 893980672 > Dec 1 16:34:35 Lubuntu1 dnsmasq-tftp[880]: sent /var/lib/tftpboot/ltsp/i386/lts.conf to 192.168.1.135 > Dec 1 16:34:38 Lubuntu1 nbd_server[1613]: connect from 192.168.1.135, assigned file is /tmp/nbd-swap/192.168.1.135 > Dec 1 16:34:38 Lubuntu1 nbd_server[1613]: Can't open authorization file /etc/ltsp/nbd-server.allow (No such file or directory). > Dec 1 16:34:38 Lubuntu1 nbd_server[1613]: Authorized client > Dec 1 16:34:38 Lubuntu1 nbd_server[1973]: Starting to serve > Dec 1 16:34:38 Lubuntu1 nbd_server[1973]: Size of exported file/device is 536870912 > ----------------------------------------------------------------- > Dec 1 16:34:53 Lubuntu1 ldminfod[1982]: connect from 192.168.1.135 (192.168.1.135) > Dec 1 16:34:59 Lubuntu1 nbd_server[1613]: connect from 192.168.1.135, assigned file is /opt/ltsp/images/i386.img > Dec 1 16:34:59 Lubuntu1 nbd_server[1613]: Can't open authorization file /etc/ltsp/nbd-server.allow (No such file or directory). > Dec 1 16:34:59 Lubuntu1 nbd_server[1613]: Authorized client > Dec 1 16:34:59 Lubuntu1 nbd_server[1993]: Starting to serve > Dec 1 16:34:59 Lubuntu1 nbd_server[1993]: Size of exported file/device is 893980672 > Dec 1 16:34:59 Lubuntu1 nbd_server[1993]: Disconnect request received. > Dec 1 16:34:59 Lubuntu1 nbd_server[1613]: Child exited with 0 > > > > On 11/29/2012 5:53 PM, John Hupp wrote: >> I thought I might be working through my last few big problems, but instead I found another one. >> >> After installing Lubuntu Quantal on a newly formatted disk and setting up LTSP some weeks ago, I have been working only with a certain two-machine test setup. In contrast to past troubleshooting, I have not been swapping in multiple server or client machines. >> >> But to address something I was working on, I tried a different client, and this one failed to boot altogether. Then I tried a couple more different clients (different makes/models), and they had the same behavior. That behavior is that after the client displays the blue splash screen, which then drops to black-and-white (normal behavior, I think), it then goes to a blank (black) screen. It does not display the GUI login screen. >> >> If in lts.conf I set SCREEN_07=shell, then I can successfully log in to a shell. I also see there among the on-screen boot messages "Starting load fallback graphics devices [fail]." >> >> The last entry in dmesg also refers to the above failure. >> >> The only client that works displays a (boot) message on/through the splash screen: "lpc_ich 0000:00:1f.0: I/O space for GPIO uninitialized." >> >> Anyone recognize this problem? </div> </body> </html>