Announcement

Collapse
No announcement yet.

r6xx 3D games

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

  • #31
    I will definitely consider buying the game once the drivers are stable enough. I can't stand the burden of installing upgrading those closed drivers.

    Comment


    • #32
      With the latest updates I cannot play quake3 anymore . When starting a level X restarts with this:
      Code:
      [drm:r600_nomm_relocate] *ERROR* bad offset! 0x2
      [drm:r600_cs_packet3] *ERROR* bad SURFACE_SYNC
      X[1882]: segfault at bf87b0e1 ip 00007fc5ac9a89d7 sp 00007fff819d72e0 error 4 in libgcc_s.so.1[7fc5ac999000+16000]
      [drm] Resetting GPU
      Last edited by Fran; 23 August 2009, 05:29 AM.

      Comment


      • #33
        Increased errors with most recent changes.

        eduke32 crashes when your player is falling down chute in very beginning location.

        CLI shows: drmRadeonCmdBuffer: -22

        dmesg shows:
        [drm:r600_nomm_relocate] *ERROR* bad offset! 0x2
        [drm:r600_cs_packet3] *ERROR* bad SURFACE_SYNC

        Comment


        • #34
          commit "r600: move full state to radeon state atoms" it known to cause problems

          It causes locks up on starting glxgears on my RV620.

          marvin24_ reported Xorg crash on starting hiverise:
          [drm:r600_nomm_relocate] *ERROR* bad offset! 0x2
          [drm:r600_cs_packet3] *ERROR* bad SURFACE_SYNC

          Now you two confirmed that.

          Comment


          • #35
            I just pulled the latest changes from mesa and glxgears still works fine for me (on an RV710)

            Comment


            • #36
              For anyone who experiencing lockups with very recent mesa code (reported with rv620 / rv635 so far) please pull the latest Mesa code and try again.
              Last edited by bridgman; 23 August 2009, 01:23 PM.
              Test signature

              Comment


              • #37
                Already confirmed on IRC. Bug fixed.

                Comment


                • #38
                  I've just pulled commit 41934be2544ac47a308719c08ee1bba344fed78d and still get the same X restarts when starting a quake3 level:

                  [drm:r600_nomm_relocate] *ERROR* bad offset! 0x2
                  [drm:r600_cs_packet3] *ERROR* bad SURFACE_SYNC
                  [drm] Resetting GPU

                  Yesterday it worked ok. I have a RV670 (3850).

                  (edit) Neverball also stopped working with the same error in dmesg, but only in some levels.
                  Last edited by Fran; 23 August 2009, 01:39 PM.

                  Comment


                  • #39
                    Originally posted by Fran View Post
                    I've just pulled commit 41934be2544ac47a308719c08ee1bba344fed78d and still get the same X restarts when starting a quake3 level:

                    [drm:r600_nomm_relocate] *ERROR* bad offset! 0x2
                    [drm:r600_cs_packet3] *ERROR* bad SURFACE_SYNC
                    [drm] Resetting GPU

                    Yesterday it worked ok. I have a RV670 (3850).
                    Hm, did you try rebooting after installing mesa? Or at least X restarting?

                    Could you verify if "r600: move full state to radeon state atoms" is first broken commit for you? To do that check what happens with these two commits:
                    1) 180c304943537210b2f6459ea21e9bff85f9827e
                    2) 17813931db4cc114262d306f4c1484cd353a13f9

                    Comment


                    • #40
                      Originally posted by Zajec View Post
                      Hm, did you try rebooting after installing mesa? Or at least X restarting?

                      Could you verify if "r600: move full state to radeon state atoms" is first broken commit for you? To do that check what happens with these two commits:
                      1) 180c304943537210b2f6459ea21e9bff85f9827e
                      2) 17813931db4cc114262d306f4c1484cd353a13f9
                      Yeah, I restarted X and got the same problem, so I rebooted and I still get it.


                      I'll see if I can get the mesa ebuild to pull specific commits.

                      (edit) Done, I just had to add the "EGIT_TREE" variable to the ebuild. Results:

                      180c304943537210b2f6459ea21e9bff85f9827e -> quake3 still restarts X when entering a level with that dmesg error
                      17813931db4cc114262d306f4c1484cd353a13f9 -> works
                      Last edited by Fran; 23 August 2009, 02:49 PM.

                      Comment

                      Working...
                      X