I have 25 old AMD K7 really thin clients ( no hd, cd, or floppy) that I used in a ltsp computing cluster (local apps) several years ago. I want to resurrect the cluster, but have to use a new server. So, I put in a new server with the latest ltsp (4.1.1). The clients all have a Linksys LNE 100TX NIC with bootrom ver 1.4 and etherboot ver 2.5.8. Unfortunately, I couldn't get booted up with these NICs and any of the kernels in the current distribution. (kernel panic, can't mount nfs, etc).
Fortunately, I had a newer Linksys NIC with bootrom 1.7 and etherboot 5.0.5 from another project. Using it, everything works fine.
So now my question: Do I have 25 orphans? I can't really afford to get new eproms or NICs.
I tried the option-129 MOPTS in dhcp with proto=tcp as well as all the nfs sizes I could think of, but no success.
Older versions of Etherboot roms can chain load. That is, they can download net versions of Etherboot which can in turn download the new kernel.
You can use the dhcpd.conf in a way similar to the way PXE is used. If the vendor-identifier is Etherboot-2.5 then download eb5.4.0.rom.
You prepare the Etherboot rom for download by running mknbi-rom eb5.4.0.rom > /tftpboot/lts/eb5.4.0.rom
Tim
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _____________________________________________________________________ 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
