Per earlier advice I added to the tftp server args the "-r blksize" option:
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -r blksize -s /tftpboot
per_source = 11
cps = 100 2
}I also executed:
echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc
These suggestions were given in lieue to the problems that occur with the eepro100 chipsets, apparently. After restarting the server (just incase) and attempting to boot off of the floppy disk image for the eepro100 Etherboot (rom-o-matic), I still get the same error:
.000021.0000 done ROM segment 0x0800 length 0x4000 reloc 0x9400 Etherboot 5.08 (GPL) Tagged ELF for [EEPRO100] Boot from (N)etwork or (L)ocal? N Probing... [EEPRO100] Found Intel EtherExpressPro100 ROM Address 0x1800 Ethernet addr: 00:D):B7:C3:97:45 Searching for server (DHCP)... ._
And stops. Once again, the only communication between the client and server is a DHCPDISCOVER and a DHCPOFFER - then nothing.
08:24:07.611108 0:d0:b7:c3:97:45 Broadcast ip 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xb7cbefbe [|bootp]
08:24:07.611644 0:3:47:12:fb:87 Broadcast ip 342: 10.0.0.9.bootps > 255.255.255.255.bootpc: xid:0xb7cbefbe Y:10.0.0.15 S:10.0.0.9 ether 0:d0:b7:c3:97:45 [|bootp] (DF)
========================================================
Part two involved trying to enable PXE boot for the same system. After installing ISC dhcp-3.x, creating a PXE image from rom-o-matic, and changing the dhcpd.conf file to run an if/then for PXE vs. Etherboot, I placed the PXE image in the root of the tftpserver, reflected that in the dhcpd.conf, and retried the process, this time booting from network.
This is what I see:
Intel UNDI, PXE-2.0 (build 074)
Copyright(C) 1997, 1998, 1999 Intel Corporation
CLIENT MAC ADDR: 00 03 47 12 59 3E
GUID: 400....... (cut out)
CLIENT IP: 10.0.0.16 MASK: 255.255.255.0 DHCP IP: 10.0.0.9
GATEWAY IP: 10.0.0.1
PXE loader for Etherboot (with ZLOADER)
0x27EK low memory
PXE unloaded...but then the same thing occurs from that point. I've been reading the howto on ltsp.org about setting up PXE boot images and tagging the kernel, etc. Is this neccesary? Is the "low memory" error indicative of the fact that I need to tag it? [Input along these lines would be most appreciated. I'd like to get PXE going instead of using boot floppies.]
So. Does this come down to difficulties with the eepro100s? I was able to get it all working with a 3c905c card in another system.
More suggestions welcome. I'm looking forward to rolling this out for 100 workstations, all with Intel Pro 100s ;)
TIA
-- Darren Spruell Sento I.S. Department [EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.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
