[Ltsp-discuss] Client stops at setting up NIC

[Rolf-Werner Eilert]

Hi folks!

My brand new Intel NUC connects to the server, loads the kernel, but
stops/hangs at setting up the network card. When booting in debug mode,
it says "try setting the option-129".

As already described, this is an older 64bit server (Suse 12.1) with an
older LTSP5.

Has anyone here an idea how to get my new NUC running? Later, I will
have to set up a new server system anyway, but for a first trial I
thought it would be nice to use the old one.

By the way, LTSP5 normally runs fine on the system. In the past, I tried
it with different small and larger systems. Sometimes it stops at
graphics, but I never had this problem with the network adapter.

Regards
Rolf

[Finn Andersen]

Hi Rolf!

I don't think it is related to your problem. But the kernel option
"ipappend 2" vs "ipappend 3" could result in a client not booting properly.

-Finn

On Mon, Feb 20, 2017 at 5:27 PM, Rolf-Werner Eilert <rwe-***@osnanet.de>
wrote:

> Hi folks!
>
> My brand new Intel NUC connects to the server, loads the kernel, but
> stops/hangs at setting up the network card. When booting in debug mode,
> it says "try setting the option-129".
>
> As already described, this is an older 64bit server (Suse 12.1) with an
> older LTSP5.
>
> Has anyone here an idea how to get my new NUC running? Later, I will
> have to set up a new server system anyway, but for a first trial I
> thought it would be nice to use the old one.
>
> By the way, LTSP5 normally runs fine on the system. In the past, I tried
> it with different small and larger systems. Sometimes it stops at
> graphics, but I never had this problem with the network adapter.
>
> Regards
> Rolf
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>

[Horst Prote]

Hi Rolf,

> My brand new Intel NUC connects to the server, loads the kernel, but
> stops/hangs at setting up the network card. When booting in debug mode,
> it says "try setting the option-129".
I had this once, many years ago (ltsp-2.x). The solution was a newer
kernel with better support for the network adapter.

Regards
Horst

[Rolf-Werner Eilert]

Am 21.02.2017 11:25, schrieb Horst Prote:
> Hi Rolf,
>
>> My brand new Intel NUC connects to the server, loads the kernel, but
>> stops/hangs at setting up the network card. When booting in debug mode,
>> it says "try setting the option-129".
> I had this once, many years ago (ltsp-2.x). The solution was a newer
> kernel with better support for the network adapter.
>

I guess it's something like that, unfortunately. And it means setting up
a newer system for the server, doesn't it?

Regards
Rolf

[Johan Kragsterman]

Hi, Rolf!


There is still the Edubuntu live DVD to download, according to this site:

http://cdimage.ubuntu.com/edubuntu/releases/14.04.2/release/

It is 14.04 though, but I'm sure it is modern enough.


Best regards from/Med vänliga hälsningar från

Johan Kragsterman

Capvert


-----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
Till: ltsp-***@lists.sourceforge.net
Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
Datum: 2017-02-21 12:28
Ärende: Re: [Ltsp-discuss] Client stops at setting up NIC

Am 21.02.2017 11:25, schrieb Horst Prote:
> Hi Rolf,
>
>> My brand new Intel NUC connects to the server, loads the kernel, but
>> stops/hangs at setting up the network card. When booting in debug mode,
>> it says "try setting the option-129".
> I had this once, many years ago (ltsp-2.x). The solution was a newer
> kernel with better support for the network adapter.
>

I guess it's something like that, unfortunately. And it means setting up
a newer system for the server, doesn't it?

Regards
Rolf



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Rolf-Werner Eilert]

Hi Johan,

thanks for that idea. I downloaded and burned one and will test as soon
as possible.

But: Wouldn't it be possible to let ltsp make a new 64bit image instead
of the i386.img it made now?

I see there is a two-step booting: First

1.
/srv/tftpboot/boot/initrd-ltsp
/srv/tftpboot/boot/linux-ltsp

are loaded and executed (and my linux-ltsp is from 2012). Then I would
expect

2.
/srv/kiwi-ltsp/i386.img

to be loaded and run. This img was made new when I invoked
ltsp-built-client the other day.

The /etc/dhcpd.conf points to pxelinux.0 to boot from, is that correct?

Maybe I'm getting something completely wrong here, but if I could get my
new NUC running on the old server, I could make a direct test under
working conditions.

Regards
Rolf


Am 21.02.2017 12:35, schrieb Johan Kragsterman:
>
> Hi, Rolf!
>
>
> There is still the Edubuntu live DVD to download, according to this site:
>
> http://cdimage.ubuntu.com/edubuntu/releases/14.04.2/release/
>
> It is 14.04 though, but I'm sure it is modern enough.
>
>
> Best regards from/Med vänliga hälsningar från
>
> Johan Kragsterman
>
> Capvert
>
>
> -----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
> Till: ltsp-***@lists.sourceforge.net
> Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
> Datum: 2017-02-21 12:28
> Ärende: Re: [Ltsp-discuss] Client stops at setting up NIC
>
> Am 21.02.2017 11:25, schrieb Horst Prote:
>> Hi Rolf,
>>
>>> My brand new Intel NUC connects to the server, loads the kernel, but
>>> stops/hangs at setting up the network card. When booting in debug mode,
>>> it says "try setting the option-129".
>> I had this once, many years ago (ltsp-2.x). The solution was a newer
>> kernel with better support for the network adapter.
>>
>
> I guess it's something like that, unfortunately. And it means setting up
> a newer system for the server, doesn't it?
>
> Regards
> Rolf
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>

[Jigish Gohil]

On Tue, Feb 21, 2017 at 10:04 PM, Rolf-Werner Eilert <rwe-***@osnanet.de> wrote:
> Hi Johan,
>
> thanks for that idea. I downloaded and burned one and will test as soon
> as possible.
>
> But: Wouldn't it be possible to let ltsp make a new 64bit image instead
> of the i386.img it made now?
>

