Nabble - Free Desktop - xorg

Re: RandR

2009-12-21T20:11:17Z

On Tue, Dec 22, 2009 at 11:47:56AM +0800, 钟威 wrote:
> hi,guys,
> I am using Fedora 12.I have an UMPC and it with touchscreen.It's
> chipset is by VIA CX700/VX700.When I added the "RandR" "false"option in
> 'xorg.conf' and there was something wrong.When I touched the screen and X
> will restart automatical.If I remove the RandR option that can't start the
> Xwindow. I very hope you can help me!!!!!Thanks....

if it crashes on a touch, my bet would be on the egalax input driver.
we'd need the Xorg.log to get some more info though.

Cheers,
Peter

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

RandR

2009-12-21T19:47:56Z

hi,guys,

I am using Fedora 12.I have an UMPC and it with touchscreen.It's chipset is by VIA CX700/VX700.When I added the "RandR" "false"option in 'xorg.conf' and there was something wrong.When I touched the screen and X will restart automatical.If I remove the RandR option that can't start the Xwindow.

I very hope you can help me!!!!!Thanks....

Best Regards,

William

好玩贺卡等你发，邮箱贺卡全新上线！
Section "ServerLayout"
InputDevice "EETI" "SendCoreEvents"
Identifier "X.org Configured"
option "RandR" "false"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc/"
FontPath "/usr/share/fonts/X11/TTF/"
FontPath "/usr/share/fonts/X11/OTF"
FontPath "/usr/share/fonts/X11/Type1/"
FontPath "/usr/share/fonts/X11/100dpi/"
FontPath "/usr/share/fonts/X11/75dpi/"
EndSection

Section "Module"
Load "dri"
Load "dbe"
Load "extmod"
Load "record"
Load "glx"
Load "xtrap"
Load "freetype"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
#BusID "PCI:01:00:0"
Identifier "Card0"
Driver "vesa"
VendorName "VIA Technologies, Inc."
Option "ActiveDevice" "LCD,CRT"
Option "Center"
Option "LCDPort" "LVDS0"
Option "PanelSize" "1024x600"
Option "NoDithering" "True"
Option "ForceLCD" "True"
Option "LCD_MSB_ENABLE" "False"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x600"
EndSubSection
EndSection

### Touch Configuration Beginning ###
Section "InputDevice"
Identifier "EETI"
Driver "egalax"
Option "Device" "usbauto"
Option "Parameters" "/var/lib/eeti.param"
Option "ScreenNo" "0"
EndSection
### Touch Configuration End ###

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: x1950 only 256mb ram accessible

2009-12-21T07:07:40Z

On Sun, Dec 20, 2009 at 9:55 AM, Andrew Lyon <andrew.lyon@...> wrote:

> On Fri, Dec 18, 2009 at 3:41 PM, Jerome Glisse <glisse@...> wrote:
>> On Fri, Dec 18, 2009 at 08:42:19AM +0000, Andrew Lyon wrote:
>>> Hi,
>>>
>>> Running X server 1.6.3.901 with Radeon x1950 and xf86-video-ati-6.12.4
>>> on kernel 2.6.31 the driver is reporting that only 256mb ram is
>>> accessible because that is the pci bar setting:
>>>
>>> (II) RADEON(0): Generation 2 PCI interface, using max accessible memory
>>> (II) RADEON(0): Detected total video RAM=524288K, accessible=262144K
>>> (PCI BAR=262144K)
>>> (--) RADEON(0): Mapped VideoRAM: 262144 kByte (256 bit DDR SDRAM)
>>>
>>>
>>> How can I use all 512mb?
>>>
>>> Full X log:
>>>
>> We don't support yet using full vram. Anyway i don't think we have
>> driver than can take advantage of all the memory so using 256M or
>> 512M shouldn't impact your use for the time being.
>>
>> This issue is being worked on in KMS world.
>>
>> Cheers,
>> Jerome
>>
>
> I tried to get kms working with xf86-video-ati and acceleration,
> according to the log X started ok but no output was displayed, a
> sudden burst of kernel errors were logged and a few seconds after
> starting X the system locked up.
>

Please file a bug and attach your xorg log and dmesg and list the
versions you are using:
https://bugs.freedesktop.org

Alex
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Building X from git

2009-12-20T16:59:37Z

Jhbuild ... http://library.gnome.org/devel/jhbuild/unstable/getting-started.html.en
with the xorg.modules works well. http://cgit.freedesktop.org/xorg/util/modular/tree/xorg.modules
You'll have to go in and take out the modules you don't want or don't need to build.

ynezz wrote:

Hi,

I would like to build X from git, and I found[1], there is a script for
this[2] task, but is little bit outdated. Before digging into it myself, does
anybody have up-to-date script handy? Thanks.

1. http://www.x.org/wiki/Development/BuildingX
2. Section "Quick and easy way to install a development build"

-- ynezz
_______________________________________________
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Error:Success

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T16:04:28Z

On Mon, Dec 21, 2009 at 09:00:25AM +1000, Peter Hutterer wrote:
> On Sun, Dec 20, 2009 at 11:58:08AM -0800, Dan Nicholson wrote:
> > +if test "$cross_compiling" != yes; then

This should be if ! test "x$cross_compiling" = xyes.

Cheers,
Daniel

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

attachment0 (204 bytes) Download Attachment

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T15:00:25Z

On Sun, Dec 20, 2009 at 11:58:08AM -0800, Dan Nicholson wrote:

> On Sun, Dec 20, 2009 at 11:24 AM, Stephan Raue <mailinglists@...> wrote:
> > Zitat von Dan Nicholson <dbn.lists@...>:
> >
> >> On Sun, Dec 20, 2009 at 5:19 AM, Stephan Raue <mailinglists@...>
> >> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> when i am crosscompiling xorg-server i get an error from configure:
> >>> checking for /etc/X11/fontpath.d... configure: error: cannot check for
> >>> file existence when cross compiling
> >>>
> >>> is it possible to make this easyer for crosscompiling without patching
> >>> configure.ac and configure in an release?
> >>
> >> That's just the way AC_CHECK_FILE works. Since you're cross-compiling,
> >> it doesn't think it's appropriate to check for files on the build
> >> system to determine behavior. It continues, right? It should just give
> >> you the fallback behavior. If you want to specify the fontpath, use
> >> --with-default-font-path.
> >
> > no it doesnt continue, and i have already set --with-default-font-path ...
>
> It looks like there's multiple issues with this approach, but the
> attached should fix the cross compiling problem. We also need to
> address the fact the file test won't resolve all the way when
> $sysconfdir is not specified on the command line. E.g.,
> sysconfdir=${prefix}/etc by default, and then test -r
> "${sysconfdir}/X11/fontpath.d" fails:
>
> checking for ${prefix}/etc/X11/fontpath.d... no
>
> --
> Dan

> From fb76047a38eb1a5ce44ecbb68fd8206a60b7af7c Mon Sep 17 00:00:00 2001
> From: Dan Nicholson <dbn.lists@...>
> Date: Sun, 20 Dec 2009 11:50:25 -0800
> Subject: [PATCH] Don't use AC_CHECK_FILE for fontpath checks when cross compiling
>
> AC_CHECK_FILE chokes when cross compiling, so instead we set the default
> to the standard FONTROOTDIR directories in that case.
>
> Signed-off-by: Dan Nicholson <dbn.lists@...>
> ---
> configure.ac | 21 ++++++++++++---------
> 1 files changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 6cdef15..6e7c214 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -503,18 +503,21 @@ XORG_FONTSUBDIR(FONT75DPIDIR, font75dpidir, 75dpi)
> XORG_FONTSUBDIR(FONT100DPIDIR, font100dpidir, 100dpi)
>
> dnl Uses --default-font-path if set, otherwise checks for /etc/X11/fontpath.d,
> -dnl otherwise uses standard subdirectories of FONTROOTDIR
> -AC_CHECK_FILE([${sysconfdir}/X11/fontpath.d],
> - [DEFAULT_FONT_PATH='catalogue:$(sysconfdir)/X11/fontpath.d'],
> - [
> - DEFAULT_FONT_PATH="${FONTMISCDIR}/,${FONTTTFDIR}/,${FONTOTFDIR}/,${FONTTYPE1DIR}/,${FONT100DPIDIR}/,${FONT75DPIDIR}/"
> - case $host_os in
> - darwin*) DEFAULT_FONT_PATH="${DEFAULT_FONT_PATH},/Library/Fonts,/System/Library/Fonts" ;;
> - esac
> - ])
> +dnl otherwise uses standard subdirectories of FONTROOTDIR. When cross
> +dnl compiling, assume default font path uses standard FONTROOTDIR directories.
> +DEFAULT_FONT_PATH="${FONTMISCDIR}/,${FONTTTFDIR}/,${FONTOTFDIR}/,${FONTTYPE1DIR}/,${FONT100DPIDIR}/,${FONT75DPIDIR}/"
> +if test "$cross_compiling" != yes; then
> + AC_CHECK_FILE([${sysconfdir}/X11/fontpath.d],
> + [DEFAULT_FONT_PATH='catalogue:$(sysconfdir)/X11/fontpath.d'],
> + [case $host_os in
> + darwin*) DEFAULT_FONT_PATH="${DEFAULT_FONT_PATH},/Library/Fonts,/System/Library/Fonts" ;;
> + esac])
> +fi
> AC_ARG_WITH(default-font-path, AS_HELP_STRING([--with-default-font-path=PATH], [Comma separated list of font dirs]),
> [ FONTPATH="$withval" ],
> [ FONTPATH="${DEFAULT_FONT_PATH}" ])
> +AC_MSG_CHECKING([for default font path])
> +AC_MSG_RESULT([$FONTPATH])
>
> AC_ARG_WITH(xkb-path, AS_HELP_STRING([--with-xkb-path=PATH], [Path to XKB base dir (default: ${datadir}/X11/xkb)]),
> [ XKBPATH="$withval" ],
> --
> 1.6.2.5
>

Reviewed-by: Peter Hutterer <peter.hutterer@...>

Cheers,
Peter
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Pointer Acceleration

2009-12-20T14:56:37Z

On Sun, Dec 20, 2009 at 10:51:28PM +0100, Simon Thum wrote:

> Gene Heskett wrote:
> > On Saturday 19 December 2009, Simon Thum wrote:
> >> Gene Heskett wrote:
> >>> I would tend to agree. With modern high resolution mice, I have often
> >>> wished I could set the gain to a below 1 condition. My mouse now uses
> >>> about a 1" x1.35" area of the pad, to cover a 1680x1250 screen, so its
> >>> way too fast for this user.
> >> I'm not sure I got it. What you describe is 'constant deceleration' (see
> >> http://www.x.org/wiki/Development/Documentation/PointerAcceleration),
> >> however the OP maintains it's not working properly.
> >>
> > It is not, in kde, if I set the pointer accel to 0.5, the slow motion is
> > normal, the fast motion is slowed, and that 'taint' what we need. :)
> KDE doesn't offer the full feature set of the X.org server. E.g. it
> doesn't allow configuring multiple devices.
>
> Essentially, what you describe is now a workaround - you're abusing
> acceleration to scale your device. KDE alone won't let you do better.

