similar to: Including 'detect_cpu' in libcom32.a ?

I just created something very similar for one of my own projects. I have a disk image that you can "dd" onto a hard drive or USB drive and a bash script demonstrating how it was done here: https://www.syslinux.org/archives/2019-July/026476.html You don't actually need the patch for the dual BIOS/UEFI support. The patch in the above link is just to enable the reading of config

Do note that not everyone is running a Debian based system, so "the current Debian Testing binary packages" are worthless to us. On Fri, Nov 08, 2019 at 12:42:45AM +0000, Ady Ady via Syslinux wrote: > > Any response would be welcome :-) > > > As usual, builds/versions should not be mixed, at least within the same > platform (bios/ia32/x64). > > Currently,

Hello all, We're having the following issue: when in UEFI mode, any output/errors from a lua script is invisible! This occurs even just running 'lua -v'. It runs and returns to a (visible) 'boot:' prompt, but there is simply no output visible from lua! (It does do a linefeed, but no visible text appears.) Has anyone encountered this? And/or know of a solution? For

Hello Greg, thanks a lot - I will try out your script next week. I jut went through the script - there is a line containing: bls1 include I would carefully assume that this line is only valid when patching syslinux, correct? What will happen if this is read by a non-patched syslinux? Will it cause errors or will it simply be ignored? Best regards, Erik Gregory Bartholomew wrote: > I just

I'm not sure if it is useful, but with the advent of UEFI only machines, we've run into a similar problem w/ out custom CentOS 7 USB installation keys. Basically, we create a gpt device w/ a single FAT16 partition (this would be your /boot partition for a full installation) containing an EFI/BOOT/ directory with the syslinux-efi files and a SYSLINUX/ directory with the syslinux-bios

If they are useful, then one should note where they can be found and how to extract them for anyone not using a Debian-based distro. Saying just that they are in the Debian Testing repo, doesn't mean much to a non-Debian-er... On Thu, Nov 14, 2019 at 09:50:40PM +0000, Ady Ady via Syslinux wrote: > > Do note that not everyone is running a Debian based system, > > so "the

I get a link error when trying to call malloc from libcom32. I tried to simplify the case by adding the malloc to the sample hello.c in the modules directory, but I still get the following error: ld -m elf_i386 -T ../lib/com32.ld -o hello.elf hello.o ../libutil/libutil_com.a ../lib/libcom32.a /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/32/libgcc.a ../lib/libcom32.a(malloc.o)(.text+0x13): In

I'll start off by saying that I'm very new to com32, but I'm having difficulty linking the libcom32.a library into an executable. I'm using syslinux-3.11, I copied the libcom32.a library into my directory and here's the output of my attmept: #ld com32io.o dtimenu.o syslnx.o tui.o --library-path=./ -lcom32 .//libcom32.a(entry.o)(.init+0x42): In function `_start':

Peter- Can you please clarify the license of libcom32, from the samples directory in syslinux? I am attempting to create .c32 files that are not encumbered by the GPL, but the conio.c file states that is is covered by the GPL. So far, I have resisted linking with libcom32.a, but is it really your intent to license the library code under GPL, and not something more like the LGPL?

Hi all, We're using the classic boot BIOS syslinux successfully for many years, but meanwhile it's getting harder to buy hardware the still supports this boot mode. The option for us would be syslinux EFI boot. To avoid too many changes we would like to generate an image for our different hardware parts that supports both - classic BIOS boot and (U)EFI boot. This would allow us to leave

Hi all, I have released SYSLINUX 2.12-pre1. This version has an initial version of libcom32, a small C library based on klibc for writing com32 programs in C. It is far from perfect yet, but it should be a lot easier to use than hand-coding everything. As usual, find this stuff in: ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hello, I poked a little bit to extract the list of modules dependencies in Syslinux v6 (see below). I have attached a bash script that generate a nice table from the tarball. The output can either be an ASCII table, or wiki markup, typically for the page Library_modules[1]. I am not in the wiki Editor group, so I can't put that in the wiki. anyway, here's an updated dependency tree for

On Fri, 2012-06-29 at 07:42 -0700, syslinux-bot for H. Peter Anvin wrote: > elflink: fix dependency problem in cmenu/Makefile > > Instead of adding library dependencies implicitly, make them explicit > and use --as-needed to avoid bogus DT_NEEDED entries from being > generated. This is fine, but... > diff --git a/com32/cmenu/Makefile b/com32/cmenu/Makefile > index

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

Hi there, i just build a new ipxelinux.0 with an EMBED=../../syslinux-5/core/pxelinux.0. i'm trying to load up my vesamenu.c32 menu from http:. and offcorse i want this as optimal as possible, with the least needed GET requests. OLD situation with v4: PXE ROM -> ipxelinux.0 (tftp) -> menu.php (http) -> vesamenu.c32 (http) NEW situation with v5: PXE ROM -> ipxelinux.0 (tftp)

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

Dear gentlemen, I think I'd better start another thread for this... thanks to Ady Ady and Gregory Lee Bartholomew for their responses to my early question. Just for the record, my fresh experience with PXElinux 6.x follows: syslinux.efi version 6.03 does boot to the extent that it shows a prompt, but if I provide it with a CFG file containing several labels, no matter what label I type

On Tue, Oct 27, 2015 at 10:15 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > Bruno Cornec via Syslinux said on Wed, Oct 28, 2015 at 01:45:22AM +0100: >> >> Is there a way to increase the debug level of syslinux.efi in order to >> check what it tries to do and diagnose more precisely what happens ? > > > Ok, I tried to modify mk/devel.mk to put:

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

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