search for: vesa

I just got a new monitor for my desktop system (the old one died after *many* years of service). The new monitor is a high res 16:9 monitor, but the VESA video driver insists on using 1024x768 (which was the resolution of the *old* monitor). It does seem to detect higher, 16:9 resolutions but it is not using them. I *think* I need to set some low-level video mode thing, but it has been a long time since I have had to do that that I have totall...

...buffer driver running already. We also only attempt to use 24bpp if the alternative would be pseudocolor, but note that since xserver 1.20 24bpp will not work at all. If you'd like to fix that case, please note that it is filed as issue #4: https://gitlab.freedesktop.org/xorg/driver/xf86-video-vesa/-/issues/4 We also notice several cases of running on emulated GPUs, in which case the shadow framebuffer is disabled by default to improve performance by reducing the number of copies. All users are recommended to upgrade, ideally to a better video card and/or driver. Full changelog: Adam Jack...

...LoadModule: "drm" (II) Loading /usr/X11R6/lib64/modules/linux/libdrm.a (II) Module drm: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) LoadModule: "vesa" (II) Loading /usr/X11R6/lib64/modules/drivers/vesa_drv.o (II) Module vesa: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (II) LoadModule: "mouse" (...

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.

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

Nothing terribly exciting, but enough bug fixes to justify a release. Adam Jackson (4): Don't build old probe method on sufficiently new servers Fall back to VGA if the palette API isn't supported Use VBEFreeVBEInfo not free vesa 2.4.0 Emil Velikov (1): autogen.sh: use quoted string variables Ian Lepore (1): Honor Option "NoDDC" correctly Matthew Green (1): When debugging, print the VGAbase as well. Mihail Konev (1): autogen: add default patch prefix Peter Hutterer (1): autogen.s...

Minor update to fix PanelID support. The minimum xserver version is now 1.6; if you haven't updated your xserver in the last six years, now would be a good time. Adam Jackson (3): configure: Drop PanelID test Don't include deprecated xf86PciInfo.h vesa 2.3.4 Alan Coopersmith (1): Raise required version of xorg-server to >= 1.6 git tag: xf86-video-vesa-2.3.4 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-vesa-2.3.4.tar.bz2 MD5: a893c37c589f7a31cea929a5d896a0e2 xf86-video-vesa-2.3.4.tar.bz2 SHA1: 88e74ccc5c11fdb60539...

...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: Mon, 7 Jan 2013 20:29:16 +0000 > > vesa: Correct screencpy() prototype > > The 'src' argument should actually be const char * because the BIOS > code performs pointer arithmetic on it. > > Signed-off-by: Matt Fleming <matt.fleming at intel.com> > Not really. The objects are uint32_t and so the prototy...

"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 argument? > > luaL_checklstring should be found in liblua.c32. Are you perhaps &...

...es. Fix boolean inversion in VBE screen clear. Remove some useless module loading cruft. Prefer a more modern depth/bpp selection. Add semi-reasonable mode validation. Clean up memory model checking, and properly refuse unsupported models. Update copyright. vesa 1.99.1 Daniel Drake (1): Bug #11090: xf86-video-vesa COPYING file Ian Romanick (4): Add conditional support for pci-rework branch. Correct '#ifdef' to '#ifndef'. Oops. Use XSERVER_LIBPCIACCESS to autodetect libpciaccess usage. Use pci_device_map_rang...

Bug #2150: Don't call VBEGetSetDACPaletteFormat when in direct colour or YUV modes. (David Sterratt) CVS tag: xf86-video-vesa-1_2_1 http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-1.2.1.tar.gz: MD5: 1bf4a36af8422245bcdd99c2aa2f8f4f xf86-video-vesa-1.2.1.tar.gz SHA1: 92323676608ff9ec357c8d94f14133794943b542 xf86-video-vesa-1.2.1.tar.gz http://xorg.freedesktop.org/releases/individual/driver/xf86-v...

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

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

> "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 argument? > > > > luaL_checklstring shou...

...94badd02799a ro single where AFAIK "ro single" gives me recovery-mode and ROOT permission; where the single VT-mode allows me to set some env. & call `startx`. I must have root-permission, since this Deb7 crap doesn't know 'sudo'. The final goal will be using "video=vesa:ywrap,mtrr vga=788" in isolinux; since these parameters are the only known way to get the important app to use proper <font sizes>. When the good fonts show [only acheivable by booting DVD-rescue] `cat /proc/cmdline` shows:--- 'video=vesa:ywrap,mtrr vga=788 initrd=/install.386/g...

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

...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 /etc/modprobe.d/blacklist.conf at startup, - when using one of the VESA modes at startup after a while screen goes blank and I get a warning in syslog e.g: Apr 2 18:58:56 darkstar kernel: fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver, - no problem when using a VGA mode (text only), this disregarding which X driver I use afterwards (I...

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 argument? > luaL_checklstring should be found in liblua.c32. Are you perhaps missing the latter? I didn'...

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

Well, I got my user back to being able to use his system, but I've still got one issue: it's running on the VESA driver - there is *no* Catalyst build for this monitor, for CentOS 7. From a lot of googling, nothing's been done since the summer of '14 (lspci reports it as a FirePro V3900). Any thoughts, or pointers, as to if/how I can get X - he's running KDE - to see the full width of the monitor...