similar to: Fwd: Minor syslinux menu system bug report

I have a menu conf as follows: LABEL enabled, use as item LABEL disabled, use as description SEPARATOR LABEL enabled, use as item LABEL disabled, use as description In this situation, I expect the cursors to be able to select from only the two enabled lines. However, the final disabled line is also selectable. Even if I put a final separator and/or disabled label the final line of the menu

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 Sat, Jul 12, 2014 at 3:15 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/11/2014 09:39 PM, Gene Cumm wrote: >> >> With everything else from 6.03-pre18, try this binary (xzip-compressed): >> http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz > > > It works! Thanks! > > Anything else I should do/report on this hardware before I upgrade the

Hi, I was hoping you could shed some light in usage of the directive MENU HIDDENKEY in syslinux (extlinux 4.04) The docs say: MENU HIDDENKEY key[,key...] command... So, in my conf I have: MENU HIDDENKEY Esc openelec Where openelec is the label of the boot option I want to run only if Esc is pressed. But pressing Esc on boot has no effect. Default is run. So, do I misunderstand the

On Sat, Jul 12, 2014 at 3:38 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/12/2014 02:24 PM, Gene Cumm wrote: >> >> On Sat, Jul 12, 2014 at 3:15 PM, Alexander Perlis <aperlis at math.lsu.edu> >> wrote: >>> >>> On 07/11/2014 09:39 PM, Gene Cumm wrote: >>>> >>>> >>>> With everything else from

On 07/01/2014 09:55 PM, Gene Cumm wrote: > On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 ... > > Odd. 4.07 should be good but the 4.10/5.1*/6.0* revisions make sense. My bad. I tried again, and in 4.07 we do get further. We couldn't boot all the way because, it seems, using

On 07/13/2014 10:54 AM, syslinux-bot for Gene Cumm wrote: > Commit-ID: 3741886cb700e1017d70f1753f013fa10f4d9272 > Gitweb: http://www.syslinux.org/commit/3741886cb700e1017d70f1753f013fa10f4d9272 > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 13 Jul 2014 11:18:50 -0400 > Committer: Gene Cumm <gene.cumm at gmail.com> > CommitDate: Sun, 13 Jul

On 07/03/2014 06:31 AM, Gene Cumm wrote: > On Jul 2, 2014 11:13 AM, Alexander Perlis wrote: > > > Or is there a different (non-ipxe?) way we can locally boot a machine > and get it to chain to our 6.0x pxelinux server? > > Unless this is a completely isolated network, talk with your IT department. > > If there's no DHCP, make a simple server. If there's DHCP and

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

On 07/03/2014 08:44 PM, Gene Cumm wrote: > On Thu, Jul 3, 2014 at 9:13 PM, Alexander Perlis wrote: > >> I suppose we could try making an ISOLINUX CD for the local boot, which then >> uses pxechn.c32 to connect to our PXE server? > > pxechn.c32 requires a functional PXELINUX. If I understand the issue correctly, is it that pxelinux.0 does not have a network stack and

On Mon, Jun 16, 2014 at 5:57 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > 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

On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu> 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 although I'll give pre18 a try soon, some

On Jul 2, 2014 11:13 AM, "Alexander Perlis" <aperlis at math.lsu.edu> wrote: > Or is there a different (non-ipxe?) way we can locally boot a machine and get it to chain to our 6.0x pxelinux server? Unless this is a completely isolated network, talk with your IT department. If there's no DHCP, make a simple server. If there's DHCP and no boot info, add a PXE server

On Thu, Jul 3, 2014 at 9:13 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > I suppose we could try making an ISOLINUX CD for the local boot, which then > uses pxechn.c32 to connect to our PXE server? pxechn.c32 requires a functional PXELINUX. -- -Gene

On Sun, Jul 13, 2014 at 10:26 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/13/2014 10:54 AM, syslinux-bot for Gene Cumm wrote: >> Commit-ID: 3741886cb700e1017d70f1753f013fa10f4d9272 >> Gitweb: http://www.syslinux.org/commit/3741886cb700e1017d70f1753f013fa10f4d9272 >> Author: Gene Cumm <gene.cumm at gmail.com> >> AuthorDate: Sun, 13 Jul 2014

On Mon, Jun 13, 2016 at 7:41 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: >> > Is syslinux.efi supposed to be able to handle HTTP URLs? >> >> If the underlying firmware can. Try just specifying an HTTP URL in the >> config or on the command line instead of the path-prefix option. > > > Doesn't work. Apparently the Dell UEFI PXE firmware

On Tue, Jun 14, 2016 at 4:44 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: >>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. >> >> >> There's a lot of variation. Do you have a shell option >> in your boot selections? > > > None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 >

On 07/12/2014 02:24 PM, Gene Cumm wrote: > On Sat, Jul 12, 2014 at 3:15 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: >> On 07/11/2014 09:39 PM, Gene Cumm wrote: >>> >>> With everything else from 6.03-pre18, try this binary (xzip-compressed): >>> http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz >> >> It works! Thanks! > > Oh

On Mon, Jun 16, 2014 at 10:23 AM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > When chainloading one pxelinux from another (e.g., chainloading from say > pxelinux 4.07 to pxelinux 6.02), can one pass parameters or somehow control > the root directory and/or server IP address? > > Here's the need: we have a loaded-up PXE server working great under 4.07, > and

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