Hi, I've been trying to get into Linux for a while now, around 2-3 years, and I love it, it's by far a more superior operating system/kernel.
Every time I install an OS, I get huge graphical lag, window drag lag, stuttering, glitches and crashes. I thought that this may have been a GPU issue, because my graphics card at the time was a GTX 660 (NON TI). Recently I've upgraded to an MSI AMD 380 GPU, and the first thing I did was try out if Linux would finally work, but sadly it still has the same graphical errors and glitches as before.
I'm not running a low end PC, my specs are: GPU: AMD 380 CPU: Intel i7 4930K Motherboard: ASRock X79 Extreme 11 3 SSD's (RAID 0)
Pictures below are some graphical errors I've been able to get.
1: I've used every driver under the sun, open source drivers and AMD's drivers. 2: I have 3 monitors, and I can assure you it's not a monitor problem. 3: Yeah, the live ISO's work, but same graphical errors occur. 4: I've tried: OpenSUSE Arch linux Antergos (Arch) Debian Fedora and a couple other ones, the most annoying thing that happens when using ANY distro is the window lag when moving them around, the mouse will be ahead of the window.
@anon37371794 Windows works like a charm, Never had a BSOD, drivers work fine etc...
Did you do performance tuning using Windows software? Like especially CPU/bus overclocking and memory timing analysis? These settings might be screwed in the UEFI, and when you start Windows, it's corrected to something that works because of the software, but linux doesn't use such software, but depends on the UEFI settings.
Maybe do a memory check. Another difference between linux and Windows is that linux basically reserves and/or allocates almost all system memory at boot, so that it can use it more efficiently for a number of things. Windows doesn't do that, instead it kind of fills-up-as-it-goes. If there is a problem with the memory, it could cause the symptoms that you've been seeing, and it could theoretically not lead to similar symptoms in Windows, but probably rather a BSOD or lock-out in the event the faulty memory would be used.
Diagnose, look at the dmesg output, see what's going wrong. It might be a funky multiplex chip on your PCIe-bus, it might be a device decriptor that doesn't parse because it's not standard compliant, etc etc ect, but it has to be something with the hardware.
which version of Mint/ubuntu are you using. this does look like a weird hardware glitch. Maybe with the motherbeard? It could be fixed if you use a newer kernel. If you are using the LTS of Mint/Ubuntu the kernel is relatively old. If you are in Mint try installing the latest available from the update manager and see what happens.
You could try this in your kernel line on boot up (e for edit on grub)
radeon.dpm=0
There has been times when I had to use that to resolve display issues, because AMD/NVIDIA power management support under Linux is dodgy atm (until new kernels are ready). With your AMD 380 you can run the new kernels with AMDGPU OSS driver, however I don't know the exact steps to achieving this.
Also give Ubuntu 15.04 MATE a shot, and keep clear of Kernel 4.2+ updates for the time being, infact try to stay around 3.19 kernel which is the most stable and will work with drivers available without compile patches/tweaks.
I'm in windows now so can't provide you with the PPA launchpad for the drivers I used atm.
I'm not sure, I'm using Ubuntu now, I used the built in driver manager. Since then I've tried installing the AMD driver from their website, but no luck...
I'm on Ubuntu 15.04 now on AMD GPU system, I installed the AMD fglrx driver with jockey, and it just worked, I just tried to switch to the beta, it also just worked. There must be something in your system that makes the reporting wrong. Have you seen anything strange from the output of glxinfo?
FGLRX detects the 300 series as 200, nothing wrong going on there. Don't panic. The issue I see is the core clock at 33mhz which is going to kill performance, this is DPM related.
The fatal mistake, you need to use the correct PPA, again not in Linux atm. I will reboot and get you the PPA I used.
EDIT: Actually what I did was use the AMD website drivers and ran the run script using a guide for installing them on Vivid. Will attempt to fine guide. Sorry. It seems I forget allot about my Linux and how I did things when I'm using Windows.
Honestly I have had your problems before myself with different distros, but since I moved to Ubuntu MATE 15.04 and Kernel 3.19, no problems persisted. Wish I could remember what guide I used or how exactly I installed the FGLRX drivers, all I know is I didn't use the default device manager method!
Here we go, I think I followed this guide. However, obviously because I use VIVID I replaced the word trusty with vivid. Find out what distro your using before doing anything so you don't make a mistake (probably won't matter so much).
