Re: How to troubleshoot intel 3D performance?
2009/2/16 Vasily Khoruzhick anars...@gmail.com: Hi, performance issue is known thing on pre-965 chipsets with new intel stuff (gem, uxa). I've filed bugs about them: http://bugs.freedesktop.org/show_bug.cgi?id=19873 http://bugs.freedesktop.org/show_bug.cgi?id=19738 AFAIK there's no fix at the moment, but as workaround you can use 2.6.27 kernel and EXA accelleration. Looking at the code it looks like a failure of the kernel side. Is there a kernel tree that tracks the Linus one with the latest pending fixes I can try? I gave a 2.6.27-stable kernel a spin but with poor results (X hung up after a few seconds). Do the X drivers need rebuilding when the kernel has been updated? -- Alex, homepage: http://www.bennee.com/~alex/ CV: http://www.bennee.com/~alex/cv.php ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: How to troubleshoot intel 3D performance?
On Tuesday 17 February 2009 10:12:56 you wrote: 2009/2/16 Vasily Khoruzhick anars...@gmail.com: Hi, performance issue is known thing on pre-965 chipsets with new intel stuff (gem, uxa). I've filed bugs about them: http://bugs.freedesktop.org/show_bug.cgi?id=19873 http://bugs.freedesktop.org/show_bug.cgi?id=19738 AFAIK there's no fix at the moment, but as workaround you can use 2.6.27 kernel and EXA accelleration. Looking at the code it looks like a failure of the kernel side. Is there a kernel tree that tracks the Linus one with the latest pending fixes I can try? I suspect this one: git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel I gave a 2.6.27-stable kernel a spin but with poor results (X hung up after a few seconds). It does with UXA enabled. Try EXA Do the X drivers need rebuilding when the kernel has been updated? Nope signature.asc Description: This is a digitally signed message part. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: How to troubleshoot intel 3D performance?
'Twas brillig, and Vasily Khoruzhick at 17/02/09 09:05 did gyre and gimble: On Tuesday 17 February 2009 10:12:56 you wrote: 2009/2/16 Vasily Khoruzhick anars...@gmail.com: Hi, performance issue is known thing on pre-965 chipsets with new intel stuff (gem, uxa). I've filed bugs about them: http://bugs.freedesktop.org/show_bug.cgi?id=19873 http://bugs.freedesktop.org/show_bug.cgi?id=19738 AFAIK there's no fix at the moment, but as workaround you can use 2.6.27 kernel and EXA accelleration. Looking at the code it looks like a failure of the kernel side. Is there a kernel tree that tracks the Linus one with the latest pending fixes I can try? I suspect this one: git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel I believe the drm-next branch is usually the bleeding edge stuff fro the next stable kernel (but I'm not 100% sure on this). Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: How to troubleshoot intel 3D performance?
'Twas brillig, and Vasily Khoruzhick at 16/02/09 19:44 did gyre and gimble: Hi, performance issue is known thing on pre-965 chipsets with new intel stuff (gem, uxa). I've filed bugs about them: http://bugs.freedesktop.org/show_bug.cgi?id=19873 http://bugs.freedesktop.org/show_bug.cgi?id=19738 AFAIK there's no fix at the moment, but as workaround you can use 2.6.27 kernel and EXA accelleration. This is going to cause some pretty bad press for Intel when the next set of distros ship which will be pretty soon. Fedora, Mandriva and Ubuntu all have releases coming up and if I'm not mistaken they will be shipping 2.6.28 or .29 kernels. This really needs to be addressed guys :( Col (who is still stuck on a .27 kernel and is feeling left out) -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: How to troubleshoot intel 3D performance?
2009/2/17 Colin Guthrie gm...@colin.guthr.ie: 'Twas brillig, and Vasily Khoruzhick at 17/02/09 09:05 did gyre and gimble: On Tuesday 17 February 2009 10:12:56 you wrote: 2009/2/16 Vasily Khoruzhick anars...@gmail.com: Hi, performance issue is known thing on pre-965 chipsets with new intel stuff (gem, uxa). I've filed bugs about them: http://bugs.freedesktop.org/show_bug.cgi?id=19873 http://bugs.freedesktop.org/show_bug.cgi?id=19738 AFAIK there's no fix at the moment, but as workaround you can use 2.6.27 kernel and EXA accelleration. Looking at the code it looks like a failure of the kernel side. Is there a kernel tree that tracks the Linus one with the latest pending fixes I can try? I suspect this one: git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel I believe the drm-next branch is usually the bleeding edge stuff fro the next stable kernel (but I'm not 100% sure on this). I'll give that a spin. An additional data point, Dave Airle's tree (commit eaaffe54249dbb4de3631b9d968456bb0458) gave a slightly different error on start up: (II) [drm] DRM open master succeeded. (II) intel(0): [drm] Using the DRM lock SAREA also for drawables. (II) intel(0): [drm] framebuffer mapped by ddx driver (II) intel(0): [drm] added 1 reserved context for kernel (II) intel(0): X context handle = 0x1 (II) intel(0): [drm] installed DRM signal handler (**) intel(0): Framebuffer compression disabled (**) intel(0): Tiling enabled (==) intel(0): VideoRam: 262144 KB (II) intel(0): Attempting memory allocation with tiled buffers. (EE) intel(0): Failed to set tiling on front buffer: Invalid argument (EE) intel(0): Failed to set tiling on back buffer: Invalid argument (EE) intel(0): Failed to set tiling on depth buffer: Invalid argument (II) intel(0): Tiled allocation successful. (II) intel(0): [drm] Registers = 0xdfd0 (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432 (II) intel(0): [dri] visual configs initialized (II) intel(0): Page Flipping disabled (II) intel(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) EXA(0): Offscreen pixmap area of 25804800 bytes (II) EXA(0): Driver registered support for the following operations: (II) Solid (II) Copy (II) Composite (RENDER acceleration) (==) intel(0): Backing store disabled (==) intel(0): Silken mouse enabled (II) intel(0): Initializing HW Cursor (II) intel(0): [DRI] installation complete (II) intel(0): Current clock rate multiplier: 8 (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0c759000 (pgoffset 51033) (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x0dff5000 (pgoffset 57333) (II) intel(0): Fixed memory allocation layout: (II) intel(0): 0x-0x9fff: HW cursors (40 kB, 0xb780 physical ) (II) intel(0): 0xa000-0xafff: overlay registers (4 kB, 0xb780a000 physical ) (II) intel(0): 0x007bf000:end of stolen memory (II) intel(0): 0x007bf000-0x0c758fff: DRI memory manager (196200 kB) (II) intel(0): 0x0c759000-0x0dff4fff: exa offscreen (25200 kB) (II) intel(0): 0x0dff5000-0x0fff4fff: classic textures (32768 kB) (II) intel(0): 0x1000:end of aperture (II) intel(0): BO memory allocation layout: (II) intel(0): 0x007bf000:start of memory manager (II) intel(0): 0x007df000-0x0101efff: depth buffer (8448 kB) (II) intel(0): 0x017df000-0x0201efff: back buffer (8448 kB) (II) intel(0): 0x0280-0x0351: front buffer (13440 kB) (II) intel(0): 0x027df000-0x027e6fff: logical 3D context (32 kB) (II) intel(0): 0x0c759000:end of memory manager But that may well be because it went through a different call path still being EXA. I shall give the latest official intel tree a go and report back. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg -- -- Alex, homepage: http://www.bennee.com/~alex/ CV: http://www.bennee.com/~alex/cv.php ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: How to troubleshoot intel 3D performance?
2009/2/17 Alex Bennee kernel-hac...@bennee.com: 2009/2/17 Colin Guthrie gm...@colin.guthr.ie: 'Twas brillig, and Vasily Khoruzhick at 17/02/09 09:05 did gyre and gimble: On Tuesday 17 February 2009 10:12:56 you wrote: Looking at the code it looks like a failure of the kernel side. Is there a kernel tree that tracks the Linus one with the latest pending fixes I can try? I suspect this one: git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel I believe the drm-next branch is usually the bleeding edge stuff fro the next stable kernel (but I'm not 100% sure on this). I'll give that a spin. An additional data point, Dave Airle's tree (commit eaaffe54249dbb4de3631b9d968456bb0458) gave a slightly different error on start up: snip But that may well be because it went through a different call path still being EXA. I shall give the latest official intel tree a go and report back. No I didn't. The intel tree is in the same state as Airle's tree (the magic of git cherry told me so). So here is the attached full Xorg.log.0 for that tree with UXA enabled. The tiling errors are different but the result is the same. Very poor 3D performance. I stand ready to try any suggested patches. Is it likely that the tiling stuff is responsible for the poor performance or could it be a red hearing? I can have a poke around in the code and see if anything stands out although reading the xf86-intel-driver code tree I can see the error message but not by what interface the request to the kernel is made. -- Alex, homepage: http://www.bennee.com/~alex/ CV: http://www.bennee.com/~alex/cv.php Xorg.0.log Description: Binary data ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: How to troubleshoot intel 3D performance?
On Tuesday 17 February 2009 11:46:33 Alex Bennee wrote: 2009/2/17 Colin Guthrie gm...@colin.guthr.ie: 'Twas brillig, and Vasily Khoruzhick at 17/02/09 09:05 did gyre and gimble: On Tuesday 17 February 2009 10:12:56 you wrote: 2009/2/16 Vasily Khoruzhick anars...@gmail.com: Hi, performance issue is known thing on pre-965 chipsets with new intel stuff (gem, uxa). I've filed bugs about them: http://bugs.freedesktop.org/show_bug.cgi?id=19873 http://bugs.freedesktop.org/show_bug.cgi?id=19738 AFAIK there's no fix at the moment, but as workaround you can use 2.6.27 kernel and EXA accelleration. Looking at the code it looks like a failure of the kernel side. Is there a kernel tree that tracks the Linus one with the latest pending fixes I can try? I suspect this one: git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel I believe the drm-next branch is usually the bleeding edge stuff fro the next stable kernel (but I'm not 100% sure on this). I'll give that a spin. An additional data point, Dave Airle's tree (commit eaaffe54249dbb4de3631b9d968456bb0458) gave a slightly different error on start up: AFAIK you also need xf86-video-intel from git to get tiling working on pre-965 hardware with GEM. Btw, unfortunately I've hit another bug - one about huge BO leakage - when tried xf86-video-intel from git and recent kernels :( Regards Vasily signature.asc Description: This is a digitally signed message part. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
radeon, DVI and coherent_mode
Hi, I've just rebuilt my system's ati driver, and now it's missing the 'coherent_mode' RandR prop. This might be correct, as I only abused this prop to reinit stuff until my display stopped showing blackouts (happens from time to time, so this saves me restarting xorg). In case this is accidental, I've got: 01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200] (Secondary) (rev 01) DVI connected DFP No KMS or GEM ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Drawing minimized windows
On Mon, Feb 16, 2009 at 12:59 PM, Keith Packard kei...@keithp.com wrote: On Sun, 2009-02-15 at 21:41 -0600, John Hamel wrote: As I understand it this is a direct result of the minimized windows not being drawn by X. 'minimized' is not a part of the window system, rather it's a window manager artifact. That window managers 'minimize' windows by unmapping them is not the fault of the window system. Danny Baumann presented an interesting idea on the Compiz Fusion forums for handling this within the server. The idea is that we split Unmap into two an input-only unmap and a total unmap. We would also have to add new events for these too. That would tell the application 'You're not mapped, but keep redrawing' and would also allow for other WM's to unmap the window completely. My personal opinion on the matter is that we should keep the normal unmap calls, not add any new events and just not destroy the window pixmap. The pixmap could be retrievable with a call to XComposite libs or something. Then we can bind it to a texture from there. Apps will need to change their behaviour to redraw on unmap though, however that should be easy to do with most apps because they use toolkits like GTK and QT to draw. Any app that doesn't keep redrawing would just be a corner case broken app. Cheers, Sam -- keith.pack...@intel.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg -- Sam Spilsbury ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Pixman Projects
Soeren Sandmann wrote: Simon Thum simon.t...@gmx.de writes: However, when you implement super sampling with respect to gamma, the quality loss drops to nearly zero. I'd say typically you need no more strange higher quality filters when that's done. Even a simple non-gamma-correct supersampling filter would be good enough for many purposes. As I recall, GdkPixbuf, which has provided acceptable quality in GNOME for many years, does essentially this. Well, AFAICT the other OS - 12 Years after its vendor crafted sRGB - starts getting things right. IMO time to do so too. I agree that gamma correct filtering would look even better, but whether that's interesting on its own instead of as a side effect of a general SRGB surface, I don't know. It seems a little iffy to me to have a PIXMAN_BOX_FILTER_GAMMA_CORRECT, instead of a general SRGB surface that could be filtered with a normal PIXMAN_FILTER_BOX. AIUI, pixman is widening to 16bit anyway. So I think a LUT-based approach to widening wouldn't hurt much but provide what you suggest. I don't intend it as anything other than a demonstration, since gamma correction should probably be considered along with color management in general. And I did it in the dumbest way possible, so it's way too slow to be practical. If you don't intend on raising all surfaces along the pipe to 16 bit per component, gamma will stay a compositing issue anyway. Though it would be nice to get the corresponding gamma (xdccc did something sufficient for this purpose) from a X CMS, it would be impractical to know in all circumstances what gamma to use. So you'll end up with some sensible gamma anyway. Bottom line: If LUT-based widening was efficient enough, why dump that implementation? sRGB, which you recently added, keeps the LUT small enough to fit in even modest caches (1024 entries * 16bit * 2 = 4k). ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] libxcb 1.2
libxcb 1.2 is now available, lucky you. git tag 1.2 Changelog = Julien Danjou (2): Stop providing autogenerated files in tarball Release libxcb 1.2 Download http://xcb.freedesktop.org/dist/libxcb-1.2.tar.gz md5: f55c731d32ec1a555c77ebbbc8f386aa sha1: 9c1c256b9bcfe78cb99a15b567ca00ffb9a45c1e http://xcb.freedesktop.org/dist/libxcb-1.2.tar.bz2 md5: ae32b7846a7d83f5ec542a5431117564 sha1: 12be595ce1e26da3b63e6a17a47ab9392259f10f Cheers, -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // Trust no one. signature.asc Description: Digital signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: radeon, DVI and coherent_mode
On Tue, Feb 17, 2009 at 6:07 AM, Simon Thum simon.t...@gmx.de wrote: Hi, I've just rebuilt my system's ati driver, and now it's missing the 'coherent_mode' RandR prop. This might be correct, as I only abused this prop to reinit stuff until my display stopped showing blackouts (happens from time to time, so this saves me restarting xorg). In case this is accidental, I've got: 01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200] (Secondary) (rev 01) DVI connected DFP No KMS or GEM That was intentional. The pre-avivo chips shouldn't have this property as we don't support it on them. Alex ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Help please, with compile drm
On Mon, Feb 16, 2009 at 10:22 PM, tac jeuse@gmail.com wrote: Hi everyone, For study reason I decide to compile the xorg myself in the distro of solaris, but I've got stuck with compile drm from the git repos on freedesktop. Before asking in irc, I was told I should use gmake to do this, but still it doesn't seem clear enough for me to do anything ahead. Suggestions appreciated! I could be wrong, but I don't think drm has solaris support. Just linux and the bsds. I could be wrong, and hopefully Alan Coopersmith will jump in to clarify that. ps. I was running into this when I type make install from the source: Making install in libdrm make: Fatal error in reader: Makefile, line 658: Unexpected end of line seen Current working directory /export/work/xorg/drm/libdrm *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo install-recursive | sed s/-recursive//`; \ list='libdrm shared-core tests'; for subdir in $list; do \ echo Making $target in $subdir; \ if test $subdir = .; then \ dot_seen=yes; \ local_target=$target-am; \ else \ local_target=$target; \ fi; \ (cd $subdir make $local_target) \ || eval $failcom; \ done; \ if test $dot_seen = no; then \ make $target-am || exit 1; \ fi; test -z $fail make: Fatal error: Command failed for target `install-recursive' That's just regular automake rules, which are pretty widely tested. It could be a GNU make issue, but I doubt it. Maybe if you could should the whole log from make it could help. -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] libX11 1.2
New libX11 release to go with libxcb 1.2. Some more fixes, janitorial work, NLS updates, and the long-awaited addition of ☭ and ♥ to your favorite Compose file. Details follow in the shortlog from 1.1.99.2. Cheers, Julien Adam Jackson (1): Fix leak in _XimXGetReadData Alan Coopersmith (1): Add README with pointers to mailing list, bugzilla git repos Brian Rogers (1): Initialize event_notify after allocating the memory for it. Colin Harrison (1): Fix copy/paste typo in imLcPrs James Cloos (7): [nls] Add some UTF-8 Compose sequences [nls] Annotate the Bépo compose sequences Use C comments rather than initial doubled hashes to exclude lines from .pre files Revert For nls/*.pre, allow people to comment lines by starting them with '##'. [i18n] s/U00DC/Udiaeresis/g NLS: Add UTF-8 compose file for Finnish dolt: allow older versions of bash to compile the library Jeremy Huddleston (1): Force local transport when using the launchd socket. Julien Cristau (2): Check Xmalloc return value in _XConnectXCB Bump to 1.2 Ken Thomases (1): [i18n] Provide translation from XK_partialderivative (8ef) to Unicode (U2202) Paulo Cesar Pereira de Andrade (10): Janitor: ansification, make distcheck, compiler warnings. Janitor: Correct some gcc/sparse warnings. patches to avoid gcc warnings for libX11 (#1) patches to avoid gcc warnings for libX11 (#2) patches to avoid gcc warnings for libX11 (#3) patches to avoid gcc warnings for libX11 (#4) WORD64 compile fix. This bug catched on a overview of the code. Don't add prototypes for functions that don't exist. Allow multiple inclusions of cursorfont.h, cosmetic patch. Check if a function argument is NULL. Peter Hutterer (2): Add XF86Suspend, XF86Hibernate to KeysymDB. Fix wrong implies symbol. Stefan Dirsch (3): Added remaining hunk of Egbert's patch to prevent XIM deadlocks (#1182). Added remaining xlib patch required for gb18030 support (#1573). Fixed strange font mixups, when fontsets are still used (#2676, Novell #74299). Will Thompson (2): Add two essential compose sequences NLS: Compose: Non-aliasing CCCP vehemens (1): [i18n] Distribute new headers which were added for gb18030 support. git tag: libX11-1.2 http://xorg.freedesktop.org/archive/individual/lib/libX11-1.2.tar.bz2 MD5: c6265b59ea2b594fd68e33f9125b4d20 libX11-1.2.tar.bz2 SHA1: b3d2bbdb5839031f4372c5711348d493c7a41dd6 libX11-1.2.tar.bz2 http://xorg.freedesktop.org/archive/individual/lib/libX11-1.2.tar.gz MD5: a8e045794665c9fb7486c0faa21e3211 libX11-1.2.tar.gz SHA1: 69649d6ea0c2d4baef593119d1d03ee487b9ded4 libX11-1.2.tar.gz signature.asc Description: Digital signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Drawing minimized windows
Why are you unmapping the window? -- keith.pack...@intel.com signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Drawing minimized windows
Hi, From: John Hamel johncha...@gmail.com My apologies if this is the wrong place for requests, but a quick browsing of the site didn't show a forum or other more obvious venue. I'd like to request that minimized windows be drawn in X, and provide a couple reasons that I think the task should be given fairly high priority. As Keith said, the WM does not need to unmap minimized windows (the ICCCM certainly give it the option of keeping them mapped and hide them in some other way; we do this in the metacity-clutter port). However, the ICCCM also specifies that to request transition from iconified to normal state the application should map the window. If the WM keeps the iconified windows mapped, this does not work, as the XMapWindow() becomes a nop. I would be interested to know how, for example, Metisse deals with this issue. Many thanks, Tomas ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Where is xkeyboard-config in the X tree
Hi, I'm trying to get an build of X from source to run independently from my system X. I've been using the instructions on the wiki but I keep running into problems. I discovered I had to manually build mesa but I'm still failing to run: (EE) intel(0): First SDVOB output reported failure to sync (EE) intel(0): Failed to set tiling on front buffer: rejected by kernel (EE) intel(0): First SDVOB output reported failure to sync The XKEYBOARD keymap compiler (xkbcomp) reports: Error:Can't find file evdev for keycodes include Exiting Abandoning keycodes file default Errors from xkbcomp are not fatal to the X server (EE) Error compiling keymap (server-0) (EE) XKB: Couldn't compile keymap XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. Fatal server error: Failed to activate core devices. Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /home/alex/src/xorg/install/var/log/Xorg.0.log for additional information. (EE) intel(0): First SDVOB output reported failure to sync giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. xauth: error in locking authority file /home/alex/.Xauthority Searching the source tree I can't find an xkeyboard-config module. Which module is it part of? -- Alex, homepage: http://www.bennee.com/~alex/ CV: http://www.bennee.com/~alex/cv.php ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Where is xkeyboard-config in the X tree
Alex Bennee wrote: Searching the source tree I can't find an xkeyboard-config module. Which module is it part of? http://www.freedesktop.org/wiki/Software/XKeyboardConfig -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: ANN: xterm patch #242
On Mon, Feb 16, 2009 at 8:46 AM, Thomas Dickey dic...@radix.net wrote: Patch #242 - 2009/2/15 The window title bar text seems broken in 242. Recompiled 241 and works on 241. Here's the string that I used to set the title bar. echo -e -n \033]2;$hostname:$LOGNAME:$PWD\007 Thanks, Jeff. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: ANN: xterm patch #242
On Tuesday 17 February 2009 18:16:49 Jeff Chua wrote: On Mon, Feb 16, 2009 at 8:46 AM, Thomas Dickey dic...@radix.net wrote: Patch #242 - 2009/2/15 The window title bar text seems broken in 242. Recompiled 241 and works on 241. Here's the string that I used to set the title bar. ... the mail you replied to lists new config items for, among other things, whether to allow applications to change the title. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: libX11: Changes to 'master'
On Tue, 2008-11-04 at 08:55 -0800, Jamey Sharp wrote: commit e6a7b70cdb2ae8b713012839a0a0bbb93817b8ef Author: Jamey Sharp ja...@minilop.net Date: Wed Oct 29 14:00:33 2008 -0700 Support multiple independent internal sync handlers Xlib has several independent tasks that need to be performed with the display unlocked. It does this by replacing the existing sync handler with one of a variety of internal sync handlers. However, if multiple internal sync handlers need to run, then the last one registering wins and previously registered internal sync handlers are never invoked. This manifested as a bug with DRI applications on Xlib/XCB as that requires both an XID handler after every XID allocation, and the periodic sequence number handler. The XID handler would win, and the sequence number handler would never be invoked. Fix this by unifying the internal sync handler mechanism into a single function that calls all of the known internal sync handlers. They all need to deal with being called when not strictly necessary now. Signed-off-by: Keith Packard kei...@keithp.com Signed-off-by: Jamey Sharp ja...@minilop.net Signed-off-by: Josh Triplett j...@freedesktop.org Hi, I can reproducibly hit some assertions added in this commit by running ico -threads 10 (or even 2). ico: ../../src/XlibInt.c:599: _XPrivSyncFunction: Assertion `dpy-synchandler == _XPrivSyncFunction' failed. ico: ../../src/XlibInt.c:600: _XPrivSyncFunction: Assertion `(dpy-flags (1L 3)) != 0' failed. Reverting this commit makes it work again, so it looks like the synchandler changes aren't multithread-safe. Any idea how to fix this? Cheers, Julien ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Hand built git X doesn't start properly
Hi, Almost there now. I seem to have successfully built git based X by hand. However now when I startx the monitor just stays blank and X emits the follow: (==) Log file: /home/alex/src/xorg/install/var/log/Xorg.0.log, Time: Tue Feb 17 18:46:11 2009 (==) Using config file: /etc/X11/xorg.conf (EE) Failed to load module freetype (module does not exist, 0) (EE) Failed to load module record (module does not exist, 0) (EE) intel(0): First SDVOB output reported failure to sync (EE) intel(0): Failed to set tiling on front buffer: rejected by kernel (EE) intel(0): First SDVOB output reported failure to sync The XKEYBOARD keymap compiler (xkbcomp) reports: Error:Can't find file uk for symbols include Exiting Abandoning symbols file default Errors from xkbcomp are not fatal to the X server No protocol specified waiting for X server to begin accepting connections . No protocol specified .. No protocol specified .. No protocol specified The No protocol specified line keeps repeating until I kill X. My system built X works fine with the same config. My config and log are attached. -- Alex, homepage: http://www.bennee.com/~alex/ CV: http://www.bennee.com/~alex/cv.php Xorg.0.log Description: Binary data xorg.conf Description: Binary data ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: ANN: xterm patch #242
On Tue, 17 Feb 2009, Bill Crawford wrote: On Tuesday 17 February 2009 18:16:49 Jeff Chua wrote: On Mon, Feb 16, 2009 at 8:46 AM, Thomas Dickey dic...@radix.net wrote: Patch #242 - 2009/2/15 The window title bar text seems broken in 242. Recompiled 241 and works on 241. Here's the string that I used to set the title bar. the mail you replied to lists new config items for, among other things, whether to allow applications to change the title. yes, but #242 didn't intentionally change any of the resource defaults (it's possible that my resource settings obscured an unintentional change of course...) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
drm Q, kernel 2.6.28.6
In rebuilding the drm.ko and radeon.ko modules, I am seeing this warning go by in large numbers: /usr/src/drm/linux-core/drm_compat.h:346:2: warning: #warning init_mm is not available on this kernel! As this kernel is home brewed, like most I've been running for the last 10 years, is there some specific option in the .config that I need to enable? Thanks. -- 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) Maturity is only a short break in adolescence. -- Jules Feiffer ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Status of XDMX
Hi List, What is the status of XDMX? Will it be supported / improved / stabilized in the future? I'm running Xdmx with xorg-server 1.3.0. I've tried X.org 7.4 (xorg-server 1.5.3) and the latest from git (master branch) and they all have problems. The current problem with Xdmx in xorg-server 1.3.0 is that is slows down over time, until I reach a point of intolerance and restart everything. Thanks! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
RE: [PATCH 8/9] handle cea-ext data block and insert mode into mode list.
On Sat, 2009-02-14 at 17:02 +0800, Ma, Ling wrote: And yeah, I think frame height is the sensible representation for modes internally. Now we just need to figure out how to fix up EDID timings that are in field height, but that's a fight for another day. So your menas (If I was wrong, please correct me): we directly duplicate interlaced mode from CEA table which contains original height (like 1080i), then mode_valide function in driver will chose it or not ? Yes, the CEA mode table should give frame height (eg 1920x1080) not field height (1920x540). So the mode table as you have it is fine. As of commit bcafdfbe... in xserver, the driver's mode_valid() hook won't need to check for interlace; the server will filter all modes for it based on whether interlaceAllowed was set (and likewise for doublescan). Drivers that want to be compatible with pre-1.7 servers can still check in mode_valid() if they want, it's harmless, but it won't be necessary. - ajax signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Where is xkeyboard-config in the X tree
Alex Bennee pisze: Hi, I'm trying to get an build of X from source to run independently from my system X. I've been using the instructions on the wiki but I keep running into problems. I discovered I had to manually build mesa but I'm still failing to run: If you have one working X installation, you should also have xkeyboard-config already installed. This is most probably [1] bug. You need to find that stuff (depend on distro you are using), try searching in /etc/X11/xkb, than create a lint pointing to that directory in prefix/share/X11 (where prefix is your installation prefix). -Jacek -- [1] http://lists.freedesktop.org/archives/xorg/2009-February/043635.html ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Help please, with compile drm
Dan Nicholson wrote: On Mon, Feb 16, 2009 at 10:22 PM, tac jeuse@gmail.com wrote: Hi everyone, For study reason I decide to compile the xorg myself in the distro of solaris, but I've got stuck with compile drm from the git repos on freedesktop. Before asking in irc, I was told I should use gmake to do this, but still it doesn't seem clear enough for me to do anything ahead. Suggestions appreciated! I could be wrong, but I don't think drm has solaris support. Just linux and the bsds. I could be wrong, and hopefully Alan Coopersmith will jump in to clarify that. DRM was ported to Solaris, but I think our DRM team failed to get the changes back upstream - I know we carry around patches for it in our build trees: http://src.opensolaris.org/source/xref/fox/fox-gate/XW_NV/open-src/lib/libdrm/ -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [Xlib] Saving state before an unmap
Andrew Troschinetz wrote: I realize that all I can do is set hints and make requests. However those actions have concrete results in terms of WM response. The only thing that matters to me is figuring out exactly how to prod the WM in such a way as to get the responses I need. You can't. You set hints and make requests; how (and even if) the WM responds is up to the WM. The relationship between the hints and the end result is intentionally vague. Window Managers are not non-deterministic, though they may be complex and vague. They may as well be non-determistic, as you don't have access to all of the information which controls their behaviour. When a WM purports to support the EWMH specification, I would except near compliance with that specification and *nothing more*. Bear in mind that compliance simply means that they interpret the requests correctly, not that they necessarily honour them. I am operating within the confines of those specifications and their implementations. It frightens me somewhat that you find that unsettling. What some of us are taking issue with is the remarks from your original post, some of which suggest that you have quite specific expectations about the WM's behaviour, e.g.: Basically I want to unmap a window, fiddle with it a bit (like removing the border, removing the maximize button, etc...) and then remap it. The problem I'm running into is that unmapping the window results in unintended side-effects. If unmapping the window has unintended side effects, so be it. You make a request (unmap the window), the WM does as it sees fit. What's the problem? Also: Essentially, I'm writing a window-manager-lite on top of a real window manager so that I can manipulate all the windows of all the disparate applications of the software suite I'm developing in various ways. Either you're writing a WM, or you're not. Utilities such as pagers are typically tied to a specific WM, even to the point of being part of the same source package as the WM. Probably because the global conventions don't provide the mechanisms necessary to write a pager which works reliably with any WM. And: Essentially the use case is that the user may at any point command the window of another application to remove (or un- remove) its border/close-button/etc, and I need to respect as much of the current window state of the target window as possible (ie: _NET_WM_STATE and possibly other Extended Window Manager Hints properties that I haven't even thought of yet.) The first part is simple enough: server-side resources such as windows aren't really owned by clients, beyond the fact that they will normally be destroyed when the client terminates. Any action you can perform on a window which you created can be performed on a window which another client created. The hard part is that the creator may have its own ideas about how it wants the window managed, and not all of that information will be visible to you. Some of it may only exist in the form of the program logic which determines how the client responds to events relating to the window. The only information which the client is likely to make visible is that which the standards require it to make visible in order to achieve its goals. If the window gets minimised, maybe the client will do something in response, maybe it won't; who knows? The fact that the _NET_WM_STATE property is cleared when the window is withdrawn isn't a problem. If the client subsequently decides to re-map the window, it will set this property accordingly before it does so. Okay, so your program doesn't know how the client intends to set it (if the client even handles this situation), but the standard wasn't written with your program in mind. For the case where it's the WM (in the broadest sense, which would include WM components such as pagers) which is messing with the window, there isn't a problem either. The WM knows exactly which properties it understands and what it does with them, so it can preserve or modify those as necessary. Your program doesn't know about any of that, but ... such is life. What exactly do you think the mechanism is for raising a window when the user clicks on its proxy on a panel like gnome-panel? Without looking, I would think that the mechanism would be to call either XMapWindow() or XMapRaised(). What the WM does about that is anyone's guess. Look guys, GNOME *has* the functions gtk_window_set_decorated() and gdk_window_hide(). I am not trying to do something out of the ordinary here. I'll thank you kindly to stop imposing your assumptions on me. There's a big difference between using the standard APIs and what you outlined in your original post. -- Glynn Clements gl...@gclements.plus.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANN] piglit v1 - automated OpenGL tests
This is to announce the release of piglit v1. The authoritative version of this release is designated by a corresponding tag in the respository on freedesktop.org. You can download a tarball directly from: http://cgit.freedesktop.org/piglit/snapshot/piglit-v1.tar.gz 1) What is piglit? piglit is an automated test framework for OpenGL, intended to make driver developers' lives easier by accessible and automatic regression testing. It incorporates Glean, many (but far too few) of the tests that come with Mesa, and a growing number of test cases that accumulated specifically during driver development. It is available from Git, and the git web interface is about as close to an official website as it gets: http://cgit.freedesktop.org/piglit I also have a page on my fd.o website, which I mostly use to hold the test results of my semi-regular regression tests (of the radeon drivers): http://people.freedesktop.org/~nh/piglit/ 2) Why the release? Many people, especially driver developers, will want to simply use piglit from git. It should be easy to set up, and being a test suite with a slow rate of change, there shouldn't be any problems associated with just using that. However, it has been pointed out to me that for distributions who want to organize tests among their testers, it would be useful to have some explicit release to point to. This is my attempt to help them with that, since I believe we can only win by getting more help with testing on a diverse range of hardware. It may be that we can improve this process -- I just looked for the most lightweight thing I could think of. If so, I'd like to hear about it, and we'll just do that. Otherwise, I simply intend to tag a new version with linearly increasing version numbers once in a while. 3) Other resources? To understand the history of piglit, this document might help: http://cgit.freedesktop.org/piglit/tree/HACKING Apart from that, there really aren't any additional resources, to my knowledge. There is no additional website, there is no mailing list -- I'm posting to mesa3d-devel, because that's where I believe most people who can benefit from piglit are, and to the xorg list because there may be people there interested in Xorg-related testing in general who could also benefit from piglit. I feel that the volume on piglit development is too low to warrant its own mailing list. I also feel that having a website just for the website's sake only sucks resources, and carries the danger of the website going stale etc. At least the first real search result of Google for 'piglit' is my personal website for it (after you ignore the typo advice), which points to the Git repository and webgit interface. That just seems good enough to me. Finally, I would like to hear from people if they have more automated tests that could be incorporated into piglit, so that we can continually improve the state of open source OpenGL driver testing. Cheers, Nicolai Hähnle ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: ANN: xterm patch #242
On Tue, 17 Feb 2009, Thomas Dickey wrote: On Tue, 17 Feb 2009, Bill Crawford wrote: On Tuesday 17 February 2009 18:16:49 Jeff Chua wrote: On Mon, Feb 16, 2009 at 8:46 AM, Thomas Dickey dic...@radix.net wrote: Patch #242 - 2009/2/15 The window title bar text seems broken in 242. Recompiled 241 and works on 241. Here's the string that I used to set the title bar. the mail you replied to lists new config items for, among other things, whether to allow applications to change the title. yes, but #242 didn't intentionally change any of the resource defaults (it's possible that my resource settings obscured an unintentional change of course...) fwiw, it's working on my machine. (more details might show the problem) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] xf86-video-vesa 2.2.0
Adam Jackson (2): Add yet another pass to mode validation. vesa 2.2.0 Alan Coopersmith (2): Remove xorgconfig xorgcfg from See Also list in man page Add README with pointers to mailing list, bugzilla git repos git tag: xf86-video-vesa-2.2.0 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-vesa-2.2.0.tar.bz2 MD5: 9a86b683f73f3806f55d05cd804a6f4a xf86-video-vesa-2.2.0.tar.bz2 SHA1: b2d0f33f811bc1a651d4ecbc84979f82281e8a59 xf86-video-vesa-2.2.0.tar.bz2 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-vesa-2.2.0.tar.gz MD5: 6d41eba832f885e42582bc202841870f xf86-video-vesa-2.2.0.tar.gz SHA1: b43331b5647f02d9065296a92870e60bad85cd9d xf86-video-vesa-2.2.0.tar.gz - ajax signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [ANN] piglit v1 - automated OpenGL tests
Nicolai Hähnle wrote: This is to announce the release of piglit v1. [...] Congrats on the release, Nicolai. Just a few notes about glean: The glean code in piglit might be a little out of date. I recently brought over a few updates/fixes from the glean tree, but there's probably more that should be pulled in. I've probably added 4-5 new glean tests so far this year. Do you want all glean tests to be incorporated into piglit, or just specific ones that interest you? Note- I'm not volunteering to do that right now, just asking. :) -Brian ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
2 Questions: recompile xorg sources + xorg git
Hello everyone, I need some help... My first question: I'm building x from git with the tiny little script from http://www.x.org/wiki/Development/git (at bottom of the page). I've got several older (like 1-2 months) builds running, which means the xserver starts up. If i want to recompile the sources on another machine I copy the src folder, change the PREFIX and PKG_CONFIG_PATH in the script and start the build process. The problem is: the server doesn't start on the other machine (which is technically identical to the one which runs the server successfully). /var/log/ says: couldn't get lock for /home/fl0/mpxsomething/var/log/Xorg.2.log which actually is a path from the original machine. I thought recompiling the sources should handle this...make clean doesn't solve this. I hope this question is not too trivial, but I cannot explain this... Second question: How do I reset all components of my local git copy (like: libXdamage,libXi,hal,mesa etc...) to a specified date? git -show gives me the date-hash for a single module...Is there a way to checkout EVERYTHING from a specified date? Cheers, and thanks in advance fl0 begin:vcard fn:Florian Lier n:Lier;Florian org:;AG AI | so far adr:;;Germany email;internet:f...@icram.de title:B. Sc. Informatics tel;work:University | AG Angewandte Informatik tel;home:/home/usr x-mozilla-html:FALSE url:www.icram.de version:2.1 end:vcard ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: ANN: xterm patch #242
On Wed, Feb 18, 2009 at 6:52 AM, Thomas Dickey dic...@his.com wrote: On Tue, 17 Feb 2009, Thomas Dickey wrote: On Tue, 17 Feb 2009, Bill Crawford wrote: On Tuesday 17 February 2009 18:16:49 Jeff Chua wrote: On Mon, Feb 16, 2009 at 8:46 AM, Thomas Dickey dic...@radix.net wrote: Patch #242 - 2009/2/15 The window title bar text seems broken in 242. Recompiled 241 and works on 241. Here's the string that I used to set the title bar. the mail you replied to lists new config items for, among other things, whether to allow applications to change the title. yes, but #242 didn't intentionally change any of the resource defaults (it's possible that my resource settings obscured an unintentional change of course...) fwiw, it's working on my machine. (more details might show the problem) # this doesn't work. Title remains as login ... # echo -e -n \033]2;hello\007 # this sets the title correctly xterm -title hello I compile 241 and 242 the same using just ./configure. gcc is 4.2.2 glibc-2.7.90 Jeff. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
RE: [PATCH 8/9] handle cea-ext data block and insert mode into mode list.
OK, I got it! Thanks a lot Ma Ling -Original Message- From: Adam Jackson [mailto:a...@nwnk.net] Sent: 2009年2月18日 4:02 To: Ma, Ling Cc: xorg@lists.freedesktop.org Subject: RE: [PATCH 8/9] handle cea-ext data block and insert mode into mode list. On Sat, 2009-02-14 at 17:02 +0800, Ma, Ling wrote: And yeah, I think frame height is the sensible representation for modes internally. Now we just need to figure out how to fix up EDID timings that are in field height, but that's a fight for another day. So your menas (If I was wrong, please correct me): we directly duplicate interlaced mode from CEA table which contains original height (like 1080i), then mode_valide function in driver will chose it or not ? Yes, the CEA mode table should give frame height (eg 1920x1080) not field height (1920x540). So the mode table as you have it is fine. As of commit bcafdfbe... in xserver, the driver's mode_valid() hook won't need to check for interlace; the server will filter all modes for it based on whether interlaceAllowed was set (and likewise for doublescan). Drivers that want to be compatible with pre-1.7 servers can still check in mode_valid() if they want, it's harmless, but it won't be necessary. - ajax ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Drawing minimized windows
On 2/18/09, Keith Packard kei...@keithp.com wrote: Why are you unmapping the window? Because applications expect their windows to be unmapped when they are not visible? -- keith.pack...@intel.com -- Sam Spilsbury ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Drawing minimized windows
On Wed, 2009-02-18 at 11:06 +0900, Sam Spilsbury wrote: On 2/18/09, Keith Packard kei...@keithp.com wrote: Why are you unmapping the window? Because applications expect their windows to be unmapped when they are not visible? And the tiny version of the window is somehow invisible? -- keith.pack...@intel.com signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Questions on How Xorg handle ACPI
Hi: I'm trying to find how Xorg handles ACPI (s3 and s4). It seems that Xorg handles S3/S4( suspend and resume) is just the same as it process VT switching, for both the flow is WaitFofSomething( )- WakeUpHandle( ) - xf86Wakeup( ) - xf86VTswitch( ) . Question 1. Is any different between Xorg handle S3/S4 and VT Switching? I notice lnxACPIOpen will test connection to /var/run/acpid.socket , can be seen in Xorg.0.log : ACPI: OSPMOpen called ACPI: Opening device (II) Open ACPI successful (/var/run/acpid.socket) BUT, xf86HandlePMEvents( ) is never called (I'm using Ubuntu8.10, Xorg 1.5.2 –- a debug version ,compiled by myself). In my system S3/S4 is OK in both console and X. Question 2. I don't know why, Is Xorg don't need to read ACPI Events ? or using some other methods Thanks ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
VESA driver does not seem to work with DPMS
Dear list, On one of my machines it is loaded with X.org 7.1 with vesa driver 1.2.1. In order to reduce the power consumption, it is set in xorg.conf to turn off the monitor if in idle for a period of time(10 minutes here). However, if using vesa driver, the setting does not seem to work while it takes effect when switching to the intel driver. At the same time, the $ xset dpms force standby command brings the monitor into standby mode with intel driver while it triggers no difference with the vesa driver. Is is a know limitation of the vesa driver or it is fixed in a recent version? Any comment would be greatly appreciated. -- Sincerely, Jyo ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: 2 Questions: recompile xorg sources + xorg git
2009/2/17 Florian Lier f...@icram.de: Hello everyone, snip original machine. I thought recompiling the sources should handle this...make clean doesn't solve this. Have you got PATH and LD_LIBRARY_PATH giving priority to your built X over the system one? I hope this question is not too trivial, but I cannot explain this... Second question: How do I reset all components of my local git copy (like: libXdamage,libXi,hal,mesa etc...) to a specified date? git -show gives me the date-hash for a single module...Is there a way to checkout EVERYTHING from a specified date? Not that I know of. You may be apply to script it though. -- Alex, homepage: http://www.bennee.com/~alex/ CV: http://www.bennee.com/~alex/cv.php ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
