Re: [X2Go-User] X2Go TCE pxe complications

[ovt]

I want to clarify my previous post:The /opt/[2gothinkclient folder should be about 1.5 GB after the thin client image is created. 30.01.2022, 15:18, "o...@zaokknm.ru" :First of all, I inform you that the descriptions of the errors refer to the creation of a thin client image for OS Debian_10 64 bit. I got them comparing x2gothinclient_create script for 32bit and 64bit. I also report that Debian_10 32 bit had no image creation errors and booted normally the first time, but this was true for April 2020. In principle, I still have these scripts, but I cannot guarantee their performance at the moment.I want to note that the capacity of the image should be about 1.5 GB.Also... in your case with a weak thin client, I would recommend creating an image for 32 bit Debian OS. I insist on Debian.Or, as a proven option, hang up hdd or usb on a thin client, put Pupy and a regular x2go client there. 30.01.2022, 06:40, "MacGregor Family" :Thank you for this info, I've had a little break and now on back on theproject. As far as I can see these lines have been added to thex2gothinclient_create script already, perhaps when you reported theproblem. I have attached a couple of screen shots showing them. Arethese lines now correct or am I missing something?I recreated the thin client using "stretch" and the boot progressedfurther, but was still unsuccessful. This time the error message was:[FAILED] Failed to start. Create volatile files and directoriesI changed the operating system on the thin client to Tiny Core Linuxand it sped up the whole process, however reached the sameconclusion.I'm going to try to base the thin client on "Jessie" andchange all the repository references to the archived ones, however Idon't hold much hope. I looked for an x2goclient package for Tiny Corehowever it looks like if I want one I need to create the Tiny Coreextension myself and this may well be beyond my limited competance.Might give it a go if the all else fails.Thanks again for replying.RegardsStuart MacGregor On Wed, 2022-01-19 at 22:30 +0300, o...@zaokknm.ru wrote: I remember this trick with the pxelinux.cfg folder. :-)) If you are at this stage, then this is only the beginning of the journey. I do not know how to find my correspondence in the x2go-user thread, so I quote from my letter - --- Without waiting for an answer, I report the errors found in the /usr/sbin/x2gothinclient_create script. Skipped lines (206-207) [ $? -eq 0] && apt-get install gnupg -y [ $? -eq 0] && apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E (251)[ $? -eq 0] && systemctl enable x2gothinclient-displaymanager   After adding these lines, x2gothinclient loads fine. Please make these corrections. --- P.S.The documentation says that the thin client RAM must be at least 512 MB. I haven't tried it with low RAM, but it makes sense   12.01.2022, 14:12, "MacGregor Family" : > Thank you for the excellent advice. I switched the virtual machine > acting as my tftp server to Debian 11 and pxe boot started. I > didn't event need to chainload ipxe with undionly.kpxe. Basically > using Ubuntu for my tftp server was the problem. > > Something of note, though. It was necessary create a new directory > /srv/tftp/pxelinux.cfg and copy /srv/tftp/default.cfg into it. I > discovered this by consulting professor Google. I did not read this > in the classic X2go-tce documentation. Perhaps this might be > explictly added to this documention to help nubes like myself? > > I am having more problems, though. The first, red X2go splash > screen comes up but I am unable to make any selections, not with > the highlighted hotkeys nor with the arrow keys or even TAB. Not a > real problem, after timeout it defaults to x2go-tce which is what I > want anyway. I just mention it in case it is a symptom of the other > problems I'm about to describe. The boot soon fails with the > following messages: > > [ 16.996870] Initramfs unpacking failed : write error > [ 17.488013] mce: Unable to init MCE device (rc: -5) > [ 19.959922] Failed to execute /init (error -2) > [ 19.190964] Kernel panic - not syncing: No working init found. Try > passing init =option to Kernel. See Linux Documentation/admin- > guide/initrst for guidance. > [ 19.961064] CPU: 0 PID : 1 Comm: swapper/0 Not tainted 5.10.0-10- > 686 #1 Debian 5.10.84-1 > [ 19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009 > [ 19.961198] Call Trace: > [ 19.961283] dump_stack+0x54/0x68 > [ 19.961355] ? rest_init+0x30/0x97 > [ 19.961429] panic+0xa3/0x25b > [ 19.961495] ? rest_init+0xe0/0xe9 > [ 19.961630] ret_from_fork+0x1c/0x28 > [ 19.961705] Kernel Offset: disabled > [ 19.961775] ---[ end Kernel panic - not syncing: No working init > found. Try passing init =option to Kernel. See Linux > Documentation/admin-guide/initrst for guidance. ]--- > > Then the whole thing hangs up 

Re: [X2Go-User] X2Go TCE pxe complications

[ovt]

First of all, I inform you that the descriptions of the errors refer to the creation of a thin client image for OS Debian_10 64 bit. I got them comparing x2gothinclient_create script for 32bit and 64bit. I also report that Debian_10 32 bit had no image creation errors and booted normally the first time, but this was true for April 2020. In principle, I still have these scripts, but I cannot guarantee their performance at the moment.I want to note that the capacity of the image should be about 1.5 GB.Also... in your case with a weak thin client, I would recommend creating an image for 32 bit Debian OS. I insist on Debian.Or, as a proven option, hang up hdd or usb on a thin client, put Pupy and a regular x2go client there. 30.01.2022, 06:40, "MacGregor Family" :Thank you for this info, I've had a little break and now on back on theproject. As far as I can see these lines have been added to thex2gothinclient_create script already, perhaps when you reported theproblem. I have attached a couple of screen shots showing them. Arethese lines now correct or am I missing something?I recreated the thin client using "stretch" and the boot progressedfurther, but was still unsuccessful. This time the error message was:[FAILED] Failed to start. Create volatile files and directoriesI changed the operating system on the thin client to Tiny Core Linuxand it sped up the whole process, however reached the sameconclusion.I'm going to try to base the thin client on "Jessie" andchange all the repository references to the archived ones, however Idon't hold much hope. I looked for an x2goclient package for Tiny Corehowever it looks like if I want one I need to create the Tiny Coreextension myself and this may well be beyond my limited competance.Might give it a go if the all else fails.Thanks again for replying.RegardsStuart MacGregor On Wed, 2022-01-19 at 22:30 +0300, o...@zaokknm.ru wrote: I remember this trick with the pxelinux.cfg folder. :-)) If you are at this stage, then this is only the beginning of the journey. I do not know how to find my correspondence in the x2go-user thread, so I quote from my letter - --- Without waiting for an answer, I report the errors found in the /usr/sbin/x2gothinclient_create script. Skipped lines (206-207) [ $? -eq 0] && apt-get install gnupg -y [ $? -eq 0] && apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E (251)[ $? -eq 0] && systemctl enable x2gothinclient-displaymanager   After adding these lines, x2gothinclient loads fine. Please make these corrections. --- P.S.The documentation says that the thin client RAM must be at least 512 MB. I haven't tried it with low RAM, but it makes sense   12.01.2022, 14:12, "MacGregor Family" : > Thank you for the excellent advice. I switched the virtual machine > acting as my tftp server to Debian 11 and pxe boot started. I > didn't event need to chainload ipxe with undionly.kpxe. Basically > using Ubuntu for my tftp server was the problem. > > Something of note, though. It was necessary create a new directory > /srv/tftp/pxelinux.cfg and copy /srv/tftp/default.cfg into it. I > discovered this by consulting professor Google. I did not read this > in the classic X2go-tce documentation. Perhaps this might be > explictly added to this documention to help nubes like myself? > > I am having more problems, though. The first, red X2go splash > screen comes up but I am unable to make any selections, not with > the highlighted hotkeys nor with the arrow keys or even TAB. Not a > real problem, after timeout it defaults to x2go-tce which is what I > want anyway. I just mention it in case it is a symptom of the other > problems I'm about to describe. The boot soon fails with the > following messages: > > [ 16.996870] Initramfs unpacking failed : write error > [ 17.488013] mce: Unable to init MCE device (rc: -5) > [ 19.959922] Failed to execute /init (error -2) > [ 19.190964] Kernel panic - not syncing: No working init found. Try > passing init =option to Kernel. See Linux Documentation/admin- > guide/initrst for guidance. > [ 19.961064] CPU: 0 PID : 1 Comm: swapper/0 Not tainted 5.10.0-10- > 686 #1 Debian 5.10.84-1 > [ 19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009 > [ 19.961198] Call Trace: > [ 19.961283] dump_stack+0x54/0x68 > [ 19.961355] ? rest_init+0x30/0x97 > [ 19.961429] panic+0xa3/0x25b > [ 19.961495] ? rest_init+0xe0/0xe9 > [ 19.961630] ret_from_fork+0x1c/0x28 > [ 19.961705] Kernel Offset: disabled > [ 19.961775] ---[ end Kernel panic - not syncing: No working init > found. Try passing init =option to Kernel. See Linux > Documentation/admin-guide/initrst for guidance. ]--- > > Then the whole thing hangs up indefinitely. It seems to me that the > old thin client (TK-3550 AMD GX III LX800 CPU, 256 MB ram) needs a > legacy BIOS boot and this is unavailable for some reason. Should I > redo my X2go-tce setup 

Re: [X2Go-User] X2Go TCE pxe complications

[MacGregor Family]

Thank you for this info, I've had a little break and now on back on the
project. As far as I can see these lines have been added to the
x2gothinclient_create script already, perhaps when you reported the
problem. I have attached a couple of screen shots showing them. Are
these lines now correct or am I missing something?

I recreated the thin client using "stretch" and the boot progressed
further, but was still unsuccessful. This time the error message was:
[FAILED] Failed to start. Create volatile files and directories

I changed the operating system on the thin client to Tiny Core Linux
and it sped up the whole process, however reached the same
conclusion.I'm going to try to base the thin client on "Jessie" and
change all the repository references to the archived ones, however I
don't hold much hope.  I looked for an x2goclient package for Tiny Core
however it looks like if I want one I need to create the Tiny Core
extension myself and this may well be beyond my limited competance.
Might give it a go if the all else fails.

Thanks again for replying.

Regards
Stuart MacGregor
 
On Wed, 2022-01-19 at 22:30 +0300, o...@zaokknm.ru wrote:
> I remember this trick with the pxelinux.cfg folder. :-))
> If you are at this stage, then this is only the beginning of the
> journey.
> I do not know how to find my correspondence in the x2go-user thread,
> so I quote from my letter -
> ---
> Without waiting for an answer, I report the errors found in the
> /usr/sbin/x2gothinclient_create script.
> Skipped lines (206-207)
> [ $? -eq 0] && apt-get install gnupg -y
> [ $? -eq 0] && apt-key adv --recv-keys --keyserver keys.gnupg.net
> E1F958385BFE2B6E
> (251)[ $? -eq 0] && systemctl enable x2gothinclient-displaymanager
>  
> After adding these lines, x2gothinclient loads fine. Please make
> these corrections.
> ---
> P.S.The documentation says that the thin client RAM must be at least
> 512 MB. I haven't tried it with low RAM, but it makes sense
>  
> 12.01.2022, 14:12, "MacGregor Family" :
> > Thank you for the excellent advice. I switched the virtual machine
> > acting as my tftp server to Debian 11 and pxe boot started. I
> > didn't event need to chainload ipxe with undionly.kpxe. Basically
> > using Ubuntu for my tftp server was the problem.
> >  
> > Something of note, though. It was necessary create a new directory
> > /srv/tftp/pxelinux.cfg and copy /srv/tftp/default.cfg into it. I
> > discovered this by consulting professor Google. I did not read this
> > in the classic X2go-tce documentation. Perhaps this might be
> > explictly added to this documention to help nubes like myself?
> >  
> > I am having more problems, though. The first, red X2go splash
> > screen comes up but I am unable to make any selections, not with
> > the highlighted hotkeys nor with the arrow keys or even TAB. Not a
> > real problem, after timeout it defaults to x2go-tce which is what I
> > want anyway. I just mention it in case it is a symptom of the other
> > problems I'm about to describe. The boot soon fails with the
> > following messages:
> >  
> > [  16.996870] Initramfs unpacking failed : write error
> > [  17.488013] mce: Unable to init MCE device (rc: -5)
> > [ 19.959922] Failed to execute /init (error -2)
> > [ 19.190964] Kernel panic - not syncing: No working init found. Try
> > passing init =option to Kernel. See Linux Documentation/admin-
> > guide/initrst for guidance.
> > [ 19.961064] CPU: 0 PID : 1 Comm: swapper/0 Not tainted 5.10.0-10-
> > 686 #1 Debian 5.10.84-1
> > [ 19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009
> > [ 19.961198] Call Trace:
> > [ 19.961283]  dump_stack+0x54/0x68
> > [ 19.961355]  ? rest_init+0x30/0x97
> > [ 19.961429]  panic+0xa3/0x25b
> > [ 19.961495]  ? rest_init+0xe0/0xe9
> > [ 19.961630]  ret_from_fork+0x1c/0x28
> > [ 19.961705] Kernel Offset: disabled
> > [ 19.961775] ---[ end Kernel panic - not syncing: No working init
> > found. Try passing init =option to Kernel. See Linux
> > Documentation/admin-guide/initrst for guidance. ]---
> >  
> > Then the whole thing hangs up indefinitely. It seems to me that the
> > old thin client (TK-3550 AMD GX III LX800 CPU, 256 MB ram) needs a
> > legacy BIOS boot and this is unavailable for some reason. Should I
> > redo my X2go-tce setup (x2gothinclient_settings) and use an older
> > version of Debian to create the chroot image? I used the default
> > "Buster". If I need to go back enough versions of Debian will I
> > need to change to archived repositories in the same file (rather
> > than just http://ftp.debian.ors/debian  main)? Do I
> > need to add to the APPEND line of x2go-tce.cfg instead with
> > init=/sbin/ or some such (professor Google again)? Once again
> > any help here would be appreciated. I recognise that the thin
> > client I am using is rubbish but the price was right and having
> > come so far I'm reluctant to give up now.
> >  
> >  

Re: [X2Go-User] X2Go TCE pxe complications

[ovt]

I remember this trick with the pxelinux.cfg folder. :-))If you are at this stage, then this is only the beginning of the journey.I do not know how to find my correspondence in the x2go-user thread, so I quote from my letter Without waiting for an answer, I report the errors found in the /usr/sbin/x2gothinclient_create script.Skipped lines (206-207)[ $? -eq 0] && apt-get install gnupg -y[ $? -eq 0] && apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E(251)[ $? -eq 0] && systemctl enable x2gothinclient-displaymanager After adding these lines, x2gothinclient loads fine. Please make these corrections.---P.S.The documentation says that the thin client RAM must be at least 512 MB. I haven't tried it with low RAM, but it makes sense 12.01.2022, 14:12, "MacGregor Family" :Thank you for the excellent advice. I switched the virtual machine acting as my tftp server to Debian 11 and pxe boot started. I didn't event need to chainload ipxe with undionly.kpxe. Basically using Ubuntu for my tftp server was the problem. Something of note, though. It was necessary create a new directory /srv/tftp/pxelinux.cfg and copy /srv/tftp/default.cfg into it. I discovered this by consulting professor Google. I did not read this in the classic X2go-tce documentation. Perhaps this might be explictly added to this documention to help nubes like myself? I am having more problems, though. The first, red X2go splash screen comes up but I am unable to make any selections, not with the highlighted hotkeys nor with the arrow keys or even TAB. Not a real problem, after timeout it defaults to x2go-tce which is what I want anyway. I just mention it in case it is a symptom of the other problems I'm about to describe. The boot soon fails with the following messages: [  16.996870] Initramfs unpacking failed : write error[  17.488013] mce: Unable to init MCE device (rc: -5)[ 19.959922] Failed to execute /init (error -2)[ 19.190964] Kernel panic - not syncing: No working init found. Try passing init =option to Kernel. See Linux Documentation/admin-guide/initrst for guidance.[ 19.961064] CPU: 0 PID : 1 Comm: swapper/0 Not tainted 5.10.0-10-686 #1 Debian 5.10.84-1[ 19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009[ 19.961198] Call Trace:[ 19.961283]  dump_stack+0x54/0x68[ 19.961355]  ? rest_init+0x30/0x97[ 19.961429]  panic+0xa3/0x25b[ 19.961495]  ? rest_init+0xe0/0xe9[ 19.961630]  ret_from_fork+0x1c/0x28[ 19.961705] Kernel Offset: disabled[ 19.961775] ---[ end Kernel panic - not syncing: No working init found. Try passing init =option to Kernel. See Linux Documentation/admin-guide/initrst for guidance. ]--- Then the whole thing hangs up indefinitely. It seems to me that the old thin client (TK-3550 AMD GX III LX800 CPU, 256 MB ram) needs a legacy BIOS boot and this is unavailable for some reason. Should I redo my X2go-tce setup (x2gothinclient_settings) and use an older version of Debian to create the chroot image? I used the default "Buster". If I need to go back enough versions of Debian will I need to change to archived repositories in the same file (rather than just http://ftp.debian.ors/debian  main)? Do I need to add to the APPEND line of x2go-tce.cfg instead with init=/sbin/ or some such (professor Google again)? Once again any help here would be appreciated. I recognise that the thin client I am using is rubbish but the price was right and having come so far I'm reluctant to give up now.   On Mon, 2022-01-10 at 10:01 +0300, o...@zaokknm.ru wrote:At one time, when, about a year ago, while installing x2go on ubuntu, I faced about the same problem. Nevertheless, in a week I was able to run x2go-server + pxe. Endless poking around in the configuration files gave me the idea to change the distribution kit. Imagine my surprise when, in 30-40 minutes, I installed and configured this bundle on Debian_10 without any problems and have already been using it with 20 clients for a whole year. I also did not find understanding and help in the x2go community.My advice to you is to change your distribution to Debian.  05.01.2022, 15:38, "MacGregor Family" :Hello,I posted an enquiry quite some time ago but it hasn't attractedanyone's interest. In the meantime I have contiued trying to solve theproblem on my own. I moved all my dchp functions from my cheap, rubbishrouter to my ubuntu 20.04 server. I spent some time fiddling with thesettings of isc-dhcp-server. I downloaded ipxe undionly.kpxe and put itin my tftp server (a virual box virtual machine with bridged netwrkingalso running a ubuntu 20.04 server) at /srv/tftp. When I boot up myTermtek TK3550 Thin Client (AMD GX III LX800 CPU, 256 MB ram, IntelUNDI network card PXE 2.0) undionly.kpxe is successfully booted viatftp and the new bootloder finds pxelinux.0 then just locks up. Nothinghappens and it continues to happen indefinitely. I have attached 

