search for: spikewhitetx

...at niif.hu> > To: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> > Subject: Re: [syslinux] Syslinux 6.03-pre7: EFI64 broken (Gene Cumm) > Message-ID: <87a9cusddh.fsf at lant.ki.iif.hu> > Content-Type: text/plain; charset=us-ascii > > Spike White <spikewhitetx at gmail.com> writes: > > > Where did you find the precompiled binaries for syslinux 6.03-pre7? > > https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.03/ > -- > Regards, > Feri. > > ------------------------------ > > Date: Thu, 13 Mar 2014 12:24:2...

>Date: Sun, 21 Sep 2014 22:19:12 -0400 >From: Gene Cumm <gene.cumm at gmail.com> >To: Spike White <spikewhitetx at gmail.com> >Cc: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> >Subject: Re: [syslinux] UEFI PXE / split config / TFTP attempted to > DHCP server, not TFTP server >Message-ID: > <CAD0RxembHwQ5VMbnNgmgbfUgzgdhnnXNCgzFWb5+BHLNTqez2g at mail...

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).

All, (This may be a Gene question, see http://www.syslinux.org/wiki/index.php/Development/Testing). I'd like to find a virtualization env to test and demo the new UEFI-based PXE boot in pxelinux. I've tried Virtualbox (BIOS-based PXE boot only). And I've tried VMWare workstation 20 (ditto). I know VMWare ESXi will now do UEFI PXE boot, I've seen it as work. But for home or

All, Is syslinux 6.03 able to UEFI boot the RHEL7.0 Linux kernel? I'm trying & failing to do this. I haven't UEFI-booted RHEL7.0 kernel via syslinux before. (But I have UEFI pxelinux booted Fedora 20, which is approximately RHEL7.0.) I remember HPA mentioned that older Linux kernels required "UEFI boot assist", something that GRUB2 offers but syslinux does not. And

On Fri, Oct 24, 2014 at 7:04 PM, Spike White <spikewhitetx at gmail.com> wrote: > All, > > Is syslinux 6.03 able to UEFI boot the RHEL7.0 Linux kernel? I'm trying & > failing > to do this. > > I haven't UEFI-booted RHEL7.0 kernel via syslinux before. (But I have UEFI > pxelinux > booted Fedora 20, which is approxi...

...;m looking at cabling a newer test server to that specific switch port that's port mirrrored. 3. Will definitely talk to vendor about 2nd style of split. That may be it! Spike >Date: Sun, 21 Sep 2014 13:54:38 -0400 >From: Gene Cumm <gene.cumm at gmail.com> >To: Spike White <spikewhitetx at gmail.com> >Cc: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> >Subject: Re: [syslinux] UEFI PXE / split config / TFTP attempted to > DHCP server, not TFTP server >Message-ID: > <CAD0Rxekir+chmCSsGEqSvDvb=bp=39zFP1_b9DdJ3hky7auROA at mail...

All, I was excited to hear about EFI boot support in pxelinux >= 6.00. So I tried it. Not working. I've tried 6.02 (from source), 6.02 (from RPM), early 6.03 (from RPM) and even pulled/compiled latest source from git. 6.0.3-pre7. No love. My boot client can boot/image fine in legacy PXE mode. My dhcpd.conf looks like this: # In initial DHCP DISCOVER packet, PXE client sets option

There are no pre-compiled binaries (official or otherwise) on kernel.org. I assume what is meant is https://www.kernel.org/pub/linux/utils/boot/syslinux/ At least, that is where the "downloads" page of syslinux.org directs you. Under there are the various source tarballs (tar.gz format, tar.bz2 format). Also a directory called RPMS/. But that kernel.org RPMS/ directory is devoid of

All, I have a question on how to deal with a quirk of the Intel Boot Agent. Both for PXE boots and for EFI boots. I've noticed this IBA quirk for years. According to the "DHCP options" RFC, variable length DHCP options are not necessarily null-terminated. Here's the details: >From DHCP Options and BOOTP Vendor Extensions (http://tools.ietf.org/html/rfc2132#section-2)

...hat. Based on that, it's natural for pxelinux's TFTP code to send the ACK back to this high port that sent it the OACK packet. The TFTP load of ldlinux.e64 by syslinux.efi is still failing, but not for the naive reason I surmised. Spike On Wed, Mar 12, 2014 at 11:52 PM, Spike White <spikewhitetx at gmail.com>wrote: > Gene, > > Where did you find the precompiled binaries for syslinux 6.03-pre7? > > Actually, I'm interested in the pre-compiled binaries for syslinux > 6.03-pre6. > > I went out to kernel.org, but the latest they have is 6.02. Which > appears...

H Peter, I notice the Intel Boot Agent (in the BOOT ROM) takes a different approach. When TFTP loading the initial syslinux.efi. It receives the OACK with both options set -- tsize (of 145744) and blksize (of 1408). Apparently it has challenges parsing this "two option" OACK packet. But it remembers the tsize of 145744. So it issues another read request, this time requesting only a

On Tue, Mar 18, 2014 at 1:02 AM, Spike White <spikewhitetx at gmail.com> wrote: > I have a question on how to deal with a quirk of the Intel Boot Agent. > Both for PXE boots and for EFI boots. > > I've noticed this IBA quirk for years. According to the "DHCP options" > RFC, variable length DHCP options are not necessarily...

...n. :-) But I know I work for a hardware vendor and I have *zero* pull with any internal firmware team. Spike > Date: Tue, 18 Mar 2014 12:02:54 -0700 > From: "H. Peter Anvin" <hpa at zytor.com> > To: Jeffrey Hutzelman <jhutz at cmu.edu>, Spike White > <spikewhitetx at gmail.com> > Cc: syslinux at zytor.com > Subject: Re: [syslinux] Best way to deal with an idiosyncracy of Intel > Boot Agent (IBA)... > Message-ID: <5328985E.4020808 at zytor.com> > Content-Type: text/plain; charset=UTF-8 > > On 03/17/2014 10:51 PM, Jeffrey...

On May 23, 2014 4:45 PM, "Spike White" <spikewhitetx at gmail.com> wrote: > > All, > > (This may be a Gene question, see > http://www.syslinux.org/wiki/index.php/Development/Testing). > > I'd like to find a virtualization env to test and demo the new UEFI-based > PXE boot in pxelinux. > > I've tried Virtualbox...

On May 23, 2014 5:27 PM, "Gene Cumm" <gene.cumm at gmail.com> wrote: > > On May 23, 2014 4:45 PM, "Spike White" <spikewhitetx at gmail.com> wrote: > > > > All, > > > > (This may be a Gene question, see > > http://www.syslinux.org/wiki/index.php/Development/Testing). > > > > I'd like to find a virtualization env to test and demo the new UEFI-based > > PXE boot in pxeli...

Raphael, Except for the : instead of the , this looks like the grub hard disk nomenclature that's been around for a thousand years. Certainly since early GRUB1. Example: (hd0,0)/grub/splash.xpm.gz Why did you chose : instead of grub's , ? I'm guessing (like grub) that disks & partitions are 0-based? (Were the original grub authors European?) Spike #Date: Wed, 4 Jun 2014

On Fri, Aug 29, 2014 at 8:01 PM, Spike White <spikewhitetx at gmail.com> wrote: > But chain-loading into WinPE would be useful too. > In order to use "wimboot", I have to use ./efi64/com32/modules/pxechn.c32 > to chain-load into ipxe? As so: pxechn.c32 contains BIOS-only code and is not going to work in any EFI environment. >...

On Mon, Oct 6, 2014 at 3:17 PM, Spike White <spikewhitetx at gmail.com> wrote: > Ady, > > This sounds interesting. I know PXE and related DHCP options > somewhat well. But I don't recognize this. > > Typically, you add PXE-related options to your DHCP server. > Either your main DHCP server, or a proxy DHCP server you stand up....

Gene and co, Now my pxelinux efi 64 boot is properly loading syslinux.efi (via TFTP) It then issues a TFTP file request for efi.x64/pxelinux.cfg/ldlinux.e64. (All my efi x64 content is under efi.x64/pxelinux.cfg). However, I see that it fails to properly negotiate the TFTP options with my TFTP server. so it never transfers ldlinux.e64 over. In its file request packet, it asks for these TFTP