search for: tftp_directori

On Mon, Sep 07, 2015 at 07:46:14AM -0500, John via Syslinux wrote: > At 05:13 AM 9/6/2015, Geert Stappers via Syslinux wrote: > > > >I do understand that your network is not 192.168.0.0 but 192.168.1.0. > >I don't understand what information is in _twice_ stating 192.168.1.9. > > /etc/default/tftpd-hpa > TFTP_USERNAME = "tftp" > TFTP_DIRECTORY =

Answers below. At 05:13 AM 9/6/2015, Geert Stappers via Syslinux wrote: >On Sat, Sep 05, 2015 at 09:55:45AM -0500, John via Syslinux wrote: > > At 03:21 PM 9/2/2015, Geert Stappers via Syslinux wrote: > > > > Still having trouble: > > (-: Welcome to real life :-) > > > > > cd /tmp > >Please confirm that it is done at the notyetOpenWRT device at

Hi, I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a PXE client (no physical machines available). This is a UEFI VM, and as per instructions I've read I have disabled secure boot on this VM for the installation of Linux. I am using the latest tftp-hpa package with the following config: # /etc/default/tftpd-hpa TFTP_USERNAME="tftp"

On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux <syslinux at zytor.com> wrote: > Hi, > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a PXE client (no physical machines available). This is a UEFI VM, and as per instructions I've read I have disabled secure boot on this VM for the installation of Linux. I am using the latest tftp-hpa package with

On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux > <syslinux at zytor.com> wrote: > > Hi, > > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a > > PXE client (no physical machines available). This is a UEFI VM, and > > as per instructions I've read

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

On 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the