Announcement

Collapse
No announcement yet.

AMD Wants To Know What's Wrong With Catalyst

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

  • Espionage724
    replied
    Originally posted by soulsource View Post
    In my opinion, they could simply drop fglrx and focus on the open source drivers. Those might atm have inferior performance and OpenCL is still work in progress, yet they are quite a bit more stable
    I've had little stability issues with fglrx on my 7850. Desktop usage, video playback, and most games were fine. Only exception were some games I ran through Wine which acted a bit strangely with crashes.

    Was a time recently on the open-source drivers where anything using VDPAU would just hard-lock the system. This was around the same time I felt like messing with my media collection too. Would be quite a drag double-clicking some video expecting it to work, then realizing my error when it's too late. This was fixed at some point a few days later, but back when I still had my 7850, it was still quite unstable. I'm talking GPU restarts and eventually hard-locks from doing simple tasks like web browsing and viewing pictures. fglrx as far as I'm concerned is more stable.

    From my general understanding though, older kernels (3.14 specifically) was more stable than later kernels. No idea if this is the case still (last kernel I tried was 3.17rc1 which still had the unstable graphics).

    Even on my 7660G + 7670M laptop fglrx wasn't too bad; only issues were with Chrome wanting to not maximize properly, and Dota 2 having some unstable FPS (going from around 50-60 down to 15 repeatedly). Open-source drivers weren't bad at all on it either though (Dota 2 instead of having unstable FPS just has low FPS), so I can actually use either driver.

    Leave a comment:


  • boffo
    replied
    Originally posted by asdfblah View Post
    As someone said, AMD could be taking advantage of Linux, but instead, they have been leaving it aside.



    APU owner, right?
    https://bugs.freedesktop.org/show_bug.cgi?id=42960#c15
    it should be fixed in the next release of kernel 3.15+
    there is a new, apparently unrelated bug, though... you have to turn the display off and on with something like
    Code:
    xrandr --output LVDS --off && xrandr --output LVDS --auto
    after resuming from suspend.

    This is why I prefer open source, at least you know (kind of) what's going on/how to fix or work around bugs. Their "unofficial" bug tracker ( http://ati.cchtml.com/ ) is a mess, devs rarely reply and things rarely get fixed... meanwhile, OSS devs are always happy to help you.
    Yes I own an Apu A8. I tried
    Code:
    xrandr --output LVDS --off && xrandr --output LVDS --auto
    the quirks and the other solutions in
    https://bugs.freedesktop.org/show_bug.cgi?id=42960#c15
    but it didn't work.
    Also I have found another problem (I forgot about it), sometimes the external vga monitor doesn't get the signal, even if I don't suspend/resume. In that case i need to turn off and on the secondary monitor with xrandr or with kscreen. It might be a synchronization problem (?), because it's random, sometimes it just works sometimes it doesn't.

    Leave a comment:


  • flim
    replied
    Originally posted by soulsource View Post
    In my opinion, they could simply drop fglrx and focus on the open source drivers. Those might atm have inferior performance and OpenCL is still work in progress, yet they are quite a bit more stable, integrate with the rest of the linux desktop and (what's really important for me) give superior font rendering (although I have no clue why...).
    Fglrx on the other hand might run faster and run more (but also by far not all) OpenCL kernels, but it crashes regularly, it requires X11 restarts for the most stupid things like switching off the secondary screen, it requires the use of either Cataclyst Control Center of atisetup to enable/disable monitors,... In short, it's pretty useless unless the only thing you are doing with your computer is playing games or cryptocurrency mining...
    Code:
    $ xrandr --output MONITOR --off
    No restart or Catalyst Control Center required.
    Last edited by flim; 28 September 2014, 12:12 PM.

    Leave a comment:


  • soulsource
    replied
    In my opinion, they could simply drop fglrx and focus on the open source drivers. Those might atm have inferior performance and OpenCL is still work in progress, yet they are quite a bit more stable, integrate with the rest of the linux desktop and (what's really important for me) give superior font rendering (although I have no clue why...).
    Fglrx on the other hand might run faster and run more (but also by far not all) OpenCL kernels, but it crashes regularly, it requires X11 restarts for the most stupid things like switching off the secondary screen, it requires the use of either Cataclyst Control Center of atisetup to enable/disable monitors,... In short, it's pretty useless unless the only thing you are doing with your computer is playing games or cryptocurrency mining...

    Leave a comment:


  • chrisr
    replied
    *** NOW *** AMD wants to know what's wrong with Catalyst!?!

    I should point out that I haven't used Catalyst for years, even before it suddenly dropped all support for every single AMD graphics card that I own, but from memory, the things that most compelled me to call for demonic forces to smite the Catalyst driver and everyone who professed to code for it were:

    - Support for newer kernels and X servers was always slow in coming, which made it a PITA for anyone who used a distribution like Fedora.
    - I never knew, month to month, whether each new release would even work! ("Work" being defined as "Play WoW without crashing or freezing"). Some months it did, other months it didn't.
    - 2D performance was eye-gougingly awful. I could actually watch the WoW launcher program being drawn on the screen, one line of pixels at a time with my M66GL GPU.
    - The RPM spec file that the fglrx driver shipped with was incorrect and unmaintained. I had to modify / update it every month before I could build my RPM.
    - The bug reporting web site that AMD ran was a complete and utter waste of time. Everything I ever reported there was either ignored or "answered" with "You need to talk to your laptop's manufacturer."

    The bottom line seemed to be that Catalyst was aimed at the Workstation market only. The corollary being that mere Fedora users could go fsck themselves.

    Leave a comment:


  • jacob
    replied
    Originally posted by asdfblah View Post
    Well, I'm not sure about this specific card... but IIRC, some cards needed a newer kernel, so I would try installing 3.16 or 3.17-rc [could be dangerous] from http://kernel.ubuntu.com/~kernel-ppa/mainline/ to see if helps. If that works, you should keep using that until Ubuntu Utopic (14.10) gets released (in october), and then upgrade to utopic, or install linux-image-generic-lts-utopic in 14.04. If that still doesn't work, you should wait until a radeon dev replies, and/or ask in http://phoronix.com/forums/forumdisp...urce-AMD-Linux or the IRC channel: https://webchat.freenode.net/?channels=radeon.
    I'm already using 3.16, does not help. I guess my next attempt will be with the new xorg and mesa from 14.10 (I'm almost inclined to upgrade to the beta to give it a go...)

    But seriously: I know Metro LL is not a Valve product, but shouldn't they require software to be tested a little bit more throroughly before they accept to distribute it through steam?

    Leave a comment:


  • asdfblah
    replied
    Originally posted by jacob View Post
    HW: CPU AMD FX8320, GPU R7 260, RAM 8GB
    SW: Ubuntu 14.04 64bit, stock gfx stack (not xorg-edgers updates etc), tried with default "generic" kernel, "generic" from 14.10 and custom built 3.16.2



    direct rendering: Yes
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD BONAIRE
    OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.1.3
    OpenGL core profile shading language version string: 1.40
    OpenGL core profile context flags: (none)
    OpenGL core profile extensions:
    GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp,
    OpenGL version string: 3.0 Mesa 10.1.3
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)
    OpenGL extensions:
    GL_NV_blend_square, GL_NV_conditional_render, GL_NV_depth_clamp,



    It makes the steam client segfault.
    Well, I'm not sure about this specific card... but IIRC, some cards needed a newer kernel, so I would try installing 3.16 or 3.17-rc [could be dangerous] from http://kernel.ubuntu.com/~kernel-ppa/mainline/ to see if helps. If that works, you should keep using that until Ubuntu Utopic (14.10) gets released (in october), and then upgrade to utopic, or install linux-image-generic-lts-utopic in 14.04. If that still doesn't work, you should wait until a radeon dev replies, and/or ask in http://phoronix.com/forums/forumdisp...urce-AMD-Linux or the IRC channel: https://webchat.freenode.net/?channels=radeon.

    Leave a comment:


  • jacob
    replied
    Originally posted by asdfblah View Post
    Give us more info: What distro?
    HW: CPU AMD FX8320, GPU R7 260, RAM 8GB
    SW: Ubuntu 14.04 64bit, stock gfx stack (not xorg-edgers updates etc), tried with default "generic" kernel, "generic" from 14.10 and custom built 3.16.2

    Originally posted by asdfblah View Post
    What does
    Code:
    $ glxinfo | egrep 'render|OpenGL'
    show?
    direct rendering: Yes
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD BONAIRE
    OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.1.3
    OpenGL core profile shading language version string: 1.40
    OpenGL core profile context flags: (none)
    OpenGL core profile extensions:
    GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp,
    OpenGL version string: 3.0 Mesa 10.1.3
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)
    OpenGL extensions:
    GL_NV_blend_square, GL_NV_conditional_render, GL_NV_depth_clamp,

    Originally posted by asdfblah View Post
    Did you try this? https://bugs.freedesktop.org/show_bug.cgi?id=71239#c5 (replace 3.2 with 3.3)
    It makes the steam client segfault.

    Leave a comment:


  • vein
    replied
    Honestly, Nothing is wrong for me. Everything is working fine. Keep up the good work! Or maybe you could release stable drivers more often

    And honestly, everybody talk about how fast the development for the open source driver is going... well, take a look at where fglrx was a few years ago. Think it has improved remarkably too. Good work AMD.

    Leave a comment:


  • asdfblah
    replied
    As someone said, AMD could be taking advantage of Linux, but instead, they have been leaving it aside.


    Originally posted by boffo View Post
    On windows I can't update windows 8.1 without uninstalling catalyst. I don't know if it is a windows or a catalyst problem, but if I don't uninstall the driver the update will fail, and the pc will need 30 minutes to return to the last working configuration.
    On linux I've never used catalyst, because I like to have a out of the box experiece. But with the open driver I can't suspend/resume. To be clear the suspend/resume works. But the integrated laptop's lvds monitor remains black, while the external vga/hdmi monitor resumes just fine.
    APU owner, right?
    https://bugs.freedesktop.org/show_bug.cgi?id=42960#c15
    it should be fixed in the next release of kernel 3.15+
    there is a new, apparently unrelated bug, though... you have to turn the display off and on with something like
    Code:
    xrandr --output LVDS --off && xrandr --output LVDS --auto
    after resuming from suspend.

    This is why I prefer open source, at least you know (kind of) what's going on/how to fix or work around bugs. Their "unofficial" bug tracker ( http://ati.cchtml.com/ ) is a mess, devs rarely reply and things rarely get fixed... meanwhile, OSS devs are always happy to help you.
    Last edited by asdfblah; 27 September 2014, 03:16 PM.

    Leave a comment:

Working...
X