Announcement

Collapse
No announcement yet.

Initial R6xx/R7xx 3D Driver

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by bridgman View Post
    Cool, I'm glad someone got it working.

    It did run better a few weeks ago before texture support was added; I suspect something got broken either then or during the subsequent cleanup before release. We'll figure it out next week...
    nice to know a cleanup breaks something: it's exactly the same when at home, cleaning you break something by accident sweet old real life

    Comment


    • #32
      Originally posted by legume View Post
      it segfaults every time at 30 seconds and there is so much debugging output that I have to redirect stderr to /dev/null
      A bit more info on the segfault - redirecting to a file (which is 200k lines after 30 secs) ends with -

      **********WARN_ONCE******************
      File r600_mem.c function r600MemAlloc line 274
      Ran out of GART memory (for 1048576)!
      *************************************

      Comment


      • #33
        Originally posted by Vighy View Post
        nice to know a cleanup breaks something: it's exactly the same when at home, cleaning you break something by accident sweet old real life
        I wouldn't equate these changes with cleanup. They're more like adding a new section to the house (some walls may get knocked down in the process).

        Comment


        • #34
          Could you tell me which application cause this problem?

          Comment


          • #35
            Wow glxgears works for me. I get "1254 frames in 5.0 seconds = 249.975 FPS" and everything looks normal. Only the cpu usage is very high, but i think that's normal right now.

            I'm using Ubuntu 8.04 with the latest ati and drm versions on a Mobility Radeon 2600.

            Comment


            • #36
              Originally posted by cooperyuan View Post
              Could you tell me which application cause this problem?
              Hi

              I replied to your PM - I guess you got linked directly to my last post. See my first post in this thread for more info and screen shots of what I see with glxgears.

              Comment


              • #37
                Originally posted by Boerkel View Post
                Wow glxgears works for me. I get "1254 frames in 5.0 seconds = 249.975 FPS" and everything looks normal. Only the cpu usage is very high, but i think that's normal right now.

                I'm using Ubuntu 8.04 with the latest ati and drm versions on a Mobility Radeon 2600.

                I also get about 250 fps with glxgears and high cpu usage when the software rasterizer is used. Are you sure you are not using the software rasterizer?

                Can yo do a:
                Code:
                glxinfo|grep renderer

                Comment


                • #38
                  Originally posted by Boerkel View Post
                  Wow glxgears works for me. I get "1254 frames in 5.0 seconds = 249.975 FPS" and everything looks normal. Only the cpu usage is very high, but i think that's normal right now.

                  I'm using Ubuntu 8.04 with the latest ati and drm versions on a Mobility Radeon 2600.
                  Unless you have built the correct branches from mesa and agd5f's drm then you will be using the software renderer - swrast.

                  glxinfo | grep renderer should tell you.

                  Edit: lol beaten by 4 minutes :-)

                  Comment


                  • #39
                    Originally posted by nanonyme View Post
                    Heh, looks like the shadows on the gears were calculated horribly wrong in all three gears. (Kinda interesting that it seems some stuff in the red gear is rendered *completely* black)
                    Edit: Oh, wait. Actually all three gears have some of their lower-right portions rendered completely black. Me blind.
                    Seems like the backface culling isn't rendered well...

                    Comment


                    • #40
                      Originally posted by DanL View Post
                      I wouldn't equate these changes with cleanup.
                      Please also read the original message which was replied to, mk?
                      As in, this:
                      Originally posted by bridgman View Post
                      I suspect something got broken either then or during the subsequent cleanup before release.

                      Comment


                      • #41
                        Probably you can synchronize tip code and have a try. I just fix memory issue.

                        Comment


                        • #42
                          Originally posted by cooperyuan View Post
                          Probably you can synchronize tip code and have a try. I just fix memory issue.
                          Still locks-up my HD 3200

                          Comment


                          • #43
                            Originally posted by cooperyuan View Post
                            Probably you can synchronize tip code and have a try. I just fix memory issue.
                            I get a lockup after a second now. It's SysRq able - some info from kern log
                            Code:
                            Apr 22 12:36:50 amd kernel: [drm] wait for fifo failed status : 0xA27334AC 0x00000103
                            Apr 22 12:37:00 amd last message repeated 96 times
                            Apr 22 12:37:00 amd kernel: SysRq : Emergency Sync
                            Apr 22 12:37:00 amd kernel: [drm] wait for fifo failed status : 0xA27334AC 0x00000103
                            Apr 22 12:37:00 amd kernel: [drm] wait for fifo failed status : 0xA27334AC 0x00000103
                            Apr 22 12:37:00 amd kernel: Emergency Sync complete
                            Apr 22 12:37:00 amd kernel: [drm] wait for fifo failed status : 0xA27334AC 0x00000103
                            Apr 22 12:37:02 amd last message repeated 24 times
                            Apr 22 12:37:03 amd kernel: SysRq : Emergency Remount R/O
                            Apr 22 12:37:03 amd kernel: [drm] wait for fifo failed status : 0xA27334AC 0x00000103
                            Output to terminal
                            Code:
                             [r600]  Mappings:
                                    Registers                         cpu 0xa79bb000   size 0x00010000   handle 0xe1000000
                                    Status                            cpu 0xa79ba000   size 0x00001000   handle 0xc0101000
                                    GART           gpu 0x00c0000000
                                    DRM buffers    gpu 0x00c0102000   cpu 0xa5b3a000   size 0x00200000
                                    GART Textures  gpu 0x00c0302000   cpu 0xa5d3a000   size 0x01c80000   handle 0xc0302000
                                    Framebuffer    gpu 0x00d0000000   cpu 0xa79cb000   size 0x10000000
                                    Front Target   gpu 0x00d0000000   cpu 0xa79cb000   size 0x00640000   pitch 0x0500
                                    Back  Target   gpu 0x00d0648000   cpu 0xa8013000   size 0x00640000   pitch 0x0500
                                    Depth Target   gpu 0x00d0c88000   cpu 0xa8653000   size 0x00640000   pitch 0x0500
                            
                            [r600] r600MakeCurrent   (r600_context.c:413)
                            [r600]    Context 0x8058560 Draw 0x8329cf0 Read 0x8329cf0
                            [r600] r600MemAlloc   (r600_mem.c:289)   allocated 1 at age 0
                            [r600] r600MemFree   (r600_mem.c:328)   freed 1 at age 0
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600MemAlloc   (r600_mem.c:289)   allocated 1 at age 0
                            [r600] r600MemFree   (r600_mem.c:328)   freed 1 at age 0
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321
                            [r600] r600CopyBuffer   (r600_screen.c:479)
                            [r600]    ClipRect 4:21-304:321

                            Comment


                            • #44
                              Originally posted by legume View Post
                              I get a lockup after a second now.
                              Nice to know that I'm now not the only one getting lock-ups with this new R6xx/R7xx 3D Driver

                              Originally posted by legume View Post
                              Code:
                              Apr 22 12:36:50 amd kernel: [drm] wait for fifo failed status : 0xA27334AC 0x00000103
                              Yep, is almost identical to what I get:
                              Code:
                              [drm] wait for fifo failed status : 0xA02034AC 0x00000003

                              Comment


                              • #45
                                Giving r600-r700 3D code a shot... without luck.

                                Hi guys, I got a Radeon HD3200 (rs780) and I'm giving the new 3D code a try. I understand it's experimental, a git branch, an unstable equilibrium and so on, but still, I'd like to get it to work.
                                So I compiled and installed the very latest DRM and Mesa stuff from the appropriate branches (r6xx-r7xx-3d for DRM and r6xx-r7xx-support for Mesa). The DRM and Radeon kernel modules build and insert correctly; in /usr/lib64/dri I get the following files:
                                Code:
                                r200_dri.so  r300_dri.so  r600_dri.so  radeon_dri.so swrast_dri.so
                                When I start X though (with AIGLX disabled, is that right?), the DRI/DRM stuff seems to work until I get the following:
                                Code:
                                (II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so
                                (II) GLX: Initialized DRISWRAST GL provider for screen 0
                                so it's using software rendering and r600_dri.so is not used. Also, why do I get a message from AIGLX, since it's disabled?
                                I took a look at the autogen command for Mesa and noticed the following:
                                Code:
                                --with-dri-drivers=swrast,radeon,r600
                                so I thought maybe the order had a meaning, but it doesn't, and even if I only build the r600 driver (like --with-dri-drivers=r600), X still looks for the swrast_dri.so library and complains that it can't be found. Should I somehow tell X which DRI driver to use (r600, in this case, I guess)?
                                Finally, I'm using xf86-video-ati 6.12.2, and, as stated above, today's git for DRM and Mesa.
                                Any further info needed, just ask, and thanks in advance!

                                Comment

                                Working...
                                X