similar to: vesamenu partly broken in 3.70?

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

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

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

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

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

Hello, vesamenu.c32 from syslinux-3.75.tar.bz2 is broken in my tests with: - qemu 0.9.1 -cdrom iso_image - qemu 0.9.1 -cdrom iso_image -std-vga - virtualbox 2.2.0 (Sun version) It blocks right after showing the copyright notice. I've since compiled the following versions in my machine, running Fedora 10: - syslinux-3.63 - syslinux-3.72 - syslinux-3.73 - syslinux-3.75-143-g080bf56 I did a

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

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.

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

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

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?

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

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

> 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

I was able to solve the problem with the following configuration: label custom1 MENU custom1 kernel pxechain.com append ::custom1/pxelinux.0 label custom2 MENU custom2 kernel pxechain.com append ::custom2/pxelinux.0 configdir1/pxelinux.cfg/default configdir2/pxelinux.cfg/default Then I dropped the custom pxelinux.0 files in their respective directories, confgdir1 and configdir2. On Tue, Nov

Hi group, currently I try do make my own PXE bootscreen. There is one thing i dont like. When I use vesamenu.c32 there is always a table on the screen (I mean the border lines are visible) Is there any command i have to add to the default file that this border lines are unvisible ? Thanks in advance

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello. I'm trying to setup an multiboot USB, mainly to install Debian using netinst images. I've mounted one of iso image and copied to a directory in USB (made with syslinux 6.03) and copied too the kernel and initrd for hd install. I've setup a directory to start the USB and, well it starts, but when I jump (using CONFIG) to the

hi list sorry my english is not perfect :( im using pxeboot with vesamenu.c32 in default file i load a backgroundpic (*.jpg) but the vesamenu border overlaps pieces of my background picture ^^ my question is an all coders from syslinux can you make a MENU command like topmargin MENU LABEL xxxx MENU WITH xx MENU MARGIN xx (from left) .... MENU TOPMARGIN xx (from top) <- new to

Hello. vesamenu.c32 can currently display a PNG image along the menu. But when the kernel is started, the image is lost. LILO supports bmp-retain option, where the bitmap graphic is retained when control is passed to the loaded kernel image; i.e., the screen is not blanked to alphanumeric mode before starting the kernel. Is it possible for vesamenu.c32 (or syslinux in general) to support