On Thu, January 20, 2005 12:01 am, Joshua Collins said: > Well as some of you may remember I tried getting LTSP running a while > ago, and I recently decided to have another go at it. Fortunately I'm > having a good deal more progress this time, however I've just hit a > hurdle. From what i can tell it get's allocated the IP address and sent > the kernel (or whatever you call the vmlinuz file), however from > ethereal output after that the server tries finding the terminal and > fails and the terminal just hangs. I have checked the IP address and > various settings and as far as I can tell they are correct and the > output of what I can see on the terminal is: > > TCP: Hash tables configured (established 2040 blind 2040) > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > RAMDISK: Compressed image found at block 0 > Freeing initrd memory 716k freed > VFS: Mounted root (ext2 filesystem) [Slosh: I believe the server is > running ext3] This is on the client, not the server. > Freeing unused kernel memory: 192k freed > ======================================================================= > Running /linuxrc > Mounting /proc > linuxrc: installing tulip driver > modprobe tulip > /sbin/insmod /lib/modules/2.4.18-ltsp-1/kernel/drivers/net/tulip/tulip.o > Using /lib/modules/2.4.18-ltsp-1/kernel/drivers/net/tulip/tulip.o > Symbol version prefix '' > Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001) > PCI: Found IRQ 11 for device 00:04.0 > tulip0:21041 Media table, efault media 0800 (Autosense). > tulip0: 21041 media #0, 10baseT. > tulip0: 21041 media #1, 10base2. > tulip0: 21041 media #2, AUI. > tulip0: 21041 media #3, 10baseT-FDX > eth0: Digital DC41041 Tulip rev 17 at 0x1000, 21041 mode, > 00:00:F8:02:07:0D, IRQ 11 > Running dhclient > > (apologies for any typoes in the above) > > I guess it is worth pointint out that I couldn't get it to work If I > used /tftpboot/lts as a softlink to /usr/lib/lts so I copied the > directory there. > > I'm running Debain unstable on 2.4.18... ask for any other info. > > --Slosh > > ...it does look like you could do with a *lot* of updating (your setup is probably 2 years old?), but that won't stop anything working.
So is bootp is talking to your box? Looks like it.That's good, as the old DEC Tulip cards were always a real pig to set up, and there's loads of slightly different versions out there! If you've got this far, it's often an X problem, and you need to specifically configure for the hardware. Does the screen flash at all? Can you post your /etc/dhcp.conf and /opt/ltsp/i386/...(forgotten!)/etc/ltsp.conf - that way we can check to see if it's a networking problem as well? Cheers, Steve -- Artificial Intelligence is no match for natural stupidity.
