Announcement

Collapse
No announcement yet.

S3TC => r600{c,g}

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

  • #46
    Originally posted by adamk View Post
    I'm happy to say that I'm wrong. I don't know when this was resolved, but doom3 and ut2004 both ran just fine here with r300g + s3tc. Now I can only hope the same happens for r600 (classic or gallium) sometime soon.
    Wonder if it requires RE work.

    Comment


    • #47
      Anyone tried Doom3 on r600c recently?

      Comment


      • #48
        Originally posted by pingufunkybeat View Post
        Anyone tried Doom3 on r600c recently?
        Doom3:

        Intro movies : OK
        Menu : OK
        Hang after loading level.

        Comment


        • #49
          Originally posted by RavFX View Post
          Doom3:

          Intro movies : OK
          Menu : OK
          Hang after loading level.
          If you are running recent/git kernel it could be -

          r600 CS parser fixes

          Which seems to regress doom3 demo and ut2004 demo (dies at nvidia ad that it starts with).

          It's a known issue on the mailing list.

          Comment


          • #50
            Similiar error causes Heroes of Newerth to crash as well

            Comment


            • #51
              Originally posted by pingufunkybeat View Post
              Anyone tried Doom3 on r600c recently?
              I tried it like a week or two ago and didn't have any problems. I don't know why other people are.

              Comment


              • #52
                Doom3 on r600c with 2.6.36rc3+xorg-edgers ppa:

                Code:
                ------------- Warnings ---------------
                2 warnings
                drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info.
                pure virtual method called
                terminate called without an active exception
                signal caught: Aborted
                si_code -6
                Trying to exit gracefully..
                pure virtual method called
                terminate called recursively
                double fault Aborted, bailing out
                shutdown terminal support
                Segmentation fault
                dmesg:

                Code:
                [ 2663.304937] radeon 0000:04:00.0: mipmap bo too small (512 512 4 0 9 6291456 -> 7340096 have 8454144)
                [ 2663.304942] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
                [ 2663.410731] doom.x86[3416]: segfault at 0 ip 00000000ef5eecf8 sp 00000000ffeb1b80 error 4 in gamex86.so[ef47b000+355000]

                Comment


                • #53
                  Ugg edit window - Menu + intro video are fine; segfaults just after the first loading screen

                  Comment


                  • #54
                    Code:
                    drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info.
                    This suggests a mismatch between the kernel drm and the driver.

                    Unfortunately, doom3 is 32-bit only, and compiling 32-bit stuff is a bit of a pain on a 64-bit system. I'll have to wait a while until a later Mesa enters the gentoo compatibility pack.

                    Comment


                    • #55
                      Originally posted by pvtcupcakes View Post
                      I tried it like a week or two ago and didn't have any problems. I don't know why other people are.
                      Do the shadows work too?

                      Comment


                      • #56
                        Originally posted by pingufunkybeat View Post
                        Code:
                        drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info.
                        This suggests a mismatch between the kernel drm and the driver.

                        Unfortunately, doom3 is 32-bit only, and compiling 32-bit stuff is a bit of a pain on a 64-bit system. I'll have to wait a while until a later Mesa enters the gentoo compatibility pack.
                        That's the error I get caused by -

                        http://news.gmane.org/find-root.php?...&article=48583

                        Shadows in doom3 have never worked properly with 600c AFAIK -

                        https://bugs.freedesktop.org/show_bug.cgi?id=28363

                        Comment


                        • #57
                          I will try to revert patch "r600 CS parser fixes".. I have the same error when playing EVE online on random basis (I think it's not so random but... but...)

                          And I will retest doom3 after.

                          Comment


                          • #58
                            Doom3 work after reverting the patch!

                            Comment


                            • #59
                              Unfortunately, doom3 is 32-bit only, and compiling 32-bit stuff is a bit of a pain on a 64-bit system. I'll have to wait a while until a later Mesa enters the gentoo compatibility pack.
                              Why would you recompile the binary?

                              http://zerowing.idsoftware.com/linux...54ac0ae8bafe17

                              "There are no amd64 builds planned at this time. However the 32 bit binaries will run in a native amd64 environement."


                              This suggests a mismatch between the kernel drm and the driver.
                              Care to elaborate?

                              Comment


                              • #60
                                Originally posted by hmmm View Post
                                Why would you recompile the binary?
                                You need 32-bit Mesa (and 32-bit X, and 32-bit everything) to run 32-bit Doom.

                                Since I'm on Gentoo, I have to compile all of that.

                                Care to elaborate?
                                Parts of the driver are in the kernel (drm), and parts in Mesa and DDX. If you are running very new Mesa on top of an old kernel, you often get that message.

                                Comment

                                Working...
                                X