Re: [Ltsp-discuss] Many clients do not display login screen, just a blank screen

Tue, 11 Dec 2012 14:58:35 -0800

Thinking about it a bit further, I should be able to use a custom startup script in /usr/share/ltsp/init-ltsp.d to set up an xorg_ltsp.conf that does not affect the server, but the other questions remain. 

On 12/11/2012 5:03 PM, John Hupp wrote:
With a very tenuous understanding of xorg workings, I created the directory /etc/X11/xorg.conf.d, and in that, a file named xorg_ltsp.conf (must end with .conf). Contents: 

Section "Device"
    Identifier  "Card2"
    Driver      "vesa"
    BusID       "PCI:0:8:0"
EndSection


The default Identifier "Card0" might have worked also, but I was fuzzy 
about bad interactions with video card configuration on the server.



And rightly so, it seems.  The server had been using the ATI driver, 
but now it is using the FBDEV driver.  This despite the fact that the 
above Device section specifies a BusID that does not match the BusID 
of the server's video card.



But apart from that, in the client an ATI Mach64 card that had stalled 
with cycling black/blank screens now proceeds to the login and then to 
a normal desktop.



So I confirmed the theory that the behavior is related to some driver 
issue despite a normal-looking client Xorg log, but I don't yet know 
how to best solve the client problem without affecting the server. And 
I would prefer to solve the client problem by making the more capable 
driver work (here, the ATI driver).


On 12/11/2012 12:20 PM, John Hupp wrote:

My understanding of this problem has evolved some, so I am keeping 
the topic but writing afresh on the description.



It now appears that there are two groups of problems.  For one group, 
the client's /var/log/Xorg.?.log makes it clear that there is a video 
driver problem, and I am putting that group aside for the moment.



For the other group, the client's /var/log/Xorg.?.log looks normal, 
but during startup after the splash screen it never reaches the login 
screen, and instead there is a cycling between blank and black 
screens.  And with client syslog messages forwarded to the server, 
there is a loop of NBD messages in the server syslog, initially mixed 
with NTP/D messages, but eventually settling down to just the loop of 
NBD messages (see toward the bottom):


(snipped normal-looking part of server syslog ...)

Dec 11 09:57:00 ltsp137 modem-manager[1087]: <info> Successfully 
loaded 20 plugins
Dec 11 09:57:04 Lubuntu1 nbd_server[1685]: connect from 
192.168.1.137, assigned file is /opt/ltsp/images/i386.img
Dec 11 09:57:04 Lubuntu1 nbd_server[1685]: Can't open authorization 
file /etc/ltsp/nbd-server.allow (No such file or directory).

Dec 11 09:57:04 Lubuntu1 nbd_server[1685]: Authorized client
Dec 11 09:57:04 Lubuntu1 nbd_server[2238]: Starting to serve

Dec 11 09:57:04 Lubuntu1 nbd_server[2238]: Size of exported 
file/device is 923074560
Dec 11 09:57:06 ltsp137 kernel: [   31.545915]  nbd9: unknown 
partition table

Dec 11 09:57:04 Lubuntu1 nbd_server[2238]: Disconnect request received.
Dec 11 09:57:04 Lubuntu1 nbd_server[1685]: Child exited with 0
Dec 11 09:57:06 ltsp137 kernel: [   31.552578] block nbd9: NBD_DISCONNECT

Dec 11 09:57:06 ltsp137 kernel: [   31.553503] block nbd9: Receive 
control failed (result -32)

Dec 11 09:57:06 ltsp137 kernel: [   31.553592] block nbd9: queue cleared

Dec 11 09:57:07 ltsp137 ntpdate[890]: step time server 128.138.140.44 
offset -1.585937 sec
Dec 11 09:57:07 ltsp137 ntpd[1216]: ntpd 4.2.6p3@1.2290-o Mon Aug 20 
14:49:15 UTC 2012 (1)

Dec 11 09:57:07 ltsp137 ntpd[1217]: proto: precision = 0.503 usec

