[argyllcms] Re: another X error

On Sunday 13 August 2006 10:26, Frédéric wrote:

> > I really need someone with this problem to trace through the code
> > in dispwin.c from line 338 in dispwin.c, and note what happens :-
> > ie. is the Xinerama extension emulated by Mergedfb/TwinView,
> > how many screens are reported by Xinerama or ScreenCount(),
> > which screen does the X protocol error trigger on, etc.
>
> Ok, I'll do that and send you back informations.

Here some informations:

dname=:0.0
mydisplay=804f008
xai=804f840
j=0
dcount=2
Create a description for each screen
screen 0
  XF86VidModeQueryExtension(mydisplay, &evb, &erb)=1
  XF86VidModeGetMonitor(mydisplay, disps[i]->uscreen, &monitor)=1
  monitor=b7ebf998
  evb=0, erb=132
  desc1=
  desc2= at 0, 0, width 1600, height 1200
screen 1
  XF86VidModeQueryExtension(mydisplay, &evb, &erb)=1
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  136 (XFree86-VidModeExtension)
  Minor opcode of failed request:  4 (XF86VidModeGetMonitor)
  Value in failed request:  0x4c
  Serial number of failed request:  13
  Current serial number in output stream:  13

It seems that the ATI MergeFB is seen as Xinerama for the number of 
screens, but then get informations (via XF86VidModeGetMonitor()) on second 
screen fails :o/

I also found some usefull options in the radeon driver:

  Option "MergedXinerama" "boolean"
    Since  merged framebuffer  mode does not use Xinerama, apps               
    are not able to intelligently place windows. Merged framebuffer mode
    provides its own pseudo-Xinerama. This allows Xinerama compliant
    applications to place  windows appropriately. There are some caveats.
    Since merged framebuffer mode is able to change relative screen sizes
    and orientations on the fly, as well has having overlapping viewports,
    pseudo-Xinerama, might not always provide the right hints. Also many 
    Xinerama compliant applications only query Xinerama once at startup; if
    the information changes, they may not be aware of the change. If you 
    are already using Xinerama (e.g., a single head card and a dualhead
    card providing three heads), pseudo-Xinerama will be disabled.
    This option allows you turn off the driver provided pseudo-Xinerama 
    extension.
    The default value is TRUE.

  Option "MergedXineramaCRT2IsScreen0" "boolean"
    By default the pseudo-Xinerama provided by the driver makes the 
    left-most or bottom head Xinerama screen 0. Xin erama-aware
    applications do special things with screen 0. To change that behavior,
    use this option.
    The default value is undefined.

I will try to play arround with them.

-- 
   Frédéric

   http://www.gbiloba.org

Other related posts: