Page 3 of 3 FirstFirst 123
Results 21 to 22 of 22

Thread: Best way to file bug reports for FirePro or Catalyst drivers?

  1. #21
    Join Date
    Apr 2013
    Posts
    65

    Default

    not sure how AMD devs are choosing bugs to look at but they use feedback provided by users filling bugs.

    Here is 2 examples where they did leave comments:

    http://ati.cchtml.com/show_bug.cgi?id=816
    http://ati.cchtml.com/show_bug.cgi?id=832

  2. #22
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    906

    Default

    Quote Originally Posted by jjmcwill2003 View Post
    I have an AMD FirePro W8000 and am having trouble with the latest fglrx driver on Centos 5.9
    running startx or gdb results in Xorg crashing before anythink is drawn. The previous fglrx driver works just fine.

    Can one of you share the link to how I can contact professional support at AMD about this?
    I didn't got any other support channel than the unofficial ati.cchtml.com bug tracker.* :/

    However, at least for the bug that I filed

    http://ati.cchtml.com/show_bug.cgi?id=733

    it turned out that the AMD devs actually fixed it within ~2 month.
    I'm pretty sure that it was due to the bug report as the bug occurs only for very exotic dual-head
    configurations with some of the displays rotated. Additionally, my displays have different resolutions.
    Not sure what the real underlying reason was though. The bug was present for all Catalyst versions I tried.
    BTW, it is still present in the legacy driver.

    The downside; the devs never replied to my bug report.

    [*] You can try to ask Bridgman. Meanwhile he might have found the contact information and he's willing to share it.

Posting Permissions

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