See parts under "If you are not using Tumbleweed..." here
https://en.opensuse.org/SDB:KIWI-LTSP_quick_start

Install kiwi-image-ltsp64 and kiwi-image-ltsp-boot64 packages from
tumbleweed repo, edit LTSP_PROFILES="i386 x86_64" in
/etc/sysconfig/kiwi-ltsp LTSP_PROFILES="i386 x86_64"

You might have to update kiwi-desc-ltsp and kiwi-ltsp packages from
tumbleweed repo if the following does not work, not sure if PROFILES
were implemented before your server installation.

Run kiwi-ltsp -c, if everything is alright then you would see latest
tubmbleweed x86_64 image in boot menu of the clients.

BTW, your server installation is too old, you should consider updating
to at least openSUSE 42.2 or use ltsp-pnp on Ubuntu Mate 16.04.2.

Cheers

Jigish

[Rolf-Werner Eilert]

Hi Jigish!

Am 25.02.2017 08:30, schrieb Jigish Gohil:
>
> See parts under "If you are not using Tumbleweed..." here
> https://en.opensuse.org/SDB:KIWI-LTSP_quick_start

I set up a Suse Leap 42.2 in a VM. Then tried to copy the instruction
from the page above into the console, changing 42.1 to 42.2. However,
zypper refuses it because the URL contains a ":"

Did I get something completely wrong here?

>
> Install kiwi-image-ltsp64 and kiwi-image-ltsp-boot64 packages from
> tumbleweed repo, edit LTSP_PROFILES="i386 x86_64" in
> /etc/sysconfig/kiwi-ltsp LTSP_PROFILES="i386 x86_64"

Do you know why the LTSP stuff was put in the Tumbleweed repos and not
in the Leap ones too?


>
> You might have to update kiwi-desc-ltsp and kiwi-ltsp packages from
> tumbleweed repo if the following does not work, not sure if PROFILES
> were implemented before your server installation.

What do you mean PROFILES?

One more question: There is a link to another, very old page about
network. It says there should be two NICs on the server. I could of
course install my VM like this, do you think this is better to make the
stuff run? And what about network anyway, now everything is running
out-of-the-box, i. e. the Suse VM uses the DHCP from our router to be
assigned an IP etc. Would it be better to have fixed addresses and its
own DHCP server (like the old server has) before I proceed with
installing LTSP?

Regards
Rolf

[Jigish Gohil MSS]

On Fri, Mar 3, 2017 at 1:26 PM, Rolf-Werner Eilert <rwe-***@osnanet.de> wrote:
> Hi Jigish!
>
> Am 25.02.2017 08:30, schrieb Jigish Gohil:
>>
>> See parts under "If you are not using Tumbleweed..." here
>> https://en.opensuse.org/SDB:KIWI-LTSP_quick_start
>
> I set up a Suse Leap 42.2 in a VM. Then tried to copy the instruction
> from the page above into the console, changing 42.1 to 42.2. However,
> zypper refuses it because the URL contains a ":"
>
> Did I get something completely wrong here?
>
As mentioned there: "If you are not on Tumbleweed, install the image
rpm packages manually, get the correct links for the kiwi-image-ltsp
and kiwi-image-ltsp-boot packages from
http://r.opensu.se/server:ltsp/openSUSE_Tumbleweed/noarch/"

So there is no zypper involved, so the links as on today are:

rpm -Uvh "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp-boot64-13.2.1-36.87.noarch.rpm"
"http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp64-13.2.1-36.87.noarch.rpm"
"http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-ltsp-0.9.10-15.4.noarch.rpm"

You can also download those files and run rpm -Uvh.

>>
>> Install kiwi-image-ltsp64 and kiwi-image-ltsp-boot64 packages from
>> tumbleweed repo, edit LTSP_PROFILES="i386 x86_64" in
>> /etc/sysconfig/kiwi-ltsp LTSP_PROFILES="i386 x86_64"
>
> Do you know why the LTSP stuff was put in the Tumbleweed repos and not
> in the Leap ones too?
>
Tumbleweed is rolling release, so we get always up to date OS.

>
>>
>> You might have to update kiwi-desc-ltsp and kiwi-ltsp packages from
>> tumbleweed repo if the following does not work, not sure if PROFILES
>> were implemented before your server installation.
>
> What do you mean PROFILES?
>
i386 and x86_64 are 2 profiles we ship, that can be customized to
create xyz profile, kiwi uses xml image descriptions of the target, it
is just the name of the image, see
https://suse.github.io/kiwi/manual/kiwi.html and
https://github.com/SUSE/kiwi-descriptions

> One more question: There is a link to another, very old page about
> network. It says there should be two NICs on the server.
>
Whatever works for you, ideally 2 nic is nice to have, but you can do
anything that fits in your network.

If you need help with this drop into #kiwi-ltsp IRC freenode, am here
for few hours.

Cheers

-J

[Rolf-Werner Eilert]

Am 03.03.2017 09:37, schrieb Jigish Gohil MSS:
> On Fri, Mar 3, 2017 at 1:26 PM, Rolf-Werner Eilert <rwe-***@osnanet.de> wrote:
>> Hi Jigish!
>>
>> Am 25.02.2017 08:30, schrieb Jigish Gohil:
>>>
>>> See parts under "If you are not using Tumbleweed..." here
>>> https://en.opensuse.org/SDB:KIWI-LTSP_quick_start
>>
>> I set up a Suse Leap 42.2 in a VM. Then tried to copy the instruction
>> from the page above into the console, changing 42.1 to 42.2. However,
>> zypper refuses it because the URL contains a ":"
>>
>> Did I get something completely wrong here?
>>
> As mentioned there: "If you are not on Tumbleweed, install the image
> rpm packages manually, get the correct links for the kiwi-image-ltsp
> and kiwi-image-ltsp-boot packages from
> http://r.opensu.se/server:ltsp/openSUSE_Tumbleweed/noarch/"
>

