Displaying 5 results from an estimated 5 matches for "tftps".
Did you mean:
tftp
2014 Mar 09
2
pxelinux.0 not fully booting in EFI 64 mode...not requesting ldlinux.e64 via TFTP...
...0\377 !
(where
# \377 is the FF).
#
#option bootfile-name "efi.x64/pxelinux.cfg/pxelinux.0";
} else {
filename "UNKNOWN_VCI";
option bootfile-name "UNKNOWN_VCI";
}
in legacy PXE mode, wireshark confirms it successfully TFTPs
bios/pxelinux.cfg/pxelinux.0, followed by (in order, all from
bios/pxelinux.cfg/ dir):
ldlinux.c32
<tries other config files>
pxelinux.cfg/default
vesamenu.c32 (referenced by pxelinux.cfg/default)
libcom32.c32
libutil.c32
In EFI PXE mode, wireshark confirms it TFTPs...
2018 Jan 09
1
pxelinux failing to boot kernel
...All 3 machines use
the same motherboard with onboard intel nic. After the upgrade, I made the
necessary changes to the pxelinux.cfg file to add the new kernel. Now only
2 of the 3 machines boot. The other machine will not boot using the new
kernel, only the old one. When I select the new kernel, it tftps the kernel
and initrd (I see two "Loading..." lines printed to the screen, also
verified in the tftpd logs). Then it just hangs, and doesn't print a single
kernel message. All the motherboards have the latest BIOS and have the
Intel Boot Agent that they shipped with (doesn't appea...
2014 Mar 09
0
pxelinux.0 not fully booting in EFI 64 mode...not requesting ldlinux.e64 via TFTP...
...0\377 !
(where
? ? ? ? # \377 is the FF).
? ? ? ? #
? ? ? ? #option bootfile-name "efi.x64/pxelinux.cfg/pxelinux.0";
? ? } else {
? ? ? filename "UNKNOWN_VCI";
? ? ? option bootfile-name "UNKNOWN_VCI";
? ? }
in legacy PXE mode, wireshark confirms it? successfully TFTPs
bios/pxelinux.cfg/pxelinux.0, followed by (in order, all from
bios/pxelinux.cfg/ dir):
? ? ldlinux.c32
? ? <tries other config files>
? ? pxelinux.cfg/default
? ? vesamenu.c32? (referenced by pxelinux.cfg/default)
? ? libcom32.c32
? ? libutil.c32
In EFI PXE mode, wireshark confirms it TFTPs...
2018 Jan 09
0
pxelinux failing to boot kernel
...All 3 machines use
the same motherboard with onboard intel nic. After the upgrade, I made the
necessary changes to the pxelinux.cfg file to add the new kernel. Now only
2 of the 3 machines boot. The other machine will not boot using the new
kernel, only the old one. When I select the new kernel, it tftps the kernel
and initrd (I see two "Loading..." lines printed to the screen, also
verified in the tftpd logs). Then it just hangs, and doesn't print a single
kernel message. All the motherboards have the latest BIOS and have the
Intel Boot Agent that they shipped with (doesn't appea...
2012 Apr 17
1
tftpd-hpa: the tftpdir is ignored if --secure isn't used
If I omit --secure from the tftpd-hpa command line, I then need to e.g.
`tftp -c get /var/lib/tftpboot/vmlinuz` instead of plain /vmlinuz, even
though I pass /var/lib/tftpboot as the tftp dir in the tftpd-hpa command
line.
That essentially means that I'm exporting my whole /, which is clearly
something I don't want to do. I basically want tftpd-hpa to serve files
from /var/lib/tftpboot