On 5/23/06, David Kirk <[EMAIL PROTECTED]> wrote: [...]
mknbi-1.4.3/first32.c (GPL) Top of ramdisk is 0X1FF80000 Ramdisk at 0X1FE62000, size 0X0011E000 The keyboard is locked up. Caps Lock doesn't work. Neither does Ctrl-Alt-Del. All I can do is cycle the power. If I run tcpdump while it is booting, I see all the tftp stuff and then: arp who-has 192.168.1.99 tell 192.168.1.23 three times, and then nothing. 192.168.1.99 is the client and 192.168.1.23 is the server. I know nfs works. I tested it from another linux box.
[...] from the tcpdump lines it seems the network is down on the ltsp client. Can you check and see if it's still connected after loading the etherboot image (power leds, ping from server). I remember some time ago that I had trouble getting etherboot to recognize the NIC you described. One thing you could try is a PXE boot (instead of the etherboot cdrom) and load the initial kernel via PXE instead of etherboot. -- mitu ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642 _____________________________________________________________________ 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
