similar to: Problem with cascading configurations

Am 04.09.2019 um 22:18 schrieb Ady Ady via Syslinux: >> I am trying to setup a PXE server for two Debian releases (stretch and >> buster) using their respective network boot images (netboot.tar.gz), >> which I extracted into subdirectories of the TFTP server's root directory: >> >> ??? ??? debian >> ??? ??? ??? buster >> ??? ??? ??? ???

> I am trying to setup a PXE server for two Debian releases (stretch and > buster) using their respective network boot images (netboot.tar.gz), > which I extracted into subdirectories of the TFTP server's root directory: > > ??? ??? debian > ??? ??? ??? buster > ??? ??? ??? ??? debian-installer > ??? ??? ??? ??? ldlinux.c32 -> >

> On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> I have a patch that I think may help your situation of syslinux.efi >> being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if >> any of you are using an EFI ia32 platform). >> >> The basics are that we try to enable UseDefaultAddress as it helps >>

On 06/16/2014 10:41 AM, Gene Cumm wrote: > [...] Initially I wrote pxechn.c32 to allow further > modifications of the DHCP data [...] Awesome! In fact, this might allow us to install an automatic 'http' prefix on all subsequent requests, to avoid slow tftp --- or is that a bad idea, and/or is there a way to default all transfers to http without using pxechn and without prefixing

On Wed, Oct 7, 2015 at 6:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> -----Original Message----- >> From: Gene Cumm [mailto:gene.cumm at gmail.com] >> Sent: Wednesday, October 07, 2015 4:43 PM >> To: For discussion of Syslinux and tftp-hpa; Geert Stappers >> Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32 >> >> On Wed, Oct

On Oct 11, 2015 1:26 AM, "Michael Glasgow" <glasgow at beer.net> wrote: > > Gene Cumm wrote: > > >> My test x86-64 binaries: > > >> > > >> https://sites.google.com/site/genecsyslinux/sl604p0g17-x64.tgz?attredirects=0&d=1 > > > > On Fri, Oct 2, 2015 at 4:46 PM, Derrick M <derrick.martinez at gmail.com> wrote: > >

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 >>

Hi, I'm trying to boot 64bit version of syslinux.efi through network. But booting is freezes with following message: Getting cached packets My IP is X.X.X.X the last file that was requested through tftp is syslinux.efi. I'm using precompiled binary from official syslinux-6.02.tar.gz. Here is the dump in ASCII - http://brom.in/dumps/syslinux-20131220.txt Any help is appreciated.

Folks, I've just released the first prelease for the 5.10 series. The intention is to leave 5.02-pre3 where it is and move to 5.10-pre1. The only difference between 5.02-pre3 and 5.10-pre1 is the merge of the lwip branch (and a single commit to fixup the -DDEBUG=2 build), which warranted a bump in the version minor number. See the shortlog below for details of the differences between

Hi I have a problem with our pxelinux server, the server works for month without any problems. We use syslinux-3.51 version on an FC2 with in.tftp. Today I want to install a new server, but it fails after loading the kernel and booting stopped with this message ide-floppy driver 0.99.newide usbcore: registered new driver libusual usbcore: registered new driver hiddev usbcore: registered

hello list, I am trying to setup a PXE boot server. Below are the details of the server: OS : Fedora Core 5 32-bit DHCP : dhcp 4.1 TFTP : tftp-hpa-5.0 Number of NIC : 2 eth0 : IP : 192.168.100.17, Subnet : 255.255.255.0, Gateway : 192.168.100.1 eth1 : IP : 192.168.1.1, Subnet : 255.255.255.0, Gateway : 192.168.1.1 Client: OS : None, fresh machine Number of NIC : 2 Intel Gigabit eth0 of server

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

On 7/2/2015 3:42 AM, Gene Cumm wrote: > This has me thinking your build system has a negative interaction. > There should be at least 2 lines of output prior to loading > ldlinux.e64. gcc less than 4.7 is one problem for the EFI binaries. This could be my problem. I'm using gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC). I will attempt from a new version of gcc and report.

Hi all, I'm trying to convers some Cisco SSCP phones to the SIP formware. The phone boots, I see it tries to fetch a bunch of files on my TFTP: Jun 17 09:37:45 firewall dnsmasq-dhcp[21202]: DHCPACK(eth2) 192.168.10.103 6c:50:4d:da:f0:67 SEP6C504DDAF067 Jun 17 09:38:10 firewall in.tftpd[22666]: RRQ from 192.168.10.103 filename CTLSEP6C504DDAF067.tlv Jun 17 09:38:10 firewall in.tftpd[22666]:

Hi, I am trying to boot the PXEclient via pxeserver and I am getting an error "file not found", following are me setup in the /tftpboot: /tftpboot: initrd.img linuz pxelinux.0 /tftpboot/pxelinux.cfg default (lower case) in the default file: # This is the default pxelinux config file. LABEL test KERNEL vmlinuz APPEND

On 06/16/2014 05:14 PM, Gene Cumm wrote: > This sounds like you're using gpxelinux.0 4.07 which as I stated will > introduce issues. Instead of using gpxelinux.0 4.07, try pxelinux.0 > 4.07 then do your chainload to lpxelinux.0 6.02. If this doesn't > solve it, try 6.03-pre14. When I DHCP boot to lpxelinux.0 6.02, and then pxechn.c32 back to lpxelinux.0 6.02 with the http

I've begun tinkering with syslinux v3 and have uncovered an anomoly with the DISPLAY file when called by pxelinux.0. If I have: DISPLAY boot.msg With an "^Xsplash.lss\n" in the file boot.msg (exactly: 18 73 70 6C 61 73 68 2E 6C 73 73 0A) file, it will fail to load the rle image. And produce some goofy results in the tftpd log: Jun 5 06:27:06 pxe in.tftpd[24649]: RRQ from

I'm setting up UEFI booting and got to the point of having the system talk to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and then continuously request the secondary image file (ldlinux.e64). I'm wondering if I'm missing something or if someone can point me in the right direction of trouble shooting this. The tftp root has all the files to boot a BIOS type

Background, Client - realtek rtl8111c tftpd version is 5.0 options on use -l -v Client: PXE-EX32 TFTP Open Timeout Server: Jun 12 10:48:38 damar in.tftpd[30132]: RRQ from 192.168.1.107 filename gpxelinux.0 Jun 12 10:48:48 damar in.tftpd[30133]: RRQ from 192.168.1.107 filename gpxelinux.0 Jun 12 10:49:24 damar in.tftpd[30134]: RRQ from 192.168.1.107 filename gpxelinux.0 Jun 12 10:50:36 damar

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???