Re: vesa driver reports many modes, but only allows a few

2010-03-04 Thread Daniel Stone
On Thu, Mar 04, 2010 at 07:52:02AM -0600, Pat Kane wrote: > Ross Boylan wrote: >> Program received signal SIGSEGV, Segmentation fault. >> 0x in ?? () >> (gdb) where >> #0 0x in ?? () >> #1 0x0051a72a in DoConfigure () >> at ../../

Re: vesa driver reports many modes, but only allows a few

2010-03-04 Thread Pat Kane
Here is an untest, not even compiled, patch to try: diff --git a/hw/xfree86/common/xf86Configure.c b/hw/xfree86/common/xf86Configure.c index bce5aae..a8d8ef9 100644 --- a/hw/xfree86/common/xf86Configure.c +++ b/hw/xfree86/common/xf86Configure.c @@ -828,7 +828,9 @@ DoConfigure(void) Configu

Re: vesa driver reports many modes, but only allows a few

2010-03-04 Thread Pat Kane
Ross Boylan wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x in ?? () > (gdb) where > #0 0x in ?? () > #1 0x0051a72a in DoConfigure () > at ../../../../hw/xfree86/common/xf86Configure.c:832 The traceback says that som

Re: vesa driver reports many modes, but only allows a few

2010-03-03 Thread Ross Boylan
On Wed, 2010-03-03 at 15:41 -0600, Pat Kane wrote: > Could you run the configure under gdb to see if you get a better trace back? > > $gdb Xorg > :r -configure > > could be some xemu hw emulated hw weirdness... > I also loaded some debug symbols. [tcsetpgrp failed in terminal_inferio

Re: vesa driver reports many modes, but only allows a few

2010-03-02 Thread Ross Boylan
On Tue, 2010-03-02 at 05:34 -0600, Pat Kane wrote: > On Mon, Mar 1, 2010 at 2:35 PM, Ross Boylan wrote: > > Do I need to create a complete xorg.conf? > > > The command "Xorg -configure" will create one for you. Hooray! With some hacking I got it working. However, I want to report that Xorg -c

Re: vesa driver reports many modes, but only allows a few

2010-03-02 Thread Pat Kane
On Mon, Mar 1, 2010 at 2:35 PM, Ross Boylan wrote: > Do I need to create a complete xorg.conf? The command "Xorg -configure" will create one for you. Pat --- ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listin

Re: vesa driver reports many modes, but only allows a few

2010-03-01 Thread Ross Boylan
On Mon, 2010-03-01 at 14:40 -0500, Adam Jackson wrote: > On Sun, 2010-02-28 at 23:28 -0800, Ross Boylan wrote: > > Could anyone explain to me what the attached log means? > > > > X 7.5 detects a rich array of BIOS modes, but then runs through a list > > of modes and says "no mode of this name". S

Re: vesa driver reports many modes, but only allows a few

2010-03-01 Thread Adam Jackson
On Sun, 2010-02-28 at 23:28 -0800, Ross Boylan wrote: > Could anyone explain to me what the attached log means? > > X 7.5 detects a rich array of BIOS modes, but then runs through a list > of modes and says "no mode of this name". Should it be using something > like "104" or "104 (1024x768)" ins

Re: vesa driver reports many modes, but only allows a few

2010-03-01 Thread Pat Kane
To get higherVMware X display resolutions I had to add these to the xorg.conf file inside my virtual machine: Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" HorizSync10 - 300 VertRefresh 10 - 200

vesa driver reports many modes, but only allows a few

2010-02-28 Thread Ross Boylan
Could anyone explain to me what the attached log means? X 7.5 detects a rich array of BIOS modes, but then runs through a list of modes and says "no mode of this name". Should it be using something like "104" or "104 (1024x768)" instead of, e.g., "1024x768"? Then X tries a less strict probe, an