search for: vesamenu

...best I can. I have been experimenting with VBox and Syslinux EFI32. In EFI, the default screen resolution for [vesa]menu.c32 is not 640 x 480 (and not 800 x600). This means that while using the same cfg file, a user might probably see a different screen presentation in BIOS than in EFI. Once vesamenu.c32 is loaded, the output of executing a menu entry can't be *immediately* seen on screen; not always. I am having trouble explaining what I mean in generic terms, so here is an example. *** DEFAULT vesamenu.c32 MENU CLEAR MENU BACKGROUND #A00000FF MENU CMDLINEROW 19 MENU ENDROW 19 L...

...have 4 of the help files linked to the F1 - F4 keys. But I just had a number of emails back and forth with a user that was getting kernel panics. It eventually turned out that the user was not typing the bzImagexx kernel name with the capital I. I have found some samples of the vesamenu configuration, and was able to create png file that displays the graphic info at the bottom of the screen versus the top, but the text info isn't there, but could be added to the png file with some effort. The help files and using F? keys doesn't do anything. I'm...

On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks this > step resolved the earlier error. Next I get failed to load com32 file > vesamenu.c32 while that file exists in /tftplinux/linux-install. Is vesamenu.c32 from 5.10? -- -Gene

...would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi target/EFI/BOOT/BOOTX64.EFI + cp /usr/lib/syslinux/modules/efi64/ldlinux.e64 target/EFI/BOOT/LDLINUX.E64 + cp /usr/lib/syslinux/modules/efi64/vesamenu.c32 /usr/lib/syslinux/modules/efi64/libcom32.c32 /usr/lib/syslinux/modules/efi64/libutil.c32 target/EFI/BOOT/SYSLINUX/EFI64 + cp /usr/lib/syslinux/modules/bios/vesamenu.c32 /usr/lib/syslinux/modules/bios/libcom32.c32 /usr/lib/syslinux/modules/bios/libutil.c32 target/boot/syslinux/ + sudo extlinux...

> On Wed, Dec 3, 2014 at 1:30 PM, Geert Stappers <stappers at stappers.nl> wrote: > > H. Peter Anvin wrote: > > } Thorsten Glaser wrote: > > } } When I have an environment that uses vesamenu, for example on PXE, > > } } how do I configure it so that, for some of the menu entries, it > > } } switches back to the text mode (03h) before handing off to the next > > } } bootloader / kernel? > > } > > } depends on the image type. We should reset for an NBP thou...

...anks, 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' <syslinux at zytor.com> Subject: Re: [syslinux] PXELINUX 6.03 / vesamenu.c32 hang I've just tried 4.07 and that has the same results. I should note that I appear to be in error about things working OK with menu.c32 as opposed to vesamenu.c32 - I do indeed see the menu (which with vesamenu.c32 it does not get that far), but when I attempt to choose the Windows Depl...

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 : https://bugzilla.syslinux.org/show_bug.cgi?id=27#c2 and that doesn't change the behaviour at all. I figured it might be already working/fixed in maste...

> On Thu, 4 Dec 2014, Ady wrote: > > > Perhaps there should be a new MENU-type directive, so to force the > > screen to text mode (as opposed to leaving it in graphics mode for as > > long as it can be)? Perhaps this could also be useful when exiting a > > vesamenu to Syslinux CLI? > > Yes, please. To make this dependent *only* on the configuration of > the menu entry started is, IMHO, the only way to go. > If you want a per-label behavior, you could try adding a new menu entry: LABEL change2menu COM32 menu.c32 And replace your 'UI vesa...

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 previously when that happened, there was an error message saying so). I have tried 6.04-pre1, same result. I have tried your simplified configuration file, same result. Basically it hangs right after...

...vices 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' <syslinux at zytor.com> > Subject: Re: [syslinux] PXELINUX 6.03 / vesamenu.c32 hang > > I've just tried 4.07 and that has the same results. Thank you. > I should note that I appear to be in error about things working OK with menu.c32 as opposed to vesamenu.c32 - I do indeed see the menu (which with vesamenu.c32 it does not get that far), but when I attempt...

...com/archives/2007-June/008673.html After several hours of searching through the list, I am still convinced that his problem was never solved and is very valid. I recently moved from the old syslinux config options model (all labels in 1 default config file) to having a main menu and submenus using vesamenu.c32. The main menu points to all of the submenus and also has a label for localboot. Each submenu has tons of labels that fit the category of the submenu. The problem is that not every user wants to navigate the menu structure to find the label they want to boot, but they would rather hit escape t...

I've just tried 4.07 and that has the same results. I should note that I appear to be in error about things working OK with menu.c32 as opposed to vesamenu.c32 - I do indeed see the menu (which with vesamenu.c32 it does not get that far), but when I attempt to choose the Windows Deployment Services option, it hangs. Thanks, Dan Jackson (Lead ITServices Technician). -----Original Message----- From: Jackson, Dan Sent: 16 June 2016 09:17 To: 'sysl...

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

I'm currently building a tree-like boot menu for my network, using pxelinux and vesamenu.c32. I jump from one page to another with "kernel vesamenu.c32" and "append newmenu". However, at some points I'd like to use the classic interface, for example with a distribution install image (in order to have the exact same interface as on the CD). I tried loading pxeli...

We're currently working for project OpenElec on a syslinux menu. We would like to know if it's possible to move the menu position to the middle/bottom instead of the top... Currently we simply use the Vesamenu as it doesn't require much more functionality. I saw a post regarding the option MENU STARTROW, but that doesn't seem to work (anymore?). Any suggestions are welcome. - Martijn

Hi, UTF8 is a standard today. Nevertheless it seems to be impossible to display UTF8 characters in vesamenu.c32. Am I wrong? There is nothing about that in the docs. Are there plans to make vesamenu.c32 UTF8 capable or make syslinux capable e.g. for LC_ALL=de_DE.UTF8? Best regards, Uwe Galle

On Thu, 4 Dec 2014, Ady wrote: > Perhaps there should be a new MENU-type directive, so to force the > screen to text mode (as opposed to leaving it in graphics mode for as > long as it can be)? Perhaps this could also be useful when exiting a > vesamenu to Syslinux CLI? Yes, please. To make this dependent *only* on the configuration of the menu entry started is, IMHO, the only way to go. bye, //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228 54881-235 HRB 5168 (AG B...

H. Peter Anvin wrote: } Thorsten Glaser wrote: } } When I have an environment that uses vesamenu, for example on PXE, } } how do I configure it so that, for some of the menu entries, it } } switches back to the text mode (03h) before handing off to the next } } bootloader / kernel? } } depends on the image type. We should reset for an NBP though. } How to keep "state" during the re...

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

On Wed, Dec 3, 2014 at 1:30 PM, Geert Stappers <stappers at stappers.nl> wrote: > H. Peter Anvin wrote: > } Thorsten Glaser wrote: > } } When I have an environment that uses vesamenu, for example on PXE, > } } how do I configure it so that, for some of the menu entries, it > } } switches back to the text mode (03h) before handing off to the next > } } bootloader / kernel? > } > } depends on the image type. We should reset for an NBP though. > } > > How...