Dec 11 09:57:07 ltsp137 ntpd[1217]: ntp_io: estimated max 
descriptors: 1024, initial socket boundary: 16
Dec 11 09:57:07 ltsp137 ntpd[1217]: Listen and drop on 0 v4wildcard 
0.0.0.0 UDP 123
Dec 11 09:57:07 ltsp137 ntpd[1217]: Listen and drop on 1 v6wildcard 
:: UDP 123
Dec 11 09:57:07 ltsp137 ntpd[1217]: Listen normally on 2 lo 127.0.0.1 
UDP 123
Dec 11 09:57:07 ltsp137 ntpd[1217]: Listen normally on 3 eth0 
192.168.1.137 UDP 123
Dec 11 09:57:07 ltsp137 ntpd[1217]: Listen normally on 4 eth0 
fdd9:1d03:df5:0:250:4ff:feb0:ccfe UDP 123
Dec 11 09:57:07 ltsp137 ntpd[1217]: Listen normally on 5 eth0 
fe80::250:4ff:feb0:ccfe UDP 123
Dec 11 09:57:07 ltsp137 ntpd[1217]: Listen normally on 6 eth0 
fdd9:1d03:df5:0:4dd4:a667:5962:d43f UDP 123

Dec 11 09:57:07 ltsp137 ntpd[1217]: Listen normally on 7 lo ::1 UDP 123
Dec 11 09:57:07 ltsp137 ntpd[1217]: peers refreshed

Dec 11 09:57:07 ltsp137 ntpd[1217]: Listening on routing socket on fd 
#24 for interface updates

Dec 11 09:57:12 ltsp137 ntpd[1217]: ntpd exiting on signal 15

Dec 11 09:57:13 Lubuntu1 nbd_server[1685]: connect from 
192.168.1.137, assigned file is /opt/ltsp/images/i386.img
Dec 11 09:57:13 Lubuntu1 nbd_server[1685]: Can't open authorization 
file /etc/ltsp/nbd-server.allow (No such file or directory).

Dec 11 09:57:13 Lubuntu1 nbd_server[1685]: Authorized client
Dec 11 09:57:13 Lubuntu1 nbd_server[2239]: Starting to serve

Dec 11 09:57:13 Lubuntu1 nbd_server[2239]: Size of exported 
file/device is 923074560
Dec 11 09:57:13 ltsp137 kernel: [   40.306413]  nbd9: unknown 
partition table

Dec 11 09:57:13 Lubuntu1 nbd_server[2239]: Disconnect request received.
Dec 11 09:57:13 Lubuntu1 nbd_server[1685]: Child exited with 0
Dec 11 09:57:13 ltsp137 kernel: [   40.313194] block nbd9: NBD_DISCONNECT

Dec 11 09:57:13 ltsp137 kernel: [   40.314074] block nbd9: Receive 
control failed (result -32)

Dec 11 09:57:13 ltsp137 kernel: [   40.314148] block nbd9: queue cleared

Dec 11 09:57:17 Lubuntu1 nbd_server[1685]: connect from 
192.168.1.137, assigned file is /opt/ltsp/images/i386.img
Dec 11 09:57:17 Lubuntu1 nbd_server[1685]: Can't open authorization 
file /etc/ltsp/nbd-server.allow (No such file or directory).

Dec 11 09:57:17 Lubuntu1 nbd_server[1685]: Authorized client
Dec 11 09:57:17 Lubuntu1 nbd_server[2240]: Starting to serve

Dec 11 09:57:17 Lubuntu1 nbd_server[2240]: Size of exported 
file/device is 923074560
Dec 11 09:57:17 ltsp137 kernel: [   44.066204]  nbd9: unknown 
partition table

Dec 11 09:57:17 Lubuntu1 nbd_server[2240]: Disconnect request received.
Dec 11 09:57:17 Lubuntu1 nbd_server[1685]: Child exited with 0
Dec 11 09:57:17 ltsp137 kernel: [   44.072999] block nbd9: NBD_DISCONNECT

Dec 11 09:57:17 ltsp137 kernel: [   44.073591] block nbd9: Receive 
control failed (result -32)

Dec 11 09:57:17 ltsp137 kernel: [   44.073644] block nbd9: queue cleared

