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

Thread: Xserver 1.14 support will arrive with Catalyst 13.6

  1. #1
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    906

    Default Xserver 1.14 support will arrive with Catalyst 13.6

    Since "some" are waiting for this to come, there is a statement
    of an AMD engineer on the semi-official bug tracker:

    http://ati.cchtml.com/show_bug.cgi?id=807#c1

  2. #2
    Join Date
    Jan 2013
    Posts
    1,116

    Default

    Nice. Now it would be good if we can get Xserver 1.13 support and support for kernels >3.4 in the Legacy driver.

  3. #3
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    906

    Default

    Quote Originally Posted by Vim_User View Post
    Now it would be good if we can get Xserver 1.13 support and support for kernels >3.4 in the Legacy driver.
    Don't hold your breath for new Xserver support in the legacy driver.
    I'd be very surprised if it sees any (minor) update at all.

    The message by AMD has been clear (more or less):
    If you're using a HD 4K and below, go use the FOSS driver instead.

  4. #4
    Join Date
    Jan 2013
    Posts
    1,116

    Default

    Quote Originally Posted by entropy View Post
    Don't hold your breath for new Xserver support in the legacy driver.
    I'd be very surprised if it sees any (minor) update at all.

    The message by AMD has been clear (more or less):
    If you're using a HD 4K and below, go use the FOSS driver instead.
    I would be happy if I could do that, I don't play games on that hardware anyways, but my laptop is unusable with the FOSS driver (overheating, no UVD support) and many people have the same problem. So that is not an option at all and AMD should know this, there are bug reports and at least bridgman was made aware of the issue. If that is really the kind of support AMD believes their customers deserve than it is no wonder that they have financial problems, why should we buy their hardware again?

  5. #5
    Join Date
    Nov 2007
    Posts
    1,353

    Default

    I can understand your frustration. In fact we are still waiting for proper power management. You'd think that would have been a higher priority than the last major feature especially since the lack thereof makes a lot of systems unusable. If if the hardware does work, in the end it doesnt matter if it burns up your lap. I'da thought that is common sense. So in that regard I certainly agree with you.

    However AMD making the OSS driver their official supported driver is not a bad thing. In fact it is a very good thing, and the driver simply would not have come even this far if they hadnt done that. I personally would -LOVE- to see catalyst dropped from Linux altogether. At least the OSS driver works. Thats more than catalyst can do in most setups.

  6. #6
    Join Date
    Jan 2013
    Posts
    1,116

    Default

    Quote Originally Posted by duby229 View Post
    However AMD making the OSS driver their official supported driver is not a bad thing.
    Of course not, but they have made it at a time where the OSS driver was (and still is) not in the state to replace the non-free driver for many of their customers and simply left them alone with their problems: "You have a HD2/3/4000? Sorry, but this three years old hardware (also, remember that the HD4000 series is still the top of the line integrated product for the FX series CPUs and still sold) is so obsolete we will support it only with a legacy driver that maybe or maybe not will be updated once in a while. If this is not what you want then use the free driver. Oh, the free driver overheats your hardware and lowers its lifetime with that? Well, we don't care!" That is how it sounds to me.

    I personally would -LOVE- to see catalyst dropped from Linux altogether. At least the OSS driver works. Thats more than catalyst can do in most setups.
    The Catalyst driver works for me, as long as I am able to install it. I could do that recently again on my main machine, but only because the Slackware team decided to move back to Xserver 1.13 (from 1.14), just because the lack of support for that from AMD. Now we expect that Slackware 14.1 is coming soon and I can't use it on my laptop because AMD thinks that Xserver 1.13 and kernel 3.8 are to new for me.

    For me AMD's driver policy comes down to: "Eat shit or buy new hardware! Oh, you have already bought new hardware, well, then you can wait until we are in the mood to support somewhat newer software, but only if we want to or maybe if it is released on Ubuntu."
    They can bet that if I buy new hardware it will not be from AMD anymore.

  7. #7
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,995

    Default

    Just pointing out that if the only 4k hw still actively sold are the chipset integrated ones, overheating is no problem: the TDP of those is <5W, the heatsinks + fans can handle that at full load.

  8. #8
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,995

    Default

    Should clarify: 5w number pulled from quick googling, may be higher in the most powerful chipsets. Still, well below the mobos cooling ability.

  9. #9
    Join Date
    Jan 2013
    Posts
    1,116

    Default

    Quote Originally Posted by curaga View Post
    Just pointing out that if the only 4k hw still actively sold are the chipset integrated ones, overheating is no problem: the TDP of those is <5W, the heatsinks + fans can handle that at full load.
    But missing UVD support for these may be an issue.

  10. #10
    Join Date
    Jul 2010
    Posts
    449

    Default

    Quote Originally Posted by Vim_User View Post
    But missing UVD support for these may be an issue.
    UVD support will be in available out of the box in the next few months, it needs kernel 3.10 and Mesa 9.2. We don't have it now, but it's not far off.

    Power management is certainly lacking, which certainly is annoying, but the open source team are doing what they can: the code is still undergoing the technical review.

Posting Permissions

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