[K12OSN] Another small K12LTSP 4.1.0 beta bug

[Eric Harrison]

Jack,

If you are stuck, as a temporary fix you should be able to use the
kernels from K12LTSP 4.0.1. These three commands should get you back
in business:

	rpm -e ltsp_i386-kernel
	rpm -ihv ftp://k12linux.mesd.k12.or.us/apt/fedora/RPMS.k12ltsp/ltsp_kernel_i386-3.0-13.k12ltsp.1.4.0.noarch.rpm
    rpm -ihv ftp://k12linux.mesd.k12.or.us/apt/fedora/RPMS.k12ltsp/ltsp_kernel_i386_pxe-3.0-13.k12ltsp.1.4.0.noarch.rpm


-Eric


On Sun, 18 Jul 2004, Jack wrote:

>Just installed LTSP 410 and I keep running into a problem with all 3 of
>my terminals not booting.  They boot about halfway then fail.
>
>All my terminals are getting kernel panics.  All 3 fail with identical
>errors, like so:
>--------------------------------
>Running /linuxrc
>Mounting /proc
>linuxrc: Installing e100 driver
>modprobe e100
>Running dhcpcd on port 67
>
>**** /bin/dhcpdcd: already running
>**** /bin/dhcpcd: if not then delete /etc/dhcpc/dhcpcd-eth0.pid file
>
>ERROR! dhcpcd failed!
>
>Kernel panic: Attempted to kill init!
><3>e100: eth0 NIC Link is Up 100 Mbps Full Duplex
>--------------------------------
>
>On the server side I get this in the messages log:
>
>--------------------------------
>Jul 18 03:13:30 tserver dhcpd: DHCPDISCOVER from 00:a0:c9:75:ca:27 via
>eth0
>Jul 18 03:13:31 tserver dhcpd: DHCPOFFER on 192.168.0.251 to
>00:a0:c9:75:ca:27 via eth0
>Jul 18 03:13:31 tserver dhcpd: DHCPREQUEST for 192.168.0.251
>(192.168.0.254) from 00:a0:c9:75:ca:27 via eth0
>Jul 18 03:13:31 tserver dhcpd: DHCPACK on 192.168.0.251 to
>00:a0:c9:75:ca:27 via eth0
>Jul 18 03:13:58 tserver dhcpd: DHCPDISCOVER from 00:a0:c9:75:ca:27 via
>eth0
>Jul 18 03:13:59 tserver dhcpd: DHCPOFFER on 192.168.0.252 to
>00:a0:c9:75:ca:27 via eth0
>Jul 18 03:13:59 tserver dhcpd: DHCPREQUEST for 192.168.0.252
>(192.168.0.254) from 00:a0:c9:75:ca:27 via eth0
>Jul 18 03:13:59 tserver dhcpd: DHCPACK on 192.168.0.252 to
>00:a0:c9:75:ca:27 via eth0
>Jul 18 03:13:59 tserver rpc.mountd: authenticated mount request from
>ws252.ltsp:657 for /opt/ltsp/i386 (/opt/ltsp/i386)
>--------------------------------
>
>It looks to me like the client(terminal) is trying to get another IP for
>some reason.  All terminals are using e100 NICs (Intel e100).  I suspect
>this may be a problem with the Intel driver.  I'll have to try another
>NIC but right now all three of my terminals are using Intel 100's and I
>don't feel like ripping them apart at this moment.  Otherwise the server
>is looks and runs great.  Thanks again guys for the great work.
>
>Jack
>