similar to: High Resolution Console

Hello all, I am trying to replace grub with extlinux without any luck. I did remove the grub from my root Partition and boot from a LiveCD. I install syslinux and did those steps Boot Partition: mkdir -pv /mnt/sda1 mke2fs -jv /dev/hda1 mkfs -t ext3 /dev/hda1 mount /dev/hda1 /mnt/sda1 Root Partition export SDB1=/mnt/sdb1 mkdir -pv $SDB1

hello all, my vm (windows server 2008) keep crashing? 2011-09-21 15:00:45.924: 1355: info : libvirt version: 0.9.6 2011-09-21 15:00:45.924: 1355: error : virSysinfoRead:465 : internal error Failed to find path for dmidecode binary 2011-09-21 15:05:43.873: 1349: warning : qemuDomainObjTaint:1128 : Domain id=1 name='IIS' uuid=a02e41a9-9f4d-d94f-43a6-995b1ca6d37d is tainted:

Hi list, Sorry if anyone had asked this. I know syslinux use 640x480 as default resolution or use resolution be defined in menu.cfg. Does anyone know there is a way to detect best resolution? If not, is this feature planned to add? Cheers, Shuduo

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 all, I would really appreciate feedback on the graphical menu system and its infrastructure. It's not really clear to me that it's what people want; it seems to me that it makes more sense than gfxboot, for example (C rather than pseudo-Forth), but I can understand people would disagree. Anyway, the more feedback I get the easier it will be to pick a direction and a priority for

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

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

On 04-08-15 17:38, Oscar Roozen wrote: > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. I was busy adding some code to dprintf.h

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 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. --------------------------------------------------------------------- SERIAL 0 38400 UI boot/syslinux/vesamenu.c32 LABEL arch64_nbd MENU LABEL Boot Arch Linux (x86_64) (NBD) LINUX boot/x86_64/vmlinuz

works with legacy, hangs with efi. where works is: No DEFAULT or UI configuration directive found! but enter and ^v make things happen hangs is: nothing happens, no response from keyboard, have to reboot. note: config prompt.cfg prompt.cfg does not exist, but I would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp

The attached config works, but gives 2 error messages that get covered up by the GUI screen so fast I cannot read them. I think they are probably about having 'LABEL' with nothing after it. I was trying to follow the example in menu.doc but somehow I'm doing it wrong. Please consider helping me figure out how to get the same resulting GUI menu without any error messages. I am using

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

We have some x86_64 systems that have DisplayPort and USB ports for a monitor & keyboard and when I use these to PXE boot, everything works fine. However, these systems will eventually become headless and in the production process access to the console will be via serial port. Using the serial port mostly works in that once we get to the PXE boot: prompt we can type in the name of the

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

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

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

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