Dec 11 09:57:21 Lubuntu1 nbd_server[1685]: connect from 
192.168.1.137, assigned file is /opt/ltsp/images/i386.img
Dec 11 09:57:21 Lubuntu1 nbd_server[1685]: Can't open authorization 
file /etc/ltsp/nbd-server.allow (No such file or directory).

Dec 11 09:57:21 Lubuntu1 nbd_server[1685]: Authorized client
Dec 11 09:57:21 Lubuntu1 nbd_server[2241]: Starting to serve

Dec 11 09:57:21 Lubuntu1 nbd_server[2241]: Size of exported 
file/device is 923074560
Dec 11 09:57:21 ltsp137 kernel: [   47.831221]  nbd9: unknown 
partition table

Dec 11 09:57:21 Lubuntu1 nbd_server[2241]: Disconnect request received.
Dec 11 09:57:21 Lubuntu1 nbd_server[1685]: Child exited with 0
Dec 11 09:57:21 ltsp137 kernel: [   47.837973] block nbd9: NBD_DISCONNECT

Dec 11 09:57:21 ltsp137 kernel: [   47.838709] block nbd9: Receive 
control failed (result -32)
Dec 11 09:57:21 ltsp137 kernel: [   47.838800] block nbd9: shutting 
down socket

Dec 11 09:57:21 ltsp137 kernel: [   47.838819] block nbd9: queue cleared

Dec 11 09:57:23 ltsp137 ntpdate[1301]: adjust time server 
208.53.158.34 offset 0.001939 sec
Dec 11 09:57:23 ltsp137 ntpd[1633]: ntpd 4.2.6p3@1.2290-o Mon Aug 20 
14:49:15 UTC 2012 (1)

Dec 11 09:57:23 ltsp137 ntpd[1634]: proto: precision = 0.505 usec

Dec 11 09:57:23 ltsp137 ntpd[1634]: ntp_io: estimated max 
descriptors: 1024, initial socket boundary: 16
Dec 11 09:57:23 ltsp137 ntpd[1634]: Listen and drop on 0 v4wildcard 
0.0.0.0 UDP 123
Dec 11 09:57:23 ltsp137 ntpd[1634]: Listen and drop on 1 v6wildcard 
:: UDP 123
Dec 11 09:57:23 ltsp137 ntpd[1634]: Listen normally on 2 lo 127.0.0.1 
UDP 123
Dec 11 09:57:23 ltsp137 ntpd[1634]: Listen normally on 3 eth0 
192.168.1.137 UDP 123
Dec 11 09:57:23 ltsp137 ntpd[1634]: Listen normally on 4 eth0 
fdd9:1d03:df5:0:250:4ff:feb0:ccfe UDP 123
Dec 11 09:57:23 ltsp137 ntpd[1634]: Listen normally on 5 eth0 
fe80::250:4ff:feb0:ccfe UDP 123
Dec 11 09:57:23 ltsp137 ntpd[1634]: Listen normally on 6 eth0 
fdd9:1d03:df5:0:4dd4:a667:5962:d43f UDP 123

Dec 11 09:57:23 ltsp137 ntpd[1634]: Listen normally on 7 lo ::1 UDP 123
Dec 11 09:57:23 ltsp137 ntpd[1634]: peers refreshed

Dec 11 09:57:23 ltsp137 ntpd[1634]: Listening on routing socket on fd 
#24 for interface updates
Dec 11 09:57:24 Lubuntu1 nbd_server[1685]: connect from 
192.168.1.137, assigned file is /opt/ltsp/images/i386.img
Dec 11 09:57:24 Lubuntu1 nbd_server[1685]: Can't open authorization 
file /etc/ltsp/nbd-server.allow (No such file or directory).

Dec 11 09:57:24 Lubuntu1 nbd_server[1685]: Authorized client
Dec 11 09:57:24 Lubuntu1 nbd_server[2242]: Starting to serve

Dec 11 09:57:24 Lubuntu1 nbd_server[2242]: Size of exported 
file/device is 923074560
Dec 11 09:57:24 ltsp137 kernel: [   51.675584]  nbd9: unknown 
partition table

Dec 11 09:57:24 Lubuntu1 nbd_server[2242]: Disconnect request received.
Dec 11 09:57:24 Lubuntu1 nbd_server[1685]: Child exited with 0
Dec 11 09:57:24 ltsp137 kernel: [   51.682372] block nbd9: NBD_DISCONNECT

