similar to: Undef symbol FAIL: luaL_checklstring in vesa.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

Ady <ady-sf at hotmail.com> writes: >> "H. Peter Anvin" <hpa at zytor.com> writes: >> >>> I didn't realize how many modules there are in Lua, and quite frankly >>> not all of them are very well named in the sense that it is clear that >>> they are Lua-related. vesa.c32 is one of those - it is one of several >>> Lua

> "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?

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:

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 argument? > luaL_checklstring should be found in liblua.c32. Are you perhaps missing the latter? I

Hi, This series targets automatic boot menu generation, but most of it is the Lua upgrade, because I got tired reading deprecated API docs. It's mostly a straightforward forward port of the earlier Syslinux specific changes to Lua 5.1, except that: * I chose the add a stub getenv() implementation to the COM32 API instead of #ifdefing out all the references in Lua, and * I kept oslib

Reinier Kleipool via Syslinux <syslinux at zytor.com> writes: > 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: symbol not found > luaL_checklstring". > This sysbol is defined in

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 >>

I am attempting to setup my server to use Lua for the dialplan (extentions.lua), but I am unable to get the asterisk configure script to find the installation of Lua on my box. I have downloaded the Lua sources from the www.lua.org site, and I have installed via the "make linux install" command. I can execute lua scripts via the command line, but asterisk configure script is unable to

I'm running pxelinux configured to use the path /bios on the tftp server for all the comboot files. The problem is dmi,syslinux,vesa etc modules are not being loaded in lua. Syslinux.version() returns not found in global index as does dmi.supported() For k,v in pairs(package.loaded) do print (k,v) end; shows that these modules that are normally loaded by lua are not loading. I got an idea

hello all: I want to install ModSecurity v2.5.4 in my system. I do the following setup to install the lua tar -xzvf lua-5.1.3.tar.gz cd lua-5.1.3/src make linux cd .. make install The ModSecurity ask me to add "LoadFile /usr/lib/liblua5.1.so" to the http.conf,but there is no liblua5.1.so in /usr/lib. I have search it and i didn't find the solution. Can any one tell me why

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

Op 20100702 om 11:21 schreef syslinux-bot for H. Peter Anvin: > > lua: Modernize the Makefile <bigsnip/> > -liblua.a: $(LIBLUA_OBJS) > +$(LIBLUA) : $(LIBLUA_OBJS) > + rm -f $@ > $(AR) cq $@ $^ > $(RANLIB) $@ FWIW: Today I also found that missing `rm -f $@` Cheers Geert Stappers

Since Syslinux 4.01-pre2, lua is the master branch. This lua.c32 moudule doesn't support much. There is a much recent lua.c32, made by Marcel Ritter's: http://syslinux.zytor.com/archives/2009-October/013383.html The last time he wrote about the state of his lua branch: ============================================================ The current state is: - VESA: - switching to vesa mode

I am a developer from the 'Frugalware Linux' distribution. I have been trying to use the syslinux lua module to support more dynamic menu generation at runtime for our distributed ISO images, as Grub2 is not very configurable for this. For example, I need raw access to the PCI bus information to configure the video output kernel boot parameters for specific hardware. Specifically,

The following are new Lua c32 modules in 6.03-pre*: cmenu.c32: cpu.c32: dhcp.c32: dmi.c32: lfs.c32: pci.c32: syslinux.c32: vesa.c32: I am wondering whether the following modules, which are _not_ new and are also included in 6.03-pre*, have _any_ relation either to the above list or to Lua: cpuid.c32: cpuidtest.c32: dmitest.c32: pcitest.c32: vesainfo.c32: TIA, Ady.

The following changes since commit 81ad566f155fac31089fde69c87059b217e7e9b6: NEWS: Update for 6.03 release (2014-10-06 09:27:44 -0700) are available in the git repository at: https://github.com/wferi/syslinux/ pub for you to fetch changes up to 68cb978ab7e692d772e4d62d3585b8f7bac43b4b: lua: simplify the function/value handling in the automenu test (2014-10-13 12:44:15 +0200)

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

> > Is this "ArchLinux" entry equivalent to "\EFI\syslinux\syslinux.efi" > > in your UEFI firmware? > > Note: UEFI firmware is supposed to use (or show) backslash "\" as path > > separator. > > You have a great point there. > I redid the "efibootmgr" installation and instead of > > efibootmgr -c -d /dev/sdd -p 1 -l

From: Matt Fleming <matt.fleming at linux.intel.com> This series includes a patch (PATCH 1/6) that I sent previously but I thought it was worth sending it again since the rest of the series depends on it, and it also gives a bit of context. These cleanups make it simpler to do the big switchover to ELF modules on the elflink branch because the libraries in $LIBS are now contained in one