<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    hallo Jim,<br>
    <br>
    thanks for the advise.<br>
    <br>
    I just tested this, and by copying some files from a previous
    install, I can indeed get this to work without green screen.<br>
    <br>
    So it seems our thinclients are out of date.<br>
    <br>
    greetings, J.<br>
    <br>
    <div class="moz-cite-prefix">Op 07-06-13 13:52, Jim Kinney schreef:<br>
    </div>
    <blockquote
cite="mid:CAEo=5Pyc60pRW4yq6HJsMYdxJUneMFa5Ru3zqJ=ys=W-G6KOmQ@mail.gmail.com"
      type="cite">
      <p dir="ltr">You'll need to rollback to an older kernel version
        for the TC or compile your own. RedHat dropped support for CPU
        styles from 15 years back and many SoC devices that are not ARM
        are still i586 command sets.</p>
      <div class="gmail_quote">On Jun 7, 2013 5:22 AM, "Johan Vermeulen"
        <<a moz-do-not-send="true"
          href="mailto:jvermeulen@cawdekempen.be">jvermeulen@cawdekempen.be</a>>
        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div bgcolor="#FFFFFF" text="#000000"> hallo Joshua,<br>
            <br>
            thanks for getting back to me.<br>
            <br>
            * I just ran <br>
            <br>
            <small>#yum clean all && yum update</small><br>
            <br>
            and that worked;<br>
            <br>
            <small>ltsp-server-5.4.5-21.el6.x86_64<br>
              ltspfs-1.1-7.el6.x86_64<br>
              ltsp-release-5-9.el6.noarch</small><br>
            <br>
            * I then did :<br>
            <br>
            <small>#mv /opt/ltsp /opt/ltsp.old<br>
              <br>
              #ltsp-build-client<br>
              <br>
              # ltsp-update-image <br>
              Your system seems to be using NFS to serve LTSP chroots.<br>
              If you're absolutely certain you want to switch to NBD,
              run:<br>
                  /usr/sbin/ltsp-update-image --config-nbd<br>
              <br>
              # ltsp-update-kernels<br>
              Updating /var/lib/tftpboot directories for chroot: i386<br>
              Skipping invalid chroot: mock</small><br>
            <br>
            * I then booted the hp thinclient: same green screen. <br>
            I will try to send you a screenshot of that.<br>
            I checked the hardware of this hp thinclient:<br>
            it has a Via Eden processor 1000Mhz, <br>
            <br>
            Googling the " unsupported processor centaurhauls" message I
            find this :<br>
            <br>
            <pre><i>nybody know the reason RedHat decided not to support the