Ok, I ran into this because the text starts with

If you are not using Li-f-e then install kiwi-ltsp and kiwi-desc-ltsp
packages from the server:ltsp repository

And I thought, this was the first step which has to be done prior to do
this one:

> So there is no zypper involved, so the links as on today are:
>
> rpm -Uvh "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp-boot64-13.2.1-36.87.noarch.rpm"
> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp64-13.2.1-36.87.noarch.rpm"
> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-ltsp-0.9.10-15.4.noarch.rpm"
>
> You can also download those files and run rpm -Uvh.

I thought, in Suse I first have to install KIWI and then LTSP. What do
you think?

>
>>>
>>> Install kiwi-image-ltsp64 and kiwi-image-ltsp-boot64 packages from
>>> tumbleweed repo, edit LTSP_PROFILES="i386 x86_64" in
>>> /etc/sysconfig/kiwi-ltsp LTSP_PROFILES="i386 x86_64"
>>
>> Do you know why the LTSP stuff was put in the Tumbleweed repos and not
>> in the Leap ones too?
>>
> Tumbleweed is rolling release, so we get always up to date OS.
>

Basic question: Would it be wise to set up the new server under tumbleweed?

>>
>>>
>>> You might have to update kiwi-desc-ltsp and kiwi-ltsp packages from
>>> tumbleweed repo if the following does not work, not sure if PROFILES
>>> were implemented before your server installation.
>>
>> What do you mean PROFILES?
>>
> i386 and x86_64 are 2 profiles we ship, that can be customized to
> create xyz profile, kiwi uses xml image descriptions of the target, it
> is just the name of the image, see
> https://suse.github.io/kiwi/manual/kiwi.html and
> https://github.com/SUSE/kiwi-descriptions

Ah, got that. Thank you :)

>
>> One more question: There is a link to another, very old page about
>> network. It says there should be two NICs on the server.
>>
> Whatever works for you, ideally 2 nic is nice to have, but you can do
> anything that fits in your network.
>
> If you need help with this drop into #kiwi-ltsp IRC freenode, am here
> for few hours.
>

I'm in the office now, people coming in talking with me... Better we
stick to emails.

And I will be off into weekend soon, so maybe I will only be back on
Monday ;)

Thanks a lot!

Rolf

[Jigish Gohil MSS]

On Fri, Mar 3, 2017 at 5:51 PM, Rolf-Werner Eilert <rwe-***@osnanet.de> wrote:
>
> Ok, I ran into this because the text starts with
>
> If you are not using Li-f-e then install kiwi-ltsp and kiwi-desc-ltsp
> packages from the server:ltsp repository
>
zypper ar http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Leap_42.2/server:ltsp.repo
zypper ref
zypper in kiwi-ltsp kiwi-desc-ltsp

Followed by the rpm command below is what you need. Looks like the
wiki page is not clear enough so it would be nice if you could edit it
so it is less confusing for everyone else trying to do this. Zypper
should not have any problem with : as in above command, I've tested
those and they work fine.

> And I thought, this was the first step which has to be done prior to do
> this one:
>
>> So there is no zypper involved, so the links as on today are:
>>
>> rpm -Uvh "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp-boot64-13.2.1-36.87.noarch.rpm"
>> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp64-13.2.1-36.87.noarch.rpm"
>> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-ltsp-0.9.10-15.4.noarch.rpm"
>>
>> You can also download those files and run rpm -Uvh.
>
> I thought, in Suse I first have to install KIWI and then LTSP. What do
> you think?
>
>>
>
> Basic question: Would it be wise to set up the new server under tumbleweed?
>
Leap is better for production server use as it is more like LTS.

[Rolf-Werner Eilert]

Thank you for this line, now it ran through and installed everything.

Am 03.03.2017 15:00, schrieb Jigish Gohil MSS:
> On Fri, Mar 3, 2017 at 5:51 PM, Rolf-Werner Eilert <rwe-***@osnanet.de> wrote:
>>
>> Ok, I ran into this because the text starts with
>>
>> If you are not using Li-f-e then install kiwi-ltsp and kiwi-desc-ltsp
>> packages from the server:ltsp repository
>>
> zypper ar http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Leap_42.2/server:ltsp.repo
> zypper ref
> zypper in kiwi-ltsp kiwi-desc-ltsp
>
> Followed by the rpm command below is what you need. Looks like the
> wiki page is not clear enough so it would be nice if you could edit it
> so it is less confusing for everyone else trying to do this. Zypper
> should not have any problem with : as in above command, I've tested
> those and they work fine.

When everything has run well, I will try to make the necessary entries
there.

But now:

>
>> And I thought, this was the first step which has to be done prior to do
>> this one:
>>
>>> So there is no zypper involved, so the links as on today are:
>>>
>>> rpm -Uvh "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp-boot64-13.2.1-36.87.noarch.rpm"
>>> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp64-13.2.1-36.87.noarch.rpm"
>>> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-ltsp-0.9.10-15.4.noarch.rpm"
>>>
>>> You can also download those files and run rpm -Uvh.

Unfortunately, rpm (or curl) says "404 not found"

Where do I get a valid URL from? I do not use rpm every day...

>>
>> I thought, in Suse I first have to install KIWI and then LTSP. What do
>> you think?
>>
>>>
>>
>> Basic question: Would it be wise to set up the new server under tumbleweed?
>>
> Leap is better for production server use as it is more like LTS.

Ok, then it's good I try to use this.


Regards
Rolf

[Rolf-Werner Eilert]

Ok, I got it. Version had already changed. I looked up the directory in
the browser and noted the new numbers, now it downloaded and installed
everything successfully.

Next step: I have to see if it runs this way. So, probably I'll be back...

Thanks for your help!

Regards
Rolf


