similar to: 5.00pre13 DISPLAY

Hi, As of syslinux-3.70, vesamenu.c32 seems to be broken. But here's the kicker: it's only broken when booting from USB, not from CD! What happens is that the colours are not set like I've set in the cfg and only one entry shows up. On my laptop that entry contains some really messed up symbols but on my stationary computer it's just empty, so it seems we're dealing with some

Hello, I was wondering if anyone had any ideas and perhaps solutions around an error i've been experiencing when using vesamenu.c32 (and the other non-vesa menu too). I have tried three different versions (the latest three) of pxelinux and the other files. The problem exists in all of them. My setup is pretty simple, filename defined in dhcpd, boot up from pxe, starts requesting configs, and

Hello I'm using PXELinux with vesamenu.c32 to load a custom knoppix image I made and to allow access to the WDS menu. The problem is that the PXElinux loads the menu automatically (unlike WDS which asks the user to press F12 before loading the menu) and I want it to load only if the user presses F12 in 5 seconds. So I tried using the hidden function of the menu with the timeout option

I have a handful of machines with older S3 Virge video onboard. They do not show the vesa menu and instead appear to revert to the older menu.c32. Vesamenu.c32 works fine with every other machine I've tried. I thought this video chipset was Vesa compliant... When I run the included vesainfo.c32 many different video modes are returned. Perhaps there's a readme I've overlooked

Hi Matt, First comments about 5.00-pre10. 1_ When using "ctrl+v" in the boot prompt, there is no space character between the version and the boot mode. Additionally, the main version number is shown twice. For example, "SYSLINUX 5.00 5.00-PRE10CHS" should be: "SYSLINUX 5.00-PRE10 CHS" 2_ Boot to menu.c32, press [ESC] to go to the boot prompt. Pressing [ESC]

I am attempting to setup a test gpxe(linux.0) http site, to test among other things the recent dynamic option 252 solution. In the process of investigation I stumbled across http://www.etherboot.org/wiki/appnotes/authmenus which indicates the gpxe can launch vesamenu.c32 directly. Various other pages on etherboot's site indicate menu.c32/vesamenu.c32 can be used independently as well.

On Wed, Dec 20, 2017 at 10:37 PM, Locane <locane at gmail.com> wrote: > Have you tried a different monitor? Has that monitor ever shown you a boot > loader menu? It might be that it just doesn't support the low-level > resolutions Grub is trying to use. I can't say I've ever seen a monitor that didn't interpolate the very low output sizes. With that, have you

Hi, I'm trying to a boot a Samsung NC20 netbook (VIA Nano CPU, VX800 chipset) via pxelinux, using the files from the netboot.tar.gz Debian installer. The last file tftp loads is vesamenu.c32, after that the notebook just reboots. I can see no error message, and no menuscreen. I also haven't used pxelinux before, so I even don't know what I am supposed to see :-) Any idea what is

Hello everyone I'm new to using menu.c32 and vesamenu.c32. I have used the original method of using pxelinux menus. I've read the wiki page and it speaks of being able to create submenus by making one of my menu options reference to (vesa)menu.c32 as the kernel and append the config file. I'm not sure I'm doing it correctly it was a little over simplified. Any help would be

I'm integrating DBAN (http://dban.sourceforge.net/) into our PXE boot menu system (using vesamenu.c32) but it just hangs when I'm using vesamenu.c32 and confusingly when I revert our menu system to using vesa.c32 it works ok. I've stripped out any extraneous configuration but it still seems to have the same problem. When I use this in pxelinux.cfg it boots into DBAN ok: default

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am having trouble with one Dell system and pxelinux: The keyboard does not properly work. The computer boots, I press F12 to select the boot device, then I select the network card. Up to that point the keyboard works fine. Then pxelinux is booted, and I use menu.c32 to display a menu (or vesamenu.c32 - same result). Now the keyboard does not

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been using the standard isolinux.cfg file for some time with great success. Have it currently display a file at the beginning with a little .lss graphic file, and some basic info then with the image names and info. Also have 4 of the help files linked to the F1 - F4 keys. But I just had a number of emails back

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

Hello SYSLINUX folks, thanks for all your hard work over the years! I'm working on a fairly complex deployment services project, and one of the aspects of it is to make it possible to federate deployment services across our university. Supporting existing deployment services is a priority, so I am presently trying to integrate an existing PXELINUX install, part of a FOG windows imaging

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

This is 100% functionally equivalent to 3.54-pre1, with only a few minor documentation changes. Changes in 3.54: * Add "menu separator", "menu indent", "menu disabled" (see README.menu). * vesamenu: fix handing of VESA modes with noncontiguous memory buffers. In particular, Qemu/KVM sets up such a mode when Cirrus

On 06/13/2013 10:15 PM, Gene Cumm wrote: > On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello >> >> While testing PXE booting, I decided to change IPAPPEND to the new >> SYSAPPEND and does not work: nothing is appended to command line. >> >> I tested using menu.c32 and vesamenu.c32, same issue.

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 all, I have pushed out a SYSLINUX 3.30-pre1. The main difference versus earlier versions is that this version contains a *preview* of a VESA graphical menu system (vesamenu.c32); it's used the same way as menu.c32, with the addition of a few more commands (which can also be used in menu.c32 in this new version): MENU BACKGROUND file.png ... loads a background image in PNG format.