Quoting Joshua Collins <[EMAIL PROTECTED]>: > 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: > > . . . > > 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 > > I had the same problems using a tulip based card with etherboot and LTSP, despite quite a few hours of (probably misguided) fiddling. As soon as I replaced the nic with a 3com or intel based one, everything burst into life.
I have had heaps of trouble with nics using digital chips (tulip driver) on linux over the years, and always found when I ditched the card and used something else things ran a lot better. Cheers Robert