> > What we need is the ability to scale the input down, and then apply the accel
> > rules as usual. These 1600-3200 dpi optical mice will be the death of me
> > yet!
> Exactly what is implemented in X server 1.6 and above. See the wiki
> page I gave above.
>

I think we* need to either implement the desktop integration soon or nudge
the people capable of doing so. Having it exposed in the server is only half
the solution.

Cheers,
Peter

* "we" as the "not me"
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Building X from git

2009-12-20T14:53:48Z

On Sun, Dec 20, 2009 at 10:51:17PM +0100, Petr Štetiar wrote:
> Hi,
>
> I would like to build X from git, and I found[1], there is a script for
> this[2] task, but is little bit outdated. Before digging into it myself, does
> anybody have up-to-date script handy? Thanks.
>
> 1. http://www.x.org/wiki/Development/BuildingX
> 2. Section "Quick and easy way to install a development build"

git clone -o util/git://anongit.freedesktop.org/util/modular util/modular
./util/modular/build.sh --clone -f built.modules /opt/xorg

This clones all modules and installs them into the /opt/xorg prefix. If one
module fails, you can resume at that module with the -r flag.
./util/modular/build.sh --clone -f built.modules -r `tail -n 1 built.modules` /opt/xorg

Cheers,
Peter
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [Patch] Documenting pointer acceleration

2009-12-20T14:42:07Z

On Sun, Dec 20, 2009 at 09:23:52PM +0100, Simon Thum wrote:

> Peter Hutterer wrote:
> > On Sat, Dec 19, 2009 at 02:25:16PM +0100, Simon Thum wrote:
> >> Peter Hutterer wrote:
> >>> given the two changes alan already suggested,
> >>> Reviewed-by: Peter Hutterer <peter.hutterer@...>
> >>>
> >>> please send out the last version of these patches and I'll push them once
> >>> they're in my inbox.
> >> I think this is it. I was unsure how to include Reviewed-by tags
> >> however, so I left it out.
> >
> > just copy it to the commit message (or re-type it, whatever tickles your
> > fancy), there's nothing particularly special about it. the same goes for
> > Acked-by, Tested-by, Reported-by, etc.
> >
> > Thanks for the patches, these ones are now missing your signed-off-by though
> > :) Just reply to this email with your s-o-b below the two patches please,
> > and I'll add it to the commit message then.
> Like this?

yes, thanks. pushed to the respective repositories.

Cheers,
Peter

> >
> >> From fd3a7020ac06c4bfcdf1a871f0764a31169bb3c1 Mon Sep 17 00:00:00 2001
> >> From: Simon Thum <simon.thum@...>
> >> Date: Sun, 18 Oct 2009 15:10:56 +0200
> >> Subject: [PATCH] xinput: clarify role of set-ptr-feedback
> Signed-off-by: Simon Thum <simon.thum@...>
> >>
> >> ---
> >> man/xinput.man | 9 +++++++--
> >> 1 files changed, 7 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/man/xinput.man b/man/xinput.man
> >> index fbf445e..6705373 100644
> >> --- a/man/xinput.man
> >> +++ b/man/xinput.man
> >> @@ -39,7 +39,11 @@ Change the mode of \fIdevice\fP.
> >> .PP
> >> .TP 8
> >> .B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
> >> -Change the acceleration of \fIdevice\fP.
> >> +Change the pointer acceleration (or feedback) parameters of \fIdevice\fP.
> >> +The xset(1) man page has more details. For X.Org Server 1.7
> >> +and above, there are additional device properties pertaining to pointer
> >> +acceleration. These do not replace, but complement the pointer feedback
> >> +setting.
> >> .PP
> >> .TP 8
> >> .B --set-integer-feedback \fIdevice\fP \fIindex\fP \fIvalue\fP
> >> @@ -103,7 +107,8 @@ device.
> >> .PP
> >> \fIproperty\fP can be the property as a string or the Atom value.
> >> .PP
> >> -
> >> +.SH "SEE ALSO"
> >> +X(__miscmansuffix__), xset(1)
> >> .SH COPYRIGHT
> >> Copyright 1996,1997, Frederic Lepied.
> >> .PP
> >> --
> >> 1.6.4.4
> >>
> >
> >> From 4ebd1ff380df40b4df4884ccd4e40cb619c70086 Mon Sep 17 00:00:00 2001
> >> From: Simon Thum <simon.thum@...>
> >> Date: Sun, 18 Oct 2009 17:49:41 +0200
> >> Subject: [PATCH] xset: update info about pointer acceleration
> >>
> >> Also, try to avoid confusion in the description of
> >> what acceleration means.
> Signed-off-by: Simon Thum <simon.thum@...>
> >> ---
> >> xset.man | 30 ++++++++++++++++++++----------
> >> 1 files changed, 20 insertions(+), 10 deletions(-)
> >>
> >> diff --git a/xset.man b/xset.man
> >> index 0377640..a9d59c0 100644
> >> --- a/xset.man
> >> +++ b/xset.man
> >> @@ -188,13 +188,16 @@ xset led named "Scroll Lock"
> >> .TP 8
> >> .B mouse
> >> The \fBm\fP option controls the mouse parameters; it may be
> >> -abbreviated to 'm'.
> >> -The parameters for the mouse are `acceleration' and `threshold'.
> >> -The acceleration can be specified as an integer, or as a simple
> >> -fraction.
> >> -The mouse, or whatever pointer the machine is connected to,
> >> -will go `acceleration' times as fast when it travels more than `threshold'
> >> -pixels in a short time. This way, the mouse can be used for precise
> >> +abbreviated to 'm'. Of course, it applies to most pointing devices, not just
> >> +mice. The parameters for the pointing device are `acceleration' and
> >> +`threshold'. The acceleration can be specified as an integer, or as a simple
> >> +fraction. Threshold is just an integer. The setting is applied to all connected
> >> +pointing devices. xinput(1) should be used if you need device-specific settings.
> >> +.PP
> >> +By default the pointer (the on-screen representation of the pointing device)
> >> +will go `acceleration' times as fast when the device travels more than
> >> +`threshold' mickeys (i.e. would-be pixels) in 10 ms, including a small
> >> +transition range. This way, the pointing device can be used for precise
> >> alignment when it is moved slowly, yet it can be set to travel across
> >> the screen in a flick of the wrist when desired. One or both
> >> parameters for the
> >> @@ -203,14 +206,21 @@ option can be omitted, but if only one is
> >> given, it will be interpreted as the acceleration.
> >> If no parameters or the flag 'default' is used, the system defaults will
> >> be set.
> >> -
> >> +.PP
> >> If the `threshold' parameter is provided and 0, the `acceleration'
> >> parameter will be used in the exponent of a more natural and continuous
> >> formula, giving precise control for slow motion but big reach for fast
> >> motion, and a progressive transition for motions in between.
> >> -Recommended `acceleration' value in this case is 3/2 to 2, but not
> >> +Recommended `acceleration' value in this case is 3/2 to 3, but not
> >> limited to that range.
> >> .PP
> >> +In the X.org X Server 1.6 and above, the behaviour described so far is linked
> >> +to the default profile. There are other profiles (i.e. functions determining
> >> +pointer acceleration from device velocity) and additional settings, so the
> >> +above description may not apply to non-default cases. In the X.org Server 1.7,
> >> +these are available as input device properties (see xinput).
> >> +
> >> +.PP
> >> .TP 8
> >> .B p
> >> The \fBp\fP option controls pixel color values.
> >> @@ -280,7 +290,7 @@ These settings will be reset to default values when you log out.
> >> Note that not all X implementations are guaranteed to honor all of these
> >> options.
> >> .SH "SEE ALSO"
> >> -X(__miscmansuffix__), Xserver(1), xmodmap(1), xrdb(1), xsetroot(1)
> >> +X(__miscmansuffix__), Xserver(1), xmodmap(1), xrdb(1), xsetroot(1), xinput(1)
> >> .SH AUTHOR
> >> Bob Scheifler, MIT Laboratory for Computer Science
> >> .br
> >> --
> >> 1.6.4.4
> >>

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Building X from git

2009-12-20T14:08:27Z

On Sun, Dec 20, 2009 at 10:51 PM, Petr Štetiar <ynezz@...> wrote:
> Hi,
>
> I would like to build X from git, and I found[1], there is a script for
> this[2] task, but is little bit outdated. Before digging into it myself, does
> anybody have up-to-date script handy? Thanks.

Well, I can't help with an up to date script, but if you want to (or
_have to_) hack on this one feel free, it's on
http://gitorious.org/x-org-build-script (I've just added the changes
from the wiki).
Now seriously, when I wrote this script I didn't think anyone will
find it useful...

Regards,
--
Łukasz [DeeJay1
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Pointer Acceleration

2009-12-20T13:51:28Z

Gene Heskett wrote:

> On Saturday 19 December 2009, Simon Thum wrote:
>> Gene Heskett wrote:
>>> I would tend to agree. With modern high resolution mice, I have often
>>> wished I could set the gain to a below 1 condition. My mouse now uses
>>> about a 1" x1.35" area of the pad, to cover a 1680x1250 screen, so its
>>> way too fast for this user.
>> I'm not sure I got it. What you describe is 'constant deceleration' (see
>> http://www.x.org/wiki/Development/Documentation/PointerAcceleration),
>> however the OP maintains it's not working properly.
>>
> It is not, in kde, if I set the pointer accel to 0.5, the slow motion is
> normal, the fast motion is slowed, and that 'taint' what we need. :)

KDE doesn't offer the full feature set of the X.org server. E.g. it
doesn't allow configuring multiple devices.

Essentially, what you describe is now a workaround - you're abusing
acceleration to scale your device. KDE alone won't let you do better.

> What we need is the ability to scale the input down, and then apply the accel
> rules as usual. These 1600-3200 dpi optical mice will be the death of me
> yet!
Exactly what is implemented in X server 1.6 and above. See the wiki
page I gave above.

Since scaling down is now properly implemented, I figured the abuse case
wasn't worth keeping 100%. I _could_ place an extra case for those
configurations in the profile, but someone will complain even with that
and the old code is readily available, so what?

If there's popular demand for keeping those workaround configs, please
speak up everyone.

Cheers,

Simon
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Building X from git

2009-12-20T13:51:17Z

Hi,

I would like to build X from git, and I found[1], there is a script for
this[2] task, but is little bit outdated. Before digging into it myself, does
anybody have up-to-date script handy? Thanks.

1. http://www.x.org/wiki/Development/BuildingX
2. Section "Quick and easy way to install a development build"

-- ynezz
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Pointer Acceleration

2009-12-20T12:29:46Z

