I'm currently troubleshooting a problem with a Lubuntu Quantal setup with LTSP (terminal server network).
Most of the clients stop responding at a blank/black screen during bootup. But only after successfully PXE network booting, getting DHCP assignments, and beginning the process of booting from an NBD image on the server. I see the Lubuntu splash screen and then the blank/black screen.
I set up forwarding of the client syslog messages to the server, and the logs always end at a block of ntpd items, the last of which is "ntpd[1314]: Listening on routing socket on fd #24 for interface updates"
I'm using network-manager for the network configuration. This is the default config, except that I am using 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.
I'm currently troubleshooting a problem with a Lubuntu Quantal setup with LTSP (terminal server network).
Most of the clients stop responding at a blank/black screen during bootup. But only after successfully PXE network booting, getting DHCP assignments, and beginning the process of booting from an NBD image on the server. I see the Lubuntu splash screen and then the blank/black screen.
I set up forwarding of the client syslog messages to the server, and the logs always end at a block of ntpd items, the last of which is "ntpd[1314]: Listening on routing socket on fd #24 for interface updates"
I'm using network-manager for the network configuration. This is the default config, except that I am using 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.
This bug seems to have some behavior in common with Bug # 959037 at https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/959037 which also addresses DNS-related bootup problems.
Comments? Troubleshooting? Workarounds?