</i>>>><i> VIA Eden Processor?</i>
</pre>
            <i><br>
              <small>If you take a look on google for "CentaurHauls
                i686" you will see that </small></i><small>><i> this
                CPU/chipset SAYS it fully supports i686 but it really
                does not. </i>><i> All of EL6 is i686 and not i586
                (which CentaurHauls really fully supports).</i></small><br>
            <br>
            So this suggests that Centos has an issue with this
            thinclient <br>
            There's also this site : <br>
            <br>
            <a moz-do-not-send="true"
              href="https://access.redhat.com/site/solutions/388693"
              target="_blank">https://access.redhat.com/site/solutions/388693</a><br>
            <br>
            that I don't have full access to.<br>
            <br>
            But then I don't understand why so far I had no issues with
            k12Linux on Centos?????<br>
            <br>
            * I then put together a new thinclient, with motherbord
            Gibabyte GA-c847n, intel Celeron processor.<br>
            <br>
            When booting this, i also see some EM, but K12Linux boots
            fine, and...<br>
            <br>
            <big>There's no green screen. It just works</big><br>
            <br>
            So this fully suggests that the issue is the HP t545
            thinclient.<br>
            <br>
            This is a showstopper for me, because this is our mainline
            thinclient.<br>
            <br>
            Thanks for any advise on this issue.<br>
            <br>
            Greetings, J.<br>
            <br>
            <br>
            <div>Op 06-06-13 00:36, Joshua Trimm schreef:<br>
            </div>
            <blockquote type="cite"> Johan, Try first cleaning your
              cache by doing a 'yum clean all' then 'yum update' and let
              me know if that works for you.<br>
              <br>
              The green glare issue i'm unfamiliar with, could you take
              a screenshot and post a link to it directly to my email? <br>
              Thanks,<br>
              <br>
              <div>On 6/5/13 2:55 AM, Johan Vermeulen wrote:<br>
              </div>
              <blockquote type="cite"> hello Jushua,<br>
                <br>
                thanks for letting me know.<br>
                <br>
                *the routing problem was solved by editing the iptables
                manualy.<br>
                <br>
                * I did put "em2" in /etc/ltsp/ltsp-server.conf before
                running the scripts.<br>
                <br>
                * my original install was with epel, yesterday evening I
                updated with the other repo:<br>
                <br>
                <small>[root@centoshofkwartier ~]# yum repolist<br>
                  Loaded plugins: fastestmirror, refresh-packagekit,
                  security<br>
                  Loading mirror speeds from cached hostfile<br>
                   * base: <a moz-do-not-send="true"
                    href="http://distrib-coffee.ipsl.jussieu.fr"
                    target="_blank">distrib-coffee.ipsl.jussieu.fr</a><br>
                   * extras: <a moz-do-not-send="true"
                    href="http://mirror.ovh.net" target="_blank">mirror.ovh.net</a><br>
                   * ltsp: <a moz-do-not-send="true"
                    href="http://ltsprepo.s3.amazonaws.com"
                    target="_blank">ltsprepo.s3.amazonaws.com</a><br>
                   * updates: <a moz-do-not-send="true"
                    href="http://distrib-coffee.ipsl.jussieu.fr"
                    target="_blank">distrib-coffee.ipsl.jussieu.fr</a><br>
                  repo id                        repo
                  name                                  status<br>
                  base                           CentOS-6 -
                  Base                            6381<br>
                  extras                         CentOS-6 -
                  Extras                            12<br>
                  ltsp                           LTSP -
                  x86_64                                60<br>
                  <br>
                </small><br>
                but something went wrong with the update,because my
                version is still:<br>
                <br>
                <small>[root@centoshofkwartier ~]# rpm -qa | grep ltsp<br>
                  ltsp-server-5.4.5-20.el6.x86_64<br>
                  ltspfs-1.1-7.el6.x86_64<br>
                  ltsp-release-5-9.el6.noarch</small><br>
                <br>
                * I then rebuilded with ltsp-build-client<br>
                <br>
                but the problem with the green glare stays.<br>
                Everything 's on the screen, but there's this filter
                over it......<br>
                <br>
                Maybe this can be solved by editing lts.conf.....<br>
                <br>
                greetings, J<br>
                <br>
                <br>
                <br>
                <br>
                <div>Op 04-06-13 20:46, Joshua Trimm schreef:<br>
                </div>
                <blockquote type="cite">Johan, I have 5.4.5-21 being
                  pushed to the repo's today which should fix the
                  scripts to accept an interface regardless of its name.
                  <br>
                  <br>
                  The reason NFS needs to be started manually is due to
                  the RPM not knowing which interface you will be using
                  for the LTSP network. This must be defined in
                  /etc/ltsp/ltsp-server.conf before ltsp-server-tweaks
                  and ltsp-server-initialize are run. <br>
                  On 6/4/13 5:23 AM, Johan Vermeulen wrote: <br>
                  <blockquote type="cite">Dear All, <br>
                    <br>
                    this is my experience with the install : <br>
                    <br>
                    version is ltsp-server-5.4.5-20.el6.x86_64 on
                    Centos6.4. <br>
                    installed with epel-repo. <br>
                    <br>
                    After starting nfs manualy like Barry and starting
                    tftp manualy, I am able to boot a thinclient. <br>
                    <br>
                    But I'm facing these problems : <br>
                    <br>
                    *ltsp-server-tweaks hangs on " about to overwrite
                    your firewall config" either with iptables on or
                    off. <br>
                    Probably because of that, laptops and workstations
                    that are on the lan cannot reach the internet. This
                    is my main concern. <br>
                    Setting up nat manualy did not help. <br>
                    <br>
                    this is /etc/sysconfig/iptables : <br>
                    <br>
                    # Firewall configuration written by
                    system-config-firewall <br>
                    # Manual customization of this file is not
                    recommended. <br>
                    *nat <br>
                    :PREROUTING ACCEPT [0:0] <br>
                    :OUTPUT ACCEPT [0:0] <br>
                    :POSTROUTING ACCEPT [0:0] <br>
                    -A POSTROUTING -o eth+ -j MASQUERADE <br>
                    -A POSTROUTING -o em2 -j MASQUERADE <br>
                    COMMIT <br>
                    *filter <br>
                    :INPUT ACCEPT [0:0] <br>
                    :FORWARD ACCEPT [0:0] <br>
                    :OUTPUT ACCEPT [0:0] <br>
                    -A INPUT -m state --state ESTABLISHED,RELATED -j
                    ACCEPT <br>
                    -A INPUT -p icmp -j ACCEPT <br>
                    -A INPUT -i lo -j ACCEPT <br>
                    -A INPUT -i eth+ -j ACCEPT <br>
                    -A INPUT -i em2 -j ACCEPT <br>
                    -A INPUT -m state --state NEW -m tcp -p tcp --dport
                    22 -j ACCEPT <br>
                    -A FORWARD -m state --state ESTABLISHED,RELATED -j
                    ACCEPT <br>
                    -A FORWARD -p icmp -j ACCEPT <br>
                    -A FORWARD -i lo -j ACCEPT <br>
                    -A FORWARD -i eth+ -j ACCEPT <br>
                    -A FORWARD -i em2 -j ACCEPT <br>
                    -A FORWARD -o eth+ -j ACCEPT <br>
                    -A FORWARD -o em2 -j ACCEPT <br>
                    -A INPUT -j REJECT --reject-with
                    icmp-host-prohibited <br>
                    -A FORWARD -j REJECT --reject-with
                    icmp-host-prohibited <br>
                    COMMIT <br>
                    <br>
                    *ltsp-server-initialize gives me a lot of EM. But
                    the thinclient boots, so maybe that's not a problem.
                    <br>
                    <br>
                    *when booting the thinclient, I get an EM :
                    unsupported device : processor centaurhauls <br>
                      The thinclient is an HP hstnc-004 that I used on 3
                    different thinclient systems in the past 3 years. <br>
                      It would be a real problem if it doesn't work with
                    this image. <br>
                    <br>
                    *when booted, I am able to log in, and adapt
                    language and other settings in lts.conf. But I can't
                    get rid of the green glare that is over the <br>
                    screen. <br>
                    Could be the Acer monitor, but it's fine when
                    attached to other devices. <br>
                    <br>
                    Any input on these issues would be greatly
                    appreciated. <br>
                    <br>
                    greetings, J. <br>
                    <br>
                    <br>
                    Op 03-06-13 20:20, Barry Cisna schreef: <br>
                    <blockquote type="cite">Hello All, <br>
                      <br>
                      Replying to my previous post. <br>
                      For completeness. <br>
                      <br>
                      The fix for the 'stuck' Booting Linux line was I
                      did not have nfs <br>
                      service started at boot on the server and had to
                      manually enter <br>
                      the /opt/ltsp dir in nfs/exports. <br>
                      After this clients will boot fine. <br>
                      <br>
                      Take Care, <br>
                      Barry <br>
                      <br>
                      <br>
                      _______________________________________________ <br>
                      K12OSN mailing list <br>
                      <a moz-do-not-send="true"
                        href="mailto:K12OSN@redhat.com" target="_blank">K12OSN@redhat.com</a>
                      <br>
                      <a moz-do-not-send="true"
                        href="https://www.redhat.com/mailman/listinfo/k12osn"
                        target="_blank">https://www.redhat.com/mailman/listinfo/k12osn</a>
                      <br>
                      For more info see <a moz-do-not-send="true"
                        href="http://www.k12os.org" target="_blank"><http://www.k12os.org></a>
                      <br>
                    </blockquote>
                    <br>
                    _______________________________________________ <br>
                    K12OSN mailing list <br>
                    <a moz-do-not-send="true"
                      href="mailto:K12OSN@redhat.com" target="_blank">K12OSN@redhat.com</a>
                    <br>
                    <a moz-do-not-send="true"
                      href="https://www.redhat.com/mailman/listinfo/k12osn"
                      target="_blank">https://www.redhat.com/mailman/listinfo/k12osn</a>
                    <br>
                    For more info see <a moz-do-not-send="true"
                      href="http://www.k12os.org" target="_blank"><http://www.k12os.org></a>
                    <br>
                  </blockquote>
                  <br>
                  _______________________________________________ <br>
                  K12OSN mailing list <br>
                  <a moz-do-not-send="true"
                    href="mailto:K12OSN@redhat.com" target="_blank">K12OSN@redhat.com</a>
                  <br>
                  <a moz-do-not-send="true"
                    href="https://www.redhat.com/mailman/listinfo/k12osn"
                    target="_blank">https://www.redhat.com/mailman/listinfo/k12osn</a>
                  <br>
                  For more info see <a moz-do-not-send="true"
                    href="http://www.k12os.org" target="_blank"><http://www.k12os.org></a>
                  <br>
                </blockquote>
                <br>
                <br>
                <fieldset></fieldset>
                <br>
                <pre>_______________________________________________
