similar to: lua not working on syslinux-6.03-pre18

Displaying 20 results from an estimated 1000 matches similar to: "lua not working on syslinux-6.03-pre18"

2014 Jul 01
1
lua not working on syslinux-6.03-pre18
Alex Bligh <alex at alex.org.uk> writes: > Firstly, this line: > > syslinux.run_kernel_image("mboot.c32", bootstr, 0, 0) > > no longer works at all as is. I think it was broken (probably > intentionally) by this commit: > > commit 4bbaf68cbf6c9a4c850f71b19bfb9604b9327efb > Author: Ferenc W?gner <wferi at niif.hu> > Date: Sun Oct 13 22:30:16
2014 Jun 30
0
lua not working on syslinux-6.03-pre18
On 30/06/2014 16:30, Alex Bligh wrote: > I've upgraded from syslinux-4.05 to syslinux-6.03-pre18 (pre11 was the same) > and am having some issues getting lua.c32 to work. I'm using lpxelinux.0 > if that's relevant. > > My boot file and the contents of default.lua are below. As you can see they > are fantastically simple. Essentially I'm just using lua to put the
2016 Jun 16
2
[PATCH] Fix recognition of keeppxe option
> On Wed, Jun 15, 2016 at 1:02 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> > > >> >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > >> >> > there is no convenient way in new_linux_kernel() to
2010 Oct 29
0
A question about XVP Xen API error.
Hi: I got problem of the combination of XVP and Xen Cloud Platform. I have compiled and installed the XVP-1.7.0 on a PC (installed Enterprise Redhat 5.4). I also installed Xen Cloud Platform on a Intel Server. Now I want connect the XVP to Xen Cloud Platform. I started the XVP by run the command on PC: #xvp but system gave me the message below "/usr/lib/libxml2.so.2:no
2016 Jun 16
0
[PATCH] Fix recognition of keeppxe option
On Thu, Jun 16, 2016 at 06:20:31PM +0300, Ady via Syslinux wrote: > the main idea: if the LINUX directive would be capable of using / > parsing "keeppxe", then it might make sense to have the same capability > in linux.c32 (in addition to mboot.c32 and chain.c32). AFAICT, the following modules lead to the syslinux_boot_linux code path: ldlinux.c32 lua.c32 (for boot_linux and
2014 Jul 09
2
isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?)
[This email is either empty or too large to be displayed at this time]
2014 Jun 29
0
SYSLINUX 6.03-pre18 crashes on Mellanox/Intel card with iPXE stack
On Jun 29, 2014 9:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Peter, > > I approached you before on this issue that I?m having with the SYSLINUX 6.03-pre18 when booting with iPXE option ROM. > > The issue was reproduced on different OEMs, and also on 2 different cards (Mellanox and Intel), with latest and 2 years old iPXE code. > > Just
2014 Jul 09
0
isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?)
On Jul 9, 2014 6:11 AM, "Michael D. Setzer II" <mikes at kuentos.guam.net> wrote: > > On 9 Jul 2014 at 6:01, Gene Cumm wrote: > > Date sent: Wed, 9 Jul 2014 06:01:22 -0400 > Subject: Re: [syslinux] isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?) > From: Gene Cumm <gene.cumm at gmail.com> > To: "Michael D. Setzer,
2014 Jul 09
0
isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?)
On Jul 9, 2014 5:15 AM, "Michael D. Setzer II" <mikes at kuentos.guam.net> wrote: > Subject: isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?) Correct, it's in the bios/ architecture binary directory. 6.00 introduced efi32/ and efi64/ making the distinction of the binaries necessary. --Gene
2014 Jul 09
0
isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?)
> > But these is no isohybrid in the efi directories? So, why wasn't the isohybrid.c > also moved to bios/utils? The source code is still in the same place; the binaries are generated into respective subdirectories. I would suggest reading: http://www.syslinux.org/wiki/index.php/Library_modules http://www.syslinux.org/wiki/index.php/Common_Problems#Multi-Arch and in the
2014 Jul 09
4
isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?)
On 9 Jul 2014 at 6:01, Gene Cumm wrote: Date sent: Wed, 9 Jul 2014 06:01:22 -0400 Subject: Re: [syslinux] isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?) From: Gene Cumm <gene.cumm at gmail.com> To: "Michael D. Setzer, II" <mikes at kuentos.guam.net> Copies to: Syslinux at zytor.com > > On Jul 9, 2014 5:15 AM, "Michael D. Setzer II" >
2010 Aug 23
1
XCP, XCCS, xe, and XVP, random thoughts
Well, that was a lot of alphabet soup acronyms :). I''ve just been thinking about the claim in a prior post that using the xe cli with XCP abnormally increases the XCP server load. The only way I could see this happening is to be running xe from the servers command line. I use xe extensively to do the grunt work of XCCS (Xen Cloud Control System). I don''t see the loading
2012 Jul 02
0
Regarding XVP nat traversal
I deployed the xvp appliance(latest) for xcp 1.1. User who are behind the nat router are unable to get the consoles. they are getting network error: connection timed out. is xvp is not nat aware? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
2019 Mar 12
2
syslinux-6.03 failed to boot ESXI 6.7
Hello, list, I'm buiding syslinux6.3 with ESXI6.7, but it says, * failed to load COM32 File http://172.16.234.112/images/esxi67/mboot.c32* Here is my config: ------------------ label esxi menu label ESXI-6.7 ^Installer kernel http://172.16.234.112/images/esxi67/mboot.c32 append -c http://172.16.234.112/images/esxi67/boot.cfg -------------------- Seeing from http access log,
2015 Oct 10
3
[PATCH] Extend Multiboot1 with support for ELF64 file format
This patch is just a (shameless) copy from bug #28 [1]. The original patch has been sitting there for a couple of years now, and it was based on Syslinux v 4.05. The patch I am posting here is just a re-base on v.6.03. Whichever inadequate formatting (tabs, trailing spaces...), or any kind of correction that was required for the original patch to be accepted, is probably still required now.
2009 Jul 21
2
mboot.c32, NUMA and tgz
Hi all, I'm attempting to PXE boot ESXi, which uses the syslinux mboot.c32 module. The mboot.c32 included with ESXi seems to be an older version that runs into an "out of memory loading.." problem halfway through, even though the box has 8GB memory. This may be related to NUMA, since it works fine on an older box but not the newer blade. I saw that some non-contiguous memory issues
2010 Apr 04
1
[PATCH] mboot: set boot device
Set the boot device based on the derivative information. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/com32/mboot/mboot.c b/com32/mboot/mboot.c index d008da0..526d10a 100644 --- a/com32/mboot/mboot.c +++ b/com32/mboot/mboot.c @@ -224,6 +224,14 @@ int main(int argc, char *argv[]) mboot_apm(); mboot_syslinux_info(); + /* Set boot device info */ + const
2010 Mar 21
6
[PATCH] mboot: set boot loader name
Set a pointer to syslinux_version()->version_string in mbinfo. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/com32/mboot/mboot.c b/com32/mboot/mboot.c index 8425e06..76ef7a0 100644 --- a/com32/mboot/mboot.c +++ b/com32/mboot/mboot.c @@ -222,6 +222,13 @@ int main(int argc, char *argv[]) /* Add auxilliary information */ mboot_make_memmap(); mboot_apm();
2019 Mar 13
1
Fwd: syslinux-6.03 failed to boot ESXI 6.7
---------- Forwarded message --------- From: Adan Calderon <adancalderon at gmail.com> Date: Wed, Mar 13, 2019 at 9:13 AM Subject: Re: [syslinux] syslinux-6.03 failed to boot ESXI 6.7 To: luckydog xf <luckydogxf at gmail.com> I can share some working examples for a USB Thumb drive and PXE servers using chain loading, but it will take me some time. If you are interested in my
2014 Dec 05
8
vesamenu back to text before booting
On Fri, 5 Dec 2014, Gene Cumm wrote: > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. It can then use disc access (not PXE), or you can pass it the ?real? kernel, but also e.g. configuration files, as Multiboot