Am 03.03.2017 15:00, schrieb Jigish Gohil MSS:
> On Fri, Mar 3, 2017 at 5:51 PM, Rolf-Werner Eilert <rwe-***@osnanet.de> wrote:
>>
>> Ok, I ran into this because the text starts with
>>
>> If you are not using Li-f-e then install kiwi-ltsp and kiwi-desc-ltsp
>> packages from the server:ltsp repository
>>
> zypper ar http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Leap_42.2/server:ltsp.repo
> zypper ref
> zypper in kiwi-ltsp kiwi-desc-ltsp
>
> Followed by the rpm command below is what you need. Looks like the
> wiki page is not clear enough so it would be nice if you could edit it
> so it is less confusing for everyone else trying to do this. Zypper
> should not have any problem with : as in above command, I've tested
> those and they work fine.
>
>> And I thought, this was the first step which has to be done prior to do
>> this one:
>>
>>> So there is no zypper involved, so the links as on today are:
>>>
>>> rpm -Uvh "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp-boot64-13.2.1-36.87.noarch.rpm"
>>> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp64-13.2.1-36.87.noarch.rpm"
>>> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-ltsp-0.9.10-15.4.noarch.rpm"
>>>
>>> You can also download those files and run rpm -Uvh.
>>
>> I thought, in Suse I first have to install KIWI and then LTSP. What do
>> you think?
>>
>>>
>>
>> Basic question: Would it be wise to set up the new server under tumbleweed?
>>
> Leap is better for production server use as it is more like LTS.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>

[Rolf-Werner Eilert]

Alright. Made a snapshot of the system up to here, so I can return to
this state any later.

Although the wiki page says "don't go on before you set up the network"
- you said LTSP will be able to cope with that - I started kiwi-ltsp -c
and got a number of infos, the most important ones:

- it will create a 32 bit setup
- but there are a number of packages missing for 32 bit
- tftp will be done by dnsmasq

So, what can I do now? Better download 32bit packages too?

Regards
Rolf


Am 03.03.2017 15:00, schrieb Jigish Gohil MSS:
> On Fri, Mar 3, 2017 at 5:51 PM, Rolf-Werner Eilert <rwe-***@osnanet.de> wrote:
>>
>> Ok, I ran into this because the text starts with
>>
>> If you are not using Li-f-e then install kiwi-ltsp and kiwi-desc-ltsp
>> packages from the server:ltsp repository
>>
> zypper ar http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Leap_42.2/server:ltsp.repo
> zypper ref
> zypper in kiwi-ltsp kiwi-desc-ltsp
>
> Followed by the rpm command below is what you need. Looks like the
> wiki page is not clear enough so it would be nice if you could edit it
> so it is less confusing for everyone else trying to do this. Zypper
> should not have any problem with : as in above command, I've tested
> those and they work fine.
>
>> And I thought, this was the first step which has to be done prior to do
>> this one:
>>
>>> So there is no zypper involved, so the links as on today are:
>>>
>>> rpm -Uvh "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp-boot64-13.2.1-36.87.noarch.rpm"
>>> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-image-ltsp64-13.2.1-36.87.noarch.rpm"
>>> "http://download.opensuse.org/repositories/server:/ltsp/openSUSE_Tumbleweed/noarch/kiwi-ltsp-0.9.10-15.4.noarch.rpm"
>>>
>>> You can also download those files and run rpm -Uvh.
>>
>> I thought, in Suse I first have to install KIWI and then LTSP. What do
>> you think?
>>
>>>
>>
>> Basic question: Would it be wise to set up the new server under tumbleweed?
>>
> Leap is better for production server use as it is more like LTS.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>

[Jigish Gohil MSS]

On Mar 6, 2017 9:22 PM, "Rolf-Werner Eilert" <rwe-***@osnanet.de> wrote


Although the wiki page says "don't go on before you set up the network"
- you said LTSP will be able to cope with that - I started kiwi-ltsp -c


No it can't cope with no network configuration, it can work with 1 or 2
nics, but network has to be configured properly. That is step 1.

Step 2 is install packages.

Step 3 is kiwi-ltsp -c

There is nothing more to it, steps can't really get simpler than that.
Output you sent is useless, you'll have to send full output from that
command and describe exactly what happens when you boot clients. See
troubleshooting wiki page, try different clients, do any of them boot?

Please do not top post, and follow the usual rules of mailing list
postings. For kiwi-ltsp issues use it's mailing list.

[Rolf-Werner Eilert]

Am 07.03.2017 04:06, schrieb Jigish Gohil MSS:
> No it can't cope with no network configuration, it can work with 1 or 2
> nics, but network has to be configured properly. That is step 1.

Ok, got it

>
> Step 2 is install packages.
>
> Step 3 is kiwi-ltsp -c
>
> There is nothing more to it, steps can't really get simpler than that.

So next I will try with 2 NICs, classical, it should be easy on a VM.

> Output you sent is useless, you'll have to send full output from that
> command and describe exactly what happens when you boot clients.

I know! Difficult from within a terminal in a VM on another machine in
the office... But I'll try to be more concise next time.

>
> Please do not top post, and follow the usual rules of mailing list
> postings. For kiwi-ltsp issues use it's mailing list.

Oh, is there a mailing list for kiwi-ltsp? Didn't know that. I thought
this one was the only support for LTSP around...

Sorry, didn't mean to bother you with my postings, thanks a lot for your
time and helping me out.

As soon as I found a way to get things running properly, I will help
updating the documentation as mentioned in our discussion some weeks
ago. But first I have to have a running LTSP and understand how
everything works together. As I do not have a spare PC at hand to
install it, I try to use a VM.

Regards
Rolf


------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Rolf-Werner Eilert]

Ok, I was alone in the office, shutdown the server and tried the
edubuntu DVD.

Everyting starts as expected, I could start live-ltsp.

