Announcement

Collapse
No announcement yet.

AMD "Hawaii" Open-Source GPU Acceleration Still Not Working Right

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

  • _SXX_
    replied
    Originally posted by Rakot View Post
    It is so fun when nvidia trolls post comments about some troubles in fglrx and when they are poked into problems in nvidia's blob refuse to see it.
    Only Nvidia GPUs I have it's some GT 430 and GeForce 210 that used in my home server for blob and nouveau testing. They working quite good for purposes low-end GPUs designed for, but Nvidia is not suitable for me (don't work with GPU passthrough).

    Only reason why I participate this topic it's because I want AMD to fix their driver and want to see more news on moving more resources towards proper driver. So I seen this news and it's message I can read: hey AMD, fix this! Unfortunately fanboys fail to see this and only see some "Nvidia trolls".
    Last edited by _SXX_; 21 July 2014, 09:14 PM.

    Leave a comment:


  • agd5f
    replied
    Originally posted by _SXX_ View Post
    No they are not.
    All R series GPU except R9 290(X) it's basically rebranded HD7XXX with slightly different clocks/voltages/etc.
    Not exactly. R7 260 and 260x are sea islands parts, same as hawaii.

    Leave a comment:


  • Rakot
    replied
    Originally posted by _SXX_ View Post
    It's just funny to see AMD fanboys in this topic: drivers will work in future, more features, Nvidia kernel crashes, fglrx not that bad, never have a problems. In same time this topic isn't about Nvidia, but about the fact: in few months it's will be year after Hawaii GPUs released and GPUs support it's still broken in open source drivers.
    It is so fun when nvidia trolls post comments about some troubles in fglrx and when they are poked into problems in nvidia's blob refuse to see it.

    Leave a comment:


  • Kivada
    replied
    Originally posted by dungeon View Post
    Seems like reverse engineering knowledge is much needed in this case , i mean to make this HAWAII chip respond . Really, when devs knows how to program it but it refuse to work and they have all information available then... how to figured out that chip other then trying small reing of fglrx .
    No need, the docs are already there, there aren't that many Linux users using high end GPUs to put it on the high priority list. Give it another year, Star Citizen, Metro Complete Pack, Civilization: Beyond Earth, Witcher 3 and whatever else gets announced will provide a need for a focus on the high end GPUs sold in the hundreds of thousands as well as the low and mid range that have sold in the millions.

    Leave a comment:


  • _SXX_
    replied
    Originally posted by Modu View Post
    R9 290X and R9 290 are high-end Sea Islands chips, R7 260 and R7260X are mid range... which are very related.
    No they are not.
    All R series GPU except R9 290(X) it's basically rebranded HD7XXX with slightly different clocks/voltages/etc.

    Leave a comment:


  • _SXX_
    replied
    Originally posted by Rakot View Post
    Unfortunately it works on fglrx as well. Mesa works because it has to mimic nvidia (read my post carefully with an example of Mesa's commit). Also I saw a couple of bug reports in fglrx's bugzilla where the problem was not in fglrx but in the software not properly following specs. But, of course, there are some troubles in fglrx but some of them are not the fault of AMD.
    Unigine it's just one example which is pretty small and surprise: it's works with FGLRX which "follows specs more closely" and in same time don't work on Intel (but work on R600g). I seen many game releases on Steam and Catalyst have a more compatibility problems compared to Mesa/Nvidia. Not so long ago "good" fglrx just crashed my X server every time I tried to run Chrome and I pretty sure it's not because Chrome didn't follow some spec.

    It's just funny to see AMD fanboys in this topic: drivers will work in future, more features, Nvidia kernel crashes, fglrx not that bad, never have a problems. In same time this topic isn't about Nvidia, but about the fact: in few months it's will be year after Hawaii GPUs released and GPUs support it's still broken in open source drivers.

    I personally stuck with my HD6950 1GB (and 1GB it's really really low in 2014) and I want new faster GPU with more VRAM and open source drivers. I don't want to waste money on "slightly better" because only alternative AMD provide it's rebranded 7XXX. Seriously I can deal with current R600g/RadeonSI limitations, but I can't buy broken GPU and I'm not going to use Catalyst because it's will never work well for most recent kernels (I need them for KVM/QEMU).

    Leave a comment:


  • Modu
    replied
    Sea Islands: High-end no accelleration support, mid-range almost perfect support.

    My R7 260X works perfect with both Catalyst and open source stack (oibaf PPA, Linux 3.15).
    Almost perfect. Runs cool, fast and stable. There isn't a single Steam game it didn't play with decent performance using OSS drivers.

    Your GPU isn't from Hawaii series.
    Hawaii is R9 290X and R9 290 only.
    R9 290X and R9 290 are high-end Sea Islands chips, R7 260 and R7260X are mid range... which are very related.

    Leave a comment:


  • dungeon
    replied
    Originally posted by Kivada View Post
    Theres a bunch of community devs, most of them got hired on.

    The Nouveau team has zero support at all from Nvidia and it shows because all of what they do has only come out of reverse engineering and as such can never be as good as the OSS Radeon drivers no matter how many dev hours they throw at it.
    Seems like reverse engineering knowledge is much needed in this case , i mean to make this HAWAII chip respond . Really, when devs knows how to program it but it refuse to work and they have all information available then... how to figured out that chip other then trying small reing of fglrx .

    Leave a comment:


  • Sdar
    replied
    a fully functional OpenCL compute stack
    It's going to be better to wait until they fixed the compiler for large kernels before calling this FULLY FUNCTIONAL.

    7950 here, with catalyst i have random crashes here and there but i give up on 14.4 drivers so i'm not sure if it's better now, foss drivers works great but lacks performance and features maybe next year they'll perform better than the proprietary driver cause they're improving faster than cataclysm.

    Also i hope amd managed to push the Opencl fix this month cause we've waited long enough to get a fully functional OpenCL compute stack.

    Leave a comment:


  • Kivada
    replied
    Originally posted by A Laggy Grunt View Post
    "Release the docs and there will be drivers" worked much better when the hardware was much simpler. Nowadays, it helps a lot to have a driver team that knows not only how to read specs, but how to work together and what they can expect of each other.

    Drivers don't write themselves, teams of people write them. The bigger, smarter, better equipped, and better coordinated the team, the faster and better the results can be.
    Theres a bunch of community devs, most of them got hired on.

    The Nouveau team has zero support at all from Nvidia and it shows because all of what they do has only come out of reverse engineering and as such can never be as good as the OSS Radeon drivers no matter how many dev hours they throw at it.

    Leave a comment:

Working...
X