similar to: VESA tests

On Tue, 25 Jun, at 01:52:00PM, Helmut Hullen wrote: > Thanks - now it crashes later ... What crash are you seeing? > I don't have the ia64 files which are needed for a complete binary. But > maybe that's only my special problem. You shouldn't need ia64 files to build ia32 and x86-64 versions of gnu-efi or Syslinux. -- Matt Fleming, Intel Open Source Technology Center

"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

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.

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

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

Hi! Recently I've been working with the rest of the X.Org board to try to get X.org access to VESA memberships so that contributors that don't have an employer who is able/willing to join VESA can potentially get access to the various benefits of a VESA membership, such as access to DisplayPort specifications. Since I need to gather a list of interested X.org members, I'd like to know

On 01/07/2013 12:51 PM, syslinux-bot for Matt Fleming wrote: > Commit-ID: 15a67011987c341814533ac4d8e23c9a72dc7605 > Gitweb: http://www.syslinux.org/commit/15a67011987c341814533ac4d8e23c9a72dc7605 > Author: Matt Fleming <matt.fleming at intel.com> > AuthorDate: Mon, 7 Jan 2013 14:42:16 +0000 > Committer: Matt Fleming <matt.fleming at intel.com> > CommitDate:

The Vesa driver works fine with CentOS 4.4. I have an NVidia 6200 video adapter. I go to Applications | System Settings | Display | Hardware tab and find my video adapter in the list and set it. The dialog tells me I have to log out for it to take effect, so I duly do that. I then getting a message from a non-graphics screen saying that the attempt to switch to the video adapter failed. When

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:

On 04-08-15 04:57, Gene Cumm wrote: >> I see. From an EFI point of view you have 4 NICs > I've still seen firmwares that allow me to disable those NIC ports > individually, though it was buried inside another menu. I did find a menu where I could adjust a lot of parameters per port, but I could not find a way to disable individual ports. By the way, I'm booting from the

Hi all, new to this list ;) I have a Lenovo Thinkpad T61. lspci|grep VGA says: 01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1) I have Slacware64-13.0 and Slackware64-current installed. Nouveau is modularized in all my kernels for -current. A problem arise even if I don't want to use nouveau under X: unless nouveau be blacklisted in

I have noticed anything using ANSI escape sequences to color text does not work if syslinux is in VESA mode. It only works if the \1#, \2#, or \3# are used. This means that libmenu which relies on csprint fails to render colors in VESA mode. I noticed the default color table has a complete table generated at runtime for all VGA color combinations, which csprint also does but from VGA attributes on

Jan, List: Is there any way we can compile a kernel to include the VESA Video Modes for 1440x900 resolution so that we can pass grub VGA=867 for 1440x900. This will all me to work in runlevel 3 without the screen resolution being stretched from 1024x768 to 1440x900. The stretch causes everything to be distorted. The necessary VESA modes and numbers are: 1440x900 (dec;

Hi I want to play Duke Nukem 3d, but I need a Vesa driver, but i can't find anyone who want to work. Is there somebody who know something about this problem?????? I have: Windows 2000 Creative Labs RIVA TNT

Does Syslinux (and pxelinux, and isolinux, etc) support setting video modes?

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'm working on a com32 module in which I need to get some file size. The only way I found was to include the "lib/sys/file.h" header file and get the i.length field from the file_info structure (once a file descriptor is open). I understand that this structure is internal to the Com32 file I/O implementation and should not be accessed from com32 modules. So is there a

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

I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I installed another linux system in other partitions of the same drive (a 64 bit system), updated syslinux.cfg, setup the new system as default, and the new entry appears in the menu. Problem is: it doesn't boot. On timeout, it starts counting down again, and that's it. No error message whatsoever. Selecting the old system

Is there any chance that nouveau will be able to support VESA Adaptive Sync before Nvidia adds it to their proprietary drivers? Or is this effectively impossible without their cooperation? I've looked, but haven't managed to find any previous discussion on this topic.