Lorenz Ruhmann wrote:
> After alternating between the two schemes several times and repeating
> specific mouse strokes a few dozen times, I'm getting less and less
> convinced that there actually is a difference. Also, considering you say
> my settings are correct (I'm not using adaptive deceleration), it might
> be a misperception from my side. Thanks for the clarification.
Actually, there is a small difference which I deemed more use- than
harmful. I'm talking about the non-visible state reset timer, which
kicks in after 200 ms and centers the pointer in the pixel it is in,
i.e. flushes sub-pixel information. You can disable that, see the wiki page.

Newer servers don't use that anymore since they expose sub-pixel
information.
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [Patch] Documenting pointer acceleration

2009-12-20T12:23:52Z

Peter Hutterer wrote:

> On Sat, Dec 19, 2009 at 02:25:16PM +0100, Simon Thum wrote:
>> Peter Hutterer wrote:
>>> given the two changes alan already suggested,
>>> Reviewed-by: Peter Hutterer <peter.hutterer@...>
>>>
>>> please send out the last version of these patches and I'll push them once
>>> they're in my inbox.
>> I think this is it. I was unsure how to include Reviewed-by tags
>> however, so I left it out.
>
> just copy it to the commit message (or re-type it, whatever tickles your
> fancy), there's nothing particularly special about it. the same goes for
> Acked-by, Tested-by, Reported-by, etc.
>
> Thanks for the patches, these ones are now missing your signed-off-by though
> :) Just reply to this email with your s-o-b below the two patches please,
> and I'll add it to the commit message then.

Like this?

>
> Cheers,
> Peter
>
>
>> From fd3a7020ac06c4bfcdf1a871f0764a31169bb3c1 Mon Sep 17 00:00:00 2001
>> From: Simon Thum <simon.thum@...>
>> Date: Sun, 18 Oct 2009 15:10:56 +0200
>> Subject: [PATCH] xinput: clarify role of set-ptr-feedback
Signed-off-by: Simon Thum <simon.thum@...>

>>
>> ---
>> man/xinput.man | 9 +++++++--
>> 1 files changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/man/xinput.man b/man/xinput.man
>> index fbf445e..6705373 100644
>> --- a/man/xinput.man
>> +++ b/man/xinput.man
>> @@ -39,7 +39,11 @@ Change the mode of \fIdevice\fP.
>> .PP
>> .TP 8
>> .B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
>> -Change the acceleration of \fIdevice\fP.
>> +Change the pointer acceleration (or feedback) parameters of \fIdevice\fP.
>> +The xset(1) man page has more details. For X.Org Server 1.7
>> +and above, there are additional device properties pertaining to pointer
>> +acceleration. These do not replace, but complement the pointer feedback
>> +setting.
>> .PP
>> .TP 8
>> .B --set-integer-feedback \fIdevice\fP \fIindex\fP \fIvalue\fP
>> @@ -103,7 +107,8 @@ device.
>> .PP
>> \fIproperty\fP can be the property as a string or the Atom value.
>> .PP
>> -
>> +.SH "SEE ALSO"
>> +X(__miscmansuffix__), xset(1)
>> .SH COPYRIGHT
>> Copyright 1996,1997, Frederic Lepied.
>> .PP
>> --
>> 1.6.4.4
>>
>
>> From 4ebd1ff380df40b4df4884ccd4e40cb619c70086 Mon Sep 17 00:00:00 2001
>> From: Simon Thum <simon.thum@...>
>> Date: Sun, 18 Oct 2009 17:49:41 +0200
>> Subject: [PATCH] xset: update info about pointer acceleration
>>
>> Also, try to avoid confusion in the description of
>> what acceleration means.

Signed-off-by: Simon Thum <simon.thum@...>

>> ---
>> xset.man | 30 ++++++++++++++++++++----------
>> 1 files changed, 20 insertions(+), 10 deletions(-)
>>
>> diff --git a/xset.man b/xset.man
>> index 0377640..a9d59c0 100644
>> --- a/xset.man
>> +++ b/xset.man
>> @@ -188,13 +188,16 @@ xset led named "Scroll Lock"
>> .TP 8
>> .B mouse
>> The \fBm\fP option controls the mouse parameters; it may be
>> -abbreviated to 'm'.
>> -The parameters for the mouse are `acceleration' and `threshold'.
>> -The acceleration can be specified as an integer, or as a simple
>> -fraction.
>> -The mouse, or whatever pointer the machine is connected to,
>> -will go `acceleration' times as fast when it travels more than `threshold'
>> -pixels in a short time. This way, the mouse can be used for precise
>> +abbreviated to 'm'. Of course, it applies to most pointing devices, not just
>> +mice. The parameters for the pointing device are `acceleration' and
>> +`threshold'. The acceleration can be specified as an integer, or as a simple
>> +fraction. Threshold is just an integer. The setting is applied to all connected
>> +pointing devices. xinput(1) should be used if you need device-specific settings.
>> +.PP
>> +By default the pointer (the on-screen representation of the pointing device)
>> +will go `acceleration' times as fast when the device travels more than
>> +`threshold' mickeys (i.e. would-be pixels) in 10 ms, including a small
>> +transition range. This way, the pointing device can be used for precise
>> alignment when it is moved slowly, yet it can be set to travel across
>> the screen in a flick of the wrist when desired. One or both
>> parameters for the
>> @@ -203,14 +206,21 @@ option can be omitted, but if only one is
>> given, it will be interpreted as the acceleration.
>> If no parameters or the flag 'default' is used, the system defaults will
>> be set.
>> -
>> +.PP
>> If the `threshold' parameter is provided and 0, the `acceleration'
>> parameter will be used in the exponent of a more natural and continuous
>> formula, giving precise control for slow motion but big reach for fast
>> motion, and a progressive transition for motions in between.
>> -Recommended `acceleration' value in this case is 3/2 to 2, but not
>> +Recommended `acceleration' value in this case is 3/2 to 3, but not
>> limited to that range.
>> .PP
>> +In the X.org X Server 1.6 and above, the behaviour described so far is linked
>> +to the default profile. There are other profiles (i.e. functions determining
>> +pointer acceleration from device velocity) and additional settings, so the
>> +above description may not apply to non-default cases. In the X.org Server 1.7,
>> +these are available as input device properties (see xinput).
>> +
>> +.PP
>> .TP 8
>> .B p
>> The \fBp\fP option controls pixel color values.
>> @@ -280,7 +290,7 @@ These settings will be reset to default values when you log out.
>> Note that not all X implementations are guaranteed to honor all of these
>> options.
>> .SH "SEE ALSO"
>> -X(__miscmansuffix__), Xserver(1), xmodmap(1), xrdb(1), xsetroot(1)
>> +X(__miscmansuffix__), Xserver(1), xmodmap(1), xrdb(1), xsetroot(1), xinput(1)
>> .SH AUTHOR
>> Bob Scheifler, MIT Laboratory for Computer Science
>> .br
>> --
>> 1.6.4.4
>>
>

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T12:21:15Z

Zitat von Dan Nicholson <dbn.lists@...>:

> On Sun, Dec 20, 2009 at 11:24 AM, Stephan Raue
> <mailinglists@...> wrote:
>> Zitat von Dan Nicholson <dbn.lists@...>:
>>
>>> On Sun, Dec 20, 2009 at 5:19 AM, Stephan Raue <mailinglists@...>
>>> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> when i am crosscompiling xorg-server i get an error from configure:
>>>> checking for /etc/X11/fontpath.d... configure: error: cannot check for
>>>> file existence when cross compiling
>>>>
>>>> is it possible to make this easyer for crosscompiling without patching
>>>> configure.ac and configure in an release?
>>>
>>> That's just the way AC_CHECK_FILE works. Since you're cross-compiling,
>>> it doesn't think it's appropriate to check for files on the build
>>> system to determine behavior. It continues, right? It should just give
>>> you the fallback behavior. If you want to specify the fontpath, use
>>> --with-default-font-path.
>>
>> no it doesnt continue, and i have already set --with-default-font-path ...
>
> It looks like there's multiple issues with this approach, but the
> attached should fix the cross compiling problem. We also need to
> address the fact the file test won't resolve all the way when
> $sysconfdir is not specified on the command line. E.g.,
> sysconfdir=${prefix}/etc by default, and then test -r
> "${sysconfdir}/X11/fontpath.d" fails:
>
> checking for ${prefix}/etc/X11/fontpath.d... no
>
> --
> Dan
>

with this patch configure doesnt stop anymore, thank you

Stephan

--
### OpenELEC.tv ###
The free and open Mediacenter Distribution 4 you
http://www.openelec.tv

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T11:58:08Z

On Sun, Dec 20, 2009 at 11:24 AM, Stephan Raue <mailinglists@...> wrote:

> Zitat von Dan Nicholson <dbn.lists@...>:
>
>> On Sun, Dec 20, 2009 at 5:19 AM, Stephan Raue <mailinglists@...>
>> wrote:
>>>
>>> Hi all,
>>>
>>> when i am crosscompiling xorg-server i get an error from configure:
>>> checking for /etc/X11/fontpath.d... configure: error: cannot check for
>>> file existence when cross compiling
>>>
>>> is it possible to make this easyer for crosscompiling without patching
>>> configure.ac and configure in an release?
>>
>> That's just the way AC_CHECK_FILE works. Since you're cross-compiling,
>> it doesn't think it's appropriate to check for files on the build
>> system to determine behavior. It continues, right? It should just give
>> you the fallback behavior. If you want to specify the fontpath, use
>> --with-default-font-path.
>
> no it doesnt continue, and i have already set --with-default-font-path ...

It looks like there's multiple issues with this approach, but the
attached should fix the cross compiling problem. We also need to
address the fact the file test won't resolve all the way when
$sysconfdir is not specified on the command line. E.g.,
sysconfdir=${prefix}/etc by default, and then test -r
"${sysconfdir}/X11/fontpath.d" fails:

checking for ${prefix}/etc/X11/fontpath.d... no

--
Dan

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

cross-fontpath.patch (2K) Download Attachment

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T11:24:08Z

Zitat von Dan Nicholson <dbn.lists@...>:

> On Sun, Dec 20, 2009 at 5:19 AM, Stephan Raue
> <mailinglists@...> wrote:
>> Hi all,
>>
>> when i am crosscompiling xorg-server i get an error from configure:
>> checking for /etc/X11/fontpath.d... configure: error: cannot check for
>> file existence when cross compiling
>>
>> is it possible to make this easyer for crosscompiling without patching
>> configure.ac and configure in an release?
>
> That's just the way AC_CHECK_FILE works. Since you're cross-compiling,
> it doesn't think it's appropriate to check for files on the build
> system to determine behavior. It continues, right? It should just give
> you the fallback behavior. If you want to specify the fontpath, use
> --with-default-font-path.

no it doesnt continue, and i have already set --with-default-font-path ...

>
> --
> Dan
>
>

--
### OpenELEC.tv ###
The free and open Mediacenter Distribution 4 you
http://www.openelec.tv

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T11:19:40Z

On Sun, Dec 20, 2009 at 5:19 AM, Stephan Raue <mailinglists@...> wrote:
> Hi all,
>
> when i am crosscompiling xorg-server i get an error from configure:
> checking for /etc/X11/fontpath.d... configure: error: cannot check for
> file existence when cross compiling
>
> is it possible to make this easyer for crosscompiling without patching
> configure.ac and configure in an release?

