<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9"> </HEAD> <BODY> Paul, I just was playing with this a couple of weeks ago. Unfortunately, I am not near my system to give all the particulars. I found that I needed to add a couple of lines in the /etc/dhcpd.conf to make sure that pxe could function properly. I also had to make sure that the pxe script was starting up correctly. Check that the dhcpd.conf has entries in it to allow for booting. Make sure that /etc/pxe/pxe.conf is looking like it will work in your environment. I hope this points you in the right direction. I am sorry that I can not give you more details. Dan On Mon, 2004-05-03 at 14:25, k12osn-request@redhat.com wrote: <BLOCKQUOTE TYPE=CITE> <PRE> Message: 9 Date: Mon, 3 May 2004 10:41:09 -0700 (PDT) From: pnelson@riverdale.k12.or.us Subject: [K12OSN] [Fwd: Re: K12LTSP boot problem] To: k12osn@redhat.com Message-ID: <32899.200.145.158.170.1083606069.squirrel@riv-mail.mesd.k12.or.us> Content-Type: text/plain;charset=iso-8859-1 >On Sun, 2004-05-02 at 15:36, Oscar Erbetta wrote: > > dear Paul: I liked the idea of thin clients to fedora, so yesterday I >have > > downloaded and installed the K12LTSP-4.0.1 (4) isos in a fresh machine, >with > > only an eth0 (192.168.53.254 - no internet access), with no problem. everything worked fine. > > > > I'm using a DELL Latitude, with pxe boot as the only client (for now), >but > > after a the initial loading process, the boot displays "could not find kernel image". Oscar, I'm going to forward this to the K12OSN group so we can all see how to troubleshoot something like this. 1. The client get's an ip address. 2. It does not get a kernel 3. The /etc/dhcpd.conf file is the default K12LTSP file. 4. The ip address of the server is 192.168.0.254 5. The line in dhcpd.conf is: option root-path "192.168.0.254:/opt/ltsp/i386"; 6. The files needed in /opt/ltsp/i386 really are there. 7. /tftpboot/lts/pxe/pxelinux.cfg exists and is default. NFS is running "service nfs status" 8. /etc/exports file is default/opt/ltsp/i386 192.168.0.0/255.255.255.0(ro,no_root_squash,sync) /var/opt/ltsp/swapfiles 192.168.0.0/255.255.255.0(rw,no_root_squash,async) So if all this is true, why won't the client boot? What did we miss? ;-) Paul ------------------------------ Message: 10 Date: Mon, 03 May 2004 13:24:27 -0500 From: Les Mikesell <les@futuresource.com> Subject: Re: [K12OSN] [Fwd: Re: K12LTSP boot problem] To: "Support list for opensource software in schools." <k12osn@redhat.com> Message-ID: <1083608667.24403.3.camel@moola.futuresource.com> Content-Type: text/plain On Mon, 2004-05-03 at 12:41, pnelson@riverdale.k12.or.us wrote: > 8. /etc/exports file is default/opt/ltsp/i386 > 192.168.0.0/255.255.255.0(ro,no_root_squash,sync) > /var/opt/ltsp/swapfiles 192.168.0.0/255.255.255.0(rw,no_root_squash,async) > > So if all this is true, why won't the client boot? What did we miss? > First guess: the PXE boot code doesn't work. Have you tried an etherboot floppy? Dell is very good about keeping support updates on-line forever so you can probably find a flash bios update if that is the problem (and I've seen it on old Optiplex GX1's). --- Les Mikesell les@futuresource.com ------------------------------ _______________________________________________ K12OSN mailing list K12OSN@redhat.com <A HREF="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</A> End of K12OSN Digest, Vol 3, Issue 8 ************************************ </PRE> </BLOCKQUOTE> </BODY> </HTML>