similar to: menu timeout restarted with single item (4.06-pre14)

Hi everybody Attached you will find a file pxe.mnu (encoded with mime). It is PXE menu file created by 3COM MBA IMGEdit.exe tool. It is very strange since: 1) When I point DHCP bootfile to this file it loads with no problem and the menu is displayed. 2) When I point DHCP bootfile to pxelinux.0 and in pxelinux.cfg I put the command "KERNEL pxe.mnu" then system hangs. I wonder why this

Hi, I am using qemu for testing new versions of syslinux before installing on an embedded computer. Everything works fine under qemu (1.5.0), so I updated extlinux from 4.06 to 5.11-pre3 on the computer. I found that the autostart's timeout does not work. The timeout value is correct but nothing happens. It worked well with extlinux 4.06... I tried with extlinux 5.01, 5.10, 5.11-pre3 and

Another week, *another* -pre. I'm really planning on this being the last one. The shortlog is appended below. Apart from a better fix for the "disabled menu entry" bug it's only documentation updates. Testing from the last -pre's has been pretty quiet, so as soon as Ady and Matt have tested this one and confirmed that the disabled entry bug is finally gone I'll do the

syslinux.txt: syslinux binary is in "linux" directory menu.txt: menu.c32 and vesamenu.c32 are in com32/menu directory --- doc/menu.txt | 2 +- doc/syslinux.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/menu.txt b/doc/menu.txt index 620527e..8a999cd 100644 --- a/doc/menu.txt +++ b/doc/menu.txt @@ -18,7 +18,7 @@ See menu/README for more

hello, I have a problem about pxe booting. I have two isolated machines, one(server) has got dhcp and tftp servers working correctly ( I am pretty confident with this). The other machine (client) using floopy to boot with pxe-request. The problem is, the client cannot get the bootfile("/tftpboot/pxelinux.0"), it always report no boot filename found. I also found the IP address, which

We are attempting to setup an automated system to build some Linux systems. We have utilised the PXELINUX bootloader after encountering the PXE 512Kb limit with bootp. We now have another issue which you may have already run into. In the DHCP configuration we specify pxelinux.0 as the bootfile, this works reasonable well, we call the Redhat vmlinuz and initrd.img files within the

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

Hi, For some time now I have been using pxelinux to add a helpful 'administrator' boot mode to our workstations with the following 'pxelinux.cfg/default' config: ---- DEFAULT local PROMPT 0 TIMEOUT 0 TOTALTIMEOUT 1 ONTIMEOUT menu ALLOWOPTIONS 0 NOESCAPE 0 LABEL local LOCALBOOT 0 LABEL menu CONFIG /pxelinux.cfg/default-menu ---- This is great as by

Hello, Here's a small enhancement feature for menu.c32. Looking for feedback before starting any coding (not sure when I'll have time for implementation) Regards, Dany St-Amant *Problem statement* When MENU HIDDEN is used on an headless server, any noise on the serial console can interrupt the boot; it would be preferable if there only specific keys were allowed to interrupt, reducing

I just started to play with syslinux 3.11 and have some problems with the configuration. I want to implement following: wait 5 seconds till the users chooses the right label. if nothing is done for 5 seconds it should boot from next boot device specified by the BIOS. I configured syslinux like that: default menu.c32 prompt 0 timeout 50 ONTIMEOUT localboot totaltimeout 200 display boot.msg MENU

Hello, I'm reporting a bug, see attached syslinux.cfg I'm using submenu entries to emulate checkbox inputs. The idea is simple, there are submenus generated for all possible cases, and each Enter keypress loads appropriate submenu section. The logic of the menu is correct. Just syslinux has some bug. It doesn't set MENU DEFAULT properly for all submenus. If your first Enter keypress

Le 29/06/2013 12:39, Gene Cumm a ?crit : > On Fri, Jun 28, 2013 at 7:24 AM, Romain Naour <romain.naour at openwide.fr> wrote: >> Hi, >> >> I am using qemu for testing new versions of syslinux before installing on an embedded computer. >> Everything works fine under qemu (1.5.0), so I updated extlinux from 4.06 to 5.11-pre3 on the computer. >> >> I found

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

We have been using syslinux (V4.05) in our product for years without a problem. Since we encounter more and more systems that do a UEFI boot by default we want to support that too. So I've been using syslinux V6.03 to create usb sticks and harddisks to allow both bios and uefi boot which works fine. The problem I run into now is that it is not possible to create a dvd that is capable of

Well, googling has failed me. We've got a pxeboot setup, but we keep getting, in the logs, parse_option_buffer: malformed option dhcp.bootfile-name (code 67): option length exceeds option buffer length. This is CentOS 6.2 The section for those machines that can pxeboot is: group { allow booting; allow bootp; filename "pxelinux.0"; option

> We have been using syslinux (V4.05) in our product for years without a problem. > Since we encounter more and more systems that do a UEFI boot by default > we want to support that too. So I've been using syslinux V6.03 to create > usb sticks and harddisks to allow both bios and uefi boot which works fine. > > The problem I run into now is that it is not possible to create

Hello, First, could you make a tar.gz instead of a tar.xz (at least on debian)? I compiled the syslinux-4.05+dfsg I would like to ask you if I shall copy the menu.elf + menu.c32 to the concerned directory? The menu.elf is needed or it shall be renamed as menu.c32 ? Shall ldlinux.sys be too coming from same file? my simple example of menu: default menu.c32 prompt 0 MENU TITLE Sample Menu

Gene, As it happened I started working on this again just as you mailed me. It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy. The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to

On Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > Gene, > > As it happened I started working on this again just as you mailed me. I saw it in IRC. > It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no

Ady: You seem to be taking (copy$paste) parts and pieces from different resources. Luke: Nope. The configuration works fine with PXE 2.01 clients, it's the UEFI PXE 3.2 that is having issues with the dhcp requests. The gospel is the Intel PXE 3 spec I'm RTFMing now. No copy and paste, I just started with someone elses configuration file that claims to support UEFI - or at least hopes to