<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>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.</div><div><br></div><div>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?</div><div><br></div><div>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:</div><div><br></div><div><i>[ 16.996870] Initramfs unpacking failed : write error</i></div><div><i>[ 17.488013] mce: Unable to init MCE device (rc: -5)</i></div><div><i>[ 19.959922] Failed to execute /init (error -2)</i></div><div><i>[ 19.190964] Kernel panic - not syncing: No working init found. Try passing init =option to Kernel. See Linux Documentation/admin-guide/initrst for guidance.</i></div><div><i>[ 19.961064] CPU: 0 PID : 1 Comm: swapper/0 Not tainted 5.10.0-10-686 #1 Debian 5.10.84-1</i></div><div><i>[ 19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009</i></div><div><i>[ 19.961198] Call Trace:</i></div><div><i>[ 19.961283] dump_stack+0x54/0x68</i></div><div><i>[ 19.961355] ? rest_init+0x30/0x97</i></div><div><i>[ 19.961429] panic+0xa3/0x25b</i></div><div><i>[ 19.961495] ? rest_init+0xe0/0xe9</i></div><div><i>[ 19.961630] ret_from_fork+0x1c/0x28</i></div><div><i>[ 19.961705] Kernel Offset: disabled</i></div><div><i>[ 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. ]---</i></div><div><br></div><div>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 <a href="http://ftp.debian.ors/debian">http://ftp.debian.ors/debian</a> <i><distr-codename></i> 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.</div><div><br></div><div><br></div><div> </div><div>On Mon, 2022-01-10 at 10:01 +0300, ovt@zaokknm.ru wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><div>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.</div><div>My advice to you is to change your distribution to Debian.</div></div><div><br></div><div><br></div><div>05.01.2022, 15:38, "MacGregor Family" <macgregorathome@iinet.net.au>:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><p>Hello,<br><br>I posted an enquiry quite some time ago but it hasn't attracted<br>anyone's interest. In the meantime I have contiued trying to solve the<br>problem on my own. I moved all my dchp functions from my cheap, rubbish<br>router to my ubuntu 20.04 server. I spent some time fiddling with the<br>settings of isc-dhcp-server. I downloaded ipxe undionly.kpxe and put it<br>in my tftp server (a virual box virtual machine with bridged netwrking<br>also running a ubuntu 20.04 server) at /srv/tftp. When I boot up my<br>Termtek TK3550 Thin Client (AMD GX III LX800 CPU, 256 MB ram, Intel<br>UNDI network card PXE 2.0) undionly.kpxe is successfully booted via<br>tftp and the new bootloder finds pxelinux.0 then just locks up. Nothing<br>happens and it continues to happen indefinitely. I have attached a<br>photo of the boot screen when it locks up.<br><br>I have created a directory of the tftp server /srv/tftp/pxelinux.cfg .<br>I copied /srv/tftp/default.cfg into this directory both as default.cfg<br>and as simply default. I also copied x2go-tce-cfg, memtest.cfg and<br>local-boot.cfg into this directory just in case. I am now at a loss. I<br>have no way of checking/altering pxelinux.0 as it is in binary or code<br>of some sort. I have spent hours in my free time to get this far, but<br>in reality the end goal of logging into my linux server on a thin<br>client seems no closer. Any help would be appreciated.<br><br>Stuart MacGregor<br><a href="mailto:macgregorathome@iinet.net.au">macgregorathome@iinet.net.au</a><br></p>,<p>_______________________________________________<br>x2go-user mailing list<br><a href="mailto:x2go-user@lists.x2go.org">x2go-user@lists.x2go.org</a><br><a href="https://lists.x2go.org/listinfo/x2go-user">https://lists.x2go.org/listinfo/x2go-user</a><br></p></blockquote></blockquote></body></html>