similar to: DEFAULT versus UI

> On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > > Gene Cumm wrote: > >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > >> <syslinux at zytor.com> wrote: > >> > Hi folks, > >> > > >> > As per Ady request (thanks for the reminder), I forgot to send the patches > >> > I

Hello Syslinux Team, I have some suggestions / requests regarding global APPEND commands. These would make the behavior more consistent and more useful for practical cases. 1_ Add some functionality equivalent to "APPEND -" to the command prompt. 2_ Activate the functionality of ONERROR from [vesa]menu.c32 too. Currently, ONERROR only works from the command prompt. 3_ Add a new

Gene Cumm wrote: > On Sat, Dec 12, 2015 at 8:21 AM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > >> > Gene Cumm wrote: > >> >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > >> >> <syslinux at zytor.com> wrote: >

Good day, I was expecting this to be a FAQ but haven't been able to find an answer... how would I arrange to, normally, not be presented with either prompt or menu when booting, yet be still able to call up prompt/menu when needed? If the right answer is "set PROMPT 0, provide a DEFAULT entry and no UI entry" then that doesn't work currently, in the sense that it is then

Hi Matt, First comments about 5.00-pre10. 1_ When using "ctrl+v" in the boot prompt, there is no space character between the version and the boot mode. Additionally, the main version number is shown twice. For example, "SYSLINUX 5.00 5.00-PRE10CHS" should be: "SYSLINUX 5.00-PRE10 CHS" 2_ Boot to menu.c32, press [ESC] to go to the boot prompt. Pressing [ESC]

Hello! I've been attempting to add EFI support to a linux live distro (slax), it's built on a syslinux bootloader. I can get EFI to work using menu.c32 on syslinux 6.03; however ideally we'd like the VESA menu as well. When we use the vesamenu.c32 and libcom32.c32 from 6.03 we end up with a blank screen and the machine seems to hang. I've tried adding MENU RESOLUTION based on

Hi. I have setup virtualbox with a windows 10 that is acting as a DHCP and TFTP server. I have created folder like this: c:\tftpboot in that folder "pxelinux.0" and "ldlinux.c32" is located. another folder is created: c:\tftpboot\pxelinux.cfg In that folder "default" is located. I have another testpc that I want to startup with pxe, but I get this error:

Gene Cumm wrote:- >TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >version that you can use the "guid" or "label" options to auto-detect >its location rather than "chain.c32 hdN M". Hopefully your FS >label/GUID is unique sdb3 Boot Primary

On 06/13/2013 10:15 PM, Gene Cumm wrote: > On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello >> >> While testing PXE booting, I decided to change IPAPPEND to the new >> SYSAPPEND and does not work: nothing is appended to command line. >> >> I tested using menu.c32 and vesamenu.c32, same issue.

Hello While testing PXE booting, I decided to change IPAPPEND to the new SYSAPPEND and does not work: nothing is appended to command line. I tested using menu.c32 and vesamenu.c32, same issue. --------------------------------------------------------------------- SERIAL 0 38400 UI boot/syslinux/vesamenu.c32 LABEL arch64_nbd MENU LABEL Boot Arch Linux (x86_64) (NBD) LINUX boot/x86_64/vmlinuz

Hello, Here are some humble suggestions for 'doc/menu.txt' and 'doc/syslinux.txt'. They might be relevant for other documentation sources too. Unfortunately, I don't know how to prepare adequate patches. For 'menu.txt': _ Line 8: "located in the menu/ subdirectly." Suggestion: "located in the 'com32/cmenu' subdirectory." _ Line 10:

Gene Cumm wrote: > On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > <syslinux at zytor.com> wrote: > > Hi folks, > > > > As per Ady request (thanks for the reminder), I forgot to send the patches > > I run in Mageia. > > > > There is two of them : > > > > One is making errors in parsing modules.alias not fatal. > > >

Hello everyone, I am trying to PXE boot my Acer Aspire G3-773G laptop. It uses UEFI, so I load 64bit syslinux.efi (v6.03) and it automatically loads ldlinux.e64. All is fine. But when I want to use cmenu.c32 (with UI cmenu.c32 in the config file), the loader downloads: * cmenu.c32 * libmenu.c32 * libcom32.c32 * libutil.c32 Then syslinux reports: "unable to load cmenu.c32:

"H. Peter Anvin" <hpa at zytor.com> writes: > On 06/03/2014 02:59 AM, Ady wrote: > >> Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, >> boot: vesa.c32 >> Undef symbol FAIL: luaL_checklstring >> Failed to load COM32 file vesa.c32 >> boot: >> >> Is there a Lua-related issue? >> >> Is vesa.c32 expecting some kind of

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

works with legacy, hangs with efi. where works is: No DEFAULT or UI configuration directive found! but enter and ^v make things happen hangs is: nothing happens, no response from keyboard, have to reboot. note: config prompt.cfg prompt.cfg does not exist, but I would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp

On Thu, Dec 6, 2018 at 5:14 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > works with legacy, hangs with efi. > > > > where works is: > > No DEFAULT or UI configuration directive found! > > but enter and ^v make things happen > > > > hangs is: nothing happens, no response from keyboard, have to reboot. > > > > note:

On 8/4/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> Note, I am using syslinux from Ubuntu 16.04.2, presume that is 6.03. >> >> Regards, >> Barry > > Before investing time in replying to each different (unexpected) > behavior, I would suggest testing with *pre-built* binaries from > 6.04-pre1 downloaded from kernel.org (considering the

Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, boot: vesa.c32 Undef symbol FAIL: luaL_checklstring Failed to load COM32 file vesa.c32 boot: Is there a Lua-related issue? Is vesa.c32 expecting some kind of argument? TIA, Ady.

Hello all, How can i get High Resolution Console? I try UI vesamenu.c32 LABEL AlDimnaOS KERNEL /vmlinux-2.6.34-AlDimnaOS-0.0.0.1 APPEND rw root=/dev/sdb1 ro quiet vga=773 in grub, resolution is passes from grub to the Console. and i am thinking the same with extlinux ? -- Sincerely,