similar to: Syslinux Text menu not redrawing/resetting the screen

On Fri, Jul 8, 2016 at 11:46 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hi, >> >> I have been using syslinux on my portable disk with success on many >> types of machines (both bios boot and EFI boot) >> >> I however hit a small issue recently >> >> If I use menu.c32, on some UEFI systems (HP) the menu does not appear

> Hi, > > I have been using syslinux on my portable disk with success on many > types of machines (both bios boot and EFI boot) > > I however hit a small issue recently > > If I use menu.c32, on some UEFI systems (HP) the menu does not appear > after the vendor splash screen. The system however goes ahead and > after the timeout configured in the menu system

On 05-08-15 04:17, Ady via Syslinux wrote: >> Now... why is vesamenu.c32 crashing like it does now? Why is the version >> I tried without Gene's latest patches crashing before even beginning to >> load the first stage: ldlinux.e64? > I think you were "hinted" about this before. About what? Did I miss something obvious? I now know why it did not load

On 8/5/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Since you are using only 2 menu entries, would you consider the > possibility of using the msg file(s) and the boot prompt, while > avoiding the use of (vesa)menu.c32 for this particular project? If you > do, there is room for improvements. > > Thanks for the info. Yes, I previously did not have a menu, for

> If I may... If I were to say something like "Syslinux doesn't boot", I > would mean that I cannot even get to a simple Syslinux's "boot:" > prompt. In other words, I would mean that _Syslinux_ (in one of its > variants / family members) is failing to boot. Whether the problem is > in Syslinux itself or in some other area (HW, FW, user error, >

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

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

> Hello everyone, > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > Since I have to use ZENworks tftp on the windows server I have only one TFTP-root directory not 2 different tftp-root directories like on a standard windows > deployment server. ZENworks itself uses for

On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > First, I'm confused. In the prior "whole" setup (the one you generated > after my 15 steps, plus one workaround), was/is the basic boot menu at > least "working" when you used the workaround for the buggy PATH > directive when booting in UEFI mode? I mean: > >

On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <atle at team-holm.net> wrote: >> Under EFI/BOOT are the following files: >> BOOTIA32.EFI (from efi32/efi/syslinux.efi) >> BOOTX64.EFI (from efi64/efi/syslinux.efi) >> ldlinux.sys (copied from root of partition) >> lua.c32 >>

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:

Greetings Syslinux forum, I used this link; https://askubuntu.com/questions/1090891/grub-menu-colors and I followed it's tutorial for implementing the grub theme and was able to delete the menu border by creating a customized grub theme for UEFI boot (grub.cfg)! Do you know if the "syslinux.cfg"(legacy boot grub) can have it's border removed, like do you know if

> > Hello everyone, > > > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > > > Since I have to use ZENworks tftp on the windows server I have only one TFTP-root directory not 2 different tftp-root directories like on a standard windows > > deployment

Under EFI/BOOT are the following files: BOOTIA32.EFI (from efi32/efi/syslinux.efi) BOOTX64.EFI (from efi64/efi/syslinux.efi) ldlinux.sys (copied from root of partition) lua.c32 mboot.c32 menu.c32 syslinux.cfg vesamenu.c32 KS.CFG (vmware specific) BOOT.CFG (vmware specific) autoselect.lua These files are also all under the root of the partition (except BOOTIA32.EFI and BOOTX64.EFI) and work fine

On 04-08-15 17:38, Oscar Roozen wrote: > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. I was busy adding some code to dprintf.h

On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > Here are some comments and questions for you. > Thanks. I've have my scripts to a better state, including installing/using qemu to uefi and legacy boot the usb stick for testing. It mostly works for me, but the "wget a tarball of binaries" step isn't going to sit well with

On Wed, Dec 5, 2018 at 2:21 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > After some discussion/debugging behind the scenes, we are back on > track, with updated Debian packages. > > > 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted > in "target" (or "$target", or some similar notation), and the version

Gene, First off, great documentation on http://www.syslinux.org/wiki/index.php/PXELINUX-Multi-Arch You clearly lay out the various techniques. Just last week, I presented a pxelinux talk to our local Linux meet-up group. (I've given this talk before.) http://2014.texaslinuxfest.org/content/creating-legacy-efi-pxe-server-using-pxelinux.html Apparently, I'm using the "distinct

I want to eufi boot this image: http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz there is a bug against it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913523 I'd like to fix the resulting usb stick for my use, and also fix it in a way that can be used to fix the upstream bug. I'm trying to follow the guids

I'm currently building a tree-like boot menu for my network, using pxelinux and vesamenu.c32. I jump from one page to another with "kernel vesamenu.c32" and "append newmenu". However, at some points I'd like to use the classic interface, for example with a distribution install image (in order to have the exact same interface as on the CD). I tried loading pxelinux.0