[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Problem starting diskless workstation



Hello Valerio,
I have encountered the exact same problems while doing the LtspDisklessWorkstation thing, while following the instructions on the Wiki very closely. I didn't manage to solve the issue with the thin-clients so it would be interesting to try Sebastiaan's hint.
THANK YOU SEBBASTIAAN.

I assume you are, as I was, more interested in getting the DWs to work, and get the TCs sorted on another thread. Unfortunately, I don’t have the machine in front of me, just moved it on site Tuesday, I'll try to describe what I did from memory so take care.
My best shot is at the 'next server' line in /etc/dhcp3/dhcpd.conf, DHCP cites this line to the pixie telling it where to get the next step for the boot process, in my system, a combi-server it is:
   next-server tjener;
Make sure it points to the right server on your system, try using ip address instead of name.
If that is correct then the 'filename' line has the same effect and should be as said:
   filename "/var/lib/tftpboot/ltsp/i386/pxelinux.0";
Make sure this file exists indeed.
The 'root-path' line is NFS related and shouldn't have effect at this stage, but I remember adding the host-name there:
   option root-path  "tjener:/opt/ltsp/i386";
Or something of that sort.

If that doesn't solve the problem make sure you completed the instructions on sections 5,6 at the Wiki page and look at the example files. http://wiki.debian.org/DebianEdu/HowTo/LtspDisklessWorkstation#head-7be1d4c82ac998711c8b800d992cb0d7c47daba4
	a) Of what I remember the file /opt/ltsp/i386/etc/lts.conf was missing on my system so I did 'locate lts.conf' and copied it from somewhere on the file system.
	b) At the file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default make sure there's NO newline only spaces: DEFAULT vmlinuz ro initrd=initrd.imgroot=/dev/nfs ip=dhcp nfsroot=/opt/ltsp/i386
Try renaming this file to 01-08-00-27-04-49-0b just to see if the pixie got that far, my guess is it is looking in the wrong location.

At the moment I'm installing again so I'll soon have the possibility to reproduce the process, if you're patient.

Odd.


Reply to: