Announcement

Collapse
No announcement yet.

r6xx 3D games

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

  • #76
    Originally posted by legume View Post
    Direct rendering issues (only tested openarena so far) have been fixed :-)

    http://cgit.freedesktop.org/mesa/mes...956daa7eb64806
    That's right!

    Confirmed in openarena and Iris2's menu! Huge congratulations for taiu and ppl helping him! Thanks a lot!

    Comment


    • #77
      Yep, I was coming to report it. Sometimes the left half of the screen flickers, but otherwise it works great. Now I don't need to disable composite in metacity to play quake3. I hope the shadow issue will be resolved soon, because I feel like I'm a cheater when I see other people's shadows through the walls


      Seeing as 3D support is becoming too boring and stable , I'd like to check the progress of KMS. Does anyone know which git repositories we need to pull? I applied this patch to the latest 31-rc8 kernel and I get KMS (1680x1050 at boot), but X doesn't work with the master branch of the radeon driver.

      Comment


      • #78
        Originally posted by Fran View Post
        Seeing as 3D support is becoming too boring and stable , I'd like to check the progress of KMS. Does anyone know which git repositories we need to pull? I applied this patch to the latest 31-rc8 kernel and I get KMS (1680x1050 at boot), but X doesn't work with the master branch of the radeon driver.
        you need this branch of the ddx, however, this isn't really ready for users yet, and will more than likely not work.
        http://cgit.freedesktop.org/~airlied.../log/?h=r6xxcs

        Comment


        • #79
          Originally posted by agd5f View Post
          you need this branch of the ddx, however, this isn't really ready for users yet, and will more than likely not work.
          http://cgit.freedesktop.org/~airlied.../log/?h=r6xxcs
          So is it safe to say that r600 kms won't be ready for 2.6.32 since the merge window is going to be opening in a couple of weeks?

          Comment


          • #80
            Originally posted by pvtcupcakes View Post
            So is it safe to say that r600 kms won't be ready for 2.6.32 since the merge window is going to be opening in a couple of weeks?
            It'll go in in staging just like r1xx-r5xx in the previous kernel.

            Comment


            • #81
              Originally posted by agd5f View Post
              It'll go in in staging just like r1xx-r5xx in the previous kernel.
              Cool. I thought when you said "probably won't work" that it wasn't even good enough to be a staging driver.

              Comment


              • #82
                Originally posted by agd5f View Post
                you need this branch of the ddx, however, this isn't really ready for users yet, and will more than likely not work.
                http://cgit.freedesktop.org/~airlied.../log/?h=r6xxcs
                Yeah, I was a bit too optimistic :P. With the kernel patch I posted the console works great (fast and high resolution) but when I start X I get exactly the same results with airlied's branch as with the master branch: a garbled screen. And it does the modesetting again, instead of using the mode set by the kernel. Switching between vt and X is not smooth either.

                Well, I had to try.

                Comment


                • #83
                  Originally posted by Fran View Post
                  Yeah, I was a bit too optimistic :P. With the kernel patch I posted the console works great (fast and high resolution) but when I start X I get exactly the same results with airlied's branch as with the master branch: a garbled screen. And it does the modesetting again, instead of using the mode set by the kernel. Switching between vt and X is not smooth either.

                  Well, I had to try.
                  Sounds like perhaps you aren't using a KMS enabled ddx. Also, make sure the radeon drm is loaded with modeset=1 before starting X.

                  Comment


                  • #84
                    Originally posted by agd5f View Post
                    Sounds like perhaps you aren't using a KMS enabled ddx. Also, make sure the radeon drm is loaded with modeset=1 before starting X.
                    I compiled drm into the kernel (2.6.31-rc8 with the patch I posted from fedora devel) and activated radeon modeset by default. I get 1680x1050 at boot without any vga=xxx parameter in grub, so the kernel is detecting my monitor resolution correctly and setting the video mode. Also, my ebuild for xf86-video-ati says that it compiled commit 608872a37345e1997dbef57cbec82101073adfef (latest in r6xxcs) and I made sure it was configured with --enable-kms. Maybe I'm missing something. Maybe the drm patch in fedora devel cvs for 2.6.31-rcX is outdated (from Aug 20), but it's the only one I found and applies cleanly over rc8.

                    Comment


                    • #85
                      Just tried doom3 without the libgl_always_indirect...=1 line

                      I was impressed it worked and I got past the cd key and selected difficulty level. Immediately thereafter, X locked up. Frontpower button worked to shutdown. Upon reboot, nothing really in logs to indicate problem. One message but I see a lot is: MTRR 4 not used.

                      So some progress with gits but not there yet.

                      Comment


                      • #86
                        Yes!

                        OpenArena works great now!

                        I don't know if I'm imagining, but it seems smoother than in indirect mode too.

                        The spots which used to crash the X server in indirect mode now only crash OpenArena. For example, when the first map finishes, I get this:

                        Code:
                        Invalid source texcoord for TEX instruction
                        validated 0x3d67520 [0xE030B000, 0xE030B000]
                        above end: 0x3d67520 0x000001B1 0xE030B000
                        Same error prevents me from playing supertuxkart.

                        But in any case, kudo to the devs for getting this working!

                        Comment


                        • #87
                          Originally posted by pingufunkybeat View Post
                          Yes!

                          OpenArena works great now!

                          I don't know if I'm imagining, but it seems smoother than in indirect mode too.

                          The spots which used to crash the X server in indirect mode now only crash OpenArena. For example, when the first map finishes, I get this:

                          Code:
                          Invalid source texcoord for TEX instruction
                          validated 0x3d67520 [0xE030B000, 0xE030B000]
                          above end: 0x3d67520 0x000001B1 0xE030B000
                          Same error prevents me from playing supertuxkart.

                          But in any case, kudo to the devs for getting this working!
                          The shader compiler doesn't yet support tex coords from shader constants, only inputs and temps. It's on the list of things to implement.

                          Comment


                          • #88
                            Originally posted by pingufunkybeat View Post
                            Yes!

                            OpenArena works great now!

                            I don't know if I'm imagining, but it seems smoother than in indirect mode too.

                            The spots which used to crash the X server in indirect mode now only crash OpenArena. For example, when the first map finishes, I get this:

                            Code:
                            Invalid source texcoord for TEX instruction
                            validated 0x3d67520 [0xE030B000, 0xE030B000]
                            above end: 0x3d67520 0x000001B1 0xE030B000
                            Same error prevents me from playing supertuxkart.

                            But in any case, kudo to the devs for getting this working!
                            It's fixed, wohoo!

                            Comment


                            • #89
                              I just tried Google Earth too, was running nice and fast, just some corruption when you zoom in near water. (slight flicker in ocean surface)

                              Comment


                              • #90
                                My xserver crashes when i try to start Google Earth. I'm using mesa from xorg-edgers and built the latest drm on Ubuntu Jaunty. (Mobility Radeon HD 2600)

                                Comment

                                Working...
                                X