LTSP thin client failure to boot

Bug #528233 reported by Nathan Murray
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ltsp (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: ltsp-server-standalone

I have installed test case: Install (LTSP server)
Link: http://testcases.qa.ubuntu.com/Testing/Cases/LTSPServer

The install completes. When trying to boot the thin client the loading process freezes with the ubuntu logo on the screen.

Thin client just hangs.

Same system runs thin client using 9.10.

ProblemType: Bug
Architecture: i386
Date: Fri Feb 26 00:49:45 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
Package: ltsp-server-standalone 5.2-0ubuntu4
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SourcePackage: ltsp
Uname: Linux 2.6.32-14-generic i686

Revision history for this message
Nathan Murray (yotux) wrote :
tags: added: iso-testing
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

Try running: sudo gedit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
removing "quiet splash" from there to better see any error messages,
and rebooting the client.
Post as much lines as you can from the client output, starting from the bottom.

E.g. it could be a DHCP problem on your network, or a module problem with your network card. What network card does your client have? Can you try with another client?

Revision history for this message
Nathan Murray (yotux) wrote :

My thin client has a network card. is the following:

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

I don't have another thin client to use. I will try the commands listed above and report the details.

Revision history for this message
Nathan Murray (yotux) wrote :

When I hit alr- cntrl -del a message displays. init disconnect system bus.

How can I get an output from the client that goes to black screen.

Revision history for this message
Nathan Murray (yotux) wrote :

I have attached the log files for my system. One is title for 9.10 os which works and the other is for 10.04 alpha 3. The log files are the syslog file.

Revision history for this message
Nathan Murray (yotux) wrote :

Log from Server Ubuntu 10.04 alpha 3

Revision history for this message
Ken (klong) wrote :

For what it's worth, I was seeing the exact same problem you described. I even loaded up two different servers - one from the normal server distro and added this package and the other from the alternate CD and picked the LTSP server mode. Both were failing. By removing "quiet splash" like the one person suggested above, I found that I was getting a crash in init and showing that it was trying to use an IP address as a variable where it shouldn't be. (this came right after udhcp was running) Turned out, that address it was sticking in there was from where I define TWO ntp servers on my dhcp server. By changing the individual entry to just have ONE address after "options ntp-servers", the problem went away and I was able to boot up the terminal.

Dunno if that might be the case for you too or not, but that sure fixed it for me. Not sure which package that problem would be with or I'd file a bug report on it... We shouldn't be limited to one ntp server, I don't think. (unless I missed that in the RFC somewhere...)

-Ken

Revision history for this message
Stéphane Graber (stgraber) wrote :

Can you confirm it also happens to you with the final 10.04 release and more importantly with 11.04?

Changed in ltsp (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ltsp (Ubuntu) because there has been no activity for 60 days.]

Changed in ltsp (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.