Radeon detected Memory!
I don't know if you remember about radeon driver doesn't detect more than 128 MB of memory, Michel Daenzer as said that max driver capabilitie was 128Mb. So i have this patch to warn that driver has detected correct amount of memory but only using 128MB. like Roland has sugested. I've implemented a more complex if expression, that only allow memory override to lower values of 128MB. I don't know if my though's were correct, or if my implementation was correct. So before merge the patch give a quick look. P.S:I don't know of i'm sending this patch to the right place Pedro Maia radeon_driver.diff Description: radeon_driver.diff
[r300]Mesa Tests
Mesa Tests R300 driver latest cvs! Remove the Warn_once from results Xorg Options #Option GARTSise "32" #Option "RenderAccel" "true" #Tiling disable SUCESS ./arbvptest1 ./arbvptest3 ./arbvptorus ./arbvpwarpmesh ./arbfptest1 ./arbfpspec ./arbfptexture ./blendminmax ./blendsquare ./bufferobj ./bug_3101 ./bug_3195 ./cva ./dinoshade ./invert ./manytex (although it passes i see some particles, i don't know if it's only visual fail, or driver) ./no_s3tc (although it has the problem with small textures, already know bug) ./packedpixels (although when we first see the window, the last square are not correct GL_unsigned_int 8_8_8_8 (normal, it's all green), but if i try take a snapshot or if i minize it the window comes normal again green with red stripe ) ./seccolor (same problem as above, first color in red is not correct and we can see garbage in 1st cube, but if program lose context, and then have it again the render is then ok, if i press 'space', the cubes appear correctly) ./yuvsquare (same problem as above if i move pad keys render works well again) ./projtex (it worked well, although textures were too dark, almost can't see girl texture) ./sharedtex ./stencil_wrap ./tex1d ./texline ./texobjshare ./texwrap ./vparray ./vptest3 ./vptorus ./vpwarpmesh ./zreaddraw Depth value range: [0.001511, 1.00] FAILS ./arbfptrig GL_RENDERER = Mesa DRI R300 20040924 AGP 4x TCL glGetError = 0x0 glError(GL_PROGRAM_ERROR_STRING_ARB) = r300_fragprog.c::parse_program(): unknown fpi->Opcode 33 pc=0* Mesa program: - MOV TEMP[0] STATE[0] SCS TEMP[0] INPUT[4]. ADD TEMP[0] TEMP[0] STATE[1]. MUL TEMP[0] TEMP[0] STATE[2]. MOV OUTPUT[0] TEMP[0] Hardware program NODE 0: alu_offset: 0, tex_offset: 0, alu_end: -1, tex_end: -1 1230 00050a80 11b0 03860820 1270 00040889 11f0 00860820 r300SetupPixelShader: No valid fragment shader, exiting ./crossbar Diferent colors, http://pwp.netcabo.pt/0448311801/xorg/crossbar.png ./fbotest1 (No FBO support no framebuffer extension, expected i think!) GL_EXT_framebuffer_object not found! GL_RENDERER = Mesa DRI R300 20040924 AGP 4x TCL Mesa 6.4 implementation error: User called no-op dispatch function (an unsupported extension function?) Please report at bugzilla.freedesktop.org fbotest1: fbotest1.c:121: Init: Assertion `MyFB' failed. Aborted ./fbotexture GL_EXT_framebuffer_object not found! ./floattex Sorry, this test requires GL_MESAX_texture_float ./fog (althought it starts, it misses extension) GL_RENDERER = Mesa DRI R300 20040924 AGP 4x TCL GL_VERSION = 1.3 Mesa 6.4 Some output of this program requires GL_EXT_fog_coord ./fogcoord GL_RENDERER = Mesa DRI R300 20040924 AGP 4x TCL GL_VERSION = 1.3 Mesa 6.4 Sorry, this program requires GL_EXT_fog_coord /fptest1 (Meaning ?!) Mesa 6.4 implementation error: User called no-op dispatch function (an unsupported extension function?) Please report at bugzilla.freedesktop.org glGetError = 1280 ./fptexture Error: GL_NV_fragment_program not supported! ./multipal Sorry, GL_EXT_paletted_texture not supported by this renderer. ./pbo GL_VERSION = 1.3 Mesa 6.4 GL_RENDERER = Mesa DRI R300 20040924 AGP 4x TCL Sorry, this demo requires GL_EXT_pixel_buffer_object ./stencilwrap - Fails complete log attach ./texrect (complete log in attach) 8 texture units supported, using 2. 2048 x 2048 max texture rectangle size Texture 0: ../images/girl.rgb (194 x 188) Texture 1: ../images/reflect.rgb (128 x 128) drmRadeonCmdBuffer: -22 (exiting) /vptest1 vptest1: vptest1.c:131: Init: Assertion `!glIsProgramNV(1)' failed. Aborted ./vptest2 Mesa 6.4 implementation error: Bad target in r300NewProgram Please report at bugzilla.freedesktop.org vptest2: vptest2.c:63: Test1: Assertion `glIsProgramNV(1)' failed. Aborted ./yuvrect (complete log in attach) Image: 194x188 drmRadeonCmdBuffer: -22 (exiting) LOGPACK http://pwp.netcabo.pt/0448311801/xorg/logs.tar.bz2 ET Screenies http://pwp.netcabo.pt/0448311801/xorg/ET-oasis.jpg http://pwp.netcabo.pt/0448311801/xorg/ET-coasis.jpg --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Some Warnings
It's a just a simple txt pointing out some warnings that i have during compilation. They should be easy to resolve... Please check this warning!! Compiler gcc 3.4.4, glibc 2.3.5 Easy Solution, just give new line. Don't know if it's possible to give new line. Special file...:( PATH= Mesa/src/mesa/shader/slang/library/slang_vertex_builtin_gc_bin.h In file included from shader/slang/slang_compile.c:2263: shader/slang/library/slang_common_builtin_gc_bin.h:943:14: warning: no newline at end of file In file included from shader/slang/slang_compile.c:2267: shader/slang/library/slang_fragment_builtin_gc_bin.h:87:11: warning: no newline at end of file In file included from shader/slang/slang_compile.c:2271: shader/slang/library/slang_vertex_builtin_gc_bin.h:82:29: warning: no newline at end of file Medium Solution (Filter '-Wmissing-prototypes' in makefile) PATH= Mesa/src/glu/sgi/ g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -Wall -Wmissing-prototypes -g -fPIC -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 -DHAVE_ALIAS -DNDEBUG -DLIBRARYBUILD libnurbs/interface/bezierEval.cc -o libnurbs/interface/bezierEval.o cc1plus: warning: command line option "-Wmissing-prototypes" is valid for C/ObjC but not for C++ libnurbs/interface/bezierEval.cc:98: warning: 'void bezierCurveEvalfast(float, float, int, float*, int, int, float, float*)' defined but not used g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -Wall -Wmissing-prototypes -g -fPIC -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 -DHAVE_ALIAS -DNDEBUG -DLIBRARYBUILD libnurbs/interface/bezierPatch.cc -o libnurbs/interface/bezierPatch.o cc1plus: warning: command line option "-Wmissing-prototypes" is valid for C/ObjC but not for C++ g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -Wall -Wmissing-prototypes -g -fPIC -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 -DHAVE_ALIAS -DNDEBUG -DLIBRARYBUILD libnurbs/interface/bezierPatchMesh.cc -o libnurbs/interface/bezierPatchMesh.o cc1plus: warning: command line option "-Wmissing-prototypes" is valid for C/ObjC but not for C++ g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -Wall -Wmissing-prototypes -g -fPIC -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 -DHAVE_ALIAS -DNDEBUG -DLIBRARYBUILD libnurbs/interface/glcurveval.cc -o libnurbs/interface/glcurveval.o cc1plus: warning: command line option "-Wmissing-prototypes" is valid for C/ObjC but not for C++ g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -Wall -Wmissing-prototypes -g -fPIC -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 -DHAVE_ALIAS -DNDEBUG -DLIBRARYBUILD libnurbs/interface/glinterface.cc -o libnurbs/interface/glinterface.o cc1plus: warning: command line option "-Wmissing-prototypes" is valid for C/ObjC but not for C++ g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -Wall -Wmissing-prototypes -g -fPIC -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 -DHAVE_ALIAS -DNDEBUG -DLIBRARYBUILD libnurbs/interface/glrenderer.cc -o libnurbs/interface/glrenderer.o cc1plus: warning: command line option "-Wmissing-prototypes" is valid for C/ObjC but not for C++ g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -Wall -Wmissing-prototypes -g -fPIC -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 -DHAVE_ALIAS -DNDEBUG -DLIBRARYBUILD libnurbs/interface/glsurfeval.cc -o libnurbs/interface/glsurfeval.o cc1plus: warning: command line option "-Wmissing-prototypes" is valid for C/ObjC but not for C++ g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -Wall -Wmissing-prototypes -g -fPIC -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 -DHAVE_ALIAS -DNDEBU
[r300] Last Commit break things!
Just to warn that in last commit to r300, aapot has forgeted to del the 2 headers that have been deleted from the project both #include "r200_tcl.h", #include "r200_sanity.h", are not needed anymore, so please update radeon_ioctl.c By the way great work Quick patch --- radeon_ioctl.c 2005-10-27 01:19:06.0 +0100 +++ Mesa/src/mesa/drivers/dri/r300/radeon_ioctl.c 2005-10-27 00:19:44.0 +0100 @@ -46,10 +46,6 @@ #include "radeon_ioctl.h" #include "r200_ioctl.h" #include "r300_ioctl.h" -#if R200_MERGED -#include "r200_tcl.h" -#include "r200_sanity.h" -#endif #include "r300_state.h" #include "radeon_reg.h" Pedro Maia --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: My experience with the r300 driver
>It's not. The driver limits it to 128 MB because the CPU can't access >more than that. Thanks for the information! By the way, if i do the override that won't do nothing, in terms of amount of memory visible to GPU, right? --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: My experience with the r300 driver
Your Xorg version, is patched with a known patch(at least by me, it's from Mike A. Harris). Are you using gentoo!? Gentoo has this patch, probably also Red Hat and Fedora Core. With that patch, you cannot override. In gentoo just go to xorg-x11--patches-.tar.bz2 , and remove the patch "1214_all_4.3.0-radeon-disable-VideoRAM-option". delete digest and redigest the ebuild. Rebuild xorg-x11. :) With this patch you will only have 128 MB, i dont know how get around! Sorry. Pedro Maia --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: RE: My experience with the r300 driver
-Mensagem original- De: [EMAIL PROTECTED] em nome de Luis Felipe Strano Moraes Enviada: ter 11-10-2005 7:12 Para: dri-devel@lists.sourceforge.net Assunto: Re: My experience with the r300 driver On Mon, Oct 10, 2005 at 10:50:02PM +0200, Roland Scheidegger wrote: > This looks like pixmap damage. Are you using exa (not obvious from this > forum thread)? If not, does the option "XaaNoOffscreenPixmaps" help? Thanks alot. That did the trick. Just one question. Is there a way of seeing how much RAM my card has ? Couldn't find anything on dmesg or /proc, and it doesn't display anything during boot. Use this cat /proc/mtrr In this case: you'll have 3 lines First - Size of system memory Second - Size of Bios AGP Aperture Third - Size of Graphic card Memory or cat /var/log/Xorg.0.log |grep VideoRAM to do if XAA is enabled cat /var/log/Xorg.0.log |grep XAA to see if FastWrites is enabled cat /var/log/Xorg.0.log |grep "Fast Write" By the way are you using latest drm. Try always to use the lates cvs version of Xorg, drm and Mesa. At least with me, i'm not complainig. Once a week total recompile. (Xorg+ drm+ Mesa). i'm using R300 from the beginig of the project (sort of), since the red_tinted_cube snap. No problems so far. I also have a Gecube, but a 9600XT with 256 MB. By the way, why i have to use the override option? I have 256 MB, of memory in the card but X only detects 128MB, it has anything to do with Bios AGP Aperture, or a bug, maybe. Pedro Maia --lf > > Roland --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel