Arch Linux

madbver

Member

Registered: 2018-04-23

Posts: 4

[SOLVED] R9 390X Artifacting

Hi, I'm relatively new to arch and I've pretty much work out all my issues except the screen artifacting i'm experiencing.

I never experience the issue when using the computer or gaining for example. The issue presents itself after I have left the computer and the screen blanks.
When I come back most times (not always) one of my monitors has tons of artifacts on it. When i log back into the desktop the problem goes away.
Today I found my computer with artifacts on both monitors and the system was completely locked up. Both screens normally dont artifact but i think it was because i was playing a steam game yesterday (one more dungeon) and left it running. We had guests come over and I forgot to shut it down.

I followed the wiki and blacklisted the radeon driver, and enabled cik support for amdgpu.

lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] (rev 80)

lsmod | grep -e amdgpu -e radeon
amdgpu               3129344  33
chash                  16384  1 amdgpu
gpu_sched              28672  1 amdgpu
i2c_algo_bit           16384  1 amdgpu
ttm                   122880  1 amdgpu
drm_kms_helper        200704  1 amdgpu
drm                   466944  10 amdgpu,gpu_sched,ttm,drm_kms_helper

dmesg | grep -e amdgpu -e radeon
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=d53b6574-7515-486c-9a3f-64cd6ff3b761 rw quiet resume=UUID=b89beb18-d2ed-47b0-92bf-82ace7fec62c amdgpu.cik_support=1 radeon.cik_support=0
[    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=d53b6574-7515-486c-9a3f-64cd6ff3b761 rw quiet resume=UUID=b89beb18-d2ed-47b0-92bf-82ace7fec62c amdgpu.cik_support=1 radeon.cik_support=0
[    2.697262] [drm] amdgpu kernel modesetting enabled.
[    2.707526] fb: switching to amdgpudrmfb from EFI VGA
[    2.707876] amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
[    2.709523] amdgpu 0000:01:00.0: VRAM: 8192M 0x000000F400000000 - 0x000000F5FFFFFFFF (8192M used)
[    2.709525] amdgpu 0000:01:00.0: GTT: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
[    2.709590] [drm] amdgpu: 8192M of VRAM memory ready
[    2.709590] [drm] amdgpu: 8192M of GTT memory ready.
[    2.722916] [drm] amdgpu: dpm initialized
[    3.007717] fbcon: amdgpudrmfb (fb0) is primary device
[    3.070062] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device
[    3.094448] [drm] Initialized amdgpu 3.23.0 20150101 for 0000:01:00.0 on minor 0

Anyhow i'm not really sure what could be causing the issue. Any help is greatly appreciated.

Last edited by madbver (2018-04-29 15:51:12)

Radioactiveman

Member

From: Germany

Registered: 2010-05-13

Posts: 388

Re: [SOLVED] R9 390X Artifacting

What kernel version are you using? And have you tried enabling AMD DC (with the kernel parameter amdgpu.dc=1)?

madbver

Member

Registered: 2018-04-23

Posts: 4

Re: [SOLVED] R9 390X Artifacting

What kernel version are you using?

4.16.4-1-ARCH

I thought support of the AMD DC is not supported on GCN2/CIK cards?

https://wiki.archlinux.org/index.php/AM … Vega_cards

Its still artifacting quite a bit. Its happened several times today already. It always happens when I have been away from the computer for a period of time. =[
I usually cant even log back in and it require a reboot.

madbver

Member

Registered: 2018-04-23

Posts: 4

Re: [SOLVED] R9 390X Artifacting

I think i have fixed the problems i was having before.

I checked dmesg again and I was seeing warning messages about the display code.

https://pastebin.com/jXSp0KUw

I added amdgpu.dc=0 to my kernel arguments and so far I have not had any of the problems i described earlier.

madbver

Member

Registered: 2018-04-23

Posts: 4

Re: [SOLVED] R9 390X Artifacting

I think i have fixed the problems i was having before.

I checked dmesg again and I was seeing warning messages about the display code.

https://pastebin.com/jXSp0KUw

I added amdgpu.dc=0 to my kernel arguments and so far I have not had any of the problems i described earlier.

I have had zero problems since adding this kernel parameter.