Re: [git pull] drm request 3
Hi, On Thu, 2010-03-04 at 10:43 -0800, Linus Torvalds wrote: it difficult to have some libdrm that can handle both versions. You shouldn't expect, by now, upgrade drm kernel without update libdrm or at least recompile libdrm. So when you saw a error message driver nouveau 0.0.n+1 and have 0.0.n is completely right. Is not a perfect world, but as talked on xorg mailing list, some time ago, we do not have resources to test it in all versions. Is better focus on just one combination. Best regards, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [git pull] drm request 3
On Sat, 2010-03-06 at 09:40 -0800, Linus Torvalds wrote: Why are people making excuses for bad programming and bad technology? Is not bad technology is new technology, the API have to change faster , unless you want wait 2 years until get stable . -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [ANNOUNCE] libdrm 2.4.7
On Fri, 2009-04-10 at 10:16 +0100, Sergio Monteiro Basto wrote: Hi, tests/drmtest.c still not compile under fedora 10, with libudev-devel installed. When I remove libudev-devel.127-3.fc10.i386 tests/drmtest.c is not build, which prevents the compiling error. seems that drmtest needs a udev 127. Thanks, code seems to depends on the new udev. Did I need new udev for the rest of libdrm ? Thanks, On Thu, 2009-04-09 at 15:23 -0400, Kristian Høgsberg wrote: Ok, here's a quick follow on release to 2.4.6 to fix an embarrasing build problem in the test suite when libudev is not available. Kristian Dave Airlie (1): drm: fix test makefile Kristian Høgsberg (3): test: Makefile.am grammar nazi test: Avoid recursive dependency in makefile Bump version to 2.4.7 git tag: libdrm-2.4.7 http://dri.freedesktop.org/libdrm/libdrm-2.4.7.tar.bz2 MD5: 696007a9090c237fd8e6c8ee84d897d7 libdrm-2.4.7.tar.bz2 SHA1: 8a82d5652ff88fa482bf4fda630d14e983f3d294 libdrm-2.4.7.tar.bz2 http://dri.freedesktop.org/libdrm/libdrm-2.4.7.tar.gz MD5: d680f92c4dd1232b750c1b2247331b50 libdrm-2.4.7.tar.gz SHA1: 4c16f0a542193d838130e0a8900ce358430f44a6 libdrm-2.4.7.tar.gz ___ xorg-announce mailing list xorg-annou...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [ANNOUNCE] libdrm-2.4.3
Hi, I would like understand this new concept of drm and libdrm . So we can't compile i915.ko anymore outside of kernel ? . When we use libdrm-2.4.3 , have we a minimum kernel required ? If libdrm is (or at least should be) safe to upgrade. I understand that should be safe if libdrm is newer than drm kernel modules. On Fedora 10, libdrm.spec clean up header files from libdrm package (rm -f $RPM_BUILD_ROOT/usr/include/drm/$1) and use libdrm headers from kernel headers. rpm -qf /usr/include/drm/* kernel-headers-2.6.27.9-163.sb1.fc10.i386 Which: 1 - kernel it self already produces liddrm headers. 2 - headers aren't from the fresh libdrm. 3 - So, (again) my problem is: libdrm and drm could not match, they are build from different sources. And this could be bad, like now when we have change of symbols. So after thinking and thinking. I have a suggestion, if libdrm also came with source kernel ? Thanks in advance , and btw merry Christmas. On Tue, 2008-12-23 at 01:27 +, Sergio Monteiro Basto wrote: On Mon, 2008-12-22 at 16:25 -0800, Eric Anholt wrote: I've tagged it and uploaded it. The big update this release is the modesetting userland support. I'm skipping the shortlog as it's noisy with the modesetting kernel changes that were merged and then reverted. I'll also push the release script updates to modular that I (almost) used to generate this. git tag: libdrm-2.4.3 http://dri.freedesktop.org/libdrm/libdrm-2.4.3.tar.bz2 MD5: 8a4a46eb3df70af64b5ea240e71f libdrm-2.4.3.tar.bz2 SHA1: 7daff622a1c68d55a02b0fe1a48205188682c018 libdrm-2.4.3.tar.bz2 http://dri.freedesktop.org/libdrm/libdrm-2.4.3.tar.gz MD5: ddf2876bd8b4b484a9c2a360a835aee8 libdrm-2.4.3.tar.gz SHA1: 465f3b7d26021225ca936043fbfadc2780f13653 libdrm-2.4.3.tar.gz -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature -- -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915.ko needs unknown symbol drm_vbl_send_signals
On Sun, 2008-10-26 at 02:57 +, Sergio Monteiro Basto wrote: Compiling drm from git ( git clone git://anongit.freedesktop.org/git/mesa/drm ) I got this message when depmod symbols kernel anything I am missing ? ah we need kernel-sources at least from 2.6.28-rc1 Now without export OS_HAS_GEM=1 i915.ko is not compiled ! I try with kernel 2.6.27 from fedora stock kernels, and works nice. Thanks -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
i915.ko needs unknown symbol drm_vbl_send_signals
Compiling drm from git ( git clone git://anongit.freedesktop.org/git/mesa/drm ) I got this message when depmod symbols kernel anything I am missing ? thanks -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
testing i915_tex , from mesa_7_0_branch
cd ../Mesa-7.0.4/ git pull origin i915tex_branch git pull origin mesa_7_0_branch git log commit 45eb62ad6159408807ff86d24dd972e0f39cefb8 Merge: 97eb335... 7734956... Author: root [EMAIL PROTECTED] Date: Mon Jul 21 09:50:15 2008 +0100 Merge branch 'i915tex_branch' of git://anongit.freedesktop.org/git/mesa/mesa into HEAD Cool, Git says that I merged i915tex into HEAD , But this i915tex, needs drm HEAD , (which is with TTM stuff) or drm-2.3.1 is enough ? TIA, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Updated i915tex
On Wed, 2008-03-12 at 12:51 +0100, Thomas Hellström wrote: Thomas Hellström wrote: Hi! Tungsten Graphics has decided to push an updated version of i915tex, that works with the latest xf86-video-intel and drm. The driver will be available on the mesa i915tex-branch, which is based off the mesa_7_0 branch. Should be i915tex_branch. Hi, that's a good new ! In this i915tex_branch just change the i915 dri code ? isn't it ? if yes, IHMO, this i915tex_branch just should have the i915tex directory and should be compiled with the rest mesa_7_0 branch. Simply don't sound good idea have a copy of all Mesa source , things should been tested with latest mesa_7_0 branch. For example last 3 commits in mesa_7_0 branch, was not reflected on i915tex_branch. or simply put the code on i915tex dir, unless we care with xf86-video-intel-2.1-branch, which have 6 months old and which is the only one that may use this code. On makefile ( as it now) -LIBNAME = i915tex_dri.so +LIBNAME = i915_dri.so and on configs/linux-dri we have to choose between i915tex and old i915. -DRI_DIRS = i810 i915tex i915 i965 mach64 mga r128 r200 r300 radeon s3v +DRI_DIRS = i810 i915tex i965 mach64 mga r128 r200 r300 radeon s3v /Thomas -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Patch] to fix libGL error: dlopen /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so: undefined symbol: _glthread_GetID
On Mon, 2007-11-12 at 08:20 -0700, Brian Paul wrote: Sergio Monteiro Basto wrote: Hi, since is for i915_dri.so , seems to me that is the best Malling list to post it. Simply clean _glthread_GetID from DBG macros. To be honest I had clean all lines with DBG and _glthread_GetID , to be more fast. I had try Mesa from git sources master. What exactly is the issue here? A compiler warning? Linker problem? undefined symbol when load /usr/lib/dri/i915_dri.so, for DRI. I saw that info in LIBGL_DEBUG=verbose glxinfo -Brian -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Patch] to fix libGL error: dlopen /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so: undefined symbol: _glthread_GetID
Hi, since is for i915_dri.so , seems to me that is the best Malling list
to post it.
Simply clean _glthread_GetID from DBG macros.
To be honest I had clean all lines with DBG and _glthread_GetID , to be
more fast.
I had try Mesa from git sources master.
Regards
--
Sérgio M. B.
--- intel_fbo.c.orig 2007-11-03 01:56:56.0 +
+++ intel_fbo.c 2007-11-03 02:00:45.0 +
@@ -615,8 +615,7 @@ intel_render_texture(GLcontext * ctx,
}
}
- DBG(Begin render texture tid %x tex=%u w=%d h=%d refcount=%d\n,
- _glthread_GetID(),
+ DBG(Begin render texture tex=%u w=%d h=%d refcount=%d\n,
att-Texture-Name, newImage-Width, newImage-Height,
irb-Base.RefCount);
@@ -656,7 +655,7 @@ intel_finish_render_texture(GLcontext *
{
struct intel_renderbuffer *irb = intel_renderbuffer(att-Renderbuffer);
- DBG(End render texture (tid %x) tex %u\n, _glthread_GetID(), att-Texture-Name);
+ DBG(End render texture tex %u\n, att-Texture-Name);
if (irb) {
/* just release the region */
smime.p7s
Description: S/MIME cryptographic signature
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
fix undefined symbol: ALIGN on /usr/lib/dri/i915_dri.so
Hi,
this patch fix my problem ,
--- a/src/mesa/drivers/dri/intel/intel_tex_layout.c
+++ b/src/mesa/drivers/dri/intel/intel_tex_layout.c
@@ -33,6 +33,7 @@
#include intel_mipmap_tree.h
#include intel_tex_layout.h
#include macros.h
+#include intel_context.h
GLuint intel_compressed_alignment(GLenum internalFormat)
{
Thanks,
--
Sérgio M. B.
smime.p7s
Description: S/MIME cryptographic signature
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
i915 state report
Hi, developers ! I had update git drm and Mesa-devel git drm and libdrm is working nice. But latest Mesa-git, give me this undefined symbol: ALIGN #LIBGL_DEBUG=verbose glxinfo name of display: :0.0 libGL: XF86DRIGetClientDriverName: 1.9.0 i915 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so libGL error: dlopen /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so: undefined symbol: ALIGN) libGL error: unable to load driver: i915_dri.so display: :0 screen: 0 direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose) Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: moved i915tex
Did we need a new xorg-x11-server 1.3 ? -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] fix drm_i915_flip_t breakage
On Sat, 2007-09-29 at 02:23 +0200, Lukas Hejtmanek wrote: you need to use drm head/master and mesa head/master. It works for me in such a case. this fix (drm_i915_flip_t) don't fix, the moved i915tex or new i915 on Mesa tree, with drm head/master and mesa head/master. Like I write a thread before, stays updated : After a small bisect of of xorg/driver/xf86-video-intel the commit 126031655c3c1db9881ad17d712461533eb59632 Merge remote branch 'origin/master' into buffer-objects breaks the things (WW) intel(0): Removed DRI frontbuffer mapping in compatibility mode. (WW) intel(0): DRIGetDeviceInfo will report incorrect frontbuffer handle. I had try, several combinations of Mesa and drm but seems to me, that don't matter versions of mesa and drm, after the the commit 126031655c3c1db9881ad17d712461533eb5963 on driver/xf86-video-intel things go wrong. Best regards, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: moved i915tex
On Tue, 2007-09-25 at 02:19 +0100, Sergio Monteiro Basto wrote: Hi I just update all gits: libdrm, drm, mesa and xf86-video-intel And now I don't have DRI (WW) intel(0): Removed DRI frontbuffer mapping in compatibility mode. (WW) intel(0): DRIGetDeviceInfo will report incorrect frontbuffer handle. After a small bisect of of xorg/driver/xf86-video-intel the commit 126031655c3c1db9881ad17d712461533eb59632 Merge remote branch 'origin/master' into buffer-objects breaks the things and begins to give the above message . With commit b73235f40497cfb10792ba191d4f6eac3a5df009 Fix pixmap offset I don't have the above message ( and I have DRI). I am using last git drm and git Mesa of 2007-09-16 Regards, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: moved i915tex
On Mon, 2007-09-24 at 19:04 -0700, Keith Packard wrote: On Tue, 2007-09-25 at 02:19 +0100, Sergio Monteiro Basto wrote: Hi I just update all gits: libdrm, drm, mesa and xf86-video-intel And now I don't have DRI No, you don't have AIGLX, which is a long ways from not having DRI. Does glxinfo report that you have direct rendering enabled? LIBGL_DEBUG=verbose glxinfo name of display: :0.0 libGL: XF86DRIGetClientDriverName: 1.9.0 i915 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: Searching for BusID pci::00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: drmOpenMinor returns 4 drmOpenByBusid: drmGetBusid reports pci::00:02.0 libGL error: drmMap of framebuffer failed (Invalid argument) libGL error: reverting to (slow) indirect rendering display: :0 screen: 0 direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose) -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: moved i915tex
On Wed, 2007-09-26 at 15:38 +0100, Sergio Monteiro Basto wrote: libGL error: drmMap of framebuffer failed (Invalid argument) the bug is pretty clear Invalid argument where this is fixed ? Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
moved i915tex
Hi I just update all gits: libdrm, drm, mesa and xf86-video-intel And now I don't have DRI (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (WW) intel(0): Bad V_BIOS checksum (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc008 to 0xd009 (WW) intel(0): PP_STATUS before: on, ready, sequencing idle (WW) intel(0): PP_STATUS after: on, ready, sequencing on (WW) intel(0): Register 0x68080 (TV_FILTER_CTL_1) changed from 0x885e to 0x800010bb (WW) intel(0): Register 0x68084 (TV_FILTER_CTL_2) changed from 0x00012d2d to 0x00028283 (WW) intel(0): Register 0x68088 (TV_FILTER_CTL_3) changed from 0x9696 to 0x00014141 (WW) intel(0): Removed DRI frontbuffer mapping in compatibility mode. (WW) intel(0): DRIGetDeviceInfo will report incorrect frontbuffer handle. (WW) intel(0): ESR is 0x0010, page table error (WW) intel(0): PGTBL_ER is 0x0010, display A pte (WW) intel(0): Existing errors found in hardware state. (WW) intel(0): fbc already enabled on plane a, not enabling on plane a (EE) AIGLX error: drmMap of framebuffer failed (Invalid argument)(EE) AIGLX: reverting to software rendering (WW) intel(0): fbc already enabled on plane a, not enabling on plane a Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: xf86-video-intel and tilling problem on my i915GM
On Fri, 2007-08-10 at 05:46 +0100, Sergio Monteiro Basto wrote: On Thu, 2007-08-09 at 09:19 -0700, Jesse Barnes wrote: Since we still have XAA+Xv tiled rendering bugs, you'll need to disable tiling or use EXA as your AccelMethod... Updating the information, after yesterday with git pull Mesa dev, drm and xf86-video-intel. XAA+Xv tiled rendering seems work well. And about coldwar demo , finally I see seeing the graphics and play smoothly. but reporting other bug, the coldwar demo suddenly crash with drm problems LIBGL_DEBUG=verbose coldwar Check kernel logs or set the LIBGL_DEBUG environment variable to verbose for more info. Detected in file ../common/dri_bufmgr.c, line 490, function driBOValidateList. bin/launcher: line 16: 13017 Aborted LD_LIBRARY_PATH=lib bin/meng pack_list=data/pack.list config=$CW/config.txt output_config=$CW/config.txt save_path=$CW/saves $* dmesg [drm:drm_buffer_object_validate] *ERROR* Failed moving buffer. Big thanks, yes that it is true , I used Option AccelMethod EXA and do the trick. I test with game coldwar demo , which need compress textures, and for the first time I can play the smoothly and seeing the graphics . Just for information with XAA, (without tiling), I don't see the image , with i915tex_dri . Big thanks - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: xf86-video-intel and tilling problem on my i915GM
On Wed, 2007-08-08 at 16:13 -0700, Jesse Barnes wrote: I just tested again on my 915 machine. Xv seems to work well, the display is ok and the speed is right, so hopefully the latest bits will work for you. Let me check :) Hi -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: xf86-video-intel and tilling problem on my i915GM
On Thu, 2007-08-09 at 09:19 -0700, Jesse Barnes wrote: Since we still have XAA+Xv tiled rendering bugs, you'll need to disable tiling or use EXA as your AccelMethod... yes that it is true , I used Option AccelMethod EXA and do the trick. I test with game coldwar demo , which need compress textures, and for the first time I can play the smoothly and seeing the graphics . Just for information with XAA, (without tiling), I don't see the image , with i915tex_dri . Big thanks -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: xf86-video-intel and tilling problem on my i915GM
On Wed, 2007-08-08 at 10:21 +0800, Zhenyu Wang wrote: Pls raise any Xorg video driver issue to [EMAIL PROTECTED], not dri-devel. xorg ML have many traffic It's good if you can pull latest fixes to test it, thanks. I just pull and test and nothing better . commit 92af2f4bbcb395cbde097776718449d99843ad67 Date: Tue Aug 7 15:18:17 2007 -0700 -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: xf86-video-intel and tilling problem on my i915GM
On Wed, 2007-08-08 at 11:12 -0700, Jesse Barnes wrote: Sergio, to reiterate (sorry I lost the earlier messages in this thread), you're having trouble with Xv unless you disable tiling and framebuffer compression right? yes but just i810 afect my i915GM ? is that right ? Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
xf86-video-intel and tilling problem on my i915GM
Hi, the new commits in git with title 6 Aug 23:04 - More tiled rendering fixes: - check for tiling, not just offset in PrepareSolid ... could resolve affect my i915GM ? the src/i830 could affect my i915GM or not ? Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-users] mesa/linux-agp-compat/README Re: i915tex prerequisites
On Tue, 2007-08-07 at 08:34 +0100, Brian Paul wrote: OK, I've checked in some updates to the README file. Please review. BTW, I think you meant to use `uname -r` above, not `uname -a`. My suggestion ( add depmod -a ) Thanks, -- Sérgio M. B. --- README.orig 2007-08-07 22:58:00.0 +0100 +++ README 2007-08-07 23:17:05.0 +0100 @@ -19,10 +19,20 @@ Compiling Compile with: make -Install (as root): - make install +Installing (as root) + + +To install the kernel modules in your kernel modules directory: + +since, make install, will copy agpgart.ko and intel-agp.ko to /lib/modules/`uname -r`/extra/ +duplicating agpgart.ko intel-agp.ko + +It is better: +cp agpgart.ko intel-agp.ko /lib/modules/`uname -r`/kernel/drivers/char/agp/ +depmod -a + Note that if your kernel uses symbol versioning, after the new AGPGART module is intalled DRM may not load, complaining about missing symbols since DRM still uses the old agpgart symbols. @@ -50,12 +60,3 @@ echo cat /usr/src/kernels/`uname -r`-i6 echo diff -up /usr/src/kernels/`uname -r`-i686/Module.symvers Module.symvers2 echo \#if ok echo cp Module.symvers2 /usr/src/kernels/`uname -r`-i686/Module.symvers - - - -Installing --- - -To install the kernel modules in your kernel modules directory: - -cp agpgart.ko intel-agp.ko /lib/modules/`uname -r`/kernel/drivers/char/agp/ smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
mesa/linux-agp-compat/README Re: [Mesa3d-users] i915tex prerequisites
On Fri, 2007-07-27 at 08:16 -0600, Brian Paul wrote: Michel suggest when install linux-agp-compat instead of delete Module.symvers I append the Module(s).symvers file generated by linux-agp-compat to the kernel's file of the same name with cat before building the DRM. And works quite well. So this could be add mesa/linux-agp-compat/README Done. has Dave wrote: It's in 2.6.21 (kernel) and later, it is just a part of agp, nothing special about compat or otherwise, I haven't used linux-agp-compat in a while. a030ce4477baa06dd9c037ccd3c8d171aac9ed44 is the kernel git commitid So , this information should also enter in mesa/linux-agp-compat/README , that this is just for kernel 2.6.21 And to install linux-agp-compat in kernel 2.6.21 we should, overwrite .ko modules kernel like this: cp agpgart.ko intel-agp.ko /lib/modules/`uname -a`/kernel/drivers/char/agp/ instead install in other location. And we should swap, not append the symbols. I done a little script which do that, replace all agp_symblos generated by this new modules on old one. Just to be more precisely ... The script is a little raw, but the 2 temporary files, tmp1 and cm, could explain the script itself. I not sure that works in all platforms. Thanks, -- Sérgio M. B. script Description: application/shellscript smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: last git xf86-video-intel have problem with video out xv
On Tue, 2007-07-31 at 07:51 +0200, Michel Dänzer wrote: On Mon, 2007-07-30 at 22:01 +0100, Sergio Monteiro Basto wrote: (WW) intel(0): Option Legacy3D is not used (II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so Did the build time configure check for DRI_MM succeed? I just found the problem, my fault, I forget update libdrm to git 2.3.(1) since this commits 37652b6... intel: oops I commited pixman local workaround - undo it 1e169be... intel: don't try and use TTM memory manager with old libdrm interface It is need it ! Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915tex prerequisites
On Sat, 2007-07-28 at 04:54 +0100, Dave Airlie wrote: It's in 2.6.21 and later, it is just a part of agp, nothing special about compat or otherwise, I haven't used linux-agp-compat in a while. a030ce4477baa06dd9c037ccd3c8d171aac9ed44 is the kernel git commitid I had try enable i915tex, with kernel 2.6.22 and with git drm/linux-core compiled against this kernel, but don't enable i915tex. ok, I forgot update libdrm, for git drm it is need libdrm bigger than 3.2.0, in this case latest git. After update libdrm, things get to normal. And kernel 2.6.22 enable i915tex. which for me is a good new because I don't have to recompile kernel again and can use the stock kernel given by distros. Thanks, Dave. -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: last git xf86-video-intel have problem with video out xv
On Mon, 2007-07-30 at 09:09 -0700, Jesse Barnes wrote: What hardware do you have? 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) Subsystem: Hewlett-Packard Company NX6110/NC6120 Latency: 0 Capabilities: [e0] Vendor Specific Information 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) (prog-if 00 [VGA]) Subsystem: Hewlett-Packard Company NX6110/NC6120 Latency: 0 Interrupt: pin A routed to IRQ 18 Region 0: Memory at d010 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at 2000 [size=8] Region 2: Memory at c000 (32-bit, prefetchable) [size=256M] Region 3: Memory at d018 (32-bit, non-prefetchable) [size=256K] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) Subsystem: Hewlett-Packard Company NX6110/NC6120 Latency: 0 Region 0: Memory at d020 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- lspci -n 00:00.0 0600: 8086:2590 (rev 03) 00:02.0 0300: 8086:2592 (rev 03) 00:02.1 0380: 8086:2792 (rev 03) 00:1d.0 0c03: 8086:2658 (rev 03) 00:1d.1 0c03: 8086:2659 (rev 03) 00:1d.2 0c03: 8086:265a (rev 03) 00:1d.3 0c03: 8086:265b (rev 03) 00:1d.7 0c03: 8086:265c (rev 03) 00:1e.0 0604: 8086:2448 (rev d3) 00:1e.2 0401: 8086:266e (rev 03) 00:1e.3 0703: 8086:266d (rev 03) 00:1f.0 0601: 8086:2641 (rev 03) 00:1f.1 0101: 8086:266f (rev 03) 02:04.0 0280: 8086:4220 (rev 05) (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) Chipset 915GM found Does Xv based video work again if you add Option tiling false to the Intel device section of your xorg.conf? no , seems that not obey to Option tiling false I try latest git and here is the xorg diff in attach Thanks, I thought Wang's fix would have taken care of this problem, but it sounds like we still have a bug here... Jesse On Sunday, July 29, 2007 11:29 am Sergio Monteiro Basto wrote: Hi , I done a bisect the git xf86-video-intel and here is the results: -- drv-intel bad vo xv: HEAD is now at 04130ac... Fix i915 rendering for tiled buffer version 1 bad vo xv: 88f8b688e2316ae4a1f7485f0010ce90de54783a HEAD is now at 88f8b68... Fix some physical address handling for 4GB addresses verison 2 bad vo xv: HEAD is now at 4359df9... Fix tiling and fb compression defaults for 965 (not yet fully supported). version 5 bad vo xv: HEAD is now at ca593a5... FBC and tiling changes version 6 good: 8798ef11321ee6957919279076758d47ad956cf3 HEAD is now at 8798ef1... Merge branch 'master' into fbc version 4 good: HEAD is now at 8919b22... Re-add tiling kludge, but only for 965 version 3 good: 3c552af65d28fafec1d09484a8914b690b961349 Update documentation and bump driver version to 2.1.0. and xorg diff of last good and first bad Xorg.log -- Sérgio M. B. 15c15 (==) Log file: /var/log/Xorg.0.log.bad, Time: Mon Jul 30 21:18:37 2007 --- (==) Log file: /var/log/Xorg.0.log.good, Time: Sun Jul 29 19:19:26 2007 390c390 (**) intel(0): Option Tiling false --- (**) intel(0): Option Legacy3D false 397c397,399 (--) intel(0): Will try to allocate texture pool for old Mesa 3D driver. --- (**) intel(0): Will not try to allocate texture pool for old Mesa 3D driver. (II) intel(0): Will try to reserve 32768 kiB of AGP aperture space for the DRM memory manager. 608,637c610,612 (WW) intel(0): Register 0x68000 (TV_CTL) changed from 0x3000 to 0x000c0c00 (WW) intel(0): Register 0x68010 (TV_CSC_Y) changed from 0x to 0x0332012d (WW) intel(0): Register 0x68014 (TV_CSC_Y2) changed from 0x to 0x07d30104 (WW) intel(0): Register 0x68018 (TV_CSC_U) changed from 0x to 0x0733052d (WW) intel(0): Register 0x6801c (TV_CSC_U2) changed from 0x to 0x05c70200 (WW) intel(0): Register 0x68020 (TV_CSC_V) changed from 0x to 0x0340030c (WW) intel(0): Register 0x68024 (TV_CSC_V2) changed from 0x to 0x06d00200 (WW) intel(0): Register 0x68028 (TV_CLR_KNOBS) changed from 0x to 0x10606000 (WW) intel(0): Register 0x6802c (TV_CLR_LEVEL) changed from 0x to 0x010b00e1 (WW) intel(0): Register 0x68030 (TV_H_CTL_1) changed from 0x to 0x00400359 (WW) intel(0): Register 0x68034 (TV_H_CTL_2) changed from 0x to 0x80480022 (WW) intel(0): Register 0x68038 (TV_H_CTL_3) changed from 0x to 0x007c0344 (WW) intel
Re: last git xf86-video-intel have problem with video out xv
On Mon, 2007-07-30 at 13:37 -0700, Jesse Barnes wrote: Does Xv based video work again if you add Option tiling false to the Intel device section of your xorg.conf? no , seems that not obey to Option tiling false I try latest git and here is the xorg diff in attach Oh, you should also add Option FramebufferCompression false for that configuration... ok now with Option FramebufferCompression false vo(video output) xv working correctly but other strange thing continue (WW) intel(0): Option Legacy3D is not used (II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so xorg diff in attach Thanks , Jesse -- Sérgio M. B. 15c15 (==) Log file: /var/log/Xorg.0.log.good, Time: Mon Jul 30 21:55:27 2007 --- (==) Log file: /var/log/Xorg.0.log.bad, Time: Mon Jul 30 21:24:42 2007 390d389 (**) intel(0): Option FramebufferCompression false 661,662c660,662 (**) intel(0): Framebuffer compression disabled (**) intel(0): Tiling disabled --- (II) intel(0): Framebuffer compression enabled, forcing tiling on. (**) intel(0): Framebuffer compression enabled (**) intel(0): Tiling enabled 663a664 (II) intel(0): Framebuffer compression enabled 668,671c669,674 (II) intel(0): 0x0002-0x00029fff: HW cursors (40 kB, 0x1f82 physical) (II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB) (II) intel(0): 0x00032000-0x00032fff: overlay registers (4 kB, 0x1f832000 physical) (II) intel(0): 0x0004-0x01837fff: front buffer (24544 kB) --- (II) intel(0): 0x0002-0x0061: compressed frame buffer (6144 kB, 0x1f82 physical) (II) intel(0): 0x0062-0x00620fff: compressed ll buffer (4 kB, 0x1fe2 physical) (II) intel(0): 0x00621000-0x0062afff: HW cursors (40 kB, 0x1fe21000 physical) (II) intel(0): 0x0062b000-0x00632fff: logical 3D context (32 kB) (II) intel(0): 0x00633000-0x00633fff: overlay registers (4 kB, 0x1fe33000 physical) (II) intel(0): 0x00634000-0x00643fff: xaa scratch (64 kB) 673,676c676,679 (II) intel(0): 0x01838000-0x01847fff: xaa scratch (64 kB) (II) intel(0): 0x01848000-0x01c47fff: back buffer (4096 kB) (II) intel(0): 0x01c48000-0x02047fff: depth buffer (4096 kB) (II) intel(0): 0x02048000-0x04047fff: textures (32768 kB) --- (II) intel(0): 0x0080-0x00bf: back buffer (4096 kB) (II) intel(0): 0x00c0-0x00ff: depth buffer (4096 kB) (II) intel(0): 0x0200-0x03ff: front buffer (24544 kB) (II) intel(0): 0x0400-0x05ff: textures (32768 kB) 678,680c681,683 (II) intel(0): front buffer is not tiled (II) intel(0): back buffer is not tiled (II) intel(0): depth buffer is not tiled --- (II) intel(0): front buffer is tiled (II) intel(0): back buffer is tiled (II) intel(0): depth buffer is tiled 692,694c695,697 (II) intel(0): [drm] added 8192 byte SAREA at 0xe03ea000 (II) intel(0): [drm] mapped SAREA 0xe03ea000 to 0xb7f6e000 (II) intel(0): [drm] framebuffer handle = 0xc004 --- (II) intel(0): [drm] added 8192 byte SAREA at 0xe0105000 (II) intel(0): [drm] mapped SAREA 0xe0105000 to 0xb7f0c000 (II) intel(0): [drm] framebuffer handle = 0xc200 700,703c703,706 (II) intel(0): [drm] Front Buffer = 0x28008000 (II) intel(0): [drm] Back Buffer = 0xc1848000 (II) intel(0): [drm] Depth Buffer = 0xc1c48000 (II) intel(0): [drm] textures = 0xc2048000 --- (II) intel(0): [drm] Front Buffer = 0x2840 (II) intel(0): [drm] Back Buffer = 0xc080 (II) intel(0): [drm] Depth Buffer = 0xc0c0 (II) intel(0): [drm] textures = 0xc400 723,727c726,729 (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007bf000 (pgoffset 1983) (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01838000 (pgoffset 6200) (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x01848000 (pgoffset 6216) (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x01c48000 (pgoffset 7240) (II) intel(0): xf86BindGARTMemory: bind key 4 at 0x02048000 (pgoffset 8264) --- (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x0080 (pgoffset 2048) (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x00c0 (pgoffset 3072) (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0200 (pgoffset 8192) (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x0400 (pgoffset 16384) 830a833,842 Synaptics DeviceOff called (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xe0105000 at 0xb7f0c000 (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 1 (II) intel(0): xf86UnbindGARTMemory: unbind key 2 (II) intel(0): xf86UnbindGARTMemory: unbind key 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 3 smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find
Re: last git xf86-video-intel have problem with video out xv
On Mon, 2007-07-30 at 14:02 -0700, Jesse Barnes wrote: but other strange thing continue (WW) intel(0): Option Legacy3D is not used I will check this problem better I'm not sure about this option, it may be obsolete now... (II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so This is generally a good message since it means your 3D accel module was loaded correctly. yes but I use to have (II) AIGLX: Loaded and initialized /usr/lib/dri/i915tex_dri.so :) Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
last git xf86-video-intel have problem with video out xv
Hi , I done a bisect the git xf86-video-intel and here is the results: -- drv-intel bad vo xv: HEAD is now at 04130ac... Fix i915 rendering for tiled buffer version 1 bad vo xv: 88f8b688e2316ae4a1f7485f0010ce90de54783a HEAD is now at 88f8b68... Fix some physical address handling for 4GB addresses verison 2 bad vo xv: HEAD is now at 4359df9... Fix tiling and fb compression defaults for 965 (not yet fully supported). version 5 bad vo xv: HEAD is now at ca593a5... FBC and tiling changes version 6 good: 8798ef11321ee6957919279076758d47ad956cf3 HEAD is now at 8798ef1... Merge branch 'master' into fbc version 4 good: HEAD is now at 8919b22... Re-add tiling kludge, but only for 965 version 3 good: 3c552af65d28fafec1d09484a8914b690b961349 Update documentation and bump driver version to 2.1.0. and xorg diff of last good and first bad Xorg.log -- Sérgio M. B. 15c15 (==) Log file: /var/log/Xorg.0.log.good, Time: Sun Jul 29 19:19:26 2007 --- (==) Log file: /var/log/Xorg.0.log.bad, Time: Sun Jul 29 19:15:14 2007 462a463 (II) intel(0): fbc disabled 658a660,662 (II) intel(0): Framebuffer compression enabled, forcing tiling on. (**) intel(0): Framebuffer compression enabled (**) intel(0): Tiling enabled 660a665 (II) intel(0): Framebuffer compression enabled 665,668c670,675 (II) intel(0): 0x0002-0x00029fff: HW cursors (40 kB, 0x1f82 physical) (II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB) (II) intel(0): 0x00032000-0x00032fff: overlay registers (4 kB, 0x1f832000 physical) (II) intel(0): 0x0004-0x01837fff: front buffer (24544 kB) --- (II) intel(0): 0x0002-0x0061: compressed frame buffer (6144 kB, 0x1f82 physical) (II) intel(0): 0x0062-0x00620fff: compressed ll buffer (4 kB, 0x1fe2 physical) (II) intel(0): 0x00621000-0x0062afff: HW cursors (40 kB, 0x1fe21000 physical) (II) intel(0): 0x0062b000-0x00632fff: logical 3D context (32 kB) (II) intel(0): 0x00633000-0x00633fff: overlay registers (4 kB, 0x1fe33000 physical) (II) intel(0): 0x00634000-0x00643fff: xaa scratch (64 kB) 670,673c677,680 (II) intel(0): 0x01838000-0x01847fff: xaa scratch (64 kB) (II) intel(0): 0x01c0-0x01ff: back buffer (4096 kB) (II) intel(0): 0x0200-0x023f: depth buffer (4096 kB) (II) intel(0): 0x0240-0x043f: DRI memory manager (32768 kB) --- (II) intel(0): 0x0080-0x00bf: back buffer (4096 kB) (II) intel(0): 0x00c0-0x00ff: depth buffer (4096 kB) (II) intel(0): 0x0200-0x03ff: front buffer (24544 kB) (II) intel(0): 0x0400-0x05ff: DRI memory manager (32768 kB) 675c682 (II) intel(0): front buffer is not tiled --- (II) intel(0): front buffer is tiled 689,691c696,698 (II) intel(0): [drm] added 8192 byte SAREA at 0xe03ea000 (II) intel(0): [drm] mapped SAREA 0xe03ea000 to 0xb7f6b000 (II) intel(0): [drm] framebuffer handle = 0xc004 --- (II) intel(0): [drm] added 8192 byte SAREA at 0xe0105000 (II) intel(0): [drm] mapped SAREA 0xe0105000 to 0xb7f6d000 (II) intel(0): [drm] framebuffer handle = 0xc200 697,699c704,706 (II) intel(0): [drm] Front Buffer = 0x28008000 (II) intel(0): [drm] Back Buffer = 0xc1c0 (II) intel(0): [drm] Depth Buffer = 0xc200 --- (II) intel(0): [drm] Front Buffer = 0x2840 (II) intel(0): [drm] Back Buffer = 0xc080 (II) intel(0): [drm] Depth Buffer = 0xc0c0 718,721c725,727 (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007bf000 (pgoffset 1983) (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01838000 (pgoffset 6200) (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x01c0 (pgoffset 7168) (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x0200 (pgoffset 8192) --- (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x0080 (pgoffset 2048) (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x00c0 (pgoffset 3072) (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0200 (pgoffset 8192) 723a730 (II) intel(0): fbc disabled 825a833,841 Synaptics DeviceOff called (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xe0105000 at 0xb7f6d000 (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 1 (II) intel(0): xf86UnbindGARTMemory: unbind key 2 (II) intel(0): xf86UnbindGARTMemory: unbind key 0 smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915tex prerequisites
On Sat, 2007-07-28 at 04:54 +0100, Dave Airlie wrote: hum ! If kernel 2.6.22 have it, I am missing something, I had test with one kernel 2.6.22 and I am seeing one configuration of kernel 2.6.23-git22 and I don't see any linux-agp-compat or it is supposed be on AGP_INTEL ? . It's in 2.6.21 and later, it is just a part of agp, nothing special about compat or otherwise, I haven't used linux-agp-compat in a while. a030ce4477baa06dd9c037ccd3c8d171aac9ed44 is the kernel git commitid I had try enable i915tex, with kernel 2.6.22 and with git drm/linux-core compiled against this kernel, but don't enable i915tex. ah ! with kernel 2.4.22 I have this message (II) intel(0): direct rendering: Enabled (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. (EE) intel(0): Could not initialize the DRM memory manager. (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xe032 at 0xb7fd2000 (--) RandR disabled now I see 3 different bugs 1 - drm last git drm don't work 2 - last git xf86-video-intel have problem with video out xv 3 - the kernel 2.4.22 gives this problem. I put xf86-video-intel with version 2.0.0-4 from fedora I done a git reset bc7d6c76fab2ff4d2f11b6bd84ca8b8f124729fd on git drm compile linux-agp-compat and drm on kernel 2.4.20 and enable i915tex ! . reboot and use kernel 2.6.22 compile the same drm code against kernel 2.4.22 and after reboot again I got the above message . I have to go I waste many time to unreset the reset, I don't handle git very well and lose many time with it :( Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915tex prerequisites
On Fri, 2007-07-27 at 01:25 +0100, Dave Airlie wrote: 2nd - will linux-agp-compat enter in kernel main stream ? It's been in the kernel for a while.. 2.6.21 has it but I've no idea when it went in.. hum ! If kernel 2.6.22 have it, I am missing something, I had test with one kernel 2.6.22 and I am seeing one configuration of kernel 2.6.23-git22 and I don't see any linux-agp-compat or it is supposed be on AGP_INTEL ? . I had try enable i915tex, with kernel 2.6.22 and with git drm/linux-core compiled against this kernel, but don't enable i915tex. I don't understand this, If we have mesa/linux-agp-compat on kernel, drm should work out of the box, no?. kernel have one drm that could enable i915tex. btw, I have an compiling error when I compile linux-agp-compat against kernel-2.6.22.1-33.fc7 custom or 2.6.23-rc1 Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
i915tex prerequisites
Since last email about this subject (3 of July) , I had installed i915tex on my laptop , and I had working without problems . Michel suggest when install linux-agp-compat instead of delete Module.symvers I append the Module(s).symvers file generated by linux-agp-compat to the kernel's file of the same name with cat before building the DRM. And works quite well. So this could be add mesa/linux-agp-compat/README 2nd - will linux-agp-compat enter in kernel main stream ? Thanks, -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Fw: Re: [Mesa3d-users] i915tex prerequisites
On Thu, 2007-06-28 at 17:12 +0200, Ulrich von Zadow wrote: Sergio Monteiro Basto schrieb: On Thu, 2007-03-01 at 19:30 +, Sergio Monteiro Basto wrote: (Yup, took me several months to actually get around to this...) you have to do something like this: make ll *ko su after install agp-compat you have to do something like this: rm drm/ -rf git clone git://anongit.freedesktop.org/git/mesa/drm cd drm/linux-core/ make Ok, I've got working mesa, libdrm and X running here, all with git versions. I'm loading the following modules: agpgart.ko, intel-agp.ko (from git://anongit.freedesktop.org/git/mesa/linux-agp-compat) drm.ko, i915.ko (from Xorg git) The dri drivers from git are used as well. I still get no i915tex driver. Some parts of the Xorg log that look relevant to my untrained eyes follow: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [...] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33 (II) Primary Device is: PCI 00:02:0 (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) Chipset 945GM found [...] (WW) intel(0): Bad V_BIOS checksum [...] (WW) intel(0): VideoRam configuration found, which is no longer recommended. (II) intel(0): Continuing with default 262144kB VideoRam instead of 131072 kB. [...] (EE) intel(0): Failed to init memory manager [...] (EE) intel(0): I830 Vblank Pipe Setup Failed 0 [...] ...and I've attached the complete Xorg.log as well. you got on Xorg.log AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so should have AIGLX: Loaded and initialized /usr/lib/dri/i915tex_dri.so I'd be grateful for any ideas, and if I'm running into a bug, I'd be happy to help fix it. -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
915tex prerequisites, agpgart.ko, intel-agp.ko from git/mesa/linux-agp-compat
Hi is there anyway put and compile this linux-agp-compat on / with kernel, and subsequently not delete symbol versions ? Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Fwd: [PATCH -mm] working 3D/DRI intel-agp.ko resume for i815 chip; Intel chipset testers wanted! (was: Re: intel-agp PM experiences ...)]
Hi forward this message to dri-devel Mailing List, where you could find more tester on i815 DRI drives . I hope I don't had made a loop :) Forwarded Message From: Andreas Mohr [EMAIL PROTECTED] To: Pavel Machek [EMAIL PROTECTED] Cc: Andrew Morton [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], Matthew Garrett [EMAIL PROTECTED], kernel list [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [PATCH -mm] working 3D/DRI intel-agp.ko resume for i815 chip; Intel chipset testers wanted! (was: Re: intel-agp PM experiences ...) Date: Tue, 1 May 2007 16:59:47 +0200 Hi, On Thu, Jan 18, 2007 at 11:16:51PM +, Pavel Machek wrote: Hi! Especially the PCI video_state trick finally got me a working resume on 2.6.19-ck2 r128 Rage Mobility M4 AGP *WITH*(!) fully enabled and working (and keeping working!) DRI (3D). Can we get whitelist entry for suspend.sf.net? s2ram from there can do all the tricks you described, one letter per trick :-). We even got PCI saving lately. Whitelist? Let me blacklist it all the way to Timbuktu instead! I've been doing more testing, and X never managed to come back to working state without some of my couple intel-agp changes: - a proper suspend method, doing a proper pci_save_state() or improved equivalent - a missing resume check for my i815 chipset - global cache flush in _configure - restoring AGP bridge PCI config space Can you post a patch? Took way longer than I'd have wanted it to (nice daughter and stuff ;), but here it is. - add .suspend handler and pci_set_power_state() calls - add i815-specific function agp_i815_remember_state() to remember important i815 register values - add generic DEBUG_AGP_PM framework which will allow people to resume properly and help identify which registers need attention - add obvious and detailed log message to make people sit up and take notice about long-standing AGP resume issues - spelling fixes Patch against 2.6.21-rc7-mm2, my Inspiron 8000 (i815 with Radeon AGP card, internal Intel VGA unit NOT active) resumes fine with both either i815-specific register saving or generic DEBUG_AGP_PM mechanism enabled. (of course my notebook needs vbetool post and manual saving of video card PCI space, too, but even when doing all this I still had X.org lockups before whenever DRI/3D was enabled) After resume I'm now still able to run both glxgears and glxinfo without anomalies. Right now all I care about is that this gets into mainline relatively soon, since I'm rather certain that many other machines suffer from similar AGP resume lockup issues that could be debugged this way (e.g. some Thinkpads, as witnessed accidentally via IRC chats, and from the well-known don't enable DRI, that will lock up on resume! chants). Yes, this code is a cludge and somewhat far from a nicely generic extended PCI space resume framework, but we've spent almost 10 (TEN!) years without anything even remotely resembling a working cludge for AGP suspend/resume in combination with DRI, so... Feel free to offer thoughts on how this missing generic extended PCI space restore functionality could be implemented, to be used by intel-agp and various other drivers. No promise that it will be me who implements that, though ;) Whitelist entry would still be welcome. OK, I'll work on this next. Thanks! Signed-off-by: Andreas Mohr [EMAIL PROTECTED] --- linux-2.6.21-rc7-mm2.orig/drivers/char/agp/intel-agp.c 2007-05-10 14:52:26.0 +0200 +++ linux-2.6.21-rc7-mm2/drivers/char/agp/intel-agp.c 2007-05-10 14:31:48.0 +0200 @@ -31,9 +31,16 @@ extern int agp_memory_reserved; -/* Intel 815 register */ -#define INTEL_815_APCONT 0x51 -#define INTEL_815_ATTBASE_MASK ~0x1FFF +/* Intel i815 registers, see Intel spec #29068801 */ +#define I815_GMCHCFG 0x50 +#define I815_APCONT0x51 +#define I815_UNKNOWN_800x80 +#define I815_ATTBASE_MASK ~0x1FFF +#define I815_SM_RCOMP 0x98 /* Sys Mem R Compensation Ctrl */ +#define I815_SM0x9c /* System Memory Control Reg */ +#define I815_AGPCMD0xa8 /* AGP Command Register */ +#define I815_ERRSTS0xc8 /* undocumented in i815 spec; since this one is modified on resume and many other related chipsets have it, I assume it *is* ERRSTS */ +#define I815_UNKNOWN_E80xe8 /* Intel i820 registers */ #define INTEL_I820_RDCR0x51 @@ -664,7 +671,7 @@ if ((pg_start + mem-page_count) num_entries) goto out_err; - /* The i830 can't check the GTT for entries since its read only, + /* The i830 can't check the GTT for entries since it's read-only, * depend on the caller to make the correct offset decisions. */ @@ -787,7 +794,7 @@ if ((pg_start + mem-page_count) num_entries) goto out_err; - /* The i915 can't check the GTT for entries since
Re: Can't find list archives
On Tue, 2007-04-03 at 15:57 -0700, Tonko Juricic wrote: List subscription page has a link to list archives that, clicked, can not be found on sourceforge. Where can I find archives for this list? Thanks Sorry I had make a big confusion, this is dri-devel not acpi-devel as I had though. The archives are on : http://sourceforge.net/mailarchive/forum.php?forum_name=dri-devel from https://lists.sourceforge.net/lists/listinfo/dri-devel the link is wrongly to http://sourceforge.net/mailarchive/forum.php?forum=dri-devel this issue should be report on http://sourceforge.net/support/getsupport.php Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Can't find list archives
Now the list is acpi devel, linux-acpi@vger.kernel.org On Tue, 2007-04-03 at 15:57 -0700, Tonko Juricic wrote: List subscription page has a link to list archives that, clicked, can not be found on sourceforge. Where can I find archives for this list? Thanks Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: xf86-video-i810 has become xf86-video-intel ?
On Mon, 2007-03-26 at 09:48 +0800, Jin, Gordon wrote: Sergio Monteiro Basto wrote: Hi, this two drives is for same intels ? http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i810-1 .7.4.tar.gz http://xorg.freedesktop.org/releases/individual/driver/xf86-video-intel- 1.9.92.tar.bz2 I have one i915 what should I use ? Yes, the driver name has been changed from i810 to intel. So if you want to use the new code, you'd choose xf86-video-intel-1.9.92. The driver supports all Intel chipsets after i810. Hi! let me check :) Thanks for information -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
xf86-video-i810 has become xf86-video-intel ?
Hi, this two drives is for same intels ? http://xorg.freedesktop.org/releases/individual/driver/xf86-video-i810-1.7.4.tar.gz http://xorg.freedesktop.org/releases/individual/driver/xf86-video-intel-1.9.92.tar.bz2 I have one i915 what should I use ? -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
compiling new xf86-video-intel drive
Hi , I need your help , I am trying compile intel video drive and give me this: checking for xf86Modes.h... no symlink mode code configure: error: Must have X server = 1.3 source tree for mode setting code. Please specify --with-xserver-source + exit 1 what I need upgrade is just xorg-x11-server-Xorg-1.1.1 ? Tanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: compiling new xf86-video-intel drive
On Sat, 2007-03-17 at 12:44 -0700, Keith Packard wrote: On Sat, 2007-03-17 at 16:41 +, Sergio Monteiro Basto wrote: Hi , I need your help , I am trying compile intel video drive and give me this: checking for xf86Modes.h... no symlink mode code configure: error: Must have X server = 1.3 source tree for mode setting code. Please specify --with-xserver-source If you aren't building from the RC tarball, I am using lastest git you'll need some source files from the X server which include new functionality that can be built into the driver when compiling for older servers. The tarball includes the needed files; if you're trying that and it isn't working, then there's a build bug. Ok but where is rc tarballs ? Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Hown compile and install linux-agp-compat
On Tue, 2007-02-06 at 21:46 +, Sergio Monteiro Basto wrote: Does your kernel config enable agpgart and intel-agp as modules? no , is compiled into kernel CONFIG_AGP=y CONFIG_AGP_ALI=y CONFIG_AGP_ATI=y CONFIG_AGP_AMD=y CONFIG_AGP_AMD64=y CONFIG_AGP_INTEL=y CONFIG_AGP_NVIDIA=y CONFIG_AGP_SIS=y CONFIG_AGP_SWORKS=y CONFIG_AGP_VIA=y CONFIG_AGP_EFFICEON=y is required be compiled has module ? I use fedora stock kernels, which are more than updated (devel ones) , so I need to know If I need recompile all kernel with agpgart and intel-agp as modules ? Thanks, PS: I just finish to read yours README - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: 2.6.20 [drm:i915_wait_irq] *ERROR*
On Wed, 2007-02-07 at 11:25 +1100, Dave Airlie wrote: I'm running a 2.6.20 kernel on my macbook. When running an openGL application, if the opengl window's region is moved somewhere outside the screen limits, then keyboard locks, I can only move the mouse, nothing response. I can only reboot the box by pressing the power button 5 seconds. /var/log/syslog contains that : kernel: [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 730561 emitted: 730570 The macbook uses an intel card : 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) I'm cc'ing dri devel in case anyone there knows why this might happen... Dave. maybe try disable : Section ServerFlags Option AIGLX off EndSection Section Extensions Option Composite Disable EndSection and use: Option Legacy3D true - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: 2.6.20 [drm:i915_wait_irq] *ERROR*
On Wed, 2007-02-07 at 17:19 +0100, Lionel Landwerlin wrote: Le mercredi 07 février 2007 à 14:34 +, Sergio Monteiro Basto a écrit : On Wed, 2007-02-07 at 11:25 +1100, Dave Airlie wrote: I'm running a 2.6.20 kernel on my macbook. When running an openGL application, if the opengl window's region is moved somewhere outside the screen limits, then keyboard locks, I can only move the mouse, nothing response. I can only reboot the box by pressing the power button 5 seconds. /var/log/syslog contains that : kernel: [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 730561 emitted: 730570 The macbook uses an intel card : 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) I'm cc'ing dri devel in case anyone there knows why this might happen... Dave. maybe try disable : Section ServerFlags Option AIGLX off EndSection Section Extensions Option Composite Disable EndSection and use: Option Legacy3D true I need the lastest i915 xorg driver, where can I find it ? http://xorg.freedesktop.org/releases/individual/driver/?C=M;O=D and drm see http://dri.freedesktop.org/wiki/Building rm drm/ -rf git clone git://anongit.freedesktop.org/git/mesa/drm cd drm/linux-core/ make KERNEL=`uname -r` cp drm.ko i810.ko i915.ko /lib/modules/$KERNEL/kernel/drivers/char/drm ll *ko su KERNEL=`uname -r` mv /lib/modules/$KERNEL/kernel/drivers/char/drm drm.backup mkdir -p /lib/modules/$KERNEL/kernel/drivers/char/drm cp *.ko /lib/modules/$KERNEL/kernel/drivers/char/drm ll /lib/modules/$KERNEL/kernel/drivers/char/drm depmod -a $KERNEL Is it going to disable AIGLX ? I mean, is it still possible to run window manager like beryl using this configuration ? of course not , - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Hown compile and install linux-agp-compat
What is wrong ? I am using FC6 git-clone git://git.freedesktop.org/git/mesa/linux-agp-compat cd linux-agp-compat/ make cc -I. -o testgart testgart.c make -C /lib/modules/2.6.19-1.2895.fc6/build SUBDIRS=/home/sergio/Mesa/linux-agp-compat modules make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686' Building modules, stage 2. MODPOST 0 modules make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686' su - ./testgart Using AGPIOC_ACQUIRE ioctl(AGPIOC_ACQUIRE): Device or resource busy - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Hown compile and install linux-agp-compat
On Tue, 2007-02-06 at 19:51 +0100, Thomas Hellström wrote: git-clone git://git.freedesktop.org/git/mesa/linux-agp-compat cd linux-agp-compat/ make cc -I. -o testgart testgart.c make -C /lib/modules/2.6.19-1.2895.fc6/build SUBDIRS=/home/sergio/Mesa/linux-agp-compat modules make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686' Building modules, stage 2. MODPOST 0 modules make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686' My problem is here, MODPOST 0 modules ? No modules are created Hmm, Testgart is only an application that slipped in. Not really needed, but I think the problem is that the X server has already acquired AGP. Try without the X server running. Also make sure you take a look at the README what README ? before trying to run any DRI apps. Thanks, - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Hown compile and install linux-agp-compat
On Tue, 2007-02-06 at 21:27 +0100, Thomas Hellström wrote: On Tue, 2007-02-06 at 19:51 +0100, Thomas Hellström wrote: git-clone git://git.freedesktop.org/git/mesa/linux-agp-compat cd linux-agp-compat/ make cc -I. -o testgart testgart.c make -C /lib/modules/2.6.19-1.2895.fc6/build SUBDIRS=/home/sergio/Mesa/linux-agp-compat modules make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686' Building modules, stage 2. MODPOST 0 modules make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686' My problem is here, MODPOST 0 modules ? No modules are created Does your kernel config enable agpgart and intel-agp as modules? no , is compiled into kernel CONFIG_AGP=y CONFIG_AGP_ALI=y CONFIG_AGP_ATI=y CONFIG_AGP_AMD=y CONFIG_AGP_AMD64=y CONFIG_AGP_INTEL=y CONFIG_AGP_NVIDIA=y CONFIG_AGP_SIS=y CONFIG_AGP_SWORKS=y CONFIG_AGP_VIA=y CONFIG_AGP_EFFICEON=y is required be compiled has module ? what README ? Seems like that last commit never got pushed. Will fix tomorrow. OK Thanks, -- Sérgio M. B. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
compile linux-core/drm_bo.o problem
Hi , following the tip on http://bugzilla.kernel.org/show_bug.cgi?id=7767 I also install kernel 2.6.19-1.2917.fc7 and kernel-devel but I can't compile git drm because give me the following error CC [M] /home/sergio/Mesa/drm/linux-core/drm_bo.o /home/sergio/Mesa/drm/linux-core/drm_bo.c: In function ‘drm_bo_cleanup_refs’: /home/sergio/Mesa/drm/linux-core/drm_bo.c:238: warning: passing argument 1 of ‘schedule_delayed_work’ from incompatible pointer type /home/sergio/Mesa/drm/linux-core/drm_bo.c: In function ‘drm_bo_delayed_workqueue’: /home/sergio/Mesa/drm/linux-core/drm_bo.c:356: warning: passing argument 1 of ‘schedule_delayed_work’ from incompatible pointer type /home/sergio/Mesa/drm/linux-core/drm_bo.c: In function ‘drm_bo_driver_finish’: /home/sergio/Mesa/drm/linux-core/drm_bo.c:1870: warning: passing argument 1 of ‘cancel_delayed_work’ from incompatible pointer type /home/sergio/Mesa/drm/linux-core/drm_bo.c:1914:51: error: macro INIT_WORK passed 3 arguments, but takes just 2 /home/sergio/Mesa/drm/linux-core/drm_bo.c: In function ‘drm_bo_driver_init’: /home/sergio/Mesa/drm/linux-core/drm_bo.c:1914: error: ‘INIT_WORK’ undeclared (first use in this function) /home/sergio/Mesa/drm/linux-core/drm_bo.c:1914: error: (Each undeclared identifier is reported only once /home/sergio/Mesa/drm/linux-core/drm_bo.c:1914: error: for each function it appears in.) make[2]: *** [/home/sergio/Mesa/drm/linux-core/drm_bo.o] Error 1 make[1]: *** [_module_/home/sergio/Mesa/drm/linux-core] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2917.fc7-i686 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915 trouble -- IRQ being disabled
Well, my report is using FC6 xorg-x11-apps-7.1 Try with one kernel 2.6.15 and kernel 2.6.19 (no differences) . Fedora updates have libdrm-2.3.0. And I just update from FC6 release, mesa-libGL-6.5.2 and xorg-x11-drv-i810-1.7.4. Which live me the conclusion that could be a problem on new release of Xorg, Xorg-7.1.1 btw : what should I have installed to test drv-i810 properly ? On Tue, 2007-01-30 at 14:52 +0100, Thomas Hellström wrote: Michel Dänzer wrote: On Tue, 2007-01-30 at 12:42 +0100, Thomas Hellström wrote: There seems to be some hardware problems with some i915s: Some chips duplicate the display IRQs on the sound IRQ lines which causes the kernel to detect unhandled IRQs on the sound line and disable it after a while. This can be worked around using an option to the sound driver. It sounds like this shouldn't affect the IRQ handling of the DRM itself though, does it? No, it shoudn't. The other problem is that when user IRQs are turned off, more often than not the display chip starts to issue false IRQs which are not reflected in the status registers. Eventually the kernel turns the IRQ line off. I ran into this when I tried to turn off IRQs when the fence driver didn't need them. It might be the problem in this case. You mean i915_driver_irq_uninstall() could trigger this problem? Yes, possibly. Intel doesn't seem to be aware of the problem. Otherwise, I'm wondering if it could be related to Zou Nan hai's recent vblank interrupt fix. OK. /Thomas - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915 trouble -- IRQ being disabled
anything related with this issue ? https://bugs.freedesktop.org/show_bug.cgi?id=9200#c8 On Sun, 2007-01-28 at 22:14 -0500, Dominik Brodowski wrote: Hi, When I switch from the X Window System Version 7.1.1 console to a terminal, IRQ 10: 10: 20XT-PIC-XTuhci_hcd:usb1, ehci_hcd:usb4, yenta, yenta, [EMAIL PROTECTED]::00:02.0 gets disabled (irq 10: nobody cared). The hardware is 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) and I was able to git bisect it down to the drm patches which went in after 2.6.19 and before 2.6.19-rc1 got released. While I have some other issues related to that IRQ line (usb autosuspend can causes the IRQ 10 becoming disabled, too), this issue only appeared once the drm/i915 patches got merged, so I logically derive that this is a separate issue. Any ideas? Any debugging you want me to do? Dominik - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Quake4 benchmarks
http://www.nuclearelephant.com/papers/s3tc.html http://homepage.hispeed.ch/rscheidegger/dri_experimental/s3tc_index.html And I has problems with one ATI mobile r300 and Xorg 6.8.2 from Fedora 4, and now with Xorg 7.0 it works quite right, and I try to see what is the trick and appears to me not just disabling dri but disable ACCEL render! . On Tue, 2006-05-23 at 19:18 -0400, Adam K Kirchhoff wrote: FYI, I downloaded the hwspirit timedemo for quake4 yesterday and decided to compare the framerate between the fglrx, r200, and xig drivers with my Radeon 9000: 9000 - xig - 14.7 9000 - fgl - 11.3 9000 - xorg - 16.2 Today I decided to give it a shot with my 9600. The fglrx drivers gave me 16.8 FPS, and the r300 drivers gave me this: http://68.44.156.246/quake4-screenshot.png As you can see, everything is quite shiny (but not quite as washed out as the screenshot shows... I had to brighten it a little to make it visible). This is with both page flipping and color tiling enabled (though I tried without page flipping and got the same results). And I have the libtxc_dxtn library compiled and installed. If I remove that library, quake4 completely refuses to start: ..using GL_ARB_multitexture ...using GL_ARB_texture_env_combine ...using GL_ARB_texture_cube_map ...using GL_ARB_texture_env_dot3 ...using GL_ARB_texture_env_add X..GL_ARB_texture_non_power_of_two not found ...using GL_NV_blend_square ...using GL_ARB_texture_compression X..GL_EXT_texture_compression_s3tc not found signal caught: Segmentation fault si_code 1 Trying to exit gracefully.. Any ideas? --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature
Re: [Mesa3d-announce] Re: [Mesa3d-users] Mesa 6.4.2 released
Hi Dave What are you talking about ? modular X ? Where I can find documentation for this new organization ? I don't found any on freedesktop wikis . On Tue, 2006-02-28 at 03:11 +, Dave Airlie wrote: There is no DRI drivers in X tree anymore.. there is no Mesa in X tree anymore... there is no X tree anymore.. Dave. -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: [Mesa3d-announce] Re: [Mesa3d-users] Mesa 6.4.2 released
On Mon, 2006-02-20 at 22:41 +0100, Roland Scheidegger wrote: Sergio Monteiro Basto wrote: On Sat, 2006-02-04 at 11:04 -0700, Brian Paul wrote: Sergio Monteiro Basto wrote: Includes updates of the DRI drivers and GLX code ? I don't recall any DRI/GLX check-ins to the 6.4 branch. It's up to the DRI developers to check in bug fixes to the stable branch, but that doesn't happen too often, unfortunately. Hi, Brian I had thinking, thinking and came up this idea. You may make some releases of stable branch with updates of DRI Drives. In times to times, because Mesa is very mature and DRI drives aren't. Like putting the Development of DRI drives in Stable branch. And in official page of building DRI, ask to use stable branch of Mesa. With this formula we can update Xorg CVS with DRI drives more often, and most important, we can put users testing code more similar. You can't just copy the dri directory from cvs head to the stable branch, if you're suggesting something like that, this usually won't compile (as internal functions/structs etc. change). FWIW, I usually do update the stable branch (if I don't forget it...), but only for bugfixes, you won't see new features / optimizations or similar from me in the stable branch (unless I'd be asked to commit it there or I'd think this really warrants an exception). So 6.4 branch got that no-tcl blender fix (it's newer than the 6.4.2 release though), but it doesn't contain things like r100 cube maps. To test last features of DRI drives, you should need lastest drives of X tree, but to test latest Mesa3D it self you don't need it latest X. Before the development of DRI has move to Mesa tree, the development was made using always the same Mesa3D code. Therefore I think DRI developers should update Mesa stable branch, not just with bug fix , but also with new features / optimizations. At same time that update driver on Xorg tree. If this is made, DRI Building should be done with Mesa stable branch and more quickly dri code enter in Xorg tree, where could be test without snapshots, therefore the Distros could put the code out faster and can be tested for a much bigger number of people. This is my ideia . Roland -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: [Bug 1709] mesa_test_os_sse_exception_support fails inside gdb
On Sat, 2005-12-17 at 14:20 -0800, Ian Romanick wrote:
There are several files, including
mesa/glapi/{glapioffsets,dispatch}.h
and mesa/main/{context,api_arrayelt}.c that depend on IN_DRI_DRIVER
being set properly. If it's not set, the drivers *will* be built
incorrectly. These are all pretty important.
Well this statement is important (at least to me). This means that my
patches are far way to be correct.
lib/GL/glx needs also IN_DRI_DRIVER because this dir have glapi.c from
mesa/glapi/ and Imakefile have -I$(MESASRCDIR)/src/mesa/glapi
and xc/programs/Xserver/GL/mesa also misses the Defines IN_DRI_DRIVER.
thanks,
--
Sérgio M.B.
smime.p7s
Description: S/MIME cryptographic signature
Re: [Bug 1709] mesa_test_os_sse_exception_support fails inside gdb
Hi Ajax, Please also see bug #5057 At my point of view defines IN_DRI_DRIVER and USE_EXTERNAL_DXTN_LIB=1 are very specific and only used in Mesa. So the patch on bug #5057 ( the last one ) or something similar, don't see what problems can cause on applying it. thanks, On Thu, 2005-12-15 at 15:45 -0800, [EMAIL PROTECTED] wrote: Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=1709 [EMAIL PROTECTED] changed: What|Removed |Added OtherBugsDependingO|1690| nThis|| --- Additional Comments From [EMAIL PROTECTED] 2005-12-16 10:40 --- withdrawn, far too late in the process now. Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: [Dri-users] Stuck with FC4 / i915 Graphics
On Wed, 2005-12-07 at 10:53 +0100, Joachim Frieben wrote: There is no need to tweak xorg.cf Well the philosophy of the patches in .specs, is to be upstream into Xorg sources. BTW: So all the patches there, except customizations, still candidates to be upstream. in order to build experimental DRI drivers. This is easily done in xorg.spec by adding savage to DevelDRIDrivers and setting #define BuildDevelDRIDrivers YES Savage no longer need be a DevelDRIDriver, you can put it on DRIDrivers without needing #define BuildDevelDRIDrivers YES btw, the site is updated ! :) http://sergiomb.no-ip.org/xorg/xorgRC3 -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: [Dri-users] Stuck with FC4 / i915 Graphics
btw, the site is updated ! :) http://sergiomb.no-ip.org/xorg/xorgRC3 On Tue, 2005-12-06 at 22:42 +0800, Steph wrote: Ok, here is what I have installed: Fedora Core 4, Updated using Yum, Using xorg-x11-6.8.99.14-3 from here (http://sergiomb.no-ip.org/xorg/xorgRC2/ - followed the instructions on that page to install it). I have a motherboard with the Intel 915 chipset on it. This statement is a little confuse, you update Fedora with yum and build rpms with xorg-x11-6.8.99.902 sources is that it ? -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: Missing some Mesa Defines in xorg-6.9 build, final patch
On Sun, 2005-12-04 at 03:09 +0100, Roland Scheidegger wrote: Otherwise, I'm unsure what the -DPTHREADS and -DHAVE_ALIAS switches actually do. Maybe they conflict with other options (some xthreads stuff maybe?) which are used in the xorg build. Yes , remove -DPTHREADS and -DHAVE_ALIAS switches, resolve the problem Now, on my r200, glxinfo|grep s3tc I got: GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_compression_s3tc, GL_SGIS_texture_lod, GL_S3_s3tc but q3demo still say that I don't find texture compression cat q3demo2.log | grep GL_S3_s3tc Mesa: Mesa GL_EXTENSIONS = GL_ARB_imaging GL_ARB_multisample GL_ARB_multitexture GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_compiled_vertex_array GL_EXT_convolution GL_EXT_copy_texture GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_histogram GL_EXT_packed_pixels GL_EXT_polygon_offset GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texture GL_EXT_texture3D GL_EXT_texture_compression_s3tc GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_vertex_array GL_APPLE_packed_pixels GL_ATI_blend_equation_separate GL_ATI_texture_env_combine3 GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_INGR_blend_func_separate GL_MESA_pack_invert GL_MESA_ycbcr_texture GL_MESA_window_pos GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texture_rectangle GL_NV_texgen_reflection GL_NV_vertex_program GL_OES_read_format GL_SGI_color_matrix GL_SGI_color_table GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_S3_s3tc ...GL_S3_s3tc not found strange Anyway q3demo runs faster Here it goes the patch that I think that should be applied on Xorg-6.9, enables 2 defines, one needed and test it on my Athlon with one Savage (bug #1709) and other on one r200 (bug #5057). I had be careful about just enable switches ifdef BuildXF86DRI. This 2 Defines doesn't appear to be crucial to a good building of Xorg monolithic tree, so my personal opinion aren't blockers but are the correct way of compiling Mesa on Xorg-6.9 build. Roland I am writing to you because hope that you can review, approved and get submit this patch :). thanks, -- Sérgio M.B. --- xc/lib/GL/mesa/array_cache/Imakefile.orig 2005-11-18 21:02:13.0 + +++ xc/lib/GL/mesa/array_cache/Imakefile 2005-11-18 21:03:02.0 + @@ -36,7 +36,7 @@ #endif #if BuildXF86DRI - DRI_DEFINES = GlxDefines + DRI_DEFINES = GlxDefines -DIN_DRI_DRIVER -DUSE_EXTERNAL_DXTN_LIB=1 DRI_INCLUDES = -I../../../dri -I../../../glx -I../../dri -I../../../include \ -I$(INCLUDESRC)/GL -I$(XF86OSSRC) -I$(SERVERSRC)/GL/dri #endif --- xc/lib/GL/mesa/main/Imakefile.orig 2005-11-18 21:03:21.0 + +++ xc/lib/GL/mesa/main/Imakefile 2005-11-18 21:03:44.0 + @@ -44,7 +44,11 @@ MATH_DEFINES = -DCCPML #endif - DEFINES = $(ALLOC_DEFINES) GlxDefines \ +#if BuildXF86DRI + DRI_DEFINES = -DIN_DRI_DRIVER -DUSE_EXTERNAL_DXTN_LIB=1 +#endif + + DEFINES = $(ALLOC_DEFINES) GlxDefines $(DRI_DEFINES) \ $(MESA_ASM_DEFINES) $(MATH_DEFINES) INCLUDES = /*-I$(INCLUDESRC) -I$(EXTINCSRC) */ -I$(XINCLUDESRC) \ -I$(MESASRCDIR)/src/mesa/glapi \ --- xc/lib/GL/mesa/math/Imakefile.orig 2005-11-18 21:04:22.0 + +++ xc/lib/GL/mesa/math/Imakefile 2005-11-18 21:04:42.0 + @@ -42,7 +42,7 @@ #endif #if BuildXF86DRI - DRI_DEFINES = GlxDefines + DRI_DEFINES = GlxDefines -DIN_DRI_DRIVER -DUSE_EXTERNAL_DXTN_LIB=1 DRI_INCLUDES = -I../../../dri -I../../../glx -I../../dri -I.. \ -I$(INCLUDESRC)/GL -I$(XF86OSSRC) -I$(SERVERSRC)/GL/dri #endif --- xc/lib/GL/mesa/shader/Imakefile.orig 2005-11-18 21:05:25.0 + +++ xc/lib/GL/mesa/shader/Imakefile 2005-11-18 21:05:42.0 + @@ -41,7 +41,7 @@ #endif #if BuildXF86DRI - DRI_DEFINES = GlxDefines + DRI_DEFINES = GlxDefines -DIN_DRI_DRIVER -DUSE_EXTERNAL_DXTN_LIB=1 DRI_INCLUDES = -I../../../dri -I../../../glx -I../../dri -I.. \ -I$(INCLUDESRC)/GL -I$(XF86OSSRC) -I$(SERVERSRC)/GL/dri #endif --- xc/lib/GL/mesa/shader/grammar/Imakefile.orig 2005-11-18 21:07:19.0 + +++ xc/lib/GL/mesa/shader/grammar/Imakefile 2005-11-18 21:07:35.0 + @@ -41,7 +41,7 @@ #endif #if BuildXF86DRI - DRI_DEFINES = GlxDefines + DRI_DEFINES = GlxDefines
Missing some Mesa Defines in xorg-6.9 build
Hi Roland, I am trying testing s3tc with q3demo adding -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DHAVE_ALIAS but I am getting this error : Mesa 6.4.1 implementation error: bad S wrap mode in r200SetTexWrap Please report at bugzilla.freedesktop.org Mesa 6.4.1 implementation error: bad T wrap mode in r200SetTexWrap Please report at bugzilla.freedesktop.org Mesa 6.4.1 implementation error: bad R wrap mode in r200SetTexWrap Please report at bugzilla.freedesktop.org any idea of what this might be ? Thanks, On Sat, 2005-12-03 at 05:23 +0100, Roland Scheidegger wrote: Sergio Monteiro Basto wrote: Xorg build also misses -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DHAVE_ALIAS Ian, and those ones are needed ? Can't comment on the others (though usually care must be taken with the threading stuff!), but not having -DUSE_EXTERNAL_DXTN_LIB=1 will obviously cause it to not support s3tc with the external library (I had already filed a bug about this, https://bugs.freedesktop.org/show_bug.cgi?id=5057). have you any sampler where I can test s3tc on my r200 ? I having been trying test it with nfsu2 game but it is cracked and doesn't start. for software compression (and hw decompression), quake3 (and other games using the same engine) is a good test (you can actually see some slight artifacts in the main game menu due to the compression (r_ext_compressed_textures 1), though it is smart enough to only use it if the extension is available. Roland -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: [PATCH] add -DIN_DRI_DRIVER to xorg-6.9 build [was Re: problem found with new xorg-6.9RC2 on savage with DRI enabled]
On Mon, 2005-11-21 at 19:15 +0100, Roland Scheidegger wrote: Xorg build also misses -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DHAVE_ALIAS Ian, and those ones are needed ? Can't comment on the others (though usually care must be taken with the threading stuff!), but not having -DUSE_EXTERNAL_DXTN_LIB=1 will obviously cause it to not support s3tc with the external library (I had already filed a bug about this, https://bugs.freedesktop.org/show_bug.cgi?id=5057). have you any sampler where I can test s3tc on my r200 ? I having been trying test it with nfsu2 game but it is cracked and doesn't start. As side note I haven't the minimum idea, what side effect this could cause on non Linux or BSD systems. Since the code in question is only built on systems which support dri, there shouldn't be any problems I suspect. The glx server code is built elsewhere (and as a side note, it can't use -DUSE_EXTERNAL_DXTN_LIB=1, at least last time I tried it was not possible to use the dl functions directly). Roland -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: [PATCH] add -DIN_DRI_DRIVER to xorg-6.9 build [was Re: problem found with new xorg-6.9RC2 on savage with DRI enabled]
Hi, I remade the patch, and I attach to bug #1709, because resolved the issue there. and I marked the bug has verified. The patch looks to me, obvious but don't know for sure. Its based on this result: http://sergiomb.no-ip.org/xorg/xorgRC2/SOURCES/list thanks, On Mon, 2005-11-21 at 19:15 +0100, Roland Scheidegger wrote: Sergio Monteiro Basto wrote: After analyze how build Mesa from CVS with make linux-x86-dri and how xorg built same Mesa source with make World. Ian Romanick has point that Mesa code should have IN_DRI_DRIVER Define. So, I found on xc/lib/GL/mesa all subdirs: shader swrast tnl x86 main math and tnl_dd have missing at least -DIN_DRI_DRIVER I think this should be blocker on the 6.9 (I guess 7.0 isn't affected?) release, though I'm not really sure on the exact consequences. Xorg build also misses -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DHAVE_ALIAS Ian, and those ones are needed ? Can't comment on the others (though usually care must be taken with the threading stuff!), but not having -DUSE_EXTERNAL_DXTN_LIB=1 will obviously cause it to not support s3tc with the external library (I had already filed a bug about this, https://bugs.freedesktop.org/show_bug.cgi?id=5057). As side note I haven't the minimum idea, what side effect this could cause on non Linux or BSD systems. Since the code in question is only built on systems which support dri, there shouldn't be any problems I suspect. The glx server code is built elsewhere (and as a side note, it can't use -DUSE_EXTERNAL_DXTN_LIB=1, at least last time I tried it was not possible to use the dl functions directly). --- xc/lib/GL/mesa/Imakefile.orig 2005-11-17 23:46:56.0 + +++ xc/lib/GL/mesa/Imakefile2005-11-17 23:04:00.0 + @@ -50,7 +50,7 @@ MATH_DEFINES = -DCCPML #endif - DEFINES = $(ALLOC_DEFINES) GlxDefines \ + DEFINES = $(ALLOC_DEFINES) GlxDefines -DIN_DRI_DRIVER \ $(MESA_ASM_DEFINES) $(MATH_DEFINES) INCLUDES = -I$(INCLUDESRC) -I$(XINCLUDESRC) -I$(EXTINCSRC) \ -I$(GLXLIBSRC)/dri \ I'm not sure if that's the best place to put it, it looks like usually the -Ddefinewhatever are all in the Imakefile.inc files, maybe that would be nicer. Roland -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208236352 (LWP 25396)]
0x00fa4afb in run_texnorm_stage (ctx=0x8ce54e0, stage=0x8e81b58) at
savagerender.c:251
251 GLboolean normalizeS = (texObj-WrapS == GL_REPEAT);
(gdb) print texObj
$1 = (struct gl_texture_object *) 0x0
(gdb) print reallyEnabled
$2 = 0
(gdb) print i
$3 = 1
is this you asking for ? anything that I can do ?
And this patch works! yes
Thanks,
On Sat, 2005-11-19 at 07:41 -0700, Brian Paul wrote:
Can you print the value of nearby local vars, such as 'texObj',
'reallyEnabled' and 'i'?
I bet a patch along the lines of what I've attached might fix the problem.
-Brian
Sergio Monteiro Basto wrote:
Hi,
with Mesa CVS no luck
just a better debug
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208609088 (LWP 21869)]
0x00ae0b1b in run_texnorm_stage (ctx=0x8a404e0, stage=0x8bdcb58) at
savagerender.c:251
251 GLboolean normalizeS = (texObj-WrapS == GL_REPEAT);
(gdb) bt
#0 0x00ae0b1b in run_texnorm_stage (ctx=0x8a404e0, stage=0x8bdcb58) at
savagerender.c:251
#1 0x00b7dabd in _tnl_run_pipeline (ctx=0x8a404e0) at tnl/t_pipeline.c:162
#2 0x00adbe5a in savageRunPipeline (ctx=0x8a404e0) at savagetris.c:806
#3 0x00b8475d in _tnl_playback_vertex_list (ctx=0x8a404e0, data=0x8da0cac)
at tnl/t_save_playback.c:209
#4 0x00b00036 in execute_list (ctx=0x8a404e0, list=1) at main/dlist.c:5678
#5 0x00b03a9a in _mesa_CallList (list=1) at main/dlist.c:6746
#6 0x00b72d8b in neutral_CallList (i=1) at main/vtxfmt_tmp.h:304
#7 0x08052d41 in DisplayFunc () at billard3d.c:3015
#8 0x080821d7 in handle_display_event () at sys_stuff.c:90
#9 0x00121a91 in processWindowWorkList (window=0x8a3a648) at
glut_event.c:1297
#10 0x00122a9b in glutMainLoop () at glut_event.c:1344
#11 0x0805819f in main (argc=1, argv=0xbfe83c24) at billard3d.c:5194
On Sun, 2005-11-13 at 21:48 +, Sergio Monteiro Basto wrote:
Hi,
Today, I test chromium, tuxracer and foobillard and none of then runs
try to dig with gdb and all stop on run_texnorm_stage()
here is the debug with backtrace:
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread -1208801600 (LWP 12723)]
0x00ec8a80 in _mesa_test_os_sse_exception_support () from
/usr/X11R6/lib/modules/dri/savage_dri.so
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x00ed575b in run_texnorm_stage () from
/usr/X11R6/lib/modules/dri/savage_dri.so
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread -1208904000 (LWP 3049)]
0x00c29a80 in _mesa_test_os_sse_exception_support () from
/usr/X11R6/lib/modules/dri/savage_dri.so
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x00c3675b in run_texnorm_stage () from
/usr/X11R6/lib/modules/dri/savage_dri.so
(gdb) bt
#0 0x00c3675b in run_texnorm_stage () from
/usr/X11R6/lib/modules/dri/savage_dri.so
#1 0x00be2a84 in _tnl_run_pipeline () from
/usr/X11R6/lib/modules/dri/savage_dri.so
#2 0x00c462e9 in savageRunPipeline () from
/usr/X11R6/lib/modules/dri/savage_dri.so
#3 0x00be7ce6 in _tnl_playback_vertex_list () from
/usr/X11R6/lib/modules/dri/savage_dri.so
#4 0x00b1f862 in execute_list () from
/usr/X11R6/lib/modules/dri/savage_dri.so
#5 0x00b1fc5c in _mesa_CallList () from
/usr/X11R6/lib/modules/dri/savage_dri.so
#6 0x08052d41 in DisplayFunc () at billard3d.c:3015
#7 0x080821d7 in handle_display_event () at sys_stuff.c:90
#8 0x00121a91 in processWindowWorkList (window=0x9f82650) at
glut_event.c:1297
#9 0x00122a9b in glutMainLoop () at glut_event.c:1344
#10 0x0805819f in main (argc=1, argv=0xbf93bec4) at billard3d.c:5194
plain text document attachment (savage.patch)
Index: savagerender.c
===
RCS file: /cvs/mesa/Mesa/src/mesa/drivers/dri/savage/savagerender.c,v
retrieving revision 1.5.2.1
diff -u -r1.5.2.1 savagerender.c
--- savagerender.c31 Oct 2005 21:53:17 - 1.5.2.1
+++ savagerender.c19 Nov 2005 14:40:22 -
@@ -248,55 +248,57 @@
for (i = 0 ; i ctx-Const.MaxTextureUnits ; i++) {
GLuint reallyEnabled = ctx-Texture.Unit[i]._ReallyEnabled;
struct gl_texture_object *texObj = ctx-Texture.Unit[i]._Current;
- GLboolean normalizeS = (texObj-WrapS == GL_REPEAT);
- GLboolean normalizeT = (reallyEnabled TEXTURE_2D_BIT)
- (texObj-WrapT == GL_REPEAT);
- GLfloat *in = (GLfloat *)VB-TexCoordPtr[i]-data;
- GLint instride = VB-TexCoordPtr[i]-stride;
- GLfloat (*out)[4] = store-texcoord[i].data;
- GLint j;
-
- if (!ctx-Texture.Unit[i]._ReallyEnabled ||
- VB-TexCoordPtr[i]-size == 4)
- /* Never try to normalize homogenous tex coords! */
- continue;
-
- if (normalizeS normalizeT) {
- /* take first texcoords as rough estimate
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
Hi, with Mesa CVS no luck just a better debug Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208609088 (LWP 21869)] 0x00ae0b1b in run_texnorm_stage (ctx=0x8a404e0, stage=0x8bdcb58) at savagerender.c:251 251 GLboolean normalizeS = (texObj-WrapS == GL_REPEAT); (gdb) bt #0 0x00ae0b1b in run_texnorm_stage (ctx=0x8a404e0, stage=0x8bdcb58) at savagerender.c:251 #1 0x00b7dabd in _tnl_run_pipeline (ctx=0x8a404e0) at tnl/t_pipeline.c:162 #2 0x00adbe5a in savageRunPipeline (ctx=0x8a404e0) at savagetris.c:806 #3 0x00b8475d in _tnl_playback_vertex_list (ctx=0x8a404e0, data=0x8da0cac) at tnl/t_save_playback.c:209 #4 0x00b00036 in execute_list (ctx=0x8a404e0, list=1) at main/dlist.c:5678 #5 0x00b03a9a in _mesa_CallList (list=1) at main/dlist.c:6746 #6 0x00b72d8b in neutral_CallList (i=1) at main/vtxfmt_tmp.h:304 #7 0x08052d41 in DisplayFunc () at billard3d.c:3015 #8 0x080821d7 in handle_display_event () at sys_stuff.c:90 #9 0x00121a91 in processWindowWorkList (window=0x8a3a648) at glut_event.c:1297 #10 0x00122a9b in glutMainLoop () at glut_event.c:1344 #11 0x0805819f in main (argc=1, argv=0xbfe83c24) at billard3d.c:5194 On Sun, 2005-11-13 at 21:48 +, Sergio Monteiro Basto wrote: Hi, Today, I test chromium, tuxracer and foobillard and none of then runs try to dig with gdb and all stop on run_texnorm_stage() here is the debug with backtrace: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208801600 (LWP 12723)] 0x00ec8a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00ed575b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208904000 (LWP 3049)] 0x00c29a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00c3675b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) bt #0 0x00c3675b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so #1 0x00be2a84 in _tnl_run_pipeline () from /usr/X11R6/lib/modules/dri/savage_dri.so #2 0x00c462e9 in savageRunPipeline () from /usr/X11R6/lib/modules/dri/savage_dri.so #3 0x00be7ce6 in _tnl_playback_vertex_list () from /usr/X11R6/lib/modules/dri/savage_dri.so #4 0x00b1f862 in execute_list () from /usr/X11R6/lib/modules/dri/savage_dri.so #5 0x00b1fc5c in _mesa_CallList () from /usr/X11R6/lib/modules/dri/savage_dri.so #6 0x08052d41 in DisplayFunc () at billard3d.c:3015 #7 0x080821d7 in handle_display_event () at sys_stuff.c:90 #8 0x00121a91 in processWindowWorkList (window=0x9f82650) at glut_event.c:1297 #9 0x00122a9b in glutMainLoop () at glut_event.c:1344 #10 0x0805819f in main (argc=1, argv=0xbf93bec4) at billard3d.c:5194 -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
[PATCH] add -DIN_DRI_DRIVER to xorg-6.9 build [was Re: problem found with new xorg-6.9RC2 on savage with DRI enabled]
Hi, After analyze how build Mesa from CVS with make linux-x86-dri and how xorg built same Mesa source with make World. Ian Romanick has point that Mesa code should have IN_DRI_DRIVER Define. So, I found on xc/lib/GL/mesa all subdirs: shader swrast tnl x86 main math and tnl_dd have missing at least -DIN_DRI_DRIVER Xorg build also misses -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DHAVE_ALIAS Ian, and those ones are needed ? As side note I haven't the minimum idea, what side effect this could cause on non Linux or BSD systems. --- xc/lib/GL/mesa/Imakefile.orig 2005-11-17 23:46:56.0 + +++ xc/lib/GL/mesa/Imakefile2005-11-17 23:04:00.0 + @@ -50,7 +50,7 @@ MATH_DEFINES = -DCCPML #endif - DEFINES = $(ALLOC_DEFINES) GlxDefines \ + DEFINES = $(ALLOC_DEFINES) GlxDefines -DIN_DRI_DRIVER \ $(MESA_ASM_DEFINES) $(MATH_DEFINES) INCLUDES = -I$(INCLUDESRC) -I$(XINCLUDESRC) -I$(EXTINCSRC) \ -I$(GLXLIBSRC)/dri \ On Tue, 2005-11-15 at 15:15 -0800, Ian Romanick wrote: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208801600 (LWP 12723)] 0x00ec8a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so What platform are you running on? Properly built drivers on Linux or BSD should *NEVER* encounter this code. That code has been removed from the Linux builds for almost a year. I suspect that you're either picking up a very old savage_dri.so or something is not right with your build. The code is #ifdef'ed out at line 186 of src/mesa/x86/x86_common.c: #if defined(__linux__) !defined(IN_DRI_DRIVER) Clearly, IN_DRI_DRIVER should be defined when building the Savage DRI driver! :) Well I downgrade to xorg-6.9RC1 and the problem disappears, so is a very recent regression. About IN_DRI_DRIVE, yes it is defined at all the places. Impossible. Edit src/mesa/x86/x86_common.c and put a '#warning Got here' before and after the '#if defined(__linux__) !defined(IN_DRI_DRIVER)' at line 186. Rebuild and grep the build output for '#warning'. With RC1 I still get this Arithmetic exception but 3D apps works without problems. If I recall correctly this Arithmetic exception is not new at all. Re-read my original reply. It was *removed* from the Linux builds about a year ago. I still stand by the problem being somewhere in your build. thanks, -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
On Tue, 2005-11-15 at 15:15 -0800, Ian Romanick wrote: Sergio Monteiro Basto wrote: On Mon, 2005-11-14 at 12:38 -0800, Ian Romanick wrote: Sergio Monteiro Basto wrote: On Mon, 2005-11-14 at 07:51 -0800, Ian Romanick wrote: Sergio Monteiro Basto wrote: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208801600 (LWP 12723)] 0x00ec8a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so What platform are you running on? Properly built drivers on Linux or BSD should *NEVER* encounter this code. That code has been removed from the Linux builds for almost a year. I suspect that you're either picking up a very old savage_dri.so or something is not right with your build. The code is #ifdef'ed out at line 186 of src/mesa/x86/x86_common.c: #if defined(__linux__) !defined(IN_DRI_DRIVER) Clearly, IN_DRI_DRIVER should be defined when building the Savage DRI driver! :) Well I downgrade to xorg-6.9RC1 and the problem disappears, so is a very recent regression. About IN_DRI_DRIVE, yes it is defined at all the places. Impossible. Edit src/mesa/x86/x86_common.c and put a '#warning Got here' before and after the '#if defined(__linux__) !defined(IN_DRI_DRIVER)' at line 186. Rebuild and grep the build output for '#warning'. Hi, Well I won make[4]: Entering directory `/home/src/redhat/BUILD/xorg-x11-6.8.99.901/xc/lib/GL' making all in lib/GL/mesa... make[5]: Entering directory `/home/src/redhat/BUILD/xorg-x11-6.8.99.901/xc/lib/GL/mesa' making all in lib/GL/mesa/x86... make[6]: Entering directory `/home/src/redhat/BUILD/xorg-x11-6.8.99.901/xc/lib/GL/mesa/x86' rm -f common_x86.o gcc -m32 -c -g -ansi -Wall -Wpointee-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -I../../../../extras/Mesa/src/mesa -I../../../../extras/Mesa/include -I../../../../lib/GL/include -I../../../../extras/Mesa/src/mesa/main -I../../../../extras/Mesa/src/mesa/x86 -I../../../../extras/Mesa/src/mesa/glapi -I../../../.. -I../../../../exports/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L-D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE-DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM common_x86.c common_x86.c:188:2: warning: ewarning Got here but what savage DRI got to do with it ? I produce this log with a simple make world type by hand. Well with my host.def ! btw yesterday I found the bug that I am talking about https://bugs.freedesktop.org/show_bug.cgi?id=1709 this is filed as notabug. thanks, -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled (correction)
not I won You won is what I meant to write sorry -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
On Mon, 2005-11-14 at 12:38 -0800, Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sergio Monteiro Basto wrote: On Mon, 2005-11-14 at 07:51 -0800, Ian Romanick wrote: Sergio Monteiro Basto wrote: Today, I test chromium, tuxracer and foobillard and none of then runs try to dig with gdb and all stop on run_texnorm_stage() here is the debug with backtrace: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208801600 (LWP 12723)] 0x00ec8a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) cont Continuing. What platform are you running on? Properly built drivers on Linux or BSD should *NEVER* encounter this code. That code has been removed from the Linux builds for almost a year. I suspect that you're either picking up a very old savage_dri.so or something is not right with your build. The code is #ifdef'ed out at line 186 of src/mesa/x86/x86_common.c: #if defined(__linux__) !defined(IN_DRI_DRIVER) Clearly, IN_DRI_DRIVER should be defined when building the Savage DRI driver! :) Hi, Well I downgrade to xorg-6.9RC1 and the problem disappears, so is a very recent regression. About IN_DRI_DRIVE, yes it is defined at all the places. With RC1 I still get this Arithmetic exception but 3D apps works without problems. If I recall correctly this Arithmetic exception is not new at all. BTW don't know if meters but my laptop is one mobile AMD Athlon(tm) 4 Processor thanks (for your time), I will go investigate this, but this is not the problem because this doesn't stop the app. That is true, but there are other places in the code that depend on IN_DRI_DRIVER being correctly set. If it's not set at this place, it is likely that it's not set at the other places either. Having it not set in the other places may be the source of the crash. -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
Hi, I just use monolithic sources, therefore I don't copy any Mesa source neither point MesaSrcDir. This is one of my goals build exclusive with one source. My host.def is one redhat custom it goes in attach I just add this patch to enable savage DRI http://sergiomb.no-ip.org/xorg/xorgRC2/SOURCES/xorg.cf.diff and build it as rpm like I explain on http://sergiomb.no-ip.org/xorg/xorgRC2 For me the best way to build it on Fedora Core 4, this formula has worked well, since xorg-6.8.99.4 snapshot Brian Paul had write recently to xorg-ML this I see that the Mesa 6.4 release has been incorporated (on RC2) . I'm not sure who's been doing that, but thanks! Any test I can do further, are welcome Thanks, On Tue, 2005-11-15 at 16:10 -0500, Felix Kühling wrote: What does your host.def file look like? What I'm getting at, when you build Xorg 6.9RC2, do you use the Mesa copy in extras or do you point MesaSrcDir at a different Mesa checkout? Regards, Felix Am Dienstag, den 15.11.2005, 20:39 + schrieb Sergio Monteiro Basto: On Mon, 2005-11-14 at 12:38 -0800, Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sergio Monteiro Basto wrote: On Mon, 2005-11-14 at 07:51 -0800, Ian Romanick wrote: Sergio Monteiro Basto wrote: Today, I test chromium, tuxracer and foobillard and none of then runs try to dig with gdb and all stop on run_texnorm_stage() here is the debug with backtrace: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208801600 (LWP 12723)] 0x00ec8a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) cont Continuing. What platform are you running on? Properly built drivers on Linux or BSD should *NEVER* encounter this code. That code has been removed from the Linux builds for almost a year. I suspect that you're either picking up a very old savage_dri.so or something is not right with your build. The code is #ifdef'ed out at line 186 of src/mesa/x86/x86_common.c: #if defined(__linux__) !defined(IN_DRI_DRIVER) Clearly, IN_DRI_DRIVER should be defined when building the Savage DRI driver! :) Hi, Well I downgrade to xorg-6.9RC1 and the problem disappears, so is a very recent regression. About IN_DRI_DRIVE, yes it is defined at all the places. With RC1 I still get this Arithmetic exception but 3D apps works without problems. If I recall correctly this Arithmetic exception is not new at all. BTW don't know if meters but my laptop is one mobile AMD Athlon(tm) 4 Processor thanks (for your time), I will go investigate this, but this is not the problem because this doesn't stop the app. That is true, but there are other places in the code that depend on IN_DRI_DRIVER being correctly set. If it's not set at this place, it is likely that it's not set at the other places either. Having it not set in the other places may be the source of the crash. -- Sérgio M.B. #define XorgCustomVersion Unsupported Custom Build by root: 6.8.99.901-1 /* Experimental custom messages */ #define XorgRedHatCustomYES #define BuilderString Build Host: darkstar.portugal\n #define LinuxDistribution LinuxRedHat #define BuildDebug 0 #define BootstrapCFlags -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables -pipe #define AsCmd CcCmd -c -x assembler #define BuildServer YES #define XVirtualFramebufferServer YES #define XnestServer YES /* by default BuildDPSLibraries is NO but we need it by ImageMagick */ #define BuildDPSLibraries YES /* Make xtrans fail gracefully by default, for bug #129622 and others */ #define XtransFailSoft YES /* We want includes in /usr/include/GL, so we move them there later on * because the LinkGLToUsrInclude option makes the GL subdirectory a symlink, * which is bad for RPM packaging as other packages may place files there, * plus there's the whole rpm replacing a symlink with a dir, etc. thing. */ #define LinkGLToUsrInclude NO /* The OpenGL ABI on Linux standard states libGL and libGLU must be present in * /usr/lib either directly, or as symlinks. The supplied Imake config option * LinkGLToUsrLib makes absolute symlinks rather than relative ones, so it is * not suitable for us to use. */ #define LinkGLToUsrLib NO /* LinkGLToUsrInclude makes an absolute symlink to the _x11includedir, which * essentially makes /usr/lib/GL a symlink, which is messy, and may conflict * with other package's files that may be installed in the GL include dir for * whatever reason. We disable this option for now, and handle things * ourselves with a bit of scripting in the spec file. */ #define BuildGLwLibrary YES #define
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
Hi, On Mon, 2005-11-14 at 07:51 -0800, Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sergio Monteiro Basto wrote: Today, I test chromium, tuxracer and foobillard and none of then runs try to dig with gdb and all stop on run_texnorm_stage() here is the debug with backtrace: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208801600 (LWP 12723)] 0x00ec8a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) cont Continuing. What platform are you running on? Properly built drivers on Linux or BSD should *NEVER* encounter this code. That code has been removed from the Linux builds for almost a year. I suspect that you're either picking up a very old savage_dri.so or something is not right with your build. The code is #ifdef'ed out at line 186 of src/mesa/x86/x86_common.c: #if defined(__linux__) !defined(IN_DRI_DRIVER) Clearly, IN_DRI_DRIVER should be defined when building the Savage DRI driver! :) I will go investigate this, but this is not the problem because this doesn't stop the app. the problem is in Program received signal SIGSEGV, Segmentation fault. 0x00c3675b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) bt #0 0x00c3675b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so #1 0x00be2a84 in _tnl_run_pipeline () from /usr/X11R6/lib/modules/dri/savage_dri.so #2 0x00c462e9 in savageRunPipeline () from /usr/X11R6/lib/modules/dri/savage_dri.so #3 0x00be7ce6 in _tnl_playback_vertex_list () from /usr/X11R6/lib/modules/dri/savage_dri.so #4 0x00b1f862 in execute_list () from /usr/X11R6/lib/modules/dri/savage_dri.so #5 0x00b1fc5c in _mesa_CallList () from /usr/X11R6/lib/modules/dri/savage_dri.so #6 0x08052d41 in DisplayFunc () at billard3d.c:3015 #7 0x080821d7 in handle_display_event () at sys_stuff.c:90 #8 0x00121a91 in processWindowWorkList (window=0x9f82650) at glut_event.c:1297 #9 0x00122a9b in glutMainLoop () at glut_event.c:1344 #10 0x0805819f in main (argc=1, argv=0xbf93bec4) at billard3d.c:5194 thanks, -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
problem found with new xorg-6.9RC2 on savage with DRI enabled
Hi, Today, I test chromium, tuxracer and foobillard and none of then runs try to dig with gdb and all stop on run_texnorm_stage() here is the debug with backtrace: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208801600 (LWP 12723)] 0x00ec8a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00ed575b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1208904000 (LWP 3049)] 0x00c29a80 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00c3675b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) bt #0 0x00c3675b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so #1 0x00be2a84 in _tnl_run_pipeline () from /usr/X11R6/lib/modules/dri/savage_dri.so #2 0x00c462e9 in savageRunPipeline () from /usr/X11R6/lib/modules/dri/savage_dri.so #3 0x00be7ce6 in _tnl_playback_vertex_list () from /usr/X11R6/lib/modules/dri/savage_dri.so #4 0x00b1f862 in execute_list () from /usr/X11R6/lib/modules/dri/savage_dri.so #5 0x00b1fc5c in _mesa_CallList () from /usr/X11R6/lib/modules/dri/savage_dri.so #6 0x08052d41 in DisplayFunc () at billard3d.c:3015 #7 0x080821d7 in handle_display_event () at sys_stuff.c:90 #8 0x00121a91 in processWindowWorkList (window=0x9f82650) at glut_event.c:1297 #9 0x00122a9b in glutMainLoop () at glut_event.c:1344 #10 0x0805819f in main (argc=1, argv=0xbf93bec4) at billard3d.c:5194 -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: [Dri-users] xorg-x11-6.9-RC2 rpm packages updated
yap after some tries I got a oops too
that goes in attach file
I am forwarding this to dri-devel because, seams to me, the place to
report this problems.
regards,
On Sun, 2005-11-13 at 22:47 +0100, Thomas Müller wrote:
Sergio Monteiro Basto schrieb:
The good new is the recent release of kernel-2.6.14-1.1637_FC4
comes with savage DRM enabled.
I get an Oops: 0002 [#1] error when trying to use the 2.6.14 savage
driver from Gentoo. DRI seems to work, but glxinfo gives me a
Segmentation fault. According to dmesg, the error occurs in
savage_bci_event_emit.
Thomas
--
Sérgio M.B.
application chromium uses obsolete OSS audio interface
agpgart: Found an AGP 2.0 compliant device at :00:00.0.
agpgart: Putting AGP V2 device at :00:00.0 into 4x mode
agpgart: Putting AGP V2 device at :01:00.0 into 4x mode
mtrr: base(0xf200) is not aligned on a size(0x500) boundary
application foobillard uses obsolete OSS audio interface
Unable to handle kernel paging request at virtual address 0001
printing eip:
d6a7bce4
*pde = 03352067
Oops: 0002 [#1]
Modules linked in: loop nfs lockd nfs_acl savage drm lp ipv6 autofs4 sunrpc
pcmcia ipt_REJECT ipt_state ip_conntrack nfnetlink iptable_filter ip_tables
nls_utf8 vfat fat dm_mod video button battery ac yenta_socket rsrc_nonstatic
pcmcia_core uhci_hcd shpchp parport_pc parport via686a hwmon i2c_isa i2c_core
snd_via82xx gameport snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore 8139too
mii floppy ext3 jbd
CPU:0
EIP:0060:[d6a7bce4]Not tainted VLI
EFLAGS: 00010282 (2.6.14-1.1637_FC4)
EIP is at savage_dma_flush+0xc7/0x309 [savage]
eax: 0001 ebx: 00e2 ecx: 00c0 edx: 0003
esi: c3e63e00 edi: ec000300 ebp: esp: c2e17e84
ds: 007b es: 007b ss: 0068
Process foobillard (pid: 11748, threadinfo=c2e17000 task=d0321030)
Stack: 0004 0010 00ff 026d
0006 08a16af0 c3baa000
c3e63e00 d6a802eb 0010 08dd57a0 c3ad8088 d5280920 c3ad8088 c3ad8088
Call Trace:
[d6a802eb] savage_bci_cmdbuf+0x350/0x491 [savage]
[d6a7ff9b] savage_bci_cmdbuf+0x0/0x491 [savage]
[d6ab9618] drm_ioctl+0x9a/0x1d8 [drm]
[d6ab957e] drm_ioctl+0x0/0x1d8 [drm]
[c016a031] do_ioctl+0x51/0x55
[c016a127] vfs_ioctl+0x50/0x1aa
[c016a2de] sys_ioctl+0x5d/0x6b
[c0102edd] syscall_call+0x7/0xb
Code: 20 89 c3 c1 e3 0a 03 5a 08 29 cb a1 84 69 ac d6 85 c0 0f 85 2f 02 00 00
ba 03 00 00 00 89 f0 ff 96 2c 01 00 00 8b 86 d0 00 00 00 c7 00 51 00 01 96 0b
7e 3c 89 78 04 d1 eb 8d 53 ff 81 ca 00 00
1Unable to handle kernel paging request at virtual address 0001
printing eip:
d6a7b4a9
*pde = 0ea6f067
Oops: 0002 [#2]
Modules linked in: loop nfs lockd nfs_acl savage drm lp ipv6 autofs4 sunrpc
pcmcia ipt_REJECT ipt_state ip_conntrack nfnetlink iptable_filter ip_tables
nls_utf8 vfat fat dm_mod video button battery ac yenta_socket rsrc_nonstatic
pcmcia_core uhci_hcd shpchp parport_pc parport via686a hwmon i2c_isa i2c_core
snd_via82xx gameport snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore 8139too
mii floppy ext3 jbd
CPU:0
EIP:0060:[d6a7b4a9]Not tainted VLI
EFLAGS: 00010286 (2.6.14-1.1637_FC4)
EIP is at savage_bci_emit_event+0xcf/0xe4 [savage]
eax: 0001 ebx: c04c3f20 ecx: c7588000 edx: 0001
esi: c3e63e00 edi: 980006e8 ebp: 06e8 esp: c04c3f00
ds: 007b es: 007b ss: 0068
Process foobillard (pid: 11760, threadinfo=c04c3000 task=c0a16570)
Stack: c04c3f20 c25d62e0 c3e63e00 d2f0a620 d6a7d260 00100100 00200200 0003
d6a7d1bf d6a83898 0001 d6ab9618 bfbdf360
d5ee44e0 c0a16570 c845eee0 c3a98d4c c0086442 c25d62e0 c3a98d4c
Call Trace:
[d6a7d260] savage_bci_event_emit+0xa1/0xcf [savage]
[d6a7d1bf] savage_bci_event_emit+0x0/0xcf [savage]
[d6ab9618] drm_ioctl+0x9a/0x1d8 [drm]
[d6ab957e] drm_ioctl+0x0/0x1d8 [drm]
[c016a031] do_ioctl+0x51/0x55
[c016a127] vfs_ioctl+0x50/0x1aa
[c016a2de] sys_ioctl+0x5d/0x6b
[c0102edd] syscall_call+0x7/0xb
Code: 01 00 00 00 eb 88 83 86 dc 00 00 00 01 e9 71 ff ff ff ba 01 00 00 00 89
f0 ff 96 2c 01 00 00 8b 86 d0 00 00 00 81 cf 00 00 00 98 89 38 89 e8 5b 5e 5f
5d c3 0f b7 80 d8 00 00 00 e9 43 ff ff ff
1Unable to handle kernel paging request at virtual address 0001
printing eip:
d6a7b4a9
*pde = 02c0d067
Oops: 0002 [#3]
Modules linked in: loop nfs lockd nfs_acl savage drm lp ipv6 autofs4 sunrpc
pcmcia ipt_REJECT ipt_state ip_conntrack nfnetlink iptable_filter ip_tables
nls_utf8 vfat fat dm_mod video button battery ac yenta_socket rsrc_nonstatic
pcmcia_core uhci_hcd shpchp parport_pc parport via686a
Re: Mesa 6.4 release was: ([PATCH] Fix memory corruption in ycbcr texture swap)
Hi, On Wed, 2005-10-05 at 21:35 +0100, Dave Airlie wrote: I plan to release Mesa 6.4 fairly soon. That'll get imported into the X.org tree. On http://dri.freedesktop.org/wiki/Building is write The Mesa drivers now require libdrm to be installed. This is correct for Mesa 6.4 or libdrm will stay only on Mesa HEAD ? No both of them need libdrm.. Dave. Just wondering since libdrm is to be imported into X.org tree, how this will be compiled on X.org monolithic tree ? -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Mesa 6.4 release was: ([PATCH] Fix memory corruption in ycbcr texture swap)
Hi, I want try to test this. On Wed, 2005-10-05 at 07:36 -0600, Brian Paul wrote: I've fixed the bug, but I did so by changing datatypes. The fix is in Mesa CVS. I plan to release Mesa 6.4 fairly soon. That'll get imported into the X.org tree. On http://dri.freedesktop.org/wiki/Building is write The Mesa drivers now require libdrm to be installed. This is correct for Mesa 6.4 or libdrm will stay only on Mesa HEAD ? thanks in advance, -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
_glthread_TSD problem [was: display lists broken in Mesa maybe due to glapi dispatch changes (?), and an Xthreads problem]
Hi, The s3v and savage drivers did not compile with exactly the same error. I hit this problem on X.org CVS with Mesa from there. Since Mesa on X.org is the stable branch 6.3.2, is your fix there ? or anyone knows how fix this problem. I can get build the others DRI drives. But make linux-dri-x86 has a strange bug, enter in loop in the finish of building and I have to stop it with Ctrl+C. thanks, On Mon, 2005-08-01 at 09:37 -0700, Ian Romanick wrote: It builds fine on my main machine. I tried a build on a fresh system install (with X.org CVS installed) and hit the same problem. I committed a fix for it just a few minutes ago. I think the problem here is related to the next problem... And, even with that change, the s3v and savage drivers did not compile, both failed the same way (though I didn't care too much as I only needed r200 anyway...). gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver -I../../../../../../dri/drm/shared-core -I../../../../../include -I../../../../../include/GL/internal -I../../../../../src/mesa -I../../../../../src/mesa/main -I../../../../../src/mesa/glapi -I../../../../../src/mesa/math -I../../../../../src/mesa/transform -I../../../../../src/mesa/shader -I../../../../../src/mesa/swrast -I../../../../../src/mesa/swrast_setup -I../../../../../src/egl/main -I../dri_client -I../dri_client/imports -Wall -O -g -m32 -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -std=c99 -ffast-math -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING s3v_state.c -o s3v_state.o In file included from ../../../../../src/mesa/main/mtypes.h:41, from s3v_screen.h:5, from s3v_context.h:13, from s3v_state.c:6: ../../../../../src/mesa/glapi/glthread.h:202: error: conflicting types for `_glthread_TSD' ../../../../../src/mesa/glapi/glthread.h:92: error: previous declaration of `_glthread_TSD' The only way this could happen is if *both* PTHREADS and XTHREADS are defined. I suspect the Xthreads.h problem was always there, but it was never hit because XTHREADS was never defined. Some how, somewhere, XTHREADS is getting set. I'll have to look into it, but I think this is a bug in whatever X.org header is defining XTHREADS for us. :( -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: [Dri-users] No Direct Rendering with Radeon and xorg-x11-6.8.99.6.tar.bz2
Hi, dri-list, (I considered this not a very good solution as you'll sacrifice quite some 3d performance, but since it now happens in snapshots something needs to be done about it probably). Roland My problem if I upgrade Mesa cvs on Xorg cvs, it will compile radeon driver ? Well, you have to try it sooner or later (what now is the ble.. edge), and will be the solution isn't it? . Last minute, finally I understand my problem, I had to update drm for compiling Mesa. Thanks, -- Sérgio M.B. --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393alloc_id=16281op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
redirecting to devel ML On Mon, 2005-01-03 at 23:38 +, Sergio Monteiro Basto wrote: If you're still using Linux 2.4 you need to upgrade that first. After think a little and put dri working with kernel 2.4. The only solution, that I see, to not private users of savage with kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code before 2005-01-01 and other for kernel 2.6 thanks, -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
problems compiling xorg cvs Re: drm CVS state...
savage_xmesa.c: In function `savageInitDriver': savage_xmesa.c:111: error: structure has no member named `frontPitch' savage_xmesa.c:113: error: structure has no member named `frontBitmapDesc' savage_xmesa.c:121: error: structure has no member named `backBitmapDesc' savage_xmesa.c:123: error: structure has no member named `depthBitmapDesc' savage_xmesa.c:136: error: structure has no member named `agpTextures' savage_xmesa.c:138: error: structure has no member named `agpTextures' savage_xmesa.c:142: error: structure has no member named `backbuffer' savage_xmesa.c:147: error: structure has no member named `depthbuffer' savage_xmesa.c: In function `savageCreateContext': savage_xmesa.c:313: error: structure has no member named `registers' savage_xmesa.c:314: error: structure has no member named `registers' savage_xmesa.c:315: error: structure has no member named `registers' savage_xmesa.c:323: error: structure has no member named `agpTextures' savage_xmesa.c:324: error: structure has no member named `agpTextures' savage_xmesa.c:325: error: structure has no member named `agpTextures' savage_xmesa.c:334: error: structure has no member named `agpTextures' savage_xmesa.c:338: error: structure has no member named `BCIcmdBuf' savage_xmesa.c:339: error: structure has no member named `registers' savage_xmesa.c:341: error: structure has no member named `registers' savage_xmesa.c:342: error: structure has no member named `BCIcmdBuf' savage_xmesa.c:344: error: structure has no member named `aperture' savage_xmesa.c:345: error: structure has no member named `aperture' make[6]: *** [savage_xmesa.o] Error 1 make[6]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib/GL/mesa/drivers/dri/savage' make[5]: *** [all] Error 2 make[5]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib/GL/mesa/drivers/dri' make[4]: *** [all] Error 2 make[4]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib/GL' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/opt/xorgcvs2/build' make[1]: *** [World] Error 2 make[1]: Leaving directory `/usr/src/opt/xorgcvs2/build' make: *** [World] Error 2 any help ? On Sun, 2005-01-02 at 12:16 +0100, Felix Kühling wrote: Am So, den 02.01.2005 schrieb Sergio Monteiro Basto um 2:42: On Fri, 2004-12-31 at 16:02 +0100, Felix Kühling wrote: I was going to change mesa/src/mesa/drivers/dri/Makefile.template to use the share-core directory for DRM includes. This will be needed for the new Savage DRM as it lives in linux-core/shared-core only. With your assessment of the status of the 2.4 DRM it looks like it will never be backported to Linux 2.4. with this all applied, just left us checkout drm and mesa cvs and apply http://freedesktop.org/~fxkuehl/savage/savage_xorg_20041229.diff on xorg tree to test it ? You don't need any of my previous patches. Just cvs update Xorg HEAD and recompile the Savage driver from there. Actually the patches are incompatible with the versions that I finally committed to CVS. So be sure you don't mix them or you will get unpredictable behavior. From now on I will keep the binary interfaces compatible though. I just check-out mesa and drm and compile with make linux-dri-x86 and cp lib/savage_dri.so /usr/X11R6/lib/modules/dri/savage_dri.so and recompile drm for my kernel 2.4.29-pre1, after reboot (to be sure that savage kernel module is loaded again), all works normally. The new Savage driver lives in drm/shared-core and drm/linux-core. This means it can only be compiled for Linux 2.6.x kernels. I'm not planning a backport to 2.4. thanks, -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: problems compiling xorg cvs Re: drm CVS state...
On Mon, 2005-01-03 at 00:18 +0100, Felix Kühling wrote: Looks like this was caused by my update of the Savage DDX driver in the X.org tree without also upating the Mesa driver in the X.org tree. At the moment the Mesa driver in X.org's extras/Mesa can't be compiled with the current Savage DDX. It is my understanding that this will be cleaned up when X.org imports Mesa sources the next time, which will happen at least once before the next major release. Since the Savage driver is being worked on you don't want to work with constantly outdated sources in extras/Mesa anyway. The recommended way to proceed is to disable the build of the Savage DRI driver in the X.org tree (it should be disabled by default, since Savage is a DevelDRIDriver) and build the Savage DRI driver directly from Mesa CVS. The instructions at http://dri.freedesktop.org/wiki/Building should work for you. now glxinfo | grep dire direct rendering: No OpenGL renderer string: Mesa GLX Indirect [snip] Regards, Felix -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drm CVS state...
On Fri, 2004-12-31 at 16:02 +0100, Felix Kühling wrote: I was going to change mesa/src/mesa/drivers/dri/Makefile.template to use the share-core directory for DRM includes. This will be needed for the new Savage DRM as it lives in linux-core/shared-core only. With your assessment of the status of the 2.4 DRM it looks like it will never be backported to Linux 2.4. with this all applied, just left us checkout drm and mesa cvs and apply http://freedesktop.org/~fxkuehl/savage/savage_xorg_20041229.diff on xorg tree to test it ? I just check-out mesa and drm and compile with make linux-dri-x86 and cp lib/savage_dri.so /usr/X11R6/lib/modules/dri/savage_dri.so and recompile drm for my kernel 2.4.29-pre1, after reboot (to be sure that savage kernel module is loaded again), all works normally. thanks, -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: radeon: Unknown symbol i2c_bit_add_bus (was: Re: new hyperz patch)
thanks, Now I can load radeon.ko after modprobe i2c_via.ko thanks, On Mon, 2004-12-13 at 17:27 -0500, Adam Jackson wrote: On Monday 13 December 2004 17:15, Dave Airlie wrote: radeon: Unknown symbol i2c_bit_add_bus radeon: Unknown symbol i2c_bit_del_bus you need i2c support modules loaded.. modprobe the radeon driver it should all work then... Shouldn't radeon.ko build without i2c hooks if CONFIG_I2C == NO ? - ajax -- Sérgio M.B. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
radeon: Unknown symbol i2c_bit_add_bus (was: Re: new hyperz patch)
Hi, Now, on FC3 testing lastest cvs I got: radeon: Unknown symbol i2c_bit_add_bus radeon: Unknown symbol i2c_bit_del_bus when I try to load radeon ko . thanks, On Mon, 2004-12-13 at 00:11 +0100, Roland Scheidegger wrote: Sergio Monteiro Basto wrote: Hi Roland, So , for hyperz patch did you need modify any makefiles ? if it positive what makefiles did you need to patch :) ? No makefile changes were/are needed. well, I think since 15 Nov some body did change makefiles, because I could compile radeon dri with xorg cvs and now I don't, but don't worry about that. I will try find out what happen. Roland -- Sérgio M.B. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
simple patches to compile xorg cvs with lastest Mesa (linked)
Hi , and I still can compile unichrome and lately radeon so I use xorg2.diff to workaround thanks, -- Sérgio M.B. --- xc/lib/GL/mesa/shader/Imakefile.inc.orig 2004-06-16 10:27:56.0 +0100 +++ xc/lib/GL/mesa/shader/Imakefile.inc 2004-10-31 18:48:35.0 + @@ -15,7 +15,8 @@ $(MESASHADERBUILDDIR)nvfragparse.c \ $(MESASHADERBUILDDIR)nvvertexec.c \ $(MESASHADERBUILDDIR)nvvertparse.c \ - $(MESASHADERBUILDDIR)program.c + $(MESASHADERBUILDDIR)program.c \ + $(MESASHADERBUILDDIR)shaderobjects.c #ifdef NeedToLinkMesaSrc LinkSourceFile(arbprogparse.c, $(MESASRCDIR)/src/mesa/shader) @@ -44,6 +45,8 @@ LinkSourceFile(grammar_syn.h, $(MESASRCDIR)/src/mesa/shader) LinkSourceFile(program.c, $(MESASRCDIR)/src/mesa/shader) LinkSourceFile(program.h, $(MESASRCDIR)/src/mesa/shader) +LinkSourceFile(shaderobjects.c, $(MESASRCDIR)/src/mesa/shader) +LinkSourceFile(shaderobjects.h, $(MESASRCDIR)/src/mesa/shader) #endif MESA_SHADER_OBJS = $(MESASHADERBUILDDIR)arbprogparse.o \ @@ -55,7 +58,8 @@ $(MESASHADERBUILDDIR)nvfragparse.o \ $(MESASHADERBUILDDIR)nvvertexec.o \ $(MESASHADERBUILDDIR)nvvertparse.o \ - $(MESASHADERBUILDDIR)program.o + $(MESASHADERBUILDDIR)program.o \ + $(MESASHADERBUILDDIR)shaderobjects.o #if defined(DoSharedLib) DoSharedLib MESA_SHADER_UOBJS = $(MESASHADERBUILDDIR)unshared/arbprogparse.o \ @@ -67,7 +71,8 @@ $(MESASHADERBUILDDIR)unshared/nvfragparse.o \ $(MESASHADERBUILDDIR)unshared/nvvertexec.o \ $(MESASHADERBUILDDIR)unshared/nvvertparse.o \ - $(MESASHADERBUILDDIR)unshared/program.o + $(MESASHADERBUILDDIR)unshared/program.o \ + $(MESASHADERBUILDDIR)unshared/shaderobjects.o #else MESA_SHADER_UOBJS = $(MESA_SHADER_OBJS) #endif @@ -81,7 +86,8 @@ $(MESASHADERBUILDDIR)debugger/nvfragparse.o \ $(MESASHADERBUILDDIR)debugger/nvvertexec.o \ $(MESASHADERBUILDDIR)debugger/nvvertparse.o \ - $(MESASHADERBUILDDIR)debugger/program.o + $(MESASHADERBUILDDIR)debugger/program.o \ + $(MESASHADERBUILDDIR)debugger/shaderobjects.o MESA_SHADER_POBJS = $(MESASHADERBUILDDIR)profiled/arbprogparse.o \ $(MESASHADERBUILDDIR)profiled/arbprogram.o \ @@ -92,4 +98,5 @@ $(MESASHADERBUILDDIR)profiled/nvfragparse.o \ $(MESASHADERBUILDDIR)profiled/nvvertexec.o \ $(MESASHADERBUILDDIR)profiled/nvvertparse.o \ - $(MESASHADERBUILDDIR)profiled/program.o + $(MESASHADERBUILDDIR)profiled/program.o \ + $(MESASHADERBUILDDIR)profiled/shaderobjects.o --- xc/lib/GL/mesa/drivers/dri/r128/Imakefile.inc.orig 2004-11-13 19:07:21.0 + +++ xc/lib/GL/mesa/drivers/dri/r128/Imakefile.inc 2004-10-21 20:29:16.0 +0100 @@ -48,8 +48,7 @@ $(MESADRVR128BUILDDIR)r128_tex.c \ $(MESADRVR128BUILDDIR)r128_texmem.c \ $(MESADRVR128BUILDDIR)r128_texstate.c \ - $(MESADRVR128BUILDDIR)r128_tris.c \ - $(MESADRVR128BUILDDIR)r128_vb.c + $(MESADRVR128BUILDDIR)r128_tris.c R128OBJS = $(MESADRVR128BUILDDIR)r128_context.o \ $(MESADRVR128BUILDDIR)r128_dd.o \ @@ -61,8 +60,7 @@ $(MESADRVR128BUILDDIR)r128_tex.o \ $(MESADRVR128BUILDDIR)r128_texmem.o \ $(MESADRVR128BUILDDIR)r128_texstate.o \ - $(MESADRVR128BUILDDIR)r128_tris.o \ - $(MESADRVR128BUILDDIR)r128_vb.o + $(MESADRVR128BUILDDIR)r128_tris.o R128UOBJS = $(MESADRVR128BUILDDIR)unshared/r128_context.o \ $(MESADRVR128BUILDDIR)unshared/r128_dd.o \ @@ -74,8 +72,7 @@ $(MESADRVR128BUILDDIR)unshared/r128_tex.o \ $(MESADRVR128BUILDDIR)unshared/r128_texmem.o \ $(MESADRVR128BUILDDIR)unshared/r128_texstate.o \ - $(MESADRVR128BUILDDIR)unshared/r128_tris.o \ - $(MESADRVR128BUILDDIR)unshared/r128_vb.o + $(MESADRVR128BUILDDIR)unshared/r128_tris.o R128DOBJS = $(MESADRVR128BUILDDIR)debugger/r128_context.o \ $(MESADRVR128BUILDDIR)debugger/r128_dd.o \ @@ -87,8 +84,7 @@ $(MESADRVR128BUILDDIR)debugger/r128_tex.o \ $(MESADRVR128BUILDDIR)debugger/r128_texmem.o \ $(MESADRVR128BUILDDIR)debugger/r128_texstate.o \ - $(MESADRVR128BUILDDIR)debugger/r128_tris.o \ - $(MESADRVR128BUILDDIR)debugger/r128_vb.o + $(MESADRVR128BUILDDIR)debugger/r128_tris.o R128POBJS = $(MESADRVR128BUILDDIR)profiled/r128_context.o \ $(MESADRVR128BUILDDIR)profiled/r128_dd.o \ @@ -100,8 +96,7 @@ $(MESADRVR128BUILDDIR)profiled/r128_tex.o \ $(MESADRVR128BUILDDIR)profiled/r128_texmem.o \ $(MESADRVR128BUILDDIR)profiled/r128_texstate.o \ - $(MESADRVR128BUILDDIR)profiled/r128_tris.o \ - $(MESADRVR128BUILDDIR)profiled/r128_vb.o + $(MESADRVR128BUILDDIR)profiled/r128_tris.o #ifdef NeedToLinkMesaSrc LinkSourceFile(r128_context.c, $(MESADRVSRCDIR)/r128) @@ -125,6 +120,4 @@ LinkSourceFile(r128_texstate.c, $(MESADRVSRCDIR)/r128) LinkSourceFile(r128_tris.c, $(MESADRVSRCDIR)/r128) LinkSourceFile(r128_tris.h, $(MESADRVSRCDIR)/r128) -LinkSourceFile(r128_vb.c, $(MESADRVSRCDIR)/r128) -LinkSourceFile(r128_vb.h, $(MESADRVSRCDIR)/r128) #endif --- xc/config/cf/xorg.cf.orig 2004-12-12 02:45:45.0 + +++ xc/config/cf/xorg.cf 2004-12-12