The NUC sees the DHCP, loads everything, starts - and ends up with a
blinking cursor which disappears from time to time and appears again,
blinking.

So it seems the graphics mode is not detected correctly, right? I tried
TTY1, it was waiting for a login, but I didn't know what to use as password.

So I rebooted my server and wrote this mail :)

Regards
Rolf

Am 21.02.2017 12:35, schrieb Johan Kragsterman:
>
> Hi, Rolf!
>
>
> There is still the Edubuntu live DVD to download, according to this site:
>
> http://cdimage.ubuntu.com/edubuntu/releases/14.04.2/release/
>
> It is 14.04 though, but I'm sure it is modern enough.
>
>
> Best regards from/Med vänliga hälsningar från
>
> Johan Kragsterman
>
> Capvert
>
>
> -----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
> Till: ltsp-***@lists.sourceforge.net
> Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
> Datum: 2017-02-21 12:28
> Ärende: Re: [Ltsp-discuss] Client stops at setting up NIC
>
> Am 21.02.2017 11:25, schrieb Horst Prote:
>> Hi Rolf,
>>
>>> My brand new Intel NUC connects to the server, loads the kernel, but
>>> stops/hangs at setting up the network card. When booting in debug mode,
>>> it says "try setting the option-129".
>> I had this once, many years ago (ltsp-2.x). The solution was a newer
>> kernel with better support for the network adapter.
>>
>
> I guess it's something like that, unfortunately. And it means setting up
> a newer system for the server, doesn't it?
>
> Regards
> Rolf
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>

[Alkis Georgopoulos]

This is an up-to-date tutorial, with an up-to-date distro (ubuntu 16.04,
proposed DE=mate), with an up-to-date ltsp, with an up-to-date kernel,
with an up-to-date xorg:

https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp

You can easily install it to VM or a USB stick or USB disk and test in
any environment you like.
When you're changing networks, the only thing to run is:
sudo ltsp-config dnsmasq --overwrite

[Rolf-Werner Eilert]

Thank you, Alkis, for this link

Am 22.02.2017 07:23, schrieb Alkis Georgopoulos:
> This is an up-to-date tutorial, with an up-to-date distro (ubuntu 16.04,
> proposed DE=mate), with an up-to-date ltsp, with an up-to-date kernel,
> with an up-to-date xorg:
>
> https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
>
> You can easily install it to VM or a USB stick or USB disk and test in
> any environment you like.
> When you're changing networks, the only thing to run is:
> sudo ltsp-config dnsmasq --overwrite
>

I think the VM way would be nice... will try as soon as possible.

When I try ltsp-config this way, will there be a dialog?

Regards
Rolf

[Alkis Georgopoulos]

On 22/02/2017 01:41 μμ, Rolf-Werner Eilert wrote:
> Thank you, Alkis, for this link
>
> Am 22.02.2017 07:23, schrieb Alkis Georgopoulos:
>> This is an up-to-date tutorial, with an up-to-date distro (ubuntu 16.04,
>> proposed DE=mate), with an up-to-date ltsp, with an up-to-date kernel,
>> with an up-to-date xorg:
>>
>> https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
>>
>> You can easily install it to VM or a USB stick or USB disk and test in
>> any environment you like.
>> When you're changing networks, the only thing to run is:
>> sudo ltsp-config dnsmasq --overwrite
>>
>
> I think the VM way would be nice... will try as soon as possible.
>
> When I try ltsp-config this way, will there be a dialog?
>


No, it's a command-line utility:
http://manpages.ubuntu.com/ltsp-config

...but it autodetects the network so it doesn't need any parameters.

[Johan Kragsterman]

Hi, Rolf!




-----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
Till: ltsp-***@lists.sourceforge.net
Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
Datum: 2017-02-21 17:35
Ärende: Re: [Ltsp-discuss] Ang: Re: Client stops at setting up NIC

Hi Johan,

thanks for that idea. I downloaded and burned one and will test as soon
as possible.

But: Wouldn't it be possible to let ltsp make a new 64bit image instead
of the i386.img it made now?





Sure, you can build many types of images with ltsp-build-client. There are many different options, like architecture, name, place, what is included, etc. I have run ltsp servers with multiple different images for multiple different client types.

Just run this, and you get a list of the options: ltsp-build-client --extra-help






I see there is a two-step booting: First

1.
/srv/tftpboot/boot/initrd-ltsp
/srv/tftpboot/boot/linux-ltsp

are loaded and executed (and my linux-ltsp is from 2012). Then I would
expect

2.
/srv/kiwi-ltsp/i386.img

to be loaded and run. This img was made new when I invoked
ltsp-built-client the other day.

The /etc/dhcpd.conf points to pxelinux.0 to boot from, is that correct?





I attach one of my old dhcpd.conf files for you to have a look at.








Maybe I'm getting something completely wrong here, but if I could get my
new NUC running on the old server, I could make a direct test under
working conditions.

Regards
Rolf


Am 21.02.2017 12:35, schrieb Johan Kragsterman:
>
> Hi, Rolf!
>
>
> There is still the Edubuntu live DVD to download, according to this site:
>
> http://cdimage.ubuntu.com/edubuntu/releases/14.04.2/release/
>
> It is 14.04 though, but I'm sure it is modern enough.
>
>
> Best regards from/Med vänliga hälsningar från
>
> Johan Kragsterman
>
> Capvert
>
>
> -----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
> Till: ltsp-***@lists.sourceforge.net
> Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
> Datum: 2017-02-21 12:28
> Ärende: Re: [Ltsp-discuss] Client stops at setting up NIC
>
> Am 21.02.2017 11:25, schrieb Horst Prote:
>> Hi Rolf,
>>
>>> My brand new Intel NUC connects to the server, loads the kernel, but
>>> stops/hangs at setting up the network card. When booting in debug mode,
>>> it says "try setting the option-129".
>> I had this once, many years ago (ltsp-2.x). The solution was a newer
>> kernel with better support for the network adapter.
>>
>
> I guess it's something like that, unfortunately. And it means setting up
> a newer system for the server, doesn't it?
>
> Regards
> Rolf
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>