K12OSN mailing list
<a moz-do-not-send="true" href="mailto:K12OSN@redhat.com" target="_blank">K12OSN@redhat.com</a>
<a moz-do-not-send="true" href="https://www.redhat.com/mailman/listinfo/k12osn" target="_blank">https://www.redhat.com/mailman/listinfo/k12osn</a>
For more info see <a moz-do-not-send="true" href="http://www.k12os.org" target="_blank"><http://www.k12os.org></a></pre>
              </blockquote>
              <br>
              <br>
              <fieldset></fieldset>
              <br>
              <pre>_______________________________________________
K12OSN mailing list
<a moz-do-not-send="true" href="mailto:K12OSN@redhat.com" target="_blank">K12OSN@redhat.com</a>
<a moz-do-not-send="true" href="https://www.redhat.com/mailman/listinfo/k12osn" target="_blank">https://www.redhat.com/mailman/listinfo/k12osn</a>
For more info see <a moz-do-not-send="true" href="http://www.k12os.org" target="_blank"><http://www.k12os.org></a></pre>
            </blockquote>
            <br>
          </div>
          <br>
          _______________________________________________<br>
          K12OSN mailing list<br>
          <a moz-do-not-send="true" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a><br>
          <a moz-do-not-send="true"
            href="https://www.redhat.com/mailman/listinfo/k12osn"
            target="_blank">https://www.redhat.com/mailman/listinfo/k12osn</a><br>
          For more info see <<a moz-do-not-send="true"
            href="http://www.k12os.org" target="_blank">http://www.k12os.org</a>><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <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>
    <br>
  </body>
</html>