[K12OSN] Problem booting thin clients on k12ltsp4.2

[Lawrence Harriott]

Hi all,
> 
> I am having the same problem, so double thanks to
> anybody who can shed some light on this.
> ......
> Lawrence, do you have another NIC you could try?
> 
> -Rob
Unfortunately no. I have 3 Davicom DM9102AF cards that 
do not get as far as a dhcp request before timing out. My only e100 is the 
only one that gets as far as this.

I do not mind getting new cards but now I do not know what the cause of
the problem really is nor whether I won't have the same problem with a
different card.
Lawrence

> --- Lawrence Harriott <lharriott at mail.gotelja.com>
> wrote:
> > Hi list,
> > 
> > I set up a K12LTSP4.2 box a few days ago and can't
> > seem to boot any thin
> > clients. I installed from the CD's then upgraded via
> > Internet using
> > apt-get to get everything up to date. The server
> > seems to be ok but my
> > thin client, a 233MHz AMD-K5 using an e100 NIC (non
> > of my DM9102AF cards
> > boot properly)gets to the point of doing the the
> > PIVOT-ROOT and just
> > sits there for a while then decides that it cannot
> > find the server. It
> > gives this message, nfs: server 192.168.0.254 not
> > responding, still
> > trying.    Var/log/messages reports that the mountd:
> > authenticated mount
> > request from ws150.
> > 
> > Using another linux machine I can mount and access
> > the nfs shares, no
> > problem.
> > 
> > Incidentally, I am booting using a rom-o-matic
> > 'universal' boot
> > diskette. This machine insists that it is
> > 192.168.0.150 regardless of
> > what I set it to in dhcpd.conf. I have no idea where
> > it gets that IP
> > from.
> > 
> > I would appreciate any help in getting this to work.
> > I have googled
> > around a bit but have not yet found anything on this
> > particular issue. I
> > am wondering whether the NIC or the upgrade may be
> > the culprit!
> > 
> > Thanks
> > Lawrence
> >