[Rolf-Werner Eilert]

Hi Johan,

when I invoke it like that

> Just run this, and you get a list of the options: ltsp-build-client --extra-help
>

it starts with building a new chroot immediately. Maybe it's too old?


> I attach one of my old dhcpd.conf files for you to have a look at.
>

Thank you very much, I will have a look at that next :)

Regards
Rolf

[Johan Kragsterman]

Hi, Rolf!



-----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
Till: ltsp-***@lists.sourceforge.net
Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
Datum: 2017-02-22 08:32
Ärende: Re: [Ltsp-discuss] Ang: Re: Ang: Re: Client stops at setting up NIC

Hi Johan,

when I invoke it like that

> Just run this, and you get a list of the options: ltsp-build-client --extra-help
>

it starts with building a new chroot immediately. Maybe it's too old?




Even with the option: --extra-help? ...strange...

Actually, I don't know much about that kiwi implementation of ltsp. Tried it some time several yrs ago, but abandoned it due to complications. But I guess you can run it in the live DVD, or if you install it on a external usb drive?

Also, you can consider Alkis suggestion to use ltsp-pnp. With that you got some good simplicity enhancements, but a trade off is less flexibility. You can not use different images for different needs and architectures, all clients need to use the same. In my setups I have preferred to use normal ltsp, but for sure, with a less complicated environment ltsp-pnp would be useful. Though for me, I prefer the flexibility of having the choice of different chroots.




> I attach one of my old dhcpd.conf files for you to have a look at.
>

Thank you very much, I will have a look at that next :)

Regards
Rolf



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Alkis Georgopoulos]

On 22/02/2017 09:57 πμ, Johan Kragsterman wrote:
>
> Also, you can consider Alkis suggestion to use ltsp-pnp.
> With that you got some good simplicity enhancements, but a trade off
is less flexibility.
> You can not use different images for different needs and
architectures, all clients need
> to use the same. In my setups I have preferred to use normal ltsp,
but for sure, with a
> less complicated environment ltsp-pnp would be useful. Though for me,
I prefer the
> flexibility of having the choice of different chroots.
>


ltsp-pnp uses the server / as a template for the default "chroot".
It doesn't prohibit you from creating 10 more chroots if you want to.

[Johan Kragsterman]

Hi!



-----Alkis Georgopoulos <***@gmail.com> skrev: -----
Till: ltsp-***@lists.sourceforge.net
Från: Alkis Georgopoulos <***@gmail.com>
Datum: 2017-02-22 09:02
Ärende: Re: [Ltsp-discuss] Ang: Re: Ang: Re: Ang: Re: Client stops at setting up NIC

On 22/02/2017 09:57 &#960;&#956;, Johan Kragsterman wrote:
>
> Also, you can consider Alkis suggestion to use ltsp-pnp.
> With that you got some good simplicity enhancements, but a trade off
is less flexibility.
> You can not use different images for different needs and
architectures, all clients need
> to use the same. In my setups I have preferred to use normal ltsp,
but for sure, with a
> less complicated environment ltsp-pnp would be useful. Though for me,
I prefer the
> flexibility of having the choice of different chroots.
>


ltsp-pnp uses the server / as a template for the default "chroot".
It doesn't prohibit you from creating 10 more chroots if you want to.






Thanks for the clarification of that, didn't know that. What I have read about ltsp-pnp is that it can't use other clients than the architecture of the server. Am I wrong there...? If so, that makes all the difference.

/Johan



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Alkis Georgopoulos]

On 22/02/2017 10:10 πμ, Johan Kragsterman wrote:
>
> Thanks for the clarification of that, didn't know that.
> What I have read about ltsp-pnp is that it can't use other clients
> than the architecture of the server. Am I wrong there...?
> If so, that makes all the difference.

For example, you can have a 64bit server,
with the default 64bit ltsp-pnp chroot that can boot 64bit thin and fat
clients,
and then you can decide to run ltsp-build-client --arch i386 to support
older i386 thin clients,
and then you can decide to follow
https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi to build an
armhf chroot to support booting raspberry pis too,
etc etc

ltsp-pnp just helps you set up your initial environment,
and gives you a graphical way to manage your default chroot,
it doesn't impose any limits to what you can do with your ltsp installation.

[Andreas-Christoph Bernstein]

Zitat von Alkis Georgopoulos <***@gmail.com>:

> On 22/02/2017 10:10 πμ, Johan Kragsterman wrote:
>>
>> Thanks for the clarification of that, didn't know that.
> > What I have read about ltsp-pnp is that it can't use other clients
> > than the architecture of the server. Am I wrong there...?
> > If so, that makes all the difference.
>
> For example, you can have a 64bit server,
> with the default 64bit ltsp-pnp chroot that can boot 64bit thin and fat
> clients,
> and then you can decide to run ltsp-build-client --arch i386 to support
> older i386 thin clients,
> and then you can decide to follow
> https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi to build an
> armhf chroot to support booting raspberry pis too,
> etc etc
>
> ltsp-pnp just helps you set up your initial environment,
> and gives you a graphical way to manage your default chroot,
> it doesn't impose any limits to what you can do with your ltsp installation.


Interesting. That is new, right? I thought ltsp-pnp doesn't create a
chroot. That's why we are still using ltsp-server-standalone on our
ubuntu server.

So nowadays i would start with ltsp-pnp? Is ltsp-server-standalone
obsolete (on ubuntu)?

Andreas

[Alkis Georgopoulos]

On 22/02/2017 10:37 πμ, Andreas-Christoph Bernstein wrote:
> Interesting. That is new, right? I thought ltsp-pnp doesn't create a
> chroot. That's why we are still using ltsp-server-standalone on our
> ubuntu server.
>
> So nowadays i would start with ltsp-pnp? Is ltsp-server-standalone
> obsolete (on ubuntu)?


