[X2Go-User] pxeboot in Debian Buster (not booting, which pxelinux.0?)

[Stefan Baur]

Am 28.02.20 um 17:27 schrieb Luciano Andino:
> Hello, I'm x2go user since some years ago. Now trying to install a new
> PXEBOOT server. What I did:
> 

[snip]
>      Build is done:
> './live-build-x2go-20200227200355-netboot-amd64-openbox-magic-pixel-workaround-buster'
>      641641 bloques
>      [2020-02-27 20:20:07] lb clean
>      P: Cleaning chroot
>      root at pxeserver:/usr/local/x2gobuild#

Looks good.

> 3)
>      * http server installed. Both x2go-tce.sessions &
> x2go-tce-filesystem.squashfs are accesible through niginx.
>      root at pxeserver:/usr/local/x2gobuild# cp
> live-build-x2go-20200227200355-netboot-amd64-openbox-magic-pixel-workaround-buster/x2go-tce-filesystem.squashfs
> /var/www/html/x2go-tce/

So what's the full URL for each of them?


>      * dhcp server installed and working.
> 
> 4) Netbooting
>      4.1) atftp server working
>      4.2) Copied x2go-tce-vmlinuz and x2go-tce-initrd.img to
> /srv/tftp/x2go-tce
>      4.3) created in tftproot "pxelinux.cfg/x2go-tce" (file reference to
> x2go-tce/vmlinuz and x2go-tce/initrd.img instead, changed that)
> 
>      4.4) looking for a pxelinux.0 file:
> 
>      4.4.1) root at pxeserver
> :/usr/local/x2gobuild/live-build-x2go-20200227200355-netboot-amd64-openbox-magic-pixel-workaround-buster#
>      cp live-image-amd64.netboot.tar /srv/tftp/
>      root at pxeserver:/usr/local/x2gobuild/live-build-x2go-20200227200355-netboot-amd64-openbox-magic-pixel-workaround-buster#
> tar xvf live-image-amd64.netboot.tar
> 
>      #    copied tftpboot directory to tftproot directory
>      root at pxeserver:/srv/tftp# ls
>      advanced.cfg  install.cfg  libcom32.c32  libmenu.c32  live menu.cfg
>   pxelinux.cfg  stdmenu.cfg x2go-tce
>      hdt.c32       ldlinux.c32  libgpl.c32 libutil.c32  live.cfg pxelinux.0
>   splash.png  vesamenu.c32
> 
>      ---> Result, system does not boot (ethernet driver fails)

The question is: what's inside the *.cfg files there?
You're not following the instructions from the Wiki if you're using the 
tar file.  I mean, it's okay to do that if you don't have an existing 
PXE setup that this might interfere with *and you know what you are 
doing*, but for a first-time setup, sticking to the instructions really 
is the better idea.

"Our" instructions say you need to copy the kernel, initrd and squashfs 
files that are created by our build script (they all start with 
x2go-tce-*), and manually edit the .cfg file, see
<https://wiki.x2go.org/doku.php/doc:howto:tce#setting_up_your_own_netbootable_x2go-tce_environment>
Section "Adding the configuration files to your Boot Server", especially 
the third bullet point there, and the example *you need to edit* below.

>      4.4.2) Using old x2gothinclient_preptftpboot script
>      ---> System boots but login screen offers to connect to an X server
> somewhere in the Internet (seems is not using sessions file)

That sounds like you're mixing NFS and Live-Boot.  Don't do that.
NFS doesn't understand Live-Boot's boot parameters, so you can't tell it 
where to find its config file via a boot parameter.

-Stefan


-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243