Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: status of r600/r700 AGP support?

  1. #1

    Default status of r600/r700 AGP support?

    I've tried KMS-support for r600/r700 cards with the 2.6.32 release candidate and can say, it looks nice. 2D and 3D acceleratioand even UTS/DFS seemed to work with my AGP card. But after a while I got again screen corruptions like before KMS and UTS/DFS enabled. Additionally I found now some entries from the edac driver in the log:

    Oct 13 09:40:50 datengrab kernel: Northbridge Error, node 0, core: -1
    Oct 13 09:40:50 datengrab kernel: K8 ECC error.

    So the radeon driver is still not usable over a longer period.
    Does anybody know how far the investigation of the AGP problems are?

  2. #2
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,538

    Default

    Does it work if you disable UTS/DFS ?

  3. #3

    Default

    Quote Originally Posted by bridgman View Post
    Does it work if you disable UTS/DFS ?
    I assume still through the xorg.conf as without KMS? I'll test, but it will take some time as I don't know how to reproduce the errors reliable.

  4. #4
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,538

    Default

    Hmmm... good question. I'm not sure, hopefully agd5f or someone else will jump in.

    The Northbridge error does not appear to be graphics related - I don't think we do anything with ECC in the graphics drivers.

  5. #5

    Default

    Quote Originally Posted by bridgman View Post
    Hmmm... good question. I'm not sure, hopefully agd5f or someone else will jump in.

    The Northbridge error does not appear to be graphics related - I don't think we do anything with ECC in the graphics drivers.
    The ECC error messages only came only with 2.6.32-rc4 and KMS. So either the edac driver catches more MCEs through the updates the driver got, or it's really triggerd by KMS. I can't really test this, since it needs 2.6.32 for KMS and the fglrx doesn't work with this version.

    I have a Opteron 144 on aTyan Tiger K8W S2875 with enabled ECC for RAM and Caches working. So it's not neccessary that KMS is doing anything with ECC. It "only" corrupts the data which is recognized by the hardware und reported by the edac driver (just a thought).

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

    Default

    If you disable KMS at boot does the error still occur ?

  7. #7

    Default

    Quote Originally Posted by bridgman View Post
    If you disable KMS at boot does the error still occur ?
    Will give it a try later. For now I've disabled UTS/DFS (options in xorg.conf work) and try if the error still occur.

    PS: Disabling UTS/DFS didn't help:

    Northbridge Error, node 0, core: -1
    K8 ECC error.
    Northbridge Error, node 0, core: -1
    K8 ECC error.

    and again screen corruptions: http://www.stud.tu-ilmenau.de/~johi-...chirmfoto1.png

    PPS: With KMS enabled and UTS/DFS disabled (at least the log says so), the system seems to be more responsible and fluid than with UTS/DFS enabled. With KMS disabled, UTS/DFS are disabled by default for AGP cards. The system is then really really slow and nearly unusable. X eats more than 80% CPU. That's the reason why I was still using fglrx. No more ECC errors since I've disabled KMS for now.
    Last edited by PuckPoltergeist; 10-13-2009 at 07:58 PM.

  8. #8
    Join Date
    Jan 2008
    Posts
    294

    Default

    KMS + RV670 AGP is going well for me so far. I haven't seen any corruption yet, and I would if dfs is used with ums.

    I also get a game perf boost, in enemy territory as much as X3 on a complex scene. This is compared with ums + agp as well as kms pcie - quite suprising really, though I think there must be some issue with ums + agp that is slowing things (maybe having to use no_wb=1 doesn't help - but then kms doesn't use wb).

    There was some uts corruption recently in drm-next that is fixed now - I didn't see it on fonts, but you could possibly be running a kernel that still has that.

    Disabling uts did fix it though - did your xorg.log confirm uts/dfs were off when you tested?

  9. #9

    Default

    Quote Originally Posted by legume View Post
    There was some uts corruption recently in drm-next that is fixed now - I didn't see it on fonts, but you could possibly be running a kernel that still has that.
    I'm using linux-2.6 master. There where some checkins since I've built the kernel but nothing radeon related.

    Disabling uts did fix it though - did your xorg.log confirm uts/dfs were off when you tested?
    Yes, it did so.

  10. #10
    Join Date
    Jan 2008
    Posts
    294

    Default

    Quote Originally Posted by PuckPoltergeist View Post
    I'm using linux-2.6 master. There where some checkins since I've built the kernel but nothing radeon related.


    Yes, it did so.
    OK I guess it's a separate issue, though if I am looking at the right tree it looks like linus hasn't pulled the fix yet.

    It may not show unless you have a recent git ddx as well and it only seemed to affect some image types for me.

Posting Permissions

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