I am very concerned for the support of ATI in fedora. Right now I am having serious issues with my video card since rpm-fusion orphaned kmod-catalyst. My fans always run at 100% Video is choppy and applications always crash, or excessively freeze for 5 to 6 seconds. Fedora has became completely unusable with out kmod-catalyst. I know fedora is not affiliated with rpm-fusion. However, I have heard that Kernel 3.13 will resolve many issues with video. I believe it should be pushed out ASAP. I do not want to leave fedora for another distribution; However, I barely can do anything without better driver support for my video card. 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750] AMD FX(tm)-6300 Six-Core Processor
The 3.13 kernel isn't released upstream yet. You can install the 3.13-rcX series from the Rawhide nodebug repo (or just use rawhide) if you wish until the stable releases are rebased.
The new Kernel did not help my card is still running loud, and there is no change on stability. Any suggestions?
Created attachment 849009 [details] journalctl output for one of these freeze periods
Created attachment 849010 [details] journalctl output for one of these freeze periods, ending up into a reboot
I have the same problems and concerns. 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400] CPU: AMD A6-5200 APU with Radeon(TM) HD Graphics I attach some findings inside journalctl, just in case it gives at least some leads. I also found some occurrences of: ''' ene 12 22:33:52 localhost.localdomain mcelog[626]: AMD Processor family 22: Please load edac_mce_amd module. : Success ene 12 22:33:52 localhost.localdomain mcelog.setup[619]: CPU is unsupported ''' Feel free to ask for more.
Created attachment 852050 [details] journal ctl
Sorry I forgot. Previous attachments were made for a 3.12.6 kernel.
Now I'm running on a 3.13.0rc8 kernel, and freezes seem to have stopped. There are still some things not working (entirely), and errors on journalctl look the same (all this 'CPU is unsupported' stuff). But I see improvements. One thing still not working is suspend. I'll attach journalctl output from a failed suspend.
Created attachment 852055 [details] journalctl output for suspend errors on kernel 3.13.0rc8
Add radeon.dpm=1 to your kernel boot option
No luck. I get the same errors, but I discovered something new. Is only from the session menu (pressing Alt) that it does not work. Is then when I get all those errors on logs, and GNOME session gets lost. When I suspend from the power (physical) button it all seems to work ok, though. That's before and after I tried radeon.dpm=1 option. So no difference there. I also found out that HDMI is working, but not well. Connecting a FullHD monitor results in a partially scrumbled screen. But hey, one bug at a time, right? Maybe they all get fixed at once. Thanks anyway. Keep waiting for kernel releases.
Just tried last kernel release 3.13.0. No changes. I discover that HDMI works perfect for some brand new screens, but not for the not-new (6-12 months old) I could test. Neither for a 1 year old FullHD TV. Will keep trying new kernel releases and reporting any change I see.
Just tried last kernel release 3.13.1. No changes.
Just tried 3.14.0rc1. No changes.
Now using Fedora Rawhide with kernel 3.14.0rc3 & mesa-libGL 10.1. Overall performance feels better now. But still the same problems with suspension and with HDMI out.
I can suspend now! Fedora Rawhide kernel 3.14.0rc7 mesa-libGL 10.1 Don't know what was wrong, but it's fixed now. Suspension works like a charm. Also slight improvement on rendering performance (smoother browser scroll, etc.). Still have to test for HDMI out, but right now I consider this fixed.
Sounds like Ruben got what he need...at the time. But, the situation has only gotten worse from where I sit. X wasn't usuable a few months ago because some menu actions and window manager actions caused 100% CPU load and X would hang entirely on logout. With recent kernels (3.10-ish -3.15), the system boots, but X isn't usable with open source drivers; I can't login. System only usable with proprietary drivers. My point is that OSS drivers are not even an option, anymore. It's not that 3D performance is poor, which is what I expect. It's not even operational. If possible, I'd like to take it back to Ruben's original question. Is there a systemic problem with OSS ati drivers in F20 or some of us just unlucky and maintainers need us to file more urgent bugs.
It has something to do with Fedora indeed. Recently I had the opportunity to try a Kubuntu distro on this very same machine, and worked flawlessly using a 3.11.x kernel.. On Fedora20 I need to upgrade to 3.15.x to get rid of all problems.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.