That's just the way AC_CHECK_FILE works. Since you're cross-compiling,
it doesn't think it's appropriate to check for files on the build
system to determine behavior. It continues, right? It should just give
you the fallback behavior. If you want to specify the fontpath, use
--with-default-font-path.

--
Dan
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T11:11:00Z

Zitat von Jeremy Huddleston <jeremyhu@...>:

> We don't intentionally make things not cross-compile.
>
> Can you provide the patch you're using, and we'll review it for
> inclusion in the next release.
>
> --Jeremy

because i dont know many of autoconf i have removed the follow code
from configure.ac for a first try (xorg works, but i think this is an
ugly way):

diff -Naur xorg-server-1.7.99.2/configure.ac
xorg-server-1.7.99.2.patch/configure.ac
--- xorg-server-1.7.99.2/configure.ac 2009-12-20 14:25:52.294986508 +0100
+++ xorg-server-1.7.99.2.patch/configure.ac 2009-12-20
14:29:22.349862339 +0100
@@ -504,14 +504,6 @@

dnl Uses --default-font-path if set, otherwise checks for
/etc/X11/fontpath.d,
dnl otherwise uses standard subdirectories of FONTROOTDIR
-AC_CHECK_FILE([${sysconfdir}/X11/fontpath.d],
- [DEFAULT_FONT_PATH='catalogue:${sysconfdir}/X11/fontpath.d'],
- [
- DEFAULT_FONT_PATH="${FONTMISCDIR}/,${FONTTTFDIR}/,${FONTOTFDIR}/,${FONTTYPE1DIR}/,${FONT100DPIDIR}/,${FONT75DPIDIR}/"
- case $host_os in
- darwin*)
DEFAULT_FONT_PATH="${DEFAULT_FONT_PATH},/Library/Fonts,/System/Library/Fonts"
;;
- esac
- ])
AC_ARG_WITH(default-font-path,
AS_HELP_STRING([--with-default-font-path=PATH], [Comma separated list
of font dirs]),
[ FONTPATH="$withval" ],
[ FONTPATH="${DEFAULT_FONT_PATH}" ])

>
> On Dec 20, 2009, at 05:19, Stephan Raue wrote:
>
>> Hi all,
>>
>> when i am crosscompiling xorg-server i get an error from configure:
>> checking for /etc/X11/fontpath.d... configure: error: cannot check for
>> file existence when cross compiling
>>
>> is it possible to make this easyer for crosscompiling without patching
>> configure.ac and configure in an release?
>>
>> greetings
>>
>> Stephan
>>
>> --
>> ### OpenELEC.tv ###
>> The free and open Mediacenter Distribution 4 you
>> http://www.openelec.tv
>>
>>
>>
>> _______________________________________________
>> xorg mailing list
>> xorg@...
>> http://lists.freedesktop.org/mailman/listinfo/xorg
>
>

--
### OpenELEC.tv ###
The free and open Mediacenter Distribution 4 you
http://www.openelec.tv

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T10:46:58Z

We don't intentionally make things not cross-compile.

Can you provide the patch you're using, and we'll review it for inclusion in the next release.

--Jeremy

On Dec 20, 2009, at 05:19, Stephan Raue wrote:

> Hi all,
>
> when i am crosscompiling xorg-server i get an error from configure:
> checking for /etc/X11/fontpath.d... configure: error: cannot check for
> file existence when cross compiling
>
> is it possible to make this easyer for crosscompiling without patching
> configure.ac and configure in an release?
>
> greetings
>
> Stephan
>
> --
> ### OpenELEC.tv ###
> The free and open Mediacenter Distribution 4 you
> http://www.openelec.tv
>
>
>
> _______________________________________________
> xorg mailing list
> xorg@...
> http://lists.freedesktop.org/mailman/listinfo/xorg

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

smime.p7s (7K) Download Attachment

Re: x1950 only 256mb ram accessible

2009-12-20T06:55:16Z

On Fri, Dec 18, 2009 at 3:41 PM, Jerome Glisse <glisse@...> wrote:

> On Fri, Dec 18, 2009 at 08:42:19AM +0000, Andrew Lyon wrote:
>> Hi,
>>
>> Running X server 1.6.3.901 with Radeon x1950 and xf86-video-ati-6.12.4
>> on kernel 2.6.31 the driver is reporting that only 256mb ram is
>> accessible because that is the pci bar setting:
>>
>> (II) RADEON(0): Generation 2 PCI interface, using max accessible memory
>> (II) RADEON(0): Detected total video RAM=524288K, accessible=262144K
>> (PCI BAR=262144K)
>> (--) RADEON(0): Mapped VideoRAM: 262144 kByte (256 bit DDR SDRAM)
>>
>>
>> How can I use all 512mb?
>>
>> Full X log:
>>
> We don't support yet using full vram. Anyway i don't think we have
> driver than can take advantage of all the memory so using 256M or
> 512M shouldn't impact your use for the time being.
>
> This issue is being worked on in KMS world.
>
> Cheers,
> Jerome
>

I tried to get kms working with xf86-video-ati and acceleration,
according to the log X started ok but no output was displayed, a
sudden burst of kernel errors were logged and a few seconds after
starting X the system locked up.

X log:

X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.31-gentoo-r6 x86_64
Current Operating System: Linux ubermicro 2.6.31-gentoo-r6 #3 SMP Fri
Dec 18 10:19:53 GMT 2009 x86_64
Build Date: 18 December 2009 01:06:12PM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec 19 13:58:43 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Simple Layout"
(**) |-->Screen "Screen 1" (0)
(**) | |-->Monitor "DVI-0"
(==) No device specified for screen "Screen 1".
Using the first device section listed.
(**) | |-->Device "Radeon x1950 Pro"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/Type1/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/local/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/OTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/Type1/" does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/75dpi/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/misc/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
(==) ModulePath set to "/usr/lib64/xorg/modules"
(**) Extension "Composite" is enabled
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or
'vmmouse' will be disabled.
(WW) Disabling Mouse1
(WW) Disabling Keyboard1
(II) Loader magic: 0xd20
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7