ltsp-pnp has been around for more than 5 years and has been used in
thousands of installations. If it suits your needs, you can surely use
it. ltsp-build-client might be deprecated in ltsp6 in favor of other
methods to build chroots, but for ltsp5 it's of course still supported.

The ltsp-pnp wiki page does say that you need to install the
ltsp-server-standalone package, so you have some misunderstanding there,
let's try to clear it up.

ltsp-server: an LTSP server where we don't want DHCPD (and possibly
TFTPD) because we have those servers elsewhere in our LAN.
ltsp-server-standalone: an LTSP server which will have DHCPD and TFTPD.

Those are true for both classic ltsp and for ltsp-pnp.
The difference is that:
The ltsp-pnp wiki page suggests that you install ltsp-server-standalone
with dnsmasq as the dhcpd and tftpd server.
While in the classic ltsp, ltsp-server-standalone installed
isc-dhcp-server and tftpd-hpa.

The reason that ltsp-pnp prefers dnsmasq instead of those 2 others, is
because it can also function as "proxyDHCP", while isc-dhcp-server
cannot do that.
ProxyDHCP means: "I have a router that does DHCP in my network, so the
LTSP server should only send the boot filename and root path, and let
the router manage the IP leases".

Since the "router is DHCPD" scenario is very very common, that's why
ltsp-pnp preferred dnsmasq and ProxyDHCP.
And it became the default in recent classic LTSP too, so new LTSP
installations (2017+) will get dnsmasq by default instead of the other 2
servers.
That means that the ltsp-pnp differences from the classic ltsp are now
really really small; just running `ltsp-update-image -c /` instead of
running `ltsp-build-client` for the default image.

Btw, `ltsp-config dnsmasq` also sets up a classic DHCPD in the
192.168.67.x range, so if you want the old "dual nic" setup, you can
just set the second nic to 192.168.67.1 and you're ready to go.



To sum up: ltsp-server-standalone used to prefer to depend on
isc-dhcp-server and tftpd-hpa, while now it prefers to depends on dnsmasq.
If someone doesn't want dnsmasq, he can just install the 2 other ones.

[Andreas-Christoph Bernstein]

Zitat von Alkis Georgopoulos <***@gmail.com>:

> On 22/02/2017 10:37 πμ, Andreas-Christoph Bernstein wrote:
>> Interesting. That is new, right? I thought ltsp-pnp doesn't create a
>> chroot. That's why we are still using ltsp-server-standalone on our
>> ubuntu server.
>>
>> So nowadays i would start with ltsp-pnp? Is ltsp-server-standalone
>> obsolete (on ubuntu)?
>
>
> ltsp-pnp has been around for more than 5 years and has been used in
> thousands of installations. If it suits your needs, you can surely use
> it. ltsp-build-client might be deprecated in ltsp6 in favor of other
> methods to build chroots, but for ltsp5 it's of course still supported.
>
> The ltsp-pnp wiki page does say that you need to install the
> ltsp-server-standalone package, so you have some misunderstanding there,
> let's try to clear it up.
>
> ltsp-server: an LTSP server where we don't want DHCPD (and possibly
> TFTPD) because we have those servers elsewhere in our LAN.
> ltsp-server-standalone: an LTSP server which will have DHCPD and TFTPD.
>
> Those are true for both classic ltsp and for ltsp-pnp.
> The difference is that:
> The ltsp-pnp wiki page suggests that you install ltsp-server-standalone
> with dnsmasq as the dhcpd and tftpd server.
> While in the classic ltsp, ltsp-server-standalone installed
> isc-dhcp-server and tftpd-hpa.
>
> The reason that ltsp-pnp prefers dnsmasq instead of those 2 others, is
> because it can also function as "proxyDHCP", while isc-dhcp-server
> cannot do that.
> ProxyDHCP means: "I have a router that does DHCP in my network, so the
> LTSP server should only send the boot filename and root path, and let
> the router manage the IP leases".
>
> Since the "router is DHCPD" scenario is very very common, that's why
> ltsp-pnp preferred dnsmasq and ProxyDHCP.
> And it became the default in recent classic LTSP too, so new LTSP
> installations (2017+) will get dnsmasq by default instead of the other 2
> servers.
> That means that the ltsp-pnp differences from the classic ltsp are now
> really really small; just running `ltsp-update-image -c /` instead of
> running `ltsp-build-client` for the default image.
>
> Btw, `ltsp-config dnsmasq` also sets up a classic DHCPD in the
> 192.168.67.x range, so if you want the old "dual nic" setup, you can
> just set the second nic to 192.168.67.1 and you're ready to go.
>
>
>
> To sum up: ltsp-server-standalone used to prefer to depend on
> isc-dhcp-server and tftpd-hpa, while now it prefers to depends on dnsmasq.
> If someone doesn't want dnsmasq, he can just install the 2 other ones.
>

Thank you Alkis for your detailed response. That clears things up.

[Johan Kragsterman]

Hi, Alkis!

Suddenly my attitude to ltsp-pnp changed....

I don't know if I have been ignorant, or if you have been not clear enough in communicating this? I have been in this community for a looooong time....

/J


-----Alkis Georgopoulos <***@gmail.com> skrev: -----
Till: ltsp-***@lists.sourceforge.net
Från: Alkis Georgopoulos <***@gmail.com>
Datum: 2017-02-22 09:17
Ärende: Re: [Ltsp-discuss] Client stops at setting up NIC

On 22/02/2017 10:10 &#960;&#956;, Johan Kragsterman wrote:
>
> Thanks for the clarification of that, didn't know that.
> What I have read about ltsp-pnp is that it can't use other clients
> than the architecture of the server. Am I wrong there...?
> If so, that makes all the difference.

