<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1">Its there, in fact in my last revision, I
accidentally have it twice. once as a global and specified under
the <br>
workstation parameters. Ill include it in case there is anything
helpful. <br>
<br>
I also just captured a packet dump. I have a couple udp packets
covering the dhcp negotiation, then its all tftp<br>
beginning with a request from the client to read the specified
kernel on the server and ending with an ack from<br>
the client to a kernel data send from the server, and thats it. <br>
<br>
rpcinfo seems to indicate nfs is ok, exports is configured wide
open as per doc. firewall stopped. selinux disabled.<br>
even set /opt 777 <br>
<br>
One thing Im curious about. What determines where the client sees
lts.conf ? I notice its now under /var/lib/tftpboot,<br>
the lts.conf in the chroot is empty, whereas in 4.2 it read the
version in the chroot.<br>
<br>
Heres the dhcpd.conf file. I've made a number of revisions, from
going with the default to using the workstation defs<br>
as specified on the wiki when using a fedora 11 chroot. <br>
<br>
Again this is an attempt at a mixed network setup. TC's have been
factory flashed to work over 1067. I have ltsp-dhcp disabled<br>
dhcp args set to 1067 under sysconfig and bridge removed. per
netstat , and log files were listening ok on the server. <br>
<br>
# Sample configuration file for LTSP dhcpd<br>
# The goal of this provided dhcpd.conf is to boot as many
different clients as possible without manual configuration.<br>
# Some clients cannot be booted with this, and you will need to
create your own custom dhcpd.conf.<br>
# Some more complex network topologies will also need a custom
dhcpd.conf.<br>
#<br>
<br>
default-lease-time 21600;<br>
max-lease-time 21600;<br>
ddns-update-style none;<br>
allow booting;<br>
allow bootp;<br>
<br>
option subnet-mask 255.255.255.0;<br>
option broadcast-address 10.10.0.255;<br>
option routers 10.10.0.58;<br>
option domain-name-servers 10.10.0.58;<br>
next-server 10.10.0.58;<br>
option domain-name "ltsp";<br>
option option-128 code 128 = string;<br>
option option-129 code 129 = text;<br>
option root-path "10.10.0.58:/opt/ltsp/fed11-i386";<br>
option option-221 code 221 = text;<br>
option option-128 e4:45:74:68:00:00;<br>
option option-129 "DPORT=1067";<br>
get-lease-hostnames true;<br>
<br>
shared-network WORKSTATIONS {<br>
subnet 10.10.0.0 netmask 255.255.255.0 {<br>
range dynamic-bootp 10.10.0.62 10.10.0.65;<br>
use-host-decl-names on;<br>
option log-servers 10.10.0.58;<br>
<br>
}<br>
}<br>
<br>
## example configurations for specifying specific kernels to
specific clients<br>
## These examples below are VERY OLD, uncertain if they work<br>
group {<br>
use-host-decl-names on;<br>
option log-servers 10.10.0.58;<br>
<br>
host lt01 {<br>
hardware ethernet 00:13:90:02:7f:11;<br>
fixed-address
lt01; ### ip of
lt01 specified in hosts<br>
filename
"/ltsp/fed11-i386/wraplinux-nbi.ltsp";<br>
option root-path "10.10.0.58:/opt/ltsp/fed11-i386";<br>
}<br>
# host ws002 {<br>
# hardware ethernet 00:D0:09:30:6A:1C;<br>
# fixed-address 172.31.100.2;<br>
# filename "/ltsp/vmlinuz.ltsp";<br>
# option option-128 e4:45:74:68:00:00;<br>
# option option-129 "NIC=ne";<br>
# }<br>
# host ws003 {<br>
# hardware ethernet 00:D0:09:30:28:B2;<br>
# fixed-address 172.31.100.3;<br>
# # kernels are specified in
/tftpboot/ltsp/i386/pxelinux.cfg/<br>
# filename "/ltsp/i386/pxelinux.0";<br>
# }<br>
<br>
# Apple Specific Settings<br>
# host ws007 {<br>
# hardware ethernet 00:30:65:69:23:60;<br>
# fixed-address 172.31.100.4;<br>
# option root-path "172.31.100.254:/opt/ltsp/ppc";<br>
## filename "yaboot";<br>
# option vendor-class-identifier "AAPLBSDPC";<br>
# }<br>
}<br>
<br>
<br>
<br>
</font><br>
On 10/21/2011 10:54 AM, Dean Jones wrote:
<blockquote
cite="mid:CAMXYB4Km6AqtzDsCqEKoERnhT4=Zatsi39_T6LBd2iuPvca+xQ@mail.gmail.com"
type="cite">
<pre wrap="">Looks like your dhcpd.conf is not specifying a root path to me, so the
clients do not know where to mount root.
On Fri, Oct 21, 2011 at 6:48 AM, Steve <a class="moz-txt-link-rfc2396E" href="mailto:skerr@rx30.com"><skerr@rx30.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">After poking around some, I discovered gdm was not configured to allow
remote
X connections, so I edited custom.conf apropriately, in hope I'll sometime
get far enough that
it matters.
ok , so I set dhcpd.conf back up to point to the fed11 chroot.
specifying elf.ltsp kernel:
After .... (ELF) .... done I get
dracut: Fatal no or empty root = argument
dracut: Refusing to continue
kernel panic - not syncing : Attempted to kill init
I then pointed filename to the wraplinux kernel:
It looks like it goes further, get a scrolling screen like the kernel is
loading
for instance I see:
registered taskstats version 1
magic number: 11:139:136
freeing unused kernel memory 404k
then basically the same dracut error messages and:
Pid: 1 init tainted:G
then a call trace
vmlinuz.ltsp - does not fit in memory
pxelinux.0
shows fedora 11 scroll bar moving left to right at the bottom of
the screen
then displays similiar dracut errors
then kernel panic - not syncing. Attempted to kill init
then another call trace
On 10/20/2011 11:08 PM, Burke Almquist wrote:
It almost looks to me as if it's having trouble mounting the NFS root for
the client.
It appears to be getting the kernel over tftpd and then hanging?
On Oct 20, 2011, at 12:43 PM, Steve wrote:
Hi All,
Im trying to setup LTSP using the InstallGuide and running into
difficulties.
I installed a fresh copy of CentOS 6 on a Dell precision T3400 in a mixed
network environment
with my dhcp server using port 1067.
I cant get into the TC console at the moment for exact specs, but its a "red
faced" jammin from disklessworkstations
, manufactured june 2009, flashed to work over 1067. It works with my older
versions of ltsp on centos 5.4.
I , think, followed the directions on the wiki carefully, didnt run into any
problems or receive any error messages.
When the TC is booting it appears to be detected as etherboot-5.4 and
attempts to load the elf.ltsp kernel.
In messages, on the server, i see
DHCPDISCOVER
DHCPOFFER
DHCPREQUEST
DHCPACK
all with sane values, dhcp looks ok
the last line is
xinetd : START tftpd pid="pidnumber" from ="ipaddy"
on the TC , it shows the dhcp negotion and the last line is:
Loading 10.10.0.58:/ltsp/i386/elf.ltsp (ELF) ... done
there it stops. No further output on TC or client.
I also tried forcing the wraplinux and pxe.0 kernels, which seem to get
further. I get the scrolling bar at the bottom that
says scientific linux 6.1 on the bottom right, but ultimately results in
dracut error messages and a kernel panic.
I hoping I missed something simple. Any pointers are appreciated.
Thanks
Steve
_______________________________________________
K12OSN mailing list
<a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a>
For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a>
_______________________________________________
K12OSN mailing list
<a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a>
For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
K12OSN mailing list
<a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a>
For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a>
.
</pre>
</blockquote>
</body>
</html>