Paul - there is an updated version in testing.
See Bugs 11927 and 11928 - don't use earlier versions. add yourself to the bugs so you can follow them.
* Mon Apr 11 2022 John Crisp <jcrisp@safeandsoundit.co.uk> 1.2-10.sme
- Update systemd unit files [SME: 11927]
- Migrate db from tftpd to tftp [SME: 11928]
yum --enablerepo=smetest install smeserver-tftp-server
(I'd remove any earlier versions)
Check it runs with
systemctl status tftp
It depends on this running:
systemctl status tftp.socket
Check the detials:
systemctl cat tftp.service
Logging:
journalctl -u tftp.service -b
Or
journalctl -u tftp.service
You might want to set:
tftp log verbose
and
signal-event smeserver-tftp-update
(that should work!! Check for -vv in the unit file)
Logging is limited and a lot of guesswork is required
You have to understand what PXE does, and does not do! Plenty of reading online about it.
This is quite concise.
https://www.system-rescue.org/manual/PXE_network_booting/Not that it boots the basic kernel image and initramfs via PXE and then the rest via http.
You can use a plain http ibay for that as a test. A lot of systems would require NFS (Or only allow NFS)
If you want a real bootable Linux try a small version like Slitaz. This is a config entry for I used to use for Slitaz v4 but should work for v5.
Here is your /tftpboot/pxelinux.cfg/default
DEFAULT Slitaz-5-Std
label Slitaz-5-Std
menu label SlitaZ ^5
kernel images/slitaz_5_0/bzImage
append initrd=images/slitaz_5_0/rootfs4.gz,images/slitaz_5_0/rootfs3.gz,images/slitaz_5_0/rootfs2.gz,images/slitaz_5_0/rootfs1.gz rw root=/dev/null vga=normal autologin
Get the iso:
http://distro.ibiblio.org/slitaz/iso/latest/slitaz-rolling.isoExtract the relevant files from it and put them in the right directory:
tftpboot/images/slitaz_5_0/bzImage
tftpboot/images/slitaz_5_0/rootfs4.gz
tftpboot/images/slitaz_5_0/rootfs3.gz
tftpboot/images/slitaz_5_0/rootfs2.gz
tftpboot/images/slitaz_5_0/rootfs1.gz
Just try and get ONE running - the rest will be easier.