Mod note: closing and unstickying this old topic.
]]>On kernels 4.19+ theres massive screen artifacting:
https://bugs.freedesktop.org/show_bug.cgi?id=108671
On mesa 18.3+ Battlefield 4 consistently crashes before entering a game:
https://bugs.freedesktop.org/show_bug.cgi?id=108742
please post lspci-knn to verify which chipset your apu uses.
]]>% sensors
amdgpu-pci-0100
Adapter: PCI adapter
vddgfx: +1.00 V
fan1: N/A
temp1: +42.0°C (crit = +97.0°C, hyst = -273.1°C)
power1: 12.00 W (cap = 35.00 W)
and radeon-profile-git agrees, shows 0% and 0rpm even though fan is running.
When amdgpu module is loaded, does it utilize all of these? = YES
amdgpu/polaris12_ce.bin polaris12_mc.bin polaris12_me.bin polaris12_mec.bin polaris12_mec2.bin polaris12_pfp.bin polaris12_rlc.bin polaris12_sdma.bin polaris12_sdma1.bin polaris12_smc.bin polaris12_uvd.bin polaris12_vce.bin
Maybe someone can help point me in the right direction? Thanks
EDIT: this comment #7 looks like answer = no fan rpm's from RX550.
mirh wrote:EDIT: also, while I am here.. Is it even normal manjaro on 4.7 works with catalyst (15.9 though) even without no specific patch?
Must be some kind of black magic . Can see that 4.6 support is covered by a sed's cut, but nothing for 4.7.
cpu_has_pge used by fglrx was removed from 4.7, and it has to be covered in some way otherwise build will fail, maybe manjaro did it in other way (?).
Ok, 2 years later I have the educated guess that maybe this weirdness might have had something to do with them still using gcc 4.9 to compile (it at least explained a lot of other differences in patching - now that they "upgraded" it, they are quite more akin)
Said this, I wanted to point out that similarly to windows there are lots of not-so-official driver branches. Sometimes more updated.
In particular after not even too much digging, I found out FirePro 15.302.2301 providing newer components all around, and Embedded 15.201 (they dropped the patch version, but judging by some libraries it must be >2401) bringing the latest [Terascale-supporting] OpenCL 1800.12
Now, it probably would make sense for one of your packages to just straightforwardly ship the newest of them and call it a day, for GCN hardware...
But for the reminder, I'm very skeptical about the value of still keeping 15.9 around.
It's really lame, both for choppy 2D acceleration and buggy ≤15.2xx opengl (pcsx2 results in a white screen, for example, without a specific patch).
A zombie amalgam of the best releases (ie 15.9 control, ^15.201 OpenCL, and ^15.302 for everything else) really seems the fine point.
p.s. also, you should have a line for the removal of /etc/ati/amdpcsdb at every uninstallation and installation. I spent an hour trying to track wtf userspace was getting reported the old drivers information
Only to realize of that thing constantly refreshing and restoring itself, reading the default *right* values only if missing on system boot (bonus for the other half hour wasted to discover of aticonfig.. but this is another story)
p.p.s. and yes, I tested all of this on my E-350/HD6310 and I couldn't find any particular issue
]]>Not sure if it was the update to wine 3.6 or mesa 18.0.0-4 or if my graphics card is just starting to show its age but I'll just hope the problem won't come back.
Anyway, thanks for your input, guys.
]]>Tim
]]>Do you have problems with native applications also ?
Haven't yet ran into any lockups with native apps, but I mainly only play TF2 which isn't using any fancy graphical effects.
What does Killing Floor 2 use : directx 9, directx 11 , directx12 , vulkan, opengl ?
directx 11, but I'm running it with the -DX10 launch option, which I think makes the game create a directx 11 context limited to directx 10 feature set.
Is this a 32-bit or 64-bit windows application and what wine prefix type are you using
64-bit executable, fresh 64-bit prefix with no overrides and nothing installed in it. (Keeping the Steam install outside of the prefix so I can easily wipe it and renamed the _CommonRedist folder to prevent Steam from junking up the prefix with useless runtimes)
Which wine are you using : stock, staging , staging-nine ?
I tested it with wine-staging-nine 3.5 and 3.4. Both work fine with mesa 17 and lock up the system with mesa 18. I think I'm going to test it with stock 3.5 later.
Have you checked killing floor 2 page in winehq app database ?
Yes, the game has a few graphical issues in dx11 mode, which is why I'm running it with -DX10. If it wasn't for that, it could be rated platinum, as everything works and it hasn't crashed or frozen once with mesa 17 or nvidia proprietary on a friend's machine.
What is your WM/DE, does using something else make a difference ?
Plasma 5 with kwin_x11 (compositing disabled). I could test it with openbox but I kinda doubt it'll make a difference.
---
@Jannis, you would file the bug at https://bugs.freedesktop.org/ with Product DRI and Component DRM/AMDgpu
I have a similar problem on another OS (I'm not asking for help, here, I'm just trying to help Jannis). I believe a kernel patch from AMD is in the works, but I've been waiting a couple of weeks and it hasn't shown up, yet.
I can work around my problem with kernel parameter amdgpu.dpm=0, so you might try that.
Thanks, that seems like the most appropriate place to report it. Out of curiosity, do you also have a GCN 1.0 card and is your problem specific to mesa 18 as well? And if I disable power management, won't the GPU always run at the lowest speed? In that case I probably prefer to hold onto mesa 17.3.7 for now instead as that seems to be less harmful to performance.
]]>I have a similar problem on another OS (I'm not asking for help, here, I'm just trying to help Jannis). I believe a kernel patch from AMD is in the works, but I've been waiting a couple of weeks and it hasn't shown up, yet.
I can work around my problem with kernel parameter amdgpu.dpm=0, so you might try that.
Tim
]]>Do you have problems with native applications also ?
What does Killing Floor 2 use : directx 9, directx 11 , directx12 , vulkan, opengl ?
Is this a 32-bit or 64-bit windows application and what wine prefix type are you using (32-bit apps can be used in 64-bit prefix)
Which wine are you using : stock, staging , staging-nine ?
Have you checked killing floor 2 page in winehq app database ?
What is your WM/DE, does using something else make a difference ?
]]>I noticed I can't play Killing Floor 2 in wine anymore as the game will crash on startup about 2/3 of the time and when it doesn't, it fully freezes the system when in main menu or trying to start a match. No response to SSH either.
I downgraded back to mesa 17.3.7-1 and the game runs fine every time, no crashes or freezes.
This is on a Radeon HD7870, GCN 1.0, with amdgpu (both linux-ck and arch kernel are affected). I also tried mesa-git but get the full freeze as well.
I'll probably file a bug report if nobody has done so yet but first I got to figure out how to get some more information.
Edit: Also not sure where to file the bug; I assume it's in amdgpu as it locks up the entire machine but it's only exposed with new mesa.
]]>[ 66.598] (==) Using config file: "/etc/X11/xorg.conf"
You did notice the note in the wiki that archlinux rarely requires extra configuration ?
Please post the content of that file.