Page 4 of 29 FirstFirst ... 2345614 ... LastLast
Results 31 to 40 of 290

Thread: r6xx 3D games

  1. #31
    Join Date
    Dec 2007
    Posts
    91

    Default

    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.

  2. #32
    Join Date
    Apr 2008
    Location
    A Coruņa (Spain)
    Posts
    100

    Default

    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; 08-23-2009 at 05:29 AM.

  3. #33
    Join Date
    Jul 2008
    Posts
    208

    Default

    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

  4. #34
    Join Date
    Oct 2008
    Location
    Poland
    Posts
    183

    Default

    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.

  5. #35
    Join Date
    Oct 2007
    Posts
    1,274

    Default

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

  6. #36
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,458

    Default

    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; 08-23-2009 at 01:23 PM.

  7. #37
    Join Date
    Oct 2008
    Location
    Poland
    Posts
    183

    Default

    Already confirmed on IRC. Bug fixed.

  8. #38
    Join Date
    Apr 2008
    Location
    A Coruņa (Spain)
    Posts
    100

    Default

    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; 08-23-2009 at 01:39 PM.

  9. #39
    Join Date
    Oct 2008
    Location
    Poland
    Posts
    183

    Default

    Quote 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

  10. #40
    Join Date
    Apr 2008
    Location
    A Coruņa (Spain)
    Posts
    100

    Default

    Quote 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; 08-23-2009 at 02:49 PM.

Posting Permissions

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