Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
AMD Graphics Open Source Hardware Linux

AMD's R9 Fury On Open-Source: Prepare for Disappointment, For Now 43

An anonymous reader writes: With Linux 4.3 AMD is adding the initial open-source driver for the R9 Fury graphics cards. Unfortunate for Linux gamers, the R9 Fury isn't yet in good shape on the open-source driver and it's not good with the Catalyst Linux driver either as previously discussed. With the initial code going into Linux 4.3, the $550 R9 Fury runs slower than graphics cards like the lower-cost and older R7 370 and HD 7950 GPUs, since AMD's open-source developers haven't yet found the time to implement power management / re-clocking support. The R9 Fury also only advertises OpenGL 3.0 support while the hardware is GL4.5-capable and the other open-source AMD GCN driver ships OpenGL 4.1. It doesn't look like AMD has any near-term R9 Fury Linux fix for either driver, but at least their older hardware is performing well with the open-source code.
This discussion has been archived. No new comments can be posted.

AMD's R9 Fury On Open-Source: Prepare for Disappointment, For Now

Comments Filter:
  • by Anonymous Coward

    that should be the new corporate slogan...

  • by Ecuador ( 740021 ) on Sunday August 30, 2015 @01:26PM (#50421599) Homepage

    As far as I can understand, AMD has released the specs for the new GPUs, which is what many Linux / Open Source advocates care about, right? Sure they haven't yet added the support for the new cards on their own, but other people could do it if they are in a hurry, right? Then you have Nvidia not releasing any specs for open drivers, but adding support (more quickly perhaps?) on their proprietary binary drivers. This upsets (hopefully a different set of) Linux users.
    And in the end, this is just about games (because I never had a problem with the Linux desktop in general, even over multiple displays with mostly AMD cards), right? Well, guess what, Linux is not a good gaming platform. It is great in many things, why should it also be good for games? Why would Nvidia and AMD spend significant resources so that very few people (compared to the total market) can play games in a specific platform that, let's face it, is not gamer-oriented? Well, they don't, so don't complain. Sorry for the rant-ish post, perhaps I would post different 15 years ago when I was still into computer games ;)

    • by janoc ( 699997 )

      I suggest that you broaden your horizon before you go ranting. You wouldn't make a fool of yourself.

      First, that card doesn't work well with *any* Linux drivers, open source or not. Even their Catalyst driver is horrible in Linux.

      Second, OpenGL in Linux is much more important for the professionals than gamers - large portion of virtual reality image generators (machines that render the landscapes, vehicles etc. depending on the instructions from the simulation system) used by all sorts of simulators (militar

    • by Kjella ( 173770 )

      As far as I can understand, AMD has released the specs for the new GPUs, which is what many Linux / Open Source advocates care about, right? Sure they haven't yet added the support for the new cards on their own, but other people could do it if they are in a hurry, right?

      Not for Fury, not yet. The shader instruction set architecture (ISA) is up to date, since the shaders are still GCN 1.2 (also known as 3rd gen GCN, IPv8) so you can write shader code for it. But the code to initialize and manage the card changes from generation to generation, if I recall correctly at launch it didn't work at all. Those parts are typically written by AMD, with the code typically preceding and more or less being the initial documentation. From what I've understood it's because AMD's legal dep

  • by tlambert ( 566799 ) on Sunday August 30, 2015 @01:45PM (#50421693)

    The whole posting is disengenuous.

    "the R9 Fury isn't yet in good shape on the open-source driver"

    The card won't be changing to fix this; the driver will have to change to accommodate the card; therefore it is more correct to say "The Open Source driver is not yet in good shape on the R9 Fury". In other words, it's not the hardware's fault that the driver doesn't support it yet.

    "AMD's open-source developers haven't yet found the time to implement power management / re-clocking support"

    The power management model in Linux is Linux's responsibility, not AMD's. The authors of the Open Source driver are accountable *only* for writing callbacks for the device power management component, and populating the structure. It's my understanding that Linux lacks a uniform model for use by all graphics drivers, in this regard. his is a Linux issue, not an AMD issue.

    Also:

    In general, in a hardware world, you either NDA people, or the Open Source is going to lag the closed source, period. This is because openly manipulating code related to an unreleased hardware product in a publicly accessible source repository, instead of a privately held repository, is tantamount to preannouncing your hardware to competitors. You might as well have the CEO call a press conference, and then shoot themselves in the head in public.

    Open Source projects have a secondary problem in that, even if the driver source was developed entirely by engineers within AMD, and released the same day as the hardware was made available, the Open Source projects aren't going to be happy just integrating the code as is. They will insist on peeing on it to make it smell like themselves, just as cats do with new furniture, and this will take time. You can either have closed source, or you can have it integrated later than the release date, but you can not have both.

  • so? (Score:4, Funny)

    by electrosoccertux ( 874415 ) on Sunday August 30, 2015 @05:07PM (#50422607)

    I just use glxgears to benchmark. glxgears is a great benchmark. I recommend glxgears if you want to benchmark your liinicks. thanks.

"What man has done, man can aspire to do." -- Jerry Pournelle, about space flight

Working...