similar to: Debug C32 Module

> we have wrote a own C32 module, loaded with "DEFAULT mod.c32" > > But sometime the module mod.32 are not loaded & started. > How we can debug this ? > Or give some debug output. > In the main of the module there is a printf, but the text are not shown > at booting. If you are building the binaries by yourself, then nobody really knows where the problem

Hi guys, Would someone mind advising me about this, a very simple menu: ui menu.c32 menu title Boot Manager default quirky timeout 100 label quirky menu label Easy 0.2.6 kernel vmlinuz append root=/dev/sda3 rootwait rw label Help menu help help.msg File 'help.msg' is a text file, if I select it, the previous menu remains in the background, between the characters. If I hit Esc to go

Hello there I built development version of syslinux from git 6.04-pre3-3-(sometag) and I am trying to boot a slackware-current system with it. I do not use a separated partition for `/boot`. It's just `/dev/sda1` here for `/` and `/boot` is just a folder. I simply use `mbr.bin` against a DOS partition table and the first partition having the bootable flag. With this layout, the only

Hello, I'm experiencing an issue where if I use vesamenu.c32 with PXELINUX 6.03 when network booting a virtual machine hosted on VMware ESXi 6.0, it hangs (the version message is printed and then nothing - the VM has to be powered off and back on again). This happens no matter if I choose the E1000 network interface or the VMXNET3 network interface when creating the VM. The same problem

Just tested with the latest VirtualBox and that works OK, so it's definitely something specific to ESXi 6.0.0 (it worked previously under 5.x ESXi versions). Thanks, Dan Jackson (Lead ITServices Technician). -----Original Message----- From: Syslinux [mailto:syslinux-bounces at zytor.com] On Behalf Of Jackson, Dan via Syslinux Sent: 16 June 2016 09:27 To: 'syslinux at zytor.com'

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

Hello, Thanks very much for your suggestions. I have double checked that all .c32 files are from the same version of syslinux. What I don't know - I only put those .c32 files I have in there on the basis of trial and error - is what .c32 files are actually needed for menu.c32 and/or vesamenu.c32. I thought perhaps there might be a .c32 file missing that I needed to put in there (though

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

On 07/14/16 05:56, Ady Ady via Syslinux wrote: > > @Peter, Erwan, Gene, Michal, (and anyone else interested)... > > Although I haven't actually tested Erwan's patch, would it be > acceptable by you (all) if I were to send a patch to this Syslinux > Mailing List with the same code while changing the wording as I > previously suggested in a prior email? Would it be

Hi Folks , Can you please let me know if there is any fix for chain loading UEFI boot loader using chain.c32 in 6.04 release ? I am booting my system with syslinux.efi and want to chain load to windows or sex specific boot loader in the second stage . Thanks Robin

Hello, i would like create a bootdisk , that can be boot from Old BIOS, EFI32 and EFI64. But for EFI Boot there is only one directory /EFI/BOOT/ In this directory I can copy BOOTia32.EFI and BOOTx64.EFI. But the *.c32 files for EFI32 & EFI64 , I can install to this directory at the same time. Is there a way to load the *.c32 from different directory ? Or is there a other solution ?

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.

"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

Hi, I have successfully installed Debian using PXE boot and the local tftp server of Qemu. To do that I grab a copy of netboot.tar.gz for the amd64 architecture from the debian website for Buster (10.1), extracted it then recreate the symlink found: - mklink ldlinux.c32 debian-installer\amd64\boot-screens\ldlinux.c32 - mklink pxelinux.0 debian-installer\amd64\pxelinux.0 - mklink /D pxelinux.cfg

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:

Hello, does someone have test syslinux EFI64 bootloader in qemu ? we have a own c32 module. And some build of this module will hang booting. Now I will (debug / test) this in qemu. Is that possible? if so, what do I need except qemu-syste-x86-64. And how do I have to start the qemu? Thanks & regards Johann

> > As opposed to "label", > "dlabel" ... > https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbf > > SeaBIOS / GRUB2 > > ... > ... > <target dev='vdc' bus='virtio'/> > <boot order='3'/> > ... > ... > <target dev='vdd' bus='virtio'/>

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

On 04/23/2014 09:06 PM, Ady wrote: > Suggestions and patches are surely welcome. Ady, Mine is only suggestion, and for sure I will just follow what Syslinux developers decide. Thanks. Steven. -- Steven Shiau <steven _at_ stevenshiau org> Public Key Server PGP Key ID: 4096R/47CF935C Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C