On Sunday 12 January 2003 11:09, Anselm Martin Hoffmeister wrote:
> Hello Peter,
>
> PC> After getting very confused by the LTSP website. After one of
> my colleges PC> decided we ought to use thin clients and then left. (I
> don't disagree with PC> the idea and actually think its a very good one).
> PC> We have LTSP running fine. But we can't seam to get out old ISA
> network cards PC> to boot correctly. etherboot seams to say that the D-Link
> 220 card should PC> work and says to use the ne driver. but when I try that
> nothing happens.
>
> That's a more or less unspecific description.
> What /does/ happen?
> I would expect the following to happen when powering on the machine
> (booting from floppy with eb-5.0.8-ne.lzdsk or so)
The Floppy can't see the network card. From this I thought that it would be
some setting in the floppy creation program to set the irq settings. but no
such setting....
The notes on the web site(s) say it should just work but it does not. If it
were an option 129 problem at least the kernal would have down loaded. Which
is all the web site seams to say.
Peter Childs
>
> BIOS boot sequence
> Etherboot displaying start message
> Found card (ne io=0x320 irq=5)
> Getting DHCP information
> Got IP Address
> Loading TFTP file
> done
> Starting Linux Kernel
> ... lots of messages ...
> Loading network driver
> Running dhclient
> ... lots of more messages ...
> starting X
>
> Where does it hang?
> Tried another version of etherboot (e.g. an older one like 5.0.4 just
> to be sure)?
> FYI: There were several changes in Etherboot (to be read in the
> etherboot-users / etherboot-developers mailing list archives) that
> could break compatibility to too old ltsp-images. Try 5.0.4 which
> worked fine for me with "ne" on old FiberLine ISA nics.
>
> PC> I guess it needs a io=x irq=y handed to it (I still use an ISA
> card on my PC> Redhat box at home) but how do I hand this to the floppy?
>
> When etherboot runs correctly, yes. You have to enter it into the
> dhcpd.conf (option option-128 e4:f5:blahblahblah:00; RTFM; and option
> option-129 "NIC=ne IO=320", irq autodetected!?).
>
> PC> I know its nothing to do with the set up because we have 2
> other thin clients PC> working happily (a Jammin 125 and a 486 with a
> 100Mbs Rtl8139 network card)
>
> With probably older etherboots, anyway.
>
> PC> The only problem with these is that the 486 can not be connected to a
> PC> 100Mbits segment as then the NFS fails I'm not sure why but bug it on a
> PC> 10Mbit hub and it works fine.
>
> Do you transfer the kernel files via NFS or use tftp there (then NFS
> for later mounting /opt/ltsp/i386)? In which way does it fail? Would
> be interesting to get that error out, as RTL8139 is a quite common
> hardware.
>
> PC> Any ideas?
> PC> Thanks in advance.
>
> PC> Peter Childs
>
> Best regards,
> Anselm mailto:[EMAIL PROTECTED]
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.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.openprojects.net
