similar to: On the whole gfxmenu topic...

H. Peter Anvin hpa at zytor.com Thu Jun 3 00:09:30 PDT 2004 Previous message: [syslinux] gfxboot for PXElinux Next message: [syslinux] chainload cdrom Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] I've been thinking about the whole gfxmenu thing, and I'm rather interested in

Hi, I'm toying with the SMP/i386 ACPI suspend/resume patches in -9. Thanks so much for this! I've noticed though that the video backlight stays off after resume. A common problem on -9, so I set hw.acpi.reset_video=1. That restores the backlight. However, the video mode isn't restored. I have my console set to VGA_80x60 and the resume seems to set it up "wrong". I get half

Greetings, Ever since the nouveau driver arrived in the Fedora distribution, I have not been able to use (or boot) my system without booting in run level 3 and loading nVidia's proprietary drivers first. With the shipped drivers in Fedora 10 and 11, regardless of how I start X, I get the animated cursor first, then random data spews across the screen and I lose the keyboard (but mouse still

--oP8mQFO4PT Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit GNU a2ps is a fairly versatile text-to-anything processor. It is useful for typsetting source code from a wide variety of programming languages. As R (ie S) wasn't supported yet, I quickly cobbled a style sheet for the S language together. Stylesheets are

Hi, (This is a recend, as the original post was refused by the CentOS moderators due to the size of the X-log file) I''ve just installed the CentOS 4.0 RC1 for x86_64 -set on my new Nforce4-based system with a PCIe GF6600-card. When installing, the screen becomes garbled as the system enters X mode, but installing with ''linux text'' works, until the system reboots and

This release rolls up a few minor bug fixes since 2.4.0. We now refuse to run on machines with UEFI firmware (on Linux only, patches welcome for other OSes) since it won't work in the general case and you probably have a kernel framebuffer 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

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

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

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

On 06/12/2017 01:34 PM, Michael S. Tsirkin wrote: > On Mon, Jun 12, 2017 at 09:42:36AM -0700, Dave Hansen wrote: >> On 06/12/2017 09:28 AM, Michael S. Tsirkin wrote: >>> >>>> The hypervisor is going to throw away the contents of these pages, >>>> right? >>> It should be careful and only throw away contents that was there before >>>

On 06/12/2017 01:34 PM, Michael S. Tsirkin wrote: > On Mon, Jun 12, 2017 at 09:42:36AM -0700, Dave Hansen wrote: >> On 06/12/2017 09:28 AM, Michael S. Tsirkin wrote: >>> >>>> The hypervisor is going to throw away the contents of these pages, >>>> right? >>> It should be careful and only throw away contents that was there before >>>

Aaron Plattner (1): Don't disable FB access when it's already disabled. Adam Jackson (9): Remove all trace of mfb Bug #10004: Fix palette initialization in 8bpp modes. 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

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

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Tags: squeeze When the monitor is being restored from power saving mode via DPMS, X will lock up/restart. This only occurs when running Xen hypervisor. Running just 2.6.32-5 -xen-amd64 doesn't produce this effect. Note that both 2.6.32-5-xen-amd64 and 2.6.32-5-xen-amd64 with Xen 4.0.1 are running with nopat (to workaround

I''m having problems booting Dom0 on an unbranded server. Server is running SuSE 9.3 x86_64 and has been working fine for a couple of years as a standard boot pc. I installed the 2.0.5c version of Xen which is part of the SuSE repository. I cannot boot into Xen though, booting Dom0 stops after: NET: Registered protocol family 16 I know from a normal boot that the next part is PCI

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

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

"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

Hi there. Application is System Shock 2. Old game that uses DX6. It runs very slow in Wine on my hardware, however other native 3D applications runs just fine as well as some other windows apps via Wine (DeusEx). Here is what i get on console when running System Shock 2(It also freezies computer almost every time when it tries to switch to initialise 3D engine, it was hard to run it and exit