On Thu, 2006-05-25 at 08:23 -0400, Jim McQuillan wrote:
> Alistair Crust wrote:
> > Am I right in saying that LTSP clients get their kernel and initrd image
> > via pxe..or etherboot then, as the kernel is executed it sets up the
> > network card, polls for an IP, then NFS mounts the /opt/ltsp/i386 dir,
> > then carries on like "normal".
> You are correct.
> > We have a thin client with a CF(actually Smart Media in a CF case) card
> > that will boot a kernel and initial RAM disk.
> > We have had DSLinux working via a bzImage initrd and a Filesystem on a
> > USB Pendrive. DSLinux however is not LTSP, the bzImage and initrd image
> > from the /tftpboot/ltsp dir doesn't work (not compiled for geode cpus, i
> > guess).
> What version of LTSP are you trying to use?
4.1... although I will try the 4.2 strain at some point.
> The latest LTSP kernel and initrd version is "22.214.171.124-ltsp-2" and those
> working fine for the Jammin-125 clients, and those use a geode GX1
> cpu. We did have trouble with the previous version of the LTSP kernel
> (ending in 'ltsp-1') with the geode. maybe you just need to upgrade to
> our latest kernel.
the kernel versions I have tried are bzImage-2.4.26-ltsp-3 and
2.6.9-ltsp-3 with respective initrd files.
the peculiar thing about our setup is that the terminals we are using
are NTe based devices and we get them to boot by creating an nk.bin file
by using make-nk (from winterm.gaast.net) and then re-flashing the
things to make them think they are booting NTe. The things don't have a
bios that is usable, but we have had DSLinux working so the theory is we
just replace the bzImage of DSLinux with the one from tftpboot/lts/.
The way that make-nk creates the nk.bin is by using a file called boot.S
(the linux boot-loader in essence... I think) but I'm no programmer so I
really have no idea where to start if the solution lies in that
Skegness Grammar School
TEL: 01754 610000 (ext'852)
FAX: 01754 896875