Page 5 of 6 FirstFirst ... 3456 LastLast
Results 41 to 50 of 57

Thread: MLAA For Mesa Is Ready For Testing

  1. #41
    Join Date
    Mar 2009
    Posts
    130

    Default HD2400 Pro test

    Hi,

    Code:
    [msaun@phobos Linux]$ ./mlaatest
    Irrlicht Engine version 1.7.2
    Linux 2.6.38.8-32.fc15.x86_64 #1 SMP Mon Jun 13 19:49:05 UTC 2011 x86_64
    Creating X window...
    ATTENTION: default value of option vblank_mode overridden by environment.
    ATTENTION: default value of option vblank_mode overridden by environment.
    Visual chosen: : 282
    Using renderer: OpenGL 2.1
    Gallium 0.4 on AMD RV610: X.Org
    OpenGL driver version is 1.2 or better.
    GLSL version: 1.2
    Loaded texture: AreaMap33
    Unsupported texture format
    Quit message received.
    
    Ran 53.019s, average fps 55.35, min 1
    
    Average on fps 14.78, average off fps 94.92
    The vid card in this system is:
    01:00.0 VGA compatible controller: ATI Technologies Inc RV610 video device [Radeon HD 2400 PRO]

  2. #42
    Join Date
    Jan 2009
    Location
    Birmingham UK
    Posts
    2

    Default

    Hi all,
    I've read this Phoronix article with some interest. I have tested the MLAA for Mesa with the nouveau nvfx driver. I'm currently on Fedora 15 with a NV40 (Geforce 6,800 GT) Graphics Card.

    The results failed for me.when I exported my paths to point to my "just built" not installed Mesa from git,I ran the ./mlaatest and the test just froze. I couldn't save the error,but it came up with something like "no GLSL detected".

    I have built the xserver from git on my system and I keep that up to date,with a git version of Mesa there too. When I logged into my git xserver, ( exported the paths pointing to /mesa/lib and /mesa/lib/gallium to the Mesa that is in my xorg-git folder where I built my git version of xserver and ran /path/to/my/xorg/git/bin/startx).

    I ran the same ./mlaatest executable,the window did flare up,bwith lots of lines,and I got this error:

    [CODE[steve@mernivia 32]$ ./mlaatest
    Irrlicht Engine version 1.7.2
    Linux 3.0.0-rc6+ #1 SMP Wed Jul 6 11:03:12 BST 2011 i686
    Using renderer: OpenGL 2.1
    Mesa X11: Brian Paul
    OpenGL driver version is 1.2 or better.
    GLSL version: 1.2
    Mesa warning: User called no-op dispatch function (an unsupported extension function?)
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Mesa: User error: GL_INVALID_ENUM in glProgramParameters4fvNV
    Loaded texture: AreaMap33
    Mesa: User error: GL_INVALID_OPERATION in glEndConditionalRender()
    Mesa: User error: GL_INVALID_ENUM in glGetIntegerIndexedv(pname=GL_FRAMEBUFFER)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Unsupported texture format
    Mesa: User error: GL_INVALID_OPERATION in glEndConditionalRender()
    Mesa: User error: GL_INVALID_ENUM in glGetIntegerIndexedv(pname=GL_FRAMEBUFFER)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    FBO error
    FBO incomplete
    Mesa: User error: GL_INVALID_OPERATION in glEndConditionalRender()
    Mesa: User error: GL_INVALID_ENUM in glGetIntegerIndexedv(pname=GL_FRAMEBUFFER)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Unsupported texture format
    Mesa: User error: GL_INVALID_OPERATION in glEndConditionalRender()
    Mesa: User error: GL_INVALID_ENUM in glGetIntegerIndexedv(pname=GL_FRAMEBUFFER)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    FBO error
    FBO incomplete
    Mesa: User error: GL_INVALID_OPERATION in glEndConditionalRender()
    Mesa: User error: GL_INVALID_ENUM in glGetIntegerIndexedv(pname=GL_FRAMEBUFFER)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Unsupported texture format
    Mesa: User error: GL_INVALID_OPERATION in glEndConditionalRender()
    Mesa: User error: GL_INVALID_ENUM in glGetIntegerIndexedv(pname=GL_FRAMEBUFFER)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    Mesa: User error: GL_INVALID_ENUM in glTexParameter(target)
    FBO error
    FBO incomplete
    No RTT
    [/CODE]

    I hope that will help the developer working on the project.

    Regards,
    Nightcast2000

  3. #43
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,995

    Default

    It looks like you're running swrast, the oldest software driver. Other than that, I can't say what's broken there.

  4. #44
    Join Date
    Jan 2009
    Location
    Birmingham UK
    Posts
    2

    Default

    Hi there curaga,
    I think you are indeed right I was using the swrast driver for some reason..
    Anyway, I got the latest commits from Mesa git and compiled mesa with:

    Code:
    ./autogen.sh --enable-debug --enable-xcb --enable-glx-tls --enable-asm --enable-xorg --with-dri-drivers=nouveau --with-gallium-drivers=nouveau,swrast --with-expat=/usr/lib  --disable-egl --enable-gbm --enable-gl-osmesa --enable-gallium-gbm --enable-shared-glapi
    After I compiled it, I exported the parameters: export LD_LIBRARY_PATH=/home/steve/mesa/lib
    export LIBGL_DRIVERS_PATH=/home/steve/mesa/lib/gallium
    export LIBGL_DEBUG=verbose

    Here is the output of glxinfo: http://pastebin.com/WSWMg71a

    I then cd'ed over to mlaatest/32 and ran ./mlaatest again I did get some errors and the whole thing froze again. I took a picture with my mobile phone which should be attacted to this post.

    I've tried to run the test again to redirect the output to a txt file,but all I got is this:
    Code:
    ATTENTION: default value of option vblank_mode overridden by environment.
    ATTENTION: default value of option vblank_mode overridden by environment.
    nvfx_screen_get_param:94 -  Warning: unknown PIPE_CAP 29
    I hope this helps, I understand the nvfx driver is certainly not ready at all, but I hope the information I have provided will be useful.

    Regards,
    Nightcast2000

  5. #45
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,995

    Default

    I think your experience is similar to Michael's - gf6 nouveau has been broken for him too for a while. PIPE_CAP 29 is SM3, which your card should support, but the driver isn't updated to know it yet.

    Thanks for the glxinfo, looks like nvfx doesn't expose ARB_shader_texture_lod yet, even though your hw would support it. So even if the driver were stable, it wouldn't run the effect right now.

    It's a bit sad that this at least for now locks out gf6 and gf7, the generations able to run it but on the nvfx driver. Fermi on the nvc0 driver is known to work.

  6. #46

    Default

    I added the pp branch to mesa and I see the new driconf options. However when I enable them nothing change (I tried also the removing of color channel). RV530 on a r300g.

    EDIT: same result with llvmpipe

    If I get it to work will be OK to add to my PPA?
    Last edited by oibaf; 07-20-2011 at 07:07 AM.

  7. #47
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,995

    Default

    The pp branch only does llvmpipe + softpipe right now. I'm currently waiting for a Brazos netbook to ship to do some hw testing.

    Sure, you can ship it - though with only software support right now, it's not too useful. It should not break anything else.


    With llvmpipe, try: PP_DEBUG=1 pp_nored=1 glxgears
    If you don't see the effect, please post the output.

  8. #48

    Default

    Quote Originally Posted by curaga View Post
    The pp branch only does llvmpipe + softpipe right now. I'm currently waiting for a Brazos netbook to ship to do some hw testing.

    Sure, you can ship it - though with only software support right now, it's not too useful. It should not break anything else.


    With llvmpipe, try: PP_DEBUG=1 pp_nored=1 glxgears
    If you don't see the effect, please post the output.
    OK, that works, thanks. Are the driconf settings still not properly working?

  9. #49
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,995

    Default

    They are for me, but llvmpipe uses "dri" as the driver name, not dri2, for some reason.

  10. #50

    Default

    Quote Originally Posted by curaga View Post
    They are for me, but llvmpipe uses "dri" as the driver name, not dri2, for some reason.
    OK, it works.

    Strange however that when I set it with driconf it always ends up with driver="r300" even when .drirc is missing and when using 'LIBGL_ALWAYS_SOFTWARE=1 driconf' (also it correctly detect llvmpipe in the GUI)...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •