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 ../../
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
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
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
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
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
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
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
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
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
10 matches
Mail list logo