Dec 11 09:57:24 ltsp137 kernel: [   51.683392] block nbd9: Receive 
control failed (result -32)

Dec 11 09:57:24 ltsp137 kernel: [   51.683470] block nbd9: queue cleared

Dec 11 09:57:28 Lubuntu1 nbd_server[1685]: connect from 
192.168.1.137, assigned file is /opt/ltsp/images/i386.img
Dec 11 09:57:28 Lubuntu1 nbd_server[1685]: Can't open authorization 
file /etc/ltsp/nbd-server.allow (No such file or directory).

Dec 11 09:57:28 Lubuntu1 nbd_server[1685]: Authorized client
Dec 11 09:57:28 Lubuntu1 nbd_server[2243]: Starting to serve

Dec 11 09:57:28 Lubuntu1 nbd_server[2243]: Size of exported 
file/device is 923074560
Dec 11 09:57:28 ltsp137 kernel: [   55.424453]  nbd9: unknown 
partition table

Dec 11 09:57:28 Lubuntu1 nbd_server[2243]: Disconnect request received.
Dec 11 09:57:28 Lubuntu1 nbd_server[1685]: Child exited with 0
Dec 11 09:57:28 ltsp137 kernel: [   55.438244] block nbd9: NBD_DISCONNECT

Dec 11 09:57:28 ltsp137 kernel: [   55.438792] block nbd9: Receive 
control failed (result -32)

Dec 11 09:57:28 ltsp137 kernel: [   55.438844] block nbd9: queue cleared

Dec 11 09:57:32 Lubuntu1 nbd_server[1685]: connect from 
192.168.1.137, assigned file is /opt/ltsp/images/i386.img
Dec 11 09:57:32 Lubuntu1 nbd_server[1685]: Can't open authorization 
file /etc/ltsp/nbd-server.allow (No such file or directory).

Dec 11 09:57:32 Lubuntu1 nbd_server[1685]: Authorized client
Dec 11 09:57:32 Lubuntu1 nbd_server[2245]: Starting to serve

Dec 11 09:57:32 Lubuntu1 nbd_server[2245]: Size of exported 
file/device is 923074560
Dec 11 09:57:32 ltsp137 kernel: [   59.196619]  nbd9: unknown 
partition table

Dec 11 09:57:32 Lubuntu1 nbd_server[2245]: Disconnect request received.
Dec 11 09:57:32 Lubuntu1 nbd_server[1685]: Child exited with 0
Dec 11 09:57:32 ltsp137 kernel: [   59.203549] block nbd9: NBD_DISCONNECT

Dec 11 09:57:32 ltsp137 kernel: [   59.204048] block nbd9: Receive 
control failed (result -32)

Dec 11 09:57:32 ltsp137 kernel: [   59.204100] block nbd9: queue cleared


I read in an IRC archive that the nbd9 messages are somehow normal: 
"nbd9 disconnection is normal, it's just a way to check for a newer 
chroot image, in order for the clients to automatically reboot."  I 
don't quite know what that means, other than it indicates that broken 
nbd/server is not the problem here.



In at least one case with a certain video chipset, that cycling block 
of messages has this message interspersed just before many of the 
"nbd9: unknown partition table" messages:
    Dec 10 20:28:10 ltsp138 kernel: [   82.844422] ldm[4166]: 
segfault at 8 ip 0804baf4 sp bf8ab830 error 4 in ldm[8048000+6000]
I think for that case, the black screen shows a spinning progress 
screen pointer for a moment before it goes to the blank screen.



Since the problem goes away with known-working video chipsets, the 
startup failure seems video related, but I have not been able to pin 
down the failure mechanism.



If I don't get more pointed advice in the meantime, I think I'm going 
to work on learning how to use xorg.conf to force usage of perhaps 
the vesa driver.  And if that works, then try to troubleshoot the 
primary intended driver.  My working theory is that, despite the 
good-looking xorg log, this is still a video driver problem.




------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d


_____________________________________________________________________
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




------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d


_____________________________________________________________________
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



------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_____________________________________________________________________
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























					Reply via email to