For example, you can have a 64bit server,
with the default 64bit ltsp-pnp chroot that can boot 64bit thin and fat
clients,
and then you can decide to run ltsp-build-client --arch i386 to support
older i386 thin clients,
and then you can decide to follow
https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi to build an
armhf chroot to support booting raspberry pis too,
etc etc

ltsp-pnp just helps you set up your initial environment,
and gives you a graphical way to manage your default chroot,
it doesn't impose any limits to what you can do with your ltsp installation.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Rolf-Werner Eilert]

Hi Johan,

you are right:

> Even with the option: --extra-help? ...strange...
>
> Actually, I don't know much about that kiwi implementation of ltsp. Tried it some time several yrs ago, but abandoned it due to complications. But I guess you can run it in the live DVD, or if you install it on a external usb drive?
>


I would never install it together with KIWI, and if Suse hasn't skipped
that by now, in case of a Suse install, I would try to download and
install it separately if possible.

Regards
Rolf

[Rolf-Werner Eilert]

Hi Johan,

>
> I attach one of my old dhcpd.conf files for you to have a look at.
>


Browsing the file, I wonder why there is this if-else clause with either
pxelinux.0 OR nbi.img. I saw this on other examples in the net.

On my system, I have only pxelinux.0 defined in dhcpd.conf, and there is
no nbi.img file anywhere. So I wonder when a client sends "PXEclient"
and when not.

Do you have an idea?

Regards
Rolf

[Vagrant Cascadian]

On 2017-02-22, Rolf-Werner Eilert wrote:
> Browsing the file, I wonder why there is this if-else clause with either
> pxelinux.0 OR nbi.img. I saw this on other examples in the net.
>
> On my system, I have only pxelinux.0 defined in dhcpd.conf, and there is
> no nbi.img file anywhere. So I wonder when a client sends "PXEclient"
> and when not.

NBI.img files were for legacy systems that used old versions of
etherboot rather than PXE. Most any recent system support PXE on-board,
or at the very least are able to load iPXE from boot media.

Support has recently been dropped in LTSP upstream, as it was broken for
some time; there were many incompatible formats for NBI.img, which made
it hard to maintain a working default. And it really is quite old by
now.

So, in short, everything can just use the pxelinux.0 clause in DHCP.

live well,
vagrant

[Johan Kragsterman]

Hi!



-----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
Till: ltsp-***@lists.sourceforge.net
Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
Datum: 2017-02-22 12:35
Ärende: Re: [Ltsp-discuss] Ang: Re: Ang: Re: Client stops at setting up NIC

Hi Johan,

>
> I attach one of my old dhcpd.conf files for you to have a look at.
>


Browsing the file, I wonder why there is this if-else clause with either
pxelinux.0 OR nbi.img. I saw this on other examples in the net.

On my system, I have only pxelinux.0 defined in dhcpd.conf, and there is
no nbi.img file anywhere. So I wonder when a client sends "PXEclient"
and when not.

Do you have an idea?

Regards
Rolf




The image files are the files that are provided for the clients, that contains the OS. The chroot is only there for you to manage software, and then the image is built from the chroot. pxelinux.0 will point to other files for the boot process to continue.

I can't say much about how your system is working, sorry...





------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Johan Kragsterman]

Hi!


Hmm, what about the bios settings for the pxe boot in that nuc? Should be set to legacy boot only, not uefi.


Best regards from/Med vänliga hälsningar från

Johan Kragsterman

Capvert


-----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
Till: ltsp-***@lists.sourceforge.net
Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
Datum: 2017-02-21 18:17
Ärende: Re: [Ltsp-discuss] Ang: Re: Client stops at setting up NIC

Ok, I was alone in the office, shutdown the server and tried the
edubuntu DVD.

Everyting starts as expected, I could start live-ltsp.

The NUC sees the DHCP, loads everything, starts - and ends up with a
blinking cursor which disappears from time to time and appears again,
blinking.

So it seems the graphics mode is not detected correctly, right? I tried
TTY1, it was waiting for a login, but I didn't know what to use as password.

So I rebooted my server and wrote this mail :)

Regards
Rolf

Am 21.02.2017 12:35, schrieb Johan Kragsterman:
>
> Hi, Rolf!
>
>
> There is still the Edubuntu live DVD to download, according to this site:
>
> http://cdimage.ubuntu.com/edubuntu/releases/14.04.2/release/
>
> It is 14.04 though, but I'm sure it is modern enough.
>
>
> Best regards from/Med vänliga hälsningar från
>
> Johan Kragsterman
>
> Capvert
>
>
> -----Rolf-Werner Eilert <rwe-***@osnanet.de> skrev: -----
> Till: ltsp-***@lists.sourceforge.net
> Från: Rolf-Werner Eilert <rwe-***@osnanet.de>
> Datum: 2017-02-21 12:28
> Ärende: Re: [Ltsp-discuss] Client stops at setting up NIC
>
> Am 21.02.2017 11:25, schrieb Horst Prote:
>> Hi Rolf,
>>
>>> My brand new Intel NUC connects to the server, loads the kernel, but
>>> stops/hangs at setting up the network card. When booting in debug mode,
>>> it says "try setting the option-129".
>> I had this once, many years ago (ltsp-2.x). The solution was a newer
>> kernel with better support for the network adapter.
>>
>
> I guess it's something like that, unfortunately. And it means setting up
> a newer system for the server, doesn't it?
>
> Regards
> Rolf
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Rolf-Werner Eilert]

Just looked it up:

Am 21.02.2017 19:14, schrieb Johan Kragsterman:
>
> Hi!
>
>
> Hmm, what about the bios settings for the pxe boot in that nuc? Should be set to legacy boot only, not uefi.
>
>

It is set to legacy, UEFI is switched off, and the first (and only)
booting device is Realtek PXE B03 D00.

So, should be ok.

Regards
Rolf