Re: Light terminal not booting from dkt
Lluís Pérez Vidal wrote:
> The light terminal does not boot from diskette
Just to help you if you google for an answer, we call the terminal
server for a "thin-client-server" and the terminals for "thin clients"
> I have set an experimental mini-web for Skolelinux with:
> - a router
> (universal IP on the outside eth0;
> 10.0.2.1 on the inside eth1)
> - a hub for the 10.0.2.zzz subnet
> - a master server MS 10.0.2.2
> - a workstation WS.
>
> - a light terminal server
>
> Here is the ifconfig of the light terminal server
> ======================================================0
> eth0 Link encap:Ethernet HWaddr 00:90:27:30:A7:13
> inet addr:10.0.2.237 Bcast:10.0.2.255 Mask:255.255.255.0
..
> eth1 Link encap:Ethernet HWaddr 00:20:18:52:4C:0C
> inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0
..
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> ======================================================0
>
> and now I want the light terminal to boot from a diskette
> connected by a cross-over (twisted) cable to
> the light terminal server,
> but I can't: It stays forever with the monitor stating
>
> ======================================================0
> 000021.0000 done
> ROM segment 0x0800 length 0x4000 reloc 0x9400
> Etherboot 5.0.7 (GPL) Tagged ELF for [EEPRO100]
> Boot from (N)etwork or from (L)ocal? N
> Probing [EEPRO100]Found Intel EtherExpressPro100 ROM address 0x0000
> Ethernet addr: 00:A0:C9:2F:49:C0
> Searching for server (DHCP)...
> .....
> ======================================================0
looks like the dhcp-server is not running on your thin-client-server
Could you please check by issuing the command
ps auxw |grep dhc
Is the machine restarted after the installation was done ?
which CD did you use ?
(if you don know, take a look at /etc/apt/sources.list)
> I have gotten the eb-5.0.7-eepro100.lzdsk
> ROM image on the boot diskette. And I think that this is the
> right one for the NIC.
>
> I am pretty sure that the hardware, connections, hub, etc are not
> at fault. Because after failing to boot as a light- terminal Skolelinux
> from the diskette I have succeeded in installing a normal stable Debian
> from the three diskettes (boot, root, net-drivers) and from the
> Internet. It connects through the light-terminal server
> (with a twistec cable, exactly the same as before)
> and here is what its ifconfig says after booting
> ======================================================0
> eth0 Link encap:Ethernet HWaddr 00:A0:C9:2F:49:C0
> inet addr:192.168.0.253 Bcast:192.168.0.255 Mask:255.255.255.0
> lo Link encap:Local Loopback
> ======================================================0
Looks like dhcp is working then.
Could you also check the output of
grep -E "dhcpd|tftp" /var/log/daemon.log
while your thin client tries to boot ?
--
Finn-Arne Johansen
faj@bzz.no http://bzz.no/
DebianEdu developer and Solution Provider
Reply to: