Hello;
Seems you are both having some similar problems getting
workstations to boot.
After some dialog with dhcp, the client performs a "tftp"
to the server to retrieve the kernel. I would suggest
testing this by booting a workstation from something
having a tftp client and retrieving it manually, like so:
1. On the server, get the name of the file specified
by dhcpd. The file should be in the "/tftpboot/lts"
directory on the server and the tftp daemon started
with root dir = "/tftpboot":
$ grep filename /etc/dhcpd.conf
filename "/lts/vmlinuz-2.4.19-ltsp-1";
2. Verify the file size, permissions and checksum. It
should be readable by everybody and its subdirectories
should have read and execute access for everybody:
$ ls -l /tftpboot/lts/vmlinuz-2.4.19-ltsp-1
-rw-r--r-- 1 root root 1418240 Sep 4 22:59
/tftpboot/lts/vmlinuz-2.4.19-ltsp-1
$ sum /tftpboot/lts/vmlinuz-2.4.19-ltsp-1
40086 1385
$ ls -dl /tftpboot/lts
drwxr-xr-x 3 root root 4096 Oct 25 03:14 /tftpboot/lts
$ ls -dl /tftpboot
drwxr-xr-x 4 root root 4096 Jan 12 16:59 /tftpboot
3. From a client, use "tftp" to retrieve the file
from the server (192.168.1.128 in my case):
$ tftp 192.168.1.128
tftp> bin
tftp> get /lts/vmlinuz-2.4.19-ltsp-1
Received 1418240 bytes in 0.1 seconds
tftp> quit
4. Verify the image checksum with the file on the
server (step 2). Note that I am using the same kernel
you are, so your checksums should match mine:
$ sum vmlinuz-2.4.19-ltsp-1
40086 1385
If this much is working, the kernel should boot like so:
Loading 192.168.1.128:/lts/vmlinuz-2.4.19-ltsp-1 ..(NBI) ... ..
...............................................................
..............(TOTAL 12 LINES OF PURE DOTS)....................
...............................................................
...........done
mknbi-1.2-7/first32.c (GPL)
Top of ramdisk is 0X17FF0000
Ramdisk at 0X17F3D000, size 0X000B3000
Uncopressing Linux... Ok, booting the kernel.
... and it starts booting here ...
If this isn't happening, something must be wrong with the
kernel image.
I hope this helps,
Tom
> From: "Tue Hellstern" <[EMAIL PROTECTED]>
> I think some of the tread didn't got to the list. But my problem is that
> my clients don't boot up.
>
> The client gets in contact with the server and gets an IP address, but
> after that nothing happens.
> On the client it looks like this:
> Me: 192.168.0.249
> Server 192.168.0.4
> Gateway 192.168.0.1
> Loading 192.168.0.4:/lts/vmlinuz-2.4.19-ltsp-1 ......
> There comes come ... but except from that nothing happens at the client.
> From: "William Dooley" <[EMAIL PROTECTED]>
>
> I am having issues with booting the linux kernel.
>
> installed the necessary RPM's for a RedHat 7.1 server
>
> also installed=20
> dhcp-3.0pl1-9 and=20
> tftp-server-0.29-3
>
> Made a etherboot disk for PCNet32=20
>
> the system boots off of the floppy=20
> initializes the card
> searches for DHCP
> receives an address
> Me: 192.168.0.17, Server: 192.168.0.10, Gateway: 192.168.0.1
>
> Loading 192.168.0.10:/lts/vmlinuz-2.4.19-ltsp-1 ...(NBI)............
> ....done
>
> and nothing more (just hangs)
--
------------------------------------------------------
Thomas L. Griffing [EMAIL PROTECTED]
Pondus Solutions, Inc. Red Hat Certified Engineer
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
