similar to: drbl EFI + TFTPBOOT

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

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

On Sat, Mar 8, 2014 at 2:05 AM, Steven Shiau <steven at nchc.org.tw> wrote: > Hi Gene, > Thanks. As you mentioned, atftpd has better logging, and my files are > smaller than 92 MB, so I switched to atftpd for testing. Now I could > find that somehow after bootx64.efi is downloaded by client, the next > ldlinux.e64 has never been fetched by client: > ====================

On 2014?03?08? 05:56, Gene Cumm wrote: > In /etc/vmware/vmnet8/dhcpd/dhcpd.conf I added the following: > > host 7x { > hardware ethernet 00:0C:29:38:6B:6E; > filename "e6/bootx64.efi"; > next-server 172.21.1.1; > # option vendor-encapsulated-options >

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

> > On 2014/4/23 09:55, Gene Cumm wrote: > > The resulting config would require suffix-less module references, i.e. > > "UI menu" or "COM32 ls". > > > > Additionally, I documented the basics of my test system here: > > > > http://www.syslinux.org/archives/2014-February/021740.html > > > > Bear in mind, by "URL-like

On 2014/4/23 ?? 09:55, Gene Cumm wrote: > The resulting config would require suffix-less module references, i.e. > "UI menu" or "COM32 ls". > > Additionally, I documented the basics of my test system here: > > http://www.syslinux.org/archives/2014-February/021740.html > > Bear in mind, by "URL-like file locations", I mean that if we have >

On 2014/3/10 ?? 05:48, Gene Cumm wrote: > 1) My assumption would be that the VMware virtualized AMD 79C970A > (PCNet32 driver; vlance virtualDev) lacks proper EFI64 support. > > 2) I have 0 speed issues using your VMX. If you only have two real > cores for this 2vCPU VM, you're choking it as the host needs time to > run. If you choke it, you mess with timers. If you mess

On Fri, Mar 7, 2014 at 10:50 AM, Steven Shiau <steven at nchc.org.tw> wrote: > > On 2014?03?07? 23:05, Ady wrote: >> I understand that these remarks might seem not the main issue, but I >> tend to think that once you are successful while using only "default" >> >> values and in a minimalistic case, you could add complexity >> (different paths,

On Fri, Mar 7, 2014 at 12:34 PM, Bryan Romine <bromine1027 at gmail.com> wrote: > I'm convinced that my Syslinux install may be broken with all the hacking > around and testing I have been doing. If I were to install fresh from the > syslinux-6.03-pre7 archive, what would I need to do. I do not see any > documentation on installation other than "make installer" in

On 2014?03?08? 20:57, Gene Cumm wrote: > Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > >> > Another thing you I'd like to mentioned is, after bootx64.efi was >> > downloaded, the next download for ldlinux.e64 was about 15 secs later. >> > Is that normal? > When it's successful for me, it takes 0.2s from the beginning of >

On Thu, Mar 6, 2014 at 6:45 PM, Bryan Romine <bromine1027 at gmail.com> wrote: > Yes, I am using efi64/efi/syslinux.efi and > efi64/com32/elflink/ldlinux/ldlinux.e64. I tried binaries from 6.03-pre7 and > it gets farther along but brings up the error "Default boot device missing > or boot failed". Maybe I am not installing all of the required dependencies? > Are

On 2014?03?07? 23:05, Ady wrote: > I understand that these remarks might seem not the main issue, but I > tend to think that once you are successful while using only "default" > > values and in a minimalistic case, you could add complexity > (different paths, multiple firmwares, additional kernels, multiple > cfg files...). Ady, Thanks. I will follow your advice to

On Mar 8, 2014 8:36 AM, "Steven Shiau" <steven at nchc.org.tw> wrote: > > > On 2014?03?08? 20:57, Gene Cumm wrote: > > Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > > > >> > Another thing you I'd like to mentioned is, after bootx64.efi was > >> > downloaded, the next download for ldlinux.e64 was about 15

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 > menu. I have not been able to get it to load the menu

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

On Sun, Mar 9, 2014 at 8:09 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sat, Mar 8, 2014 at 12:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: >>> >>> vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware >>> VMXNet3? Feel free to

Gene, I found a document from IBM that explains why it didn't like Vendor-Class-Identifier option I was using "PXEClient" was causing EFI boot rooms to dummy spit, that's very useful, that combined with RTFMing the PXE specs 3.0-3.2 might solve my problem if I keep at it. http://www-01.ibm.com/support/docview.wss?uid=swg21247032 Even the PXELinux docs suggest encapsulating

Still interested in pre-compiled binaries for 6.03-pre6. But my comment about 6.02 TFTP brokenness may speak more to my lack of understanding of the TFTP protocol than to any pxelinux 6.02 code problems. It seems that when TFTP sends an OACK back to syslinux.efi, it sends it from another port than 69. So, it seems to be opening a data connection back to the TFTP client off an ephemeral port.