[K12OSN] Re: K12LTSP 6.0 client booting problems

Mon Jan 8 15:13:40 UTC 2007

> 
> Mark McSweeney wrote:
>> I'm sorry if this has been covered before but I searched the K12OS
>> archives and documentation and could not find a reference to this
>> problem.
>>
>> On the older versions (pre 5.0) of K12LTSP I was able to simply
>> install the OS and boot the client with a boot disk.
>>
>> Since I installed 6.0 when I try to boot the client acquires an IP ok
>> then I get this:
>>
>>> Doing the pivot_root
>>> Mounting the devfs filesystem
>>> Running /sbin/init
>>>
>>> Enter runlevel:
>>
>>
>> I did find this post on the LTSP mailing list:
>>
>> http://marc.theaimsgroup.com/?l=ltsp-discuss&m=114572079627648&w=2
>>
>> but I am a little confused because I thought that K12LTSP was ready to
>> go "out of the box" and the instructions for addressing this problem
>> seem to be to update the LTSP packages and kernel.
> 
> 
> 
>> For reference my /etc/dhcpd-k12ltsp.conf file looks like this:
> 
>> and my /opt/ltsp/i386/etc/lts.conf looks like this:
> 
> 
> At first glance, your dhcpd & lts conf files look ok.
> 
> 
> It appears that you are getting past TFTP, so we'll assume that is
> working ok.
> 
> NFS is probably ok as well, but we should double-check that. What is the
> contents of /etc/exports ?   Also, run these commands just to make sure
> that NFS is running properly:
> 
> 	/sbin/chkconfig portmap on
> 	/sbin/chkconfig nfs on
> 	/sbin/service portmap restart
> 	/sbin/service nfs restart
> 

Eric,

The contents of /etc/exports are as follows:

-------------------------------------------------
## LTS-begin ##
#
# The lines between the 'LTS-begin' and the 'LTS-end' were added
# on: Wed Nov 28 11:19:42 PST 2001 by the ltsp installation script.
# For more information, visit the ltsp homepage
# at http://www.ltsp.org
#

/opt/ltsp/i386            192.168.2.0/255.255.255.0(ro,no_root_squash,sync)
/var/opt/ltsp/swapfiles   192.168.2.0/255.255.255.0(rw,no_root_squash,async)

#
# The following entries need to be uncommented if you want
# Local App support in ltsp
#
#/home                    192.168.2.0/255.255.255.0(rw,root_squash,sync)

## LTS-end ##

## LTS-begin ##
#
# The lines between the 'LTS-begin' and the 'LTS-end' were added
# on: Wed Nov 28 11:19:42 PST 2001 by the ltsp installation script.
# For more information, visit the ltsp homepage
# at http://www.ltsp.org
#

/usr/X11R6/lib/X11/fonts   192.168.2.0/255.255.255.0(ro,no_root_squash,sync)
/usr/share/AbiSuite/fonts  192.168.2.0/255.255.255.0(ro,no_root_squash,sync)
/usr/share/fonts           192.168.2.0/255.255.255.0(ro,no_root_squash,sync)
/usr/lib/openoffice/share/fonts 
192.168.2.0/255.255.255.0(ro,no_root_squash,sync)

## LTS-end ##

## LTS-end ##

## LTS-begin ##
#
# The lines between the 'LTS-begin' and the 'LTS-end' were added
# on: Wed Nov 28 11:19:42 PST 2001 by the ltsp installation script.
# For more information, visit the ltsp homepage
# at http://www.ltsp.org
#

/opt/ltsp/ppc            192.168.2.0/255.255.255.0(ro,no_root_squash,sync)

## LTS-end ##

-------------------------------------------------

As far as checking the status of portmap and nfs:

[root at aalborg ~]# chkconfig --list portmap
portmap         0:off   1:off   2:on    3:on    4:on    5:on    6:off

[root at aalborg ~]# chkconfig --list nfs
nfs             0:off   1:off   2:on    3:on    4:on    5:on    6:off

[root at aalborg ~]# /sbin/service portmap status
portmap (pid 1831) is running...

[root at aalborg ~]# /sbin/service nfs status
rpc.mountd (pid 2159) is running...
nfsd (pid 2156 2155 2154 2153 2152 2149 2148 2147) is running...
rpc.rquotad (pid 2130) is running...

> 
> Just to make sure that the security mechanisms are not bitting you, run
> these two commands and then try to boot a terminal:
> 
> 	/sbin/service iptables stop
> 	/usr/sbin/setenforce 0
> 
> 

When I did the install I disabled the firewall and SELinux so I could 
try to avoid any issues.

> 
> Finally, a couple of questions to help us debug...
> 
> * what is the output of:
> 
> 	rpm -q ltsp_i386-boot ltsp_i386
> 	rpm -V ltsp_i386-boot ltsp_i386

[root at aalborg ~]# rpm -q ltsp_i386-boot ltsp_i386
ltsp_i386-boot-2.6.17.8-1.k12ltsp.6.0.0
ltsp_i386-4.2-4.k12ltsp.6.0.0

[root at aalborg ~]# rpm -V ltsp_i386-boot ltsp_i386
S.5....T   /opt/ltsp/i386/etc/ld.so.cache

> 
> * was this a fresh install or an upgrade?
> 

Fresh install

> * I see that you are using 192.168.2.x. How did you make this change &
> did you make any other changes?

When I did the install I knew what ethernet adapter (eth0)I would be 
using for the client side and edited the ip information accordingly. 
For what it's worth the other interface (eth1) is specified as 
192.168.10.2.  It is connected to my private network that is firewalled 
appropriately.

I can connect regular machines to the switch on eth0 and receive DHCP 
addresses fine and the machines connect to the internet.

> 
> * what type of terminals are you using?

This is where the problem gets funky.  I am using old IBM 380EZ laptops 
with 3Com 3CCFE574BT PCMCIA ethernet adapters.  The way I always booted 
these clients with K12LTSP 4.X.X and earlier was to get the 
wireless_ltsp-3.0.5-i386.tgz package and extract the floppy.img image 
and either make a boot floppy or copied this image to the harddisk of 
the terminal and edited the grub boot menu accordingly.  I found these 
instructions on the mailing list here:

http://marc.theaimsgroup.com/?l=ltsp-discuss&m=108789847231845&w=2

I have done some experimenting and I have learned that I can 
successfully boot a client that has a built in ethernet connector when I 
enable the BOOTROM in the BIOS so the problem seems to be related to the 
boot image I am using.......

I hope that I can resolve this problem because the client/terminals I am 
using are ideal for my setup because of several reasons...I got them for 
free, they are real space savers and my daughters don't need to use my 
wife and my desktops to access their accounts.....

Thanks for you help so far.

Mark