syslinux PXE: Forced all TFTP paths to be absolute.
syslinux always interprets TFTP paths as relative to the location of the *.c32 modules, regardless whether a path starts with a slash. Without the :: that I added to all of these paths, syslinux cannot find these files and the boot fails. It searches for them in /syslinux//%INSTALL_DIR%/boot/x86_64/vmlinuz-linux, etc.
Merge request reports
Activity
- Resolved by Eric Toombs
Please document your change in
CHANGELOG.rstperCONTRIBUTING.rst. - Last reply by Eric Toombs
changed milestone to %v62
added scopebug label
- Resolved by Eric Toombs
I can't find any reference to PXELINUX not supporting absolute paths for TFTP. Could it instead be an issue with the used TFTP server?
- Last reply by Eric Toombs
assigned to @nl6720
- Resolved by nl6720
I think it is also necessary to say somewhere inside this project how to use the PXE support. Specifically, how to configure the DHCP server. The dnsmasq settings I had to use were
dhcp-boot=/syslinux/lpxelinux.0,<tftpd-hostname>,<tftpd.ip.ad.dress> dhcp-option-force=209,syslinux.cfgWhere should this be documented?
- Last reply by nl6720
added 1 commit
- c4878869 - syslinux PXE: Changed all TFTP paths to relative paths.
- Resolved by Eric Toombs
If you can test and confirm that it works with dnsmasq as the TFTP server, then I'll merge this.
- Last reply by Eric Toombs
added 1 commit
- 8c8a59cd - syslinux PXE: Forced all TFTP paths to be absolute
added 1 commit
- fbb60344 - syslinux PXE: Forced all TFTP paths to be absolute
added 1 commit
- 0c6ecb6b - syslinux PXE: Forced all TFTP paths to be absolute
mentioned in commit 914382c6
- Resolved by nl6720
Splendid! Thanks for your work! I'll update the wiki as soon as the next archiso is built and released. April 1st, presumably.
Edited by Eric Toombs - Last reply by nl6720
