similar to: pxelinux HTTP transport UEFI vmlinuz

On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > Hi, > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > kernel http://host.lan/netboot/vmlinuz > > means vmlinuz should be transported over HTTP? For non-EFI systems, this has meant use HTTP services if available (ie, iPXE/gPXE or lwIP as in

Op 2014-07-23 om 17:57 schreef Gene Cumm: > On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > > Hi, > > > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > > > kernel http://host.lan/netboot/vmlinuz > > > > means vmlinuz should be transported over HTTP? > > For non-EFI

I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some advice on how to isolate and troubleshoot this. (I can't try pre18 at the moment, but did try 4.07 and 5.10 and saw similar behavior, also with pxelinux.0, so although I'll give pre18 a try soon, some isolation/troubleshooting advice will be a good education no matter what.) To get to our PXE-launched tools from

On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 06:18 schreef upen: > > On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers wrote: > > > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > > > The tcpdump[1] shows strang HTTP

On Sat, Jun 8, 2013 at 1:44 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 12:20 schreef upen: > > On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> > wrote: > > > Op 2013-06-07 om 06:18 schreef upen: > > > > [ ... dhcp server configuration ... ] > > > > Everything has been always like this on

Op 2014-07-01 om 22:55 schreef Gene Cumm: > On Jul 1, 2014 10:37 PM, "Alexander Perlis" wrote: > > > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some > > advice on how to isolate and troubleshoot this. (I can't try pre18 > > at the moment, but did try 4.07 and 5.10 and saw similar behavior, > > also with pxelinux.0, so

On Sun, 22 Jun, at 06:15:50PM, Andrew Rae wrote: > > Matt - I'd love to try it - but I'm not so good at fixing compiling > issues. right now I get stuck at being unable to 'make' the efi32 or > efi64 components due to an error: Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release button yesterday and -pre18 contains my change. It would be good to

Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel Boot Agent 1.3.81 (2.1 build 089). It gets network and launches lpxelinux.0, I see the PXELINUX banner line, but there it hangs. I tried both 6.03-pre18 and 5.10, same hanging behavior. If I instead use pxelinux.0 or gpxelinux.0, either 6.03-pre18 or 5.10 or 4.07, there are no problems. The problem seems isolated to

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD

> > From: Matt Fleming [matt at console-pimps.org] > > Sent: 25 June 2014 07:39 > > To: Andrew Rae > > Cc: Gene Cumm; syslinux at zytor.com > > Subject: Re: [syslinux] testing out 6.03 network booting... > > > > Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release > > button yesterday and -pre18 contains my change. It would be

On 07/11/2014 10:17 AM, Alexander Perlis wrote: > > Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after that > there is only ARP traffic: a "gratuitous" ARP announcement by the > client, and then a string of ARP requests and replies in which the > client is asking for the MAC of the PXE server, about every 3 seconds, > for about 2 minutes, after which I

Hello, On 23.07.2014 15:07, Ady wrote: >> Is there something I can test or help to diagnose? > > What about 6.03-pre18 (or newer)? > http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ 6.03-pre18 is still slow: > 16:06:07.494125 IP dell.phahn.dev.49232 > xen12.phahn.dev.57501: UDP, length 4 > 16:06:07.494250 IP xen12.phahn.dev.57501 >

Hi syslinux experts, So, I have a pxe boot tree that looks something like this: /menu.cfg /linux /ubuntu /amd64 /meerkat (contains a mirror of the netboot ubuntu image) If I set the following in the appropriate stanza of my dhcpd.conf (for isc dhcpd v3), I can boot the ubuntu installer: filename "linux/ubuntu/amd64/meerkat/pxelinux.0"; next-server <tftp_server_ip>; I would

On Thu, Jul 24, 2014 at 4:56 AM, Philipp Hahn <hahn at univention.de> wrote: > Hello, > > On 23.07.2014 22:46, Alexander Perlis wrote: >> On Wed, 23 Jul 2014, Philipp Hahn wrote: >>> [...] >>> I tried lpxelinux.0, but it fails to resolve the gateway >>> address via ARP: >>> 17:25:51.399119 ARP, Request who-has 10.200.17.1 tell >>>

On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/10/2014 04:07 PM, Alexander Perlis wrote: >> Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel >> Boot Agent 1.3.81 (2.1 build 089). It gets network and launches >> lpxelinux.0, I see the PXELINUX banner line, but there it hangs. >> >> I tried both 6.03-pre18

On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> wrote: > Hello, > > On 24.07.2014 13:52, Gene Cumm wrote: >> On Thu, Jul 24, 2014 at 4:56 AM, Philipp Hahn <hahn at univention.de> wrote: >>> PS: <http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz> did not work. >> >> As expected. You have a different OUI (the first 3

On Fri, Jul 11, 2014 at 5:49 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/11/2014 04:31 PM, H. Peter Anvin wrote: >> >> On 07/11/2014 10:17 AM, Alexander Perlis wrote: >>> >>> >>> Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after that >>> there is only ARP traffic: a "gratuitous" ARP announcement by

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

I am trying to set a uniform PXE environment to load multiple distros. RHEL 5.1 and 4.7 SUSE 10.2 and 11 Solaris 10 X86 Window Multiple server versions.... - Why? Because I am in hell. What I want is to have an upper level pxelinux.0 call the default menu directories that come with the releases. Is there a way to call pxelinux.0 and point it at a different pxelinux.cfg directory?

Hi, I have just joined the list. I am the original creator of Puppy Linux, now letting other guys take the reins, and I am working on a fork of Puppy called Quirky Linux, where I try various experimental ideas. Up until now, in Puppy and all offshoots, we have used syslinux 4.05 or older. Over the last few days I have been testing 6.03 (using the binary DEBs from Ubuntu 14.10 Utopic Unicorn),