Re: [X2Go-User] X2Go TCE pxe complications

[MacGregor Family]

Thank you for the excellent advice. I switched the virtual machine
acting as my tftp server to Debian 11 and pxe boot started. I didn't
event need to chainload ipxe with undionly.kpxe. Basically using Ubuntu
for my tftp server was the problem.
Something of note, though. It was necessary create a new directory
/srv/tftp/pxelinux.cfg and copy /srv/tftp/default.cfg into it. I
discovered this by consulting professor Google. I did not read this in
the classic X2go-tce documentation. Perhaps this might be explictly
added to this documention to help nubes like myself?
I am having more problems, though. The first, red X2go splash screen
comes up but I am unable to make any selections, not with the
highlighted hotkeys nor with the arrow keys or even TAB. Not a real
problem, after timeout it defaults to x2go-tce which is what I want
anyway. I just mention it in case it is a symptom of the other problems
I'm about to describe. The boot soon fails with the following messages:
[  16.996870] Initramfs unpacking failed : write error[  17.488013]
mce: Unable to init MCE device (rc: -5)[ 19.959922] Failed to execute
/init (error -2)[ 19.190964] Kernel panic - not syncing: No working
init found. Try passing init =option to Kernel. See Linux
Documentation/admin-guide/initrst for guidance.[ 19.961064] CPU: 0 PID
: 1 Comm: swapper/0 Not tainted 5.10.0-10-686 #1 Debian 5.10.84-1[
19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009[ 19.961198]
Call Trace:[ 19.961283]  dump_stack+0x54/0x68[ 19.961355]  ?
rest_init+0x30/0x97[ 19.961429]  panic+0xa3/0x25b[ 19.961495]  ?
rest_init+0xe0/0xe9[ 19.961630]  ret_from_fork+0x1c/0x28[ 19.961705]
Kernel Offset: disabled[ 19.961775] ---[ end Kernel panic - not
syncing: No working init found. Try passing init =option to Kernel. See
Linux Documentation/admin-guide/initrst for guidance. ]---
Then the whole thing hangs up indefinitely. It seems to me that the old
thin client (TK-3550 AMD GX III LX800 CPU, 256 MB ram) needs a legacy
BIOS boot and this is unavailable for some reason. Should I redo my
X2go-tce setup (x2gothinclient_settings) and use an older version of
Debian to create the chroot image? I used the default "Buster". If I
need to go back enough versions of Debian will I need to change to
archived repositories in the same file (rather than just 
http://ftp.debian.ors/debian  main)? Do I need to add
to the APPEND line of x2go-tce.cfg instead with init=/sbin/ or some
such (professor Google again)? Once again any help here would be
appreciated. I recognise that the thin client I am using is rubbish but
the price was right and having come so far I'm reluctant to give up
now.

 On Mon, 2022-01-10 at 10:01 +0300, o...@zaokknm.ru wrote:
> At one time, when, about a year ago, while installing x2go on ubuntu,
> I faced about the same problem. Nevertheless, in a week I was able to
> run x2go-server + pxe. Endless poking around in the configuration
> files gave me the idea to change the distribution kit. Imagine my
> surprise when, in 30-40 minutes, I installed and configured this
> bundle on Debian_10 without any problems and have already been using
> it with 20 clients for a whole year. I also did not find
> understanding and help in the x2go community.
> My advice to you is to change your distribution to Debian.
> 
> 05.01.2022, 15:38, "MacGregor Family" :
> > Hello,
> > 
> > I posted an enquiry quite some time ago but it hasn't attracted
> > anyone's interest. In the meantime I have contiued trying to solve
> > the
> > problem on my own. I moved all my dchp functions from my cheap,
> > rubbish
> > router to my ubuntu 20.04 server. I spent some time fiddling with
> > the
> > settings of isc-dhcp-server. I downloaded ipxe undionly.kpxe and
> > put it
> > in my tftp server (a virual box virtual machine with bridged
> > netwrking
> > also running a ubuntu 20.04 server) at /srv/tftp. When I boot up my
> > Termtek TK3550 Thin Client (AMD GX III LX800 CPU, 256 MB ram, Intel
> > UNDI network card PXE 2.0) undionly.kpxe is successfully booted via
> > tftp and the new bootloder finds pxelinux.0 then just locks up.
> > Nothing
> > happens and it continues to happen indefinitely. I have attached a
> > photo of the boot screen when it locks up.
> > 
> > I have created a directory of the tftp server
> > /srv/tftp/pxelinux.cfg .
> > I copied /srv/tftp/default.cfg into this directory both as
> > default.cfg
> > and as simply default. I also copied x2go-tce-cfg, memtest.cfg and
> > local-boot.cfg into this directory just in case. I am now at a
> > loss. I
> > have no way of checking/altering pxelinux.0 as it is in binary or
> > code
> > of some sort. I have spent hours in my free time to get this far,
> > but
> > in reality the end goal of logging into my linux server on a thin
> > client seems no closer. Any help would be appreciated.
> > 
> > Stuart MacGregor
> > macgregorath...@iinet.net.au
> > ,___
> > x2go-user mailing list
> > 

Re: [X2Go-User] X2Go TCE pxe complications

[ovt]

At one time, when, about a year ago, while installing x2go on ubuntu, I faced about the same problem. Nevertheless, in a week I was able to run x2go-server + pxe. Endless poking around in the configuration files gave me the idea to change the distribution kit. Imagine my surprise when, in 30-40 minutes, I installed and configured this bundle on Debian_10 without any problems and have already been using it with 20 clients for a whole year. I also did not find understanding and help in the x2go community.My advice to you is to change your distribution to Debian.05.01.2022, 15:38, "MacGregor Family" :Hello,I posted an enquiry quite some time ago but it hasn't attractedanyone's interest. In the meantime I have contiued trying to solve theproblem on my own. I moved all my dchp functions from my cheap, rubbishrouter to my ubuntu 20.04 server. I spent some time fiddling with thesettings of isc-dhcp-server. I downloaded ipxe undionly.kpxe and put itin my tftp server (a virual box virtual machine with bridged netwrkingalso running a ubuntu 20.04 server) at /srv/tftp. When I boot up myTermtek TK3550 Thin Client (AMD GX III LX800 CPU, 256 MB ram, IntelUNDI network card PXE 2.0) undionly.kpxe is successfully booted viatftp and the new bootloder finds pxelinux.0 then just locks up. Nothinghappens and it continues to happen indefinitely. I have attached aphoto of the boot screen when it locks up.I have created a directory of the tftp server /srv/tftp/pxelinux.cfg .I copied /srv/tftp/default.cfg into this directory both as default.cfgand as simply default. I also copied x2go-tce-cfg, memtest.cfg andlocal-boot.cfg into this directory just in case. I am now at a loss. Ihave no way of checking/altering pxelinux.0 as it is in binary or codeof some sort. I have spent hours in my free time to get this far, butin reality the end goal of logging into my linux server on a thinclient seems no closer. Any help would be appreciated.Stuart MacGregormacgregorath...@iinet.net.au,___x2go-user mailing listx2go-user@lists.x2go.orghttps://lists.x2go.org/listinfo/x2go-user___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user