RE: PXES on Debian

That problem means that the client cannot find a /sbin/init and all linux
distros do something similar.

How did you modify the initrd file?  Did you gunzip it and mount it?  I had
a problem similar caused by putting the kernel and initrd file to my remote
tftp server and failing to use bin mode.

In pxesconfig are you sure you've used the right processor options?  

As for memory, 128 Mb is ample... My clients use 32 Mb, and I used to have
some with 24 that worked fine too.

In order to get pxesconfig running I had to install some extra debian
packages... Diego gave me this reference to find them:

> To install PXES on Debian you can follow the steps showed in 
> http://ltsp-es.hispalinux.es/tiki-download_file.php?fileId=10 (in 
> Spanish !!) but search for apt-get inside the document.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Gil Freund
Sent: Wednesday, 17 March 2004 10:06 a.m.
To: [email protected]
Subject: [pxes-devel] PXES on Debian

I installed the PXES and PXESconfig on debian and can boot the pre-made 
images with no problem on a few test system.
I tried to modify the initrd using pxesconfig, and the system halt with 
"no init found" error, and the CAPS and Scroll Lock lights blinking.

Reading the list it seems that this error is related to memory so I 
assigned  more memory to the RAM disk, but still to the same effect.

I tried several configurations with as much ram disk space I could spare 
(the test terminal has 128MB of ram) with the same effect.

Could this be a configuration issue in pxesconfig? I see no error 
messages and the initrd file seems to be in order.

The server is Debian Sarge, kernel 2.4.25.



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click