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

Thread: AMD Puts Catalyst 13.10 GPU Driver Into Beta State

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,387

    Default AMD Puts Catalyst 13.10 GPU Driver Into Beta State

    Phoronix: AMD Puts Catalyst 13.10 GPU Driver Into Beta State

    Just before the end of the month, AMD released the Catalyst 13.10 Beta Linux graphics driver...

    http://www.phoronix.com/vr.php?view=MTQ3MzY

  2. #2
    Join Date
    Jun 2013
    Posts
    226

    Default

    AMD closed drivers SUCK!

  3. #3
    Join Date
    Aug 2012
    Posts
    434

    Default

    Quote Originally Posted by verde View Post
    AMD closed drivers SUCK!
    Then why are they 20x faster than the open source drivers? I don't have any outstanding problems with them with my 7950 other than performance in games. I mean, at least my games are playable unlike the open source drivers lacking critical functionality.

  4. #4
    Join Date
    Feb 2012
    Posts
    52

    Question

    Quote Originally Posted by mmstick View Post
    Then why are they 20x faster than the open source drivers?
    You got a source on that claim, broski?

  5. #5
    Join Date
    Jun 2013
    Posts
    226

    Default

    Quote Originally Posted by mmstick View Post
    Then why are they 20x faster than the open source drivers? I don't have any outstanding problems with them with my 7950 other than performance in games. I mean, at least my games are playable unlike the open source drivers lacking critical functionality.
    Who talked about Open drivers? AMD Opensource drivers are 10 years behing closed (on features and performance). I can't even imagine someone with a beast like 6970 or 7970 using open drivers. Even with DPM.

    Still AMD closed drivers are pathetic in comparison to Nvidia. And opensource drivers at least they dont have not even 5% of the Catalyst bugs. That makes them better choice if you are NOT a gamer and you CAN (your kernel is at least 3.11) enable DPM.

    I think AMD should drop support of Catalyst and follow "the Intel way" with real/strong support of opensource drivers...
    Last edited by verde; 09-30-2013 at 08:13 PM.

  6. #6
    Join Date
    Nov 2008
    Location
    UK
    Posts
    64

    Default

    May seem a daft Q, but does the linux driver support there new Rx cards ?

    My 5870 is starting to feel its age! Having said that, Its been no problem and runs all the steam games for me in *nix. LGP's port of X3:r been the only hiccup its had.


    Pete.

    Edit :

    Never mind, I guess not going on the release notes.
    Last edited by pete910; 09-30-2013 at 08:43 PM.

  7. #7
    Join Date
    Jan 2007
    Location
    Germany
    Posts
    2,162

    Default

    It doesn't have new features because it's still the same release stream since Catalyst 13.8 Beta 1 from few months ago.

    But it's still a good driver. Permission issue for Linux 3.10/3.11 fixed, Laptop display brightness finally works again and Unigine crash also fixed. Also the OpenGL performance regression of Catalyst 13.8 is fixed (input lag remains a problem).
    Last edited by d2kx; 09-30-2013 at 09:03 PM.

  8. #8
    Join Date
    Aug 2012
    Posts
    111

    Default

    Quote Originally Posted by mmstick View Post
    Then why are they 20x faster than the open source drivers? I don't have any outstanding problems with them with my 7950 other than performance in games. I mean, at least my games are playable unlike the open source drivers lacking critical functionality.
    Depends which chip. It's been shown pretty extensively that the 6000 series, on the open drivers, are about 80-90% as fast as the closed drivers.

    Radeonsi? Well, sure, that's another story.

  9. #9

    Default

    Quote Originally Posted by mmstick View Post
    Then why are they 20x faster than the open source drivers? I don't have any outstanding problems with them with my 7950 other than performance in games. I mean, at least my games are playable unlike the open source drivers lacking critical functionality.
    Im curious where you get that 20x from. Maybe radeonsi is slower.

    But on a 7560D IGP (A8-5500 APU) radeon drivers are better overall right now (im talking about the latest stuff from git, both kernel and mesa, xfce 4.10, no compositing).

    Games - Maybe there are some high resource eater games where fglrx is much faster, but for example Steam/Source games are faster with the oss radeon driver and they run smooth (fglrx has input lag and sometimes stutters). For these kinds of games the oss driver really works.
    The older radeon versions that came with kernels up to 3.10 were indeed slow, especially on APUs, but beginning with 3.11 and the dpm code, they are pretty much the same regarding temperatures (didnt measure power consumption) and pretty much the same speed in not that demanding games (Source/TF2 etc) than fglrx.

    Desktop - pretty much the same speed

    Video Playback - here the OSS driver wins hands down. Why?
    1. It has proper synced tear free video whereas fglrx tears everywhere, you have to force the "tear free" option to stop it (higher video memeory consumption+lower playback frame rate, sometimes choppiness, decreased opengl performance sometimes). The only video player that could deliver consistently tearfree movies was xbmc.
    2. hardware decoding (native implementation, not the libva plugin that just plain sucks):
    -fglrx has hardware decoding in the form of xvba. There is 2 issues with it: only 1 player (xbmc) supports it (works quite well), and only in a specific branch (fernetmenta's) + they plan on dropping support for it since the fglrx team doesnt really seem to care about their bug reports and it breaks frequenty after new drivers are released. They said they focus on the OSS implementation of hw decoding, there everything goes smooth in the development.
    Dont even mention the fglrx-libva mess (used by vlc for example), that uses only a fraction of its true power and its buggy as hell (both on fglrx and nvidia).
    -radeon OSS implemented recently the hw decoding via VDPAU (yes, that's exactly nvidia's open source solution) - meaning that players such as mplayer can use vdpau with it with no necessary modifications (and they indeed work). As Vlc implements VDPAU too beginning with 2.10, fglrx is left in the dust here.
    Even certain sites (youtube for example) can use the radeon VDPAU hw decoding (but other sites will crash if the option is set in mms.cfg, its a half assed implementation by Adobe).

    So, for casual gamers, people who watch movies the OSS driver is better (or it will be when all these goodies arrive in the stable packages).

  10. #10
    Join Date
    Feb 2012
    Location
    Barcelona, Spain
    Posts
    322

    Default

    Quote Originally Posted by gradinaruvasile View Post
    Im curious where you get that 20x from. Maybe radeonsi is slower.

    But on a 7560D IGP (A8-5500 APU) radeon drivers are better overall right now (im talking about the latest stuff from git, both kernel and mesa, xfce 4.10, no compositing).

    Games - Maybe there are some high resource eater games where fglrx is much faster, but for example Steam/Source games are faster with the oss radeon driver and they run smooth (fglrx has input lag and sometimes stutters). For these kinds of games the oss driver really works.
    The older radeon versions that came with kernels up to 3.10 were indeed slow, especially on APUs, but beginning with 3.11 and the dpm code, they are pretty much the same regarding temperatures (didnt measure power consumption) and pretty much the same speed in not that demanding games (Source/TF2 etc) than fglrx.

    Desktop - pretty much the same speed

    Video Playback - here the OSS driver wins hands down. Why?
    1. It has proper synced tear free video whereas fglrx tears everywhere, you have to force the "tear free" option to stop it (higher video memeory consumption+lower playback frame rate, sometimes choppiness, decreased opengl performance sometimes). The only video player that could deliver consistently tearfree movies was xbmc.
    2. hardware decoding (native implementation, not the libva plugin that just plain sucks):
    -fglrx has hardware decoding in the form of xvba. There is 2 issues with it: only 1 player (xbmc) supports it (works quite well), and only in a specific branch (fernetmenta's) + they plan on dropping support for it since the fglrx team doesnt really seem to care about their bug reports and it breaks frequenty after new drivers are released. They said they focus on the OSS implementation of hw decoding, there everything goes smooth in the development.
    Dont even mention the fglrx-libva mess (used by vlc for example), that uses only a fraction of its true power and its buggy as hell (both on fglrx and nvidia).
    -radeon OSS implemented recently the hw decoding via VDPAU (yes, that's exactly nvidia's open source solution) - meaning that players such as mplayer can use vdpau with it with no necessary modifications (and they indeed work). As Vlc implements VDPAU too beginning with 2.10, fglrx is left in the dust here.
    Even certain sites (youtube for example) can use the radeon VDPAU hw decoding (but other sites will crash if the option is set in mms.cfg, its a half assed implementation by Adobe).

    So, for casual gamers, people who watch movies the OSS driver is better (or it will be when all these goodies arrive in the stable packages).
    Same with a apu amd a8 5600k , fglrx simply is not 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
  •