(--) PCI:*(0:3:0:0) 1002:7280:174b:e190 ATI Technologies Inc RV570
[Radeon X1950 Pro] rev 154, Mem @ 0xc0000000/268435456,
0xd0600000/65536, I/O @ 0x00002000/256, BIOS @ 0x????????/131072
(--) PCI: (0:3:0:1) 1002:72a0:174b:e191 ATI Technologies Inc RV570
[Radeon X1950 Pro] (secondary) rev 154, Mem @ 0xd0610000/65536
(II) Open ACPI successful (/var/run/acpid.socket)
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[40] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[41] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[42] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[43] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[54] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[55] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[56] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[57] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[58] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[59] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[60] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[61] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[62] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[63] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[64] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[65] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) "extmod" will be loaded. This was enabled by default and also
specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also
specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also
specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded. This was enabled by default and also
specified in the config file.
(II) "dri2" will be loaded by default.
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) LoadModule: "vbe"
(II) Loading /usr/lib64/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.1.0
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "dbe"
(II) Loading /usr/lib64/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
(II) LoadModule: "extmod"
(II) Loading /usr/lib64/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib64/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "record"
(II) Loading /usr/lib64/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri2"
(II) Loading /usr/lib64/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "radeon"
(II) Loading /usr/lib64/xorg/modules/drivers//radeon_drv.so
(II) Module radeon: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 6.12.99
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
ATI Radeon 8500 AIW BB (AGP), ATI Radeon 8500 AIW BC (AGP),
ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9700 Pro ND (AGP),
ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9600TX NF (AGP),
ATI FireGL X1 NG (AGP), ATI Radeon 9800PRO NH (AGP),
ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
ATI Radeon 9800XT NJ (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
ATI Radeon Mobility X300 (M22) 5460 (PCIE),
ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
ATI FireGL unknown (R423) UR (PCIE),
ATI FireGL unknown (R423) UT (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility Radeon X700 XL (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon XPRESS 200 5954 (PCIE),
ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
ATI Radeon XPRESS 200M 5975 (PCIE),
ATI Radeon XPRESS 200 5A41 (PCIE),
ATI Radeon XPRESS 200M 5A42 (PCIE),
ATI Radeon XPRESS 200 5A61 (PCIE),
ATI Radeon XPRESS 200M 5A62 (PCIE),
ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI Radeon X550 (RV370) 5B63 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
ATI Mobility Radeon X800 XT (M28) (PCIE),
ATI Mobility FireGL V5100 (M28) (PCIE),
ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE),
ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
ATI Radeon X700 PRO (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
ATI Mobility Radeon X1700, ATI Radeon X2300HD,
ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
AMD FireStream 9250, ATI FirePro V8700 (FireGL),
ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
ATI Radeon 4800 Series, ATI Radeon 4800 Series, ATI FirePro M7750,
ATI M98, ATI M98, ATI M98, ATI Mobility Radeon HD 4650,
ATI Radeon RV730 (AGP), ATI Mobility Radeon HD 4670,
ATI FirePro M5750, ATI Radeon RV730 (AGP),
ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
ATI Mobility Radeon HD 3850 X2, ATI RV670,
ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
ATI Radeon RV710, ATI Radeon RV710, ATI Radeon HD 4350,
ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series,
ATI Mobility Radeon 4500 Series, ATI FirePro RG220, ATI RV630,
ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
ATI FireGL V3600, ATI Radeon HD 2600 LE,
ATI Mobility FireGL Graphics Processor, ATI Radeon RV710,
ATI Radeon HD 3470, ATI Mobility Radeon HD 3430,
ATI Mobility Radeon HD 3400 Series, ATI Radeon HD 3450,
ATI Radeon HD 3450, ATI Radeon HD 3430, ATI Radeon HD 3450,
ATI FirePro V3700, ATI FireMV 2450, ATI FireMV 2260, ATI FireMV 2260,
ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
ATI Radeon HD 3600 PRO, ATI Mobility Radeon HD 3650,
ATI Mobility Radeon HD 3670, ATI Mobility FireGL V5700,
ATI Mobility FireGL V5725, ATI Radeon HD 3200 Graphics,
ATI Radeon 3100 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3100 Graphics, ATI Radeon HD 3300 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3000 Graphics,
ATI Radeon HD 4200, ATI Radeon 4100, ATI Mobility Radeon HD 4200,
ATI Mobility Radeon 4100, ATI RS880
(II) Primary Device is: PCI 03@00:00:0
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[40] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[41] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[42] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[43] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[54] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[55] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[56] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[57] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[58] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[59] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[60] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[61] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[62] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[63] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[64] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[65] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) [KMS] Kernel modesetting enabled.
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[40] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[41] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[42] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[43] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[44] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[45] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[46] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[47] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[48] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[49] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[50] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[51] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[52] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[53] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[54] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[55] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[56] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[57] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[58] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[59] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[60] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[61] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[62] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[63] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[64] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[65] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[66] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[67] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[68] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[69] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[70] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(**) RADEON(0): Depth 16, (--) framebuffer bpp 16
(II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(**) RADEON(0): Option "EnablePageFlip" "true"
(**) RADEON(0): Option "AccelDFS" "True"
(**) RADEON(0): Option "ColorTiling" "on"
(**) RADEON(0): Option "RenderAccel" "on"
(**) RADEON(0): Option "AccelMethod" "EXA"
(**) RADEON(0): Option "DRI" "on"
(**) RADEON(0): Option "EXAVSync" "yes"
(==) RADEON(0): RGB weight 565
(II) RADEON(0): Using 6 bits per RGB (8 bit DAC)
(--) RADEON(0): Chipset: "ATI Radeon X1950" (ChipID = 0x7280)
(II) RADEON(0): PCIE card detected
(II) RADEON(0): KMS Color Tiling: enabled
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: Searching for BusID pci:0000:03:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci:0000:03:00.0
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) RADEON(0): Output DVI-0 using monitor section DVI-0
(**) RADEON(0): Option "Position" "1920 0"
(II) RADEON(0): Output DVI-1 using monitor section DVI-1
(**) RADEON(0): Option "RightOf" "DVI-0"
(II) RADEON(0): EDID vendor "SAM", prod id 873
(II) RADEON(0): Using EDID range info for horizontal sync
(II) RADEON(0): Using EDID range info for vertical refresh
(II) RADEON(0): Printing DDC gathered Modelines:
(II) RADEON(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080
1200 1203 1209 1235 +hsync -vsync (74.0 kHz)
(II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600
601 605 628 +hsync +vsync (37.9 kHz)
(II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600
601 603 625 +hsync +vsync (35.2 kHz)
(II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480
481 484 500 -hsync -vsync (37.5 kHz)
(II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480
489 492 520 -hsync -vsync (37.9 kHz)
(II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480
483 486 525 -hsync -vsync (35.0 kHz)
(II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480
490 492 525 -hsync -vsync (31.5 kHz)
(II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400
412 414 449 -hsync +vsync (31.5 kHz)
(II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688
1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312
768 769 772 800 +hsync +vsync (60.0 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328
768 771 777 806 -hsync -vsync (56.5 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344
768 771 777 806 -hsync -vsync (48.4 kHz)
(II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624
625 628 667 -hsync -vsync (49.7 kHz)
(II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600
601 604 625 +hsync +vsync (46.9 kHz)
(II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600
637 643 666 +hsync +vsync (48.1 kHz)
(II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600
864 865 868 900 +hsync +vsync (67.5 kHz)
(II) RADEON(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160
1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
(II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688
1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800
960 961 964 1000 +hsync +vsync (60.0 kHz)
(II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600
864 865 868 900 +hsync +vsync (67.5 kHz)
(II) RADEON(0): Output DVI-0 connected
(II) RADEON(0): Output DVI-1 connected
(II) RADEON(0): Using user preference for initial modes
(II) RADEON(0): Output DVI-0 using initial mode 1920x1200
(II) RADEON(0): Output DVI-1 using initial mode 1920x1200
(II) RADEON(0): mem size init: gart size :20000000 vram size:
s:10000000 visible:fc00000
(II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM
(**) RADEON(0): Display dimensions: (520, 320) mm
(**) RADEON(0): DPI set to (187, 95)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib64/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) RADEON(0): Kernel too old missing accel information, assuming
accel is working
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib64/xorg/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 2.4.0
ABI class: X.Org Video Driver, version 5.0
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[36] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[37] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[38] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[39] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[40] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[41] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[42] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[43] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[44] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[45] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[46] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[47] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[48] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[49] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[50] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[51] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[52] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[53] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[54] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[55] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[56] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[57] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[58] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[59] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[60] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[61] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[62] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[63] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[64] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[65] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[66] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[67] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[68] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[69] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[70] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) RADEON(0): [DRI2] Setup complete
(II) RADEON(0): Front buffer size: 9000K
(II) RADEON(0): VRAM usage limit set to 224143K
(==) RADEON(0): Backing store disabled
(II) RADEON(0): Direct rendering enabled
(II) RADEON(0): Render acceleration enabled for R300/R400/R500 type cards.
(II) RADEON(0): Setting EXA maxPitchBytes
(II) RADEON(0): EXA VSync enabled
(II) EXA(0): Driver allocated offscreen pixmaps
(II) EXA(0): Driver registered support for the following operations:
(II) Solid
(II) Copy
(II) Composite (RENDER acceleration)
(II) UploadToScreen
(II) DownloadFromScreen
(II) RADEON(0): Acceleration enabled
(II) RADEON(0): DPMS enabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Set up textured video
(II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(WW) RADEON(0): Option "DVI-0" is not used
(WW) RADEON(0): Option "DVI-1" is not used
(WW) RADEON(0): Option "ClockGating" is not used
(WW) RADEON(0): Option "DMAForXv" is not used
(WW) RADEON(0): Option "TripleBuffer" is not used
(WW) RADEON(0): Option "DynamicClocks" is not used
(WW) RADEON(0): Option "DynamicPM" is not used
(WW) RADEON(0): Option "Position" is not used
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(EE) AIGLX error: Calling driver entry point failed
(EE) AIGLX: reverting to software rendering
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) RADEON(0): Setting screen physical size to 1036 x 324
(II) config/hal: Adding input device C-Media USB Headphone Set
(II) LoadModule: "evdev"
(II) Loading /usr/lib64/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.5, module version = 2.3.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) C-Media USB Headphone Set: always reports core events
(**) C-Media USB Headphone Set: Device: "/dev/input/event6"
(II) C-Media USB Headphone Set: Found keys
(II) C-Media USB Headphone Set: Configuring as keyboard
(II) XINPUT: Adding extended input device "C-Media USB Headphone Set"
(type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event5"
(II) Logitech USB Receiver: Found 1 mouse buttons
(II) Logitech USB Receiver: Found scroll wheel(s)
(II) Logitech USB Receiver: Found relative axes
(II) Logitech USB Receiver: Found absolute axes
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as mouse
(II) Logitech USB Receiver: Configuring as keyboard
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4,
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Receiver"
(type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(EE) Logitech USB Receiver: failed to initialize for relative axes.
(**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
(**) Logitech USB Receiver: (accel) filter chain progression: 2.00
(**) Logitech USB Receiver: (accel) filter stage 0: 20.00 ms
(**) Logitech USB Receiver: (accel) set acceleration profile 0
(II) Logitech USB Receiver: initialized for absolute axes.
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event4"
(II) Logitech USB Receiver: Found 20 mouse buttons
(II) Logitech USB Receiver: Found scroll wheel(s)
(II) Logitech USB Receiver: Found relative axes
(II) Logitech USB Receiver: Found x and y relative axes
(II) Logitech USB Receiver: Configuring as mouse
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4,
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE)
(**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
(**) Logitech USB Receiver: (accel) filter chain progression: 2.00
(**) Logitech USB Receiver: (accel) filter stage 0: 20.00 ms
(**) Logitech USB Receiver: (accel) set acceleration profile 0
(II) Logitech USB Receiver: initialized for relative axes.
(II) config/hal: Adding input device CHICONY USB Keyboard
(**) CHICONY USB Keyboard: always reports core events
(**) CHICONY USB Keyboard: Device: "/dev/input/event3"
(II) CHICONY USB Keyboard: Found 3 mouse buttons
(II) CHICONY USB Keyboard: Found scroll wheel(s)
(II) CHICONY USB Keyboard: Found relative axes
(II) CHICONY USB Keyboard: Found x and y relative axes
(II) CHICONY USB Keyboard: Configuring as mouse
(**) CHICONY USB Keyboard: YAxisMapping: buttons 4 and 5
(**) CHICONY USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia:
10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "CHICONY USB Keyboard" (type: MOUSE)
(**) CHICONY USB Keyboard: (accel) keeping acceleration scheme 1
(**) CHICONY USB Keyboard: (accel) filter chain progression: 2.00
(**) CHICONY USB Keyboard: (accel) filter stage 0: 20.00 ms
(**) CHICONY USB Keyboard: (accel) set acceleration profile 0
(II) CHICONY USB Keyboard: initialized for relative axes.
(II) config/hal: Adding input device CHICONY USB Keyboard
(**) CHICONY USB Keyboard: always reports core events
(**) CHICONY USB Keyboard: Device: "/dev/input/event2"
(II) CHICONY USB Keyboard: Found keys
(II) CHICONY USB Keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "CHICONY USB Keyboard"
(type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "gb"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event1"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event0"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"

And the kernel errors:

Dec 19 13:51:33 ubermicro acpid: client connected from 24321[0:1000]
Dec 19 13:51:33 ubermicro acpid: 1 client rule loaded
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_fence_wait] *ERROR*
fence(ffff8803d333e600:0x00000012) 504ms timeout going to reset GPU
Dec 19 13:51:38 ubermicro kernel: [drm] CP reset succeed
(RBBM_STATUS=0x9000C100)
Dec 19 13:51:38 ubermicro kernel: [drm] radeon: cp idle (0x10000000)
Dec 19 13:51:38 ubermicro kernel: radeon: wait for empty RBBM fifo
failed ! Bad things might happen.
Dec 19 13:51:38 ubermicro kernel: Failed to wait GUI idle while
programming pipes. Bad things might happen.
Dec 19 13:51:38 ubermicro kernel: [drm] Loading R500 Microcode
Dec 19 13:51:38 ubermicro kernel: [drm] radeon: ring at 0x0000000020000000
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_ring_test] *ERROR*
radeon: ring test failed (sracth(0x15E4)=0xCAFEDEAD)
Dec 19 13:51:38 ubermicro kernel: [drm:r100_cp_init] *ERROR* radeon:
cp isn't working (-22).
Dec 19 13:51:38 ubermicro kernel: [drm:rv515_gpu_reset] *ERROR* Failed
to reset GPU (RBBM_STATUS=0x9001C100)
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_fence_wait] *ERROR*
fence(ffff8803d333e600:0x00000012) 976ms timeout
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_fence_wait] *ERROR* last
signaled fence(0x00000012)
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(1).
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(1).
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(1).
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(1).
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
Dec 19 13:51:38 ubermicro kernel: [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(1).

The radeon_cs_ioctl/radeon_ib_schedule errors were logged for a few
more seconds then the system locked up.

Andy
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [ANNOUNCE] xorg-server 1.7.99.2

2009-12-20T05:19:25Z

Hi all,

when i am crosscompiling xorg-server i get an error from configure:
checking for /etc/X11/fontpath.d... configure: error: cannot check for
file existence when cross compiling

is it possible to make this easyer for crosscompiling without patching
configure.ac and configure in an release?

greetings

Stephan

--
### OpenELEC.tv ###
The free and open Mediacenter Distribution 4 you
http://www.openelec.tv

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [Patch] Documenting pointer acceleration

2009-12-19T21:14:01Z

On Sat, Dec 19, 2009 at 02:25:16PM +0100, Simon Thum wrote:
> Peter Hutterer wrote:
> > given the two changes alan already suggested,
> > Reviewed-by: Peter Hutterer <peter.hutterer@...>
> >
> > please send out the last version of these patches and I'll push them once
> > they're in my inbox.
> I think this is it. I was unsure how to include Reviewed-by tags
> however, so I left it out.

just copy it to the commit message (or re-type it, whatever tickles your
fancy), there's nothing particularly special about it. the same goes for
Acked-by, Tested-by, Reported-by, etc.

Thanks for the patches, these ones are now missing your signed-off-by though
:) Just reply to this email with your s-o-b below the two patches please,
and I'll add it to the commit message then.

Cheers,
Peter

> From fd3a7020ac06c4bfcdf1a871f0764a31169bb3c1 Mon Sep 17 00:00:00 2001
> From: Simon Thum <simon.thum@...>
> Date: Sun, 18 Oct 2009 15:10:56 +0200
> Subject: [PATCH] xinput: clarify role of set-ptr-feedback
>
> ---
> man/xinput.man | 9 +++++++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/man/xinput.man b/man/xinput.man
> index fbf445e..6705373 100644
> --- a/man/xinput.man
> +++ b/man/xinput.man
> @@ -39,7 +39,11 @@ Change the mode of \fIdevice\fP.
> .PP
> .TP 8
> .B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
> -Change the acceleration of \fIdevice\fP.
> +Change the pointer acceleration (or feedback) parameters of \fIdevice\fP.
> +The xset(1) man page has more details. For X.Org Server 1.7
> +and above, there are additional device properties pertaining to pointer
> +acceleration. These do not replace, but complement the pointer feedback
> +setting.
> .PP
> .TP 8
> .B --set-integer-feedback \fIdevice\fP \fIindex\fP \fIvalue\fP
> @@ -103,7 +107,8 @@ device.
> .PP
> \fIproperty\fP can be the property as a string or the Atom value.
> .PP
> -
> +.SH "SEE ALSO"
> +X(__miscmansuffix__), xset(1)
> .SH COPYRIGHT
> Copyright 1996,1997, Frederic Lepied.
> .PP
> --
> 1.6.4.4
>

> From 4ebd1ff380df40b4df4884ccd4e40cb619c70086 Mon Sep 17 00:00:00 2001
> From: Simon Thum <simon.thum@...>
> Date: Sun, 18 Oct 2009 17:49:41 +0200
> Subject: [PATCH] xset: update info about pointer acceleration
>
> Also, try to avoid confusion in the description of
> what acceleration means.
> ---
> xset.man | 30 ++++++++++++++++++++----------
> 1 files changed, 20 insertions(+), 10 deletions(-)
>
> diff --git a/xset.man b/xset.man
> index 0377640..a9d59c0 100644
> --- a/xset.man
> +++ b/xset.man
> @@ -188,13 +188,16 @@ xset led named "Scroll Lock"
> .TP 8
> .B mouse
> The \fBm\fP option controls the mouse parameters; it may be
> -abbreviated to 'm'.
> -The parameters for the mouse are `acceleration' and `threshold'.
> -The acceleration can be specified as an integer, or as a simple
> -fraction.
> -The mouse, or whatever pointer the machine is connected to,
> -will go `acceleration' times as fast when it travels more than `threshold'
> -pixels in a short time. This way, the mouse can be used for precise
> +abbreviated to 'm'. Of course, it applies to most pointing devices, not just
> +mice. The parameters for the pointing device are `acceleration' and
> +`threshold'. The acceleration can be specified as an integer, or as a simple
> +fraction. Threshold is just an integer. The setting is applied to all connected
> +pointing devices. xinput(1) should be used if you need device-specific settings.
> +.PP
> +By default the pointer (the on-screen representation of the pointing device)
> +will go `acceleration' times as fast when the device travels more than
> +`threshold' mickeys (i.e. would-be pixels) in 10 ms, including a small
> +transition range. This way, the pointing device can be used for precise
> alignment when it is moved slowly, yet it can be set to travel across
> the screen in a flick of the wrist when desired. One or both
> parameters for the
> @@ -203,14 +206,21 @@ option can be omitted, but if only one is
> given, it will be interpreted as the acceleration.
> If no parameters or the flag 'default' is used, the system defaults will
> be set.
> -
> +.PP
> If the `threshold' parameter is provided and 0, the `acceleration'
> parameter will be used in the exponent of a more natural and continuous
> formula, giving precise control for slow motion but big reach for fast
> motion, and a progressive transition for motions in between.
> -Recommended `acceleration' value in this case is 3/2 to 2, but not
> +Recommended `acceleration' value in this case is 3/2 to 3, but not
> limited to that range.
> .PP
> +In the X.org X Server 1.6 and above, the behaviour described so far is linked
> +to the default profile. There are other profiles (i.e. functions determining
> +pointer acceleration from device velocity) and additional settings, so the
> +above description may not apply to non-default cases. In the X.org Server 1.7,
> +these are available as input device properties (see xinput).
> +
> +.PP
> .TP 8
> .B p
> The \fBp\fP option controls pixel color values.
> @@ -280,7 +290,7 @@ These settings will be reset to default values when you log out.
> Note that not all X implementations are guaranteed to honor all of these
> options.
> .SH "SEE ALSO"
> -X(__miscmansuffix__), Xserver(1), xmodmap(1), xrdb(1), xsetroot(1)
> +X(__miscmansuffix__), Xserver(1), xmodmap(1), xrdb(1), xsetroot(1), xinput(1)
> .SH AUTHOR
> Bob Scheifler, MIT Laboratory for Computer Science
> .br
> --
> 1.6.4.4
>

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

[ANNOUNCE] xorg-server 1.7.99.2

2009-12-19T20:03:41Z

Here's the second snapshot towards 1.8. Sorry for the long lag since the
first snapshot; I was waiting to get the 'fb' issue resolved.

Note that this release includes new ABI versions for version 1.8,
affecting the input, video and extension interfaces as
CreateNewResourceType has gotten an additional argument, while
RegisterResourceName should no longer be needed outside of DIX.

Thanks to all involved for their work and also for helping with the new
release process.

-keith

Adam Jackson (9):
dix: Fix up colormap fixup.
modes: Decorate interlaced mode names with a trailing 'i'
EDID: Fix interlaced detailed timings to be frame size, not field size
modes: De-duplicate a clock range check.
modes: Fix duplicate detection, and do it more consistently
EDID: Extend the HDTV hack to handle "1368x769"
randr: Turn on ModeDebug during server setup
randr: Fill in errorValue when verifying outputs/crtcs/modes
glx: swrast can do GLX 1.4 too

Alan Coopersmith (14):
Use $(MAKE) instead of "make" to build Solaris inline assembly
Enable XF86PM on all Solaris platforms, not just x86/x64
Fix builds with --with-int10=stub
Fix dtrace object builds of libos to link with SHA1_LIBS
COPYING: Update license preamble
Update Sun license notices to current X.Org standard form
Add freetype & type1 to the LoadModules ignore list
Convert checks for PC98 support from platform #ifdefs to configure flag
Add platform compatibility defines for Sun Studio compilers
Change sysconfdir brackets to avoid some shells trying to run it as a command
Change default xkb model from pc104 to pc105
Check for failures from CreateNewResourceType
Ensure all resource types created have names registered
Add type name argument to CreateNewResourceType

Chase Douglas (1):
Move FD_CLR above pInfo->read_input

Colin Harrison (6):
Xming: Replace all the uses of deprecated functions in hw/xwin with current ones
Xming: Add mouse motion events with flag POINTER_SCREEN in winEnqueueMotion()
Xming: Add FORCEEXIT option to configuration file
Xming: Fix UT8String and CompoundText clipboard text sharing with windows clipboard
Xming: Tidy up code for initial native window positioning
Xming: Make -auth option work in with -multiwindow

Dave Airlie (1):
loader: actually stat something that has some chance of existing. (v2)

Gaetan Nadon (5):
.gitignore: use common defaults with custom section #24239
Makefile.am: ChangeLog not required: EXTRA_DIST or *CLEANFILES #24432
Deploy the new XORG_DEFAULT_OPTIONS #24242
INSTALL, NEWS, README or AUTHORS files are missing/incorrect #24206
configure.ac: error while checking for XDMXCONFIG_DEP

Hans Nieser (1):
Xinput: allow non-integer values again for Constant- and AdaptiveDeceleration

Ingmar Vanhassel (2):
Update COMPILEDDEFAULTFONTPATH to match the new default font path
Update man-pages for new default font paths

Jamey Sharp (5):
Alloc/free drawables array for each ProcPanoramiXShmGetImage call.
Add video driver flag to indicate that console access is not needed.
Suppress GCC warnings like "the address of `u1' will always evaluate as `true'".
Don't cast double to int: use default conversions or explicitly round.
Suppress certain GCC warnings in auto-generated code.

Jeremy Huddleston (17):
XQuartz: Run xmodmap after programatically updating the keymap.
dix: Properly detect if the other device is frozen
XQuartz: Controller thread launches clients
XQuartz: Don't weed out duplicates in generated keymap
XQuartz: Use dixLookupResourceByType instead of LookupIDByType
XQuartz: Cleanup X11Controller.m compilation warnings.
SHA1: Add support for Common Crypto
configure.ac: Notify user about which SHA1 implementation is being used
XQuartz: Buildfix for Leopard and older
XQuartz: pbproxy: Wait for the server to finish starting up, so display is valid.
XQuartz: Explicitly pass a bellProc to make XBell() work again.
XQuartz: Allow better compatability with older versions of xinit
XQuartz: Drop calls to alloca
Miscellaneous compilation warning fixes
XQuartz: pbproxy: Fix building of standalone xpbproxy executable
dtrace: Add Xserver-dtrace.h to CLEANFILES
Xfake: Nuke -Wl,-undefined=InitExtensions from LDFLAGS

Jon TURNEY (10):
Resolve an inconsistency between libX11 and Xserver over GetModifierMapping
dmx: Correctly compute DMXGetScreenAttributes reply length
Cygwin/X: Remove a couple of extraneous '\n' in logged version info
Cygwin/X: Fix typo in g_fAnotherWMRunning and tidy up WM detection code
Cygwin/X: Add a workaround for a SWT/Motif bug to internal window manager
Cygwin/X: Clearly diagnose a timeout while waiting for SelectionNotify event
Avoid a null dereference if IFF_BROADCAST is set but there is no broadcast address
Cygwin/X: Always use an authorization cookie for internal clients
Cygwin/X: Setup screen layout in Xinerama mode
Cygwin/X: Ensure WM_STATE atom exists in multiwindow mode

Julien Cristau (5):
Move SHA1 computation from render/glyph.c to os/
configure: add --with-sha1={libmd,libcrypto} option
Add libgcrypt as an option for SHA1
xfree86: set a sane umask before opening the log
Move config_init() after CreateWellKnownSockets() and InitCoreDevices()

Keith Packard (9):
Bump to 1.7.99.2 (unreleased)
DRI2: Report the correct extension minor version
Revert "fb: Don't crash if copy_drawable() returns NULL."
Revert "Reserve space for two GC values in copy_drawable()."
Revert "Use IncludeInferiors when copying windows before compositing."
Revert "Fix clipping when windows are used as sources"
Split fbGetDrawable into fbGetDrawablePixmap and fbGetPixmapBitsData
fb: Adjust transform or composite coordinates for pixman operations
Set release date for 1.7.99.2

Luc Verhaegen (1):
Xv: Fix AdjustFrame when driver implements ReputImage.

Ma Ling (1):
EDID: CEA extension support

Maarten Maathuis (10):
exa: remove some outdated comment
exa/mixed: avoid copying back pixmap data when no migration took place
exa/mixed: be more thorough about setting fb_pitch when needed
Revert "exa/mixed: be more thorough about setting fb_pitch when needed"
exa: handle pixmap create/destroy in lower layers
exa: s/PixmapIsOffscreen/PixmapHasGpuCopy and s/pExaPixmap->offscreen/pExaPixmap->use_gpu_copy
exa: a few small pitch related changes
Revert "exa: a few small pitch related changes"
exa/mixed: setting devKind before exaCopyDirty* is not needed
exa/mixed: pixmaps that succeed prepare access have no need for a cpu copy

Marcin Baczyński (1):
Kill compilation warnings.

Matt Turner (3):
Make sys.c use unaligned access functions provided in compiler.
Remove lnx_font.c and lnx.h
Use glibc's in/out routines

Matthieu Herrb (1):
add libc as a choice for SHA1 implementation

Michel Dänzer (8):
EXA: Don't use UploadToScreen for CopyNtoN with mixed pixmaps.
Revert "EXA: Accumulate arbitrary number of glyphs without flushing."
EXA: Don't defragment offscreen memory at allocation time.
fb: Don't crash if copy_drawable() returns NULL.
EXA: Use correct coordinate system for calculating Composite fallback region.
EXA: ExaDoPrepareAccess return value fixes.
EXA: ModifyPixmapHeader_mixed fixes.
EXA/mixed: Don't consider devKind for detecting dimension change.

Mikhail Gusarov (4):
Add missing DLOPEN_LIBS to kdrive compilation flags
os: Add libsha1 as a choice of SHA1 implementation
kdrive: Grab evdev mouse/keyboard devices when X server is active
Supply all code using dl*() with DLOPEN_LIBS

Paul Loewenstein (1):
Cygwin/X: Handle fake keypresses generated by speech recognizers

Paulo Ricardo Zanoni (1):
configure: change 'sigio-default' to 'use-sigio-by-default'

Peter Hutterer (16):
dix: increase default number of buttons to 10.
Move xdmxconfig modules into DMX conditionals (#25102)
Xi: don't crash when deleting invalid device properties.
Revert "Move xdmxconfig modules into DMX conditionals (#25102)"
Move xdmxconfig modules into DMX conditionals (#25102)
Xi: when deleting all properties, reset property handler to NULL.
dix: clean up accel old scheme data when switching schemes.
dix: fix memory leak, free event list on shutdown. (#25028)
dix: remove some obsolete comment.
dix: remove core devices when shutting down. (#25028)
Set the source and deviceid for key repeat events (#24785)
xfree86: tell users to disable AutoAddDevices, not AllowEmptyInput.
xfree86: remove unused variable in configureDDMonitorSection.
Xi: reset device properties to NULL after deleting them. (#25374)
xkb: don't assign garbage value to led_return.
xfree86: belately init RandR12 if xinerama fails. (#24627)

Rami Ylimaki (2):
dix: Fixes a memory leak when a cursor resource is released.
Xext: Fix a memory leak on GE client disconnect.

Tiago Vignatti (5):
EXA: Preserve pPixmap->devPrivate.ptr in exaPixmapIsOffscreen_driver
configure: remove unused kdrive Xvesa config variable
xfree86: spam output but with verbose level checked instead
os: print log markers only if log level is >= 0
xfree86: fix -quiet option behaviour

Tomas Carnecky (2):
XkbWriteCountedString(): return early if str is NULL
Fix possible NULL dereference in XkbFlushLedEvents()

Tormod Volden (1):
xfree86: Fix description of DDC_QUIRK_DETAILED_USE_MAXIMUM_SIZE

Ville Syrjälä (1):
xf86xv: Fix off-by-one in viewport clipping

Yaakov Selkowitz (4):
Set default font path with fontutil 1.1 and fontpath.d
Cygwin/X: Mount options have changed in cygwin-1.7
Cygwin/X: Allow composite to be enabled for Xwin
Cygwin/X: Enable clipboard integration by default

Zhao Yakui (1):
xfree86: Edid quirk for Philips LCD LP154W01

git tag: xorg-server-1.7.99.2

http://xorg.freedesktop.org/archive/individual/xserver/xorg-server-1.7.99.2.tar.bz2
MD5: cafc4e2d4ef6cf6e47f3e7dffeb3346a xorg-server-1.7.99.2.tar.bz2
SHA1: fb0725abd9ad1741722a93b085f93f877bc3da58 xorg-server-1.7.99.2.tar.bz2

http://xorg.freedesktop.org/archive/individual/xserver/xorg-server-1.7.99.2.tar.gz
MD5: 5663ff413945120d66cfc460f8a65125 xorg-server-1.7.99.2.tar.gz
SHA1: c895dc594e1e133e7efedc0ca5312e7ee40113e2 xorg-server-1.7.99.2.tar.gz

--
keith.packard@...

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

attachment0 (195 bytes) Download Attachment

Re: Pointer Acceleration

2009-12-19T16:53:13Z

Simon Thum wrote:

Essentially, you have done exactly the right thing. Please ensure you
don't use adaptive deceleration, which would explain that.

You might try using the default profile and xset m 1 0. Technically this
is polynomial but flat, ruling out adaptive decel.

If the inaccuracy prevails, it would be helpful if you could be more
descriptive about what's wrong.

Thanks in advance,

Simon

After alternating between the two schemes several times and repeating specific mouse strokes a few dozen times, I'm getting less and less convinced that thereactually is a difference. Also, considering you say my settings are correct (I'm not using adaptive deceleration), it might be a misperception from my side. Thanks for the clarification.
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Pointer Acceleration

2009-12-19T15:06:29Z

Gene Heskett wrote:
> I would tend to agree. With modern high resolution mice, I have often wished
> I could set the gain to a below 1 condition. My mouse now uses about a 1"
> x1.35" area of the pad, to cover a 1680x1250 screen, so its way too fast for
> this user.
I'm not sure I got it. What you describe is 'constant deceleration' (see
http://www.x.org/wiki/Development/Documentation/PointerAcceleration),
however the OP maintains it's not working properly.
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: touchscreens in multiscreen setups

2009-12-19T14:08:34Z

>>>>> "Peter" == Peter Hutterer <peter.hutterer@...> writes:

Hi,

Peter> I don't think either is a particularly large undertaking, so
Peter> it's worth tackling if you have the hardware and the test setups
Peter> to actually do it.

Thanks - I do. I'm going on holidays from Tuesday on, but I'm back at
work where I have access to multiple NW (and other) touchscreens the
first week of January.

--
Bye, Peter Korsgaard
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Pointer Acceleration

2009-12-19T13:47:02Z

On Saturday 19 December 2009, Simon Thum wrote:

>Justin Piszcz wrote:
>> On Fri, 18 Dec 2009, Lorenz Ruhmann wrote:
>>> Is there a way to exactly reproduce this old behavior with the new code?
>>> I don't like to rely on a scheme that is kinda considered obsolete.
>
>[..]
>
>> Yes, this is VERY annoying to me as well (all of the new acceleration
>> methods except the old one):
>
>You're free to choose your annoyances. However, as the OP already found
>out, scaling down is an important use case and when it doesn't work well
>that's a bug. Reporting it generally gets better results than piling up
>grudges. Your mileage may vary.
>
>> Add this to your:
>> /etc/hal/fdi/policy/10-x11-input.fdi
>>
>> $ cat 10-x11-input.fdi
>> <match key="info.capabilities" contains="input.mouse">
>> <merge key="input.x11_options.AccelerationScheme"
>> type="string">lightweight</merge> </match>
>
>Obviously the OP knew how to switch back. I suppose he read the
>documentation. BTW it's not obsolete, it's just broken for anything but
>linear scaling (or none).
>

I would tend to agree. With modern high resolution mice, I have often wished
I could set the gain to a below 1 condition. My mouse now uses about a 1"
x1.35" area of the pad, to cover a 1680x1250 screen, so its way too fast for
this user.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>

Mene, mene, tekel, upharsen.
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Pointer Acceleration

2009-12-19T12:31:39Z

Justin Piszcz wrote:
> On Fri, 18 Dec 2009, Lorenz Ruhmann wrote:
>> Is there a way to exactly reproduce this old behavior with the new code?
>> I don't like to rely on a scheme that is kinda considered obsolete.
[..]
> Yes, this is VERY annoying to me as well (all of the new acceleration
> methods except the old one):
You're free to choose your annoyances. However, as the OP already found
out, scaling down is an important use case and when it doesn't work well
that's a bug. Reporting it generally gets better results than piling up
grudges. Your mileage may vary.

> Add this to your:
> /etc/hal/fdi/policy/10-x11-input.fdi
>
> $ cat 10-x11-input.fdi
> <match key="info.capabilities" contains="input.mouse">
> <merge key="input.x11_options.AccelerationScheme" type="string">lightweight</merge>
> </match>
Obviously the OP knew how to switch back. I suppose he read the
documentation. BTW it's not obsolete, it's just broken for anything but
linear scaling (or none).

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Pointer Acceleration

2009-12-19T06:25:24Z

Lorenz Ruhmann wrote:

> With the old pointer acceleration code (now lightweight scheme) my mouse
> cursor behaves perfectly with the following command:
>
> xset m 16/100 1
>
> Even for far and fast mouse movement I can accurately hit small objects.
>
> However, I'm not able to reproduce that accuracy with the new code. I
> tried the Simple Profile (4) with a ConstantDeceleration of 6.25 and
> xset m 1 1, but it just doesn't feel right; neither does polynomial
> acceleration.
>
> Is there a way to exactly reproduce this old behavior with the new code?
> I don't like to rely on a scheme that is kinda considered obsolete.

Essentially, you have done exactly the right thing. Please ensure you
don't use adaptive deceleration, which would explain that.

You might try using the default profile and xset m 1 0. Technically this
is polynomial but flat, ruling out adaptive decel.

If the inaccuracy prevails, it would be helpful if you could be more
descriptive about what's wrong.

Thanks in advance,

Simon

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

[PATCH] Another profile

2009-12-19T05:44:33Z

Hi,

I created another acceleration profile, inspired by the bits removed
from the wacom driver.

I think it's worth adding to the server because it has some qualities no
other profile has.

Cheers,

Simon

From fcc93189b031ee78c6292d18c57e71a5c7e423f4 Mon Sep 17 00:00:00 2001
From: Simon Thum <simon.thum@...>
Date: Fri, 11 Dec 2009 20:55:56 +0100
Subject: [PATCH] dix: add smooth limited pointer acceleration profile

This profile is inspired by the accel code removed from the wacom driver.
It ascends from zero to acceleration, maxing out at threshold. This means you
can control the slope using threshold, which wasn't possible in wacom.
For sanity's sake, threshold should grow with acceleration.

Works best with adaptive deceleration, since otherwise it only generates
acceleration above 1, causing seldom pixel skips.

Reviewed-by: Peter Hutterer <peter.hutterer@...>
---
dix/ptrveloc.c | 28 +++++++++++++++++++++++++++-
include/ptrveloc.h | 3 ++-
2 files changed, 29 insertions(+), 2 deletions(-)

diff --git a/dix/ptrveloc.c b/dix/ptrveloc.c
index 6fb9e21..c2f4378 100644
--- a/dix/ptrveloc.c
+++ b/dix/ptrveloc.c
@@ -868,6 +868,31 @@ SmoothLinearProfile(
}

+/**
+ * From 0 to threshold, the response graduates smoothly from min_accel to
+ * acceleration. Beyond threshold it is exactly the specified acceleration.
+ */
+static float
+SmoothLimitedProfile(
+ DeviceIntPtr dev,
+ DeviceVelocityPtr vel,
+ float velocity,
+ float threshold,
+ float acc)
+{
+ float res;
+
+ if(velocity >= threshold || threshold == 0.0f)
+ return acc;
+
+ velocity /= threshold; /* should be [0..1[ now */
+
+ res = CalcPenumbralGradient(velocity) * (acc - vel->min_acceleration);
+
+ return vel->min_acceleration + res;
+}
+
+
static float
LinearProfile(
DeviceIntPtr dev,
@@ -879,7 +904,6 @@ LinearProfile(
return acc * velocity;
}

-
static float
NoProfile(
DeviceIntPtr dev,
@@ -911,6 +935,8 @@ GetAccelerationProfile(
return PowerProfile;
case AccelProfileLinear:
return LinearProfile;
+ case AccelProfileSmoothLimited:
+ return SmoothLimitedProfile;
case AccelProfileNone:
return NoProfile;
default:
diff --git a/include/ptrveloc.h b/include/ptrveloc.h
index 2a4b40b..676c464 100644
--- a/include/ptrveloc.h
+++ b/include/ptrveloc.h
@@ -37,7 +37,8 @@
#define AccelProfileSimple 4
#define AccelProfilePower 5
#define AccelProfileLinear 6
-#define AccelProfileLAST AccelProfileLinear
+#define AccelProfileSmoothLimited 7
+#define AccelProfileLAST AccelProfileSmoothLimited

/* fwd */
struct _DeviceVelocityRec;
--
1.6.4.4

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: [Patch] Documenting pointer acceleration

2009-12-19T05:25:16Z

Peter Hutterer wrote:
> given the two changes alan already suggested,
> Reviewed-by: Peter Hutterer <peter.hutterer@...>
>
> please send out the last version of these patches and I'll push them once
> they're in my inbox.
I think this is it. I was unsure how to include Reviewed-by tags
however, so I left it out.

Cheers,

Simon

From fd3a7020ac06c4bfcdf1a871f0764a31169bb3c1 Mon Sep 17 00:00:00 2001
From: Simon Thum <simon.thum@...>
Date: Sun, 18 Oct 2009 15:10:56 +0200
Subject: [PATCH] xinput: clarify role of set-ptr-feedback

---
man/xinput.man | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/man/xinput.man b/man/xinput.man
index fbf445e..6705373 100644
--- a/man/xinput.man
+++ b/man/xinput.man
@@ -39,7 +39,11 @@ Change the mode of \fIdevice\fP.
.PP
.TP 8
.B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
-Change the acceleration of \fIdevice\fP.
+Change the pointer acceleration (or feedback) parameters of \fIdevice\fP.
+The xset(1) man page has more details. For X.Org Server 1.7
+and above, there are additional device properties pertaining to pointer
+acceleration. These do not replace, but complement the pointer feedback
+setting.
.PP
.TP 8
.B --set-integer-feedback \fIdevice\fP \fIindex\fP \fIvalue\fP
@@ -103,7 +107,8 @@ device.
.PP
\fIproperty\fP can be the property as a string or the Atom value.
.PP
-
+.SH "SEE ALSO"
+X(__miscmansuffix__), xset(1)
.SH COPYRIGHT
Copyright 1996,1997, Frederic Lepied.
.PP
--
1.6.4.4

From 4ebd1ff380df40b4df4884ccd4e40cb619c70086 Mon Sep 17 00:00:00 2001
From: Simon Thum <simon.thum@...>
Date: Sun, 18 Oct 2009 17:49:41 +0200
Subject: [PATCH] xset: update info about pointer acceleration

Also, try to avoid confusion in the description of
what acceleration means.
---
xset.man | 30 ++++++++++++++++++++----------
1 files changed, 20 insertions(+), 10 deletions(-)

diff --git a/xset.man b/xset.man
index 0377640..a9d59c0 100644
--- a/xset.man
+++ b/xset.man
@@ -188,13 +188,16 @@ xset led named "Scroll Lock"
.TP 8
.B mouse
The \fBm\fP option controls the mouse parameters; it may be
-abbreviated to 'm'.
-The parameters for the mouse are `acceleration' and `threshold'.
-The acceleration can be specified as an integer, or as a simple
-fraction.
-The mouse, or whatever pointer the machine is connected to,
-will go `acceleration' times as fast when it travels more than `threshold'
-pixels in a short time. This way, the mouse can be used for precise
+abbreviated to 'm'. Of course, it applies to most pointing devices, not just
+mice. The parameters for the pointing device are `acceleration' and
+`threshold'. The acceleration can be specified as an integer, or as a simple
+fraction. Threshold is just an integer. The setting is applied to all connected
+pointing devices. xinput(1) should be used if you need device-specific settings.
+.PP
+By default the pointer (the on-screen representation of the pointing device)
+will go `acceleration' times as fast when the device travels more than
+`threshold' mickeys (i.e. would-be pixels) in 10 ms, including a small
+transition range. This way, the pointing device can be used for precise
alignment when it is moved slowly, yet it can be set to travel across
the screen in a flick of the wrist when desired. One or both
parameters for the
@@ -203,14 +206,21 @@ option can be omitted, but if only one is
given, it will be interpreted as the acceleration.
If no parameters or the flag 'default' is used, the system defaults will
be set.
-
+.PP
If the `threshold' parameter is provided and 0, the `acceleration'
parameter will be used in the exponent of a more natural and continuous
formula, giving precise control for slow motion but big reach for fast
motion, and a progressive transition for motions in between.
-Recommended `acceleration' value in this case is 3/2 to 2, but not
+Recommended `acceleration' value in this case is 3/2 to 3, but not
limited to that range.
.PP
+In the X.org X Server 1.6 and above, the behaviour described so far is linked
+to the default profile. There are other profiles (i.e. functions determining
+pointer acceleration from device velocity) and additional settings, so the
+above description may not apply to non-default cases. In the X.org Server 1.7,
+these are available as input device properties (see xinput).
+
+.PP
.TP 8
.B p
The \fBp\fP option controls pixel color values.
@@ -280,7 +290,7 @@ These settings will be reset to default values when you log out.
Note that not all X implementations are guaranteed to honor all of these
options.
.SH "SEE ALSO"
-X(__miscmansuffix__), Xserver(1), xmodmap(1), xrdb(1), xsetroot(1)
+X(__miscmansuffix__), Xserver(1), xmodmap(1), xrdb(1), xsetroot(1), xinput(1)
.SH AUTHOR
Bob Scheifler, MIT Laboratory for Computer Science
.br
--
1.6.4.4

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Cairo and Opengl

2009-12-19T02:23:59Z

Hai all,

Anybody tried using the same surface for rendering opengl and cairo. In the new release of cairo(cairo-1.9.4.tar.gz) I saw the implemetation of cairo_gl_surface_create.

Is it possible to render opengl and cairo together to this surface.

My problem is,

I have one application which is using cairo for rendering. I have five different layers ,one main surface and all others are image surfaces. I am doing merging operation at certain point of time. This is working fine. Now I want to give one surface to an opengl application and let it render on to that. After this I need to merge these things.

Is it possible in cairo.

I know this is bad in a way that I am trying to bring 3d to 2d world. But anybody have some idea about this?

Best Regards,

susi

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: cairo performance and poulsbo driver

2009-12-18T21:11:00Z

Johan Bilien <jobi@...> writes:

> > So I'm left wondering where the overhead of the xlib backend comes from.
> > If I run sysprof (profile attached) while running the trace (in the
> > Composite disabled case), I can see that pixman gets only 27.5% of the
> > CPU time, while 39.4% is spent "in kernel". I'm vaguely thinking that
> > these could be from moving pixmap data to and from the VRAM, but really
> > I have no idea.
> >
> > Any idea on how to further investigate this?

The latest version of sysprof (1.1.4) can trace into the kernel as
well, but requires a 2.6.31 or later kernel though. If you don't have
that, you may want to check out

a7a1ab3081f58557a5997a667d713186f12

from sysprof git. That is the last version that still used a
standalone module. It can also trace into the kernel.

> Profiling with oprofile shows that when running the firefox trace (xlib
> backend, Composite exa hook disabled), the CPU is idle a lot of the
> time. Maybe it's waiting for the GPU a lot?
>
> Here's the top of the profile:
>
> 10082 33.9999 vmlinux-2.6.24-24-lpia vmlinux-2.6.24-24-lpia
> acpi_idle_enter_bm

I don't really know what this is, but I don't think oprofile reports
CPU idle time like that. (Though I don't know oprofile very well).

> 3179 10.7207 vmlinux-2.6.24-24-lpia vmlinux-2.6.24-24-lpia
> get_page_from_freelist

When I have seen this show up, it has been because of page faults,
often triggered from pixman_fill_sse2().

> 1662 5.6048 vmlinux-2.6.24-24-lpia vmlinux-2.6.24-24-lpia
> acpi_idle_enter_simple
> 1317 4.4414 libpixman-1.so.0.16.2 libpixman-1.so.0.16.2
> pixman_fill_sse2
> 1080 3.6421 libpixman-1.so.0.16.2 libpixman-1.so.0.16.2
> bits_image_fetch_transformed

It doesn't show up very high, but FWIW, the pixman 0.17.2 development
snapshot has faster transformed compositing, and there will likely be
further improvements in a future 0.17.x release.

Soren
_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Sporadically erroneous keystroke repetitions

2009-12-18T10:01:50Z

Tomasz Torcz wrote:
> On Sun, Nov 15, 2009 at 11:25:25AM +0000, Colin Guthrie wrote:
>> Is there anything I can do to debug (e.g. via SSH) when this situation
>> arises? I'm on 2.6.31.5, still on xserver 1.6.x but will be upgrading to
>> the latest packages all round today!
>>
>
> Ajax may have found cause: http://ajaxxx.livejournal.com/62378.html

If that is the case, Xorg 1.7 has a possible workaround in the "UseSIGIO"
flag you can set to "False" in the xorg.conf ServerFlags to disable the
use of SIGIO for input events.

--
-Alan Coopersmith- alan.coopersmith@...
Sun Microsystems, Inc. - X Window System Engineering

_______________________________________________
xorg mailing list
xorg@...
http://lists.freedesktop.org/mailman/listinfo/xorg