Arch Linux

vectro

Member

Registered: 2016-10-15

Posts: 14

[Solved] AMDGPU issues with FirePro W2100 and Kernel > 4.10

I'm getting checkered-box artifacts on my system when using kernels above 4.10. The artifacts occur on active animations (clicking the chromium 3-dot menu icon, google maps rendering, my entire SDDM qt5 greeter). HW accelerated video decoding is working fine mind you. Also I'm not using a compositor.  I was holding out for kernel 4.12 to see if the issue would be solved, but no luck. There seem to have been AMDGPU changes made to kernel 4.11 to improve power saving, but changing my card to high performance mode doesn't solve it.
Here's my system info, GLX info, xorg configs, lsmod, and mkinitcpio.conf:

 
vec@xeon-arch ~ $ screenfetch -n
 vec@xeon-arch
 OS: arch  
 Kernel: x86_64 Linux 4.12.4-1-ARCH
 Uptime: 1h 8m
 Packages: Unknown
 Shell: zsh 5.3.1
 Resolution: 3840x2160
 WM: i3
 GTK Theme: Arc-Darker [GTK2/3]
 Icon Theme: Arc
 Font: Ubuntu 13
 CPU: Intel Xeon E5-1620 v3 @ 8x 3.6GHz [50.0°C]
 GPU: Gallium 0.4 on AMD OLAND (DRM 3.15.0 / 4.12.4-1-ARCH, LLVM 4.0.1)
 RAM: 1787MiB / 24102MiB


vec@xeon-arch ~ $ glxinfo -B    
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD OLAND (DRM 3.15.0 / 4.12.4-1-ARCH, LLVM 4.0.1) (0x6608)
    Version: 17.1.5
    Accelerated: yes
    Video memory: 1978MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD OLAND (DRM 3.15.0 / 4.12.4-1-ARCH, LLVM 4.0.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.5
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 17.1.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.1.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10



vec@xeon-arch ~ $ cat /etc/X11/xorg.conf.d/20-amd.conf 
Section "Device"
    Identifier "AMD"
	BusID "PCI:02:0:0"
    Driver "amdgpu"
    Option "TearFree" "true"
EndSection


vec@xeon-arch ~ $ cat /etc/modprobe.d/radeon.conf 
blacklist radeon
blacklist nouveau


vec@xeon-arch ~ $ lsmod | grep amd
amdgpu               1732608  15
i2c_algo_bit           16384  1 amdgpu
drm_kms_helper        131072  1 amdgpu
ttm                    81920  1 amdgpu
drm                   299008  11 amdgpu,ttm,drm_kms_helpe


vec@xeon-arch ~ $ pacman -Qs amd
local/xf86-video-amdgpu 1.3.0-1 (xorg-drivers)
    X.org amdgpu video driver


vec@xeon-arch ~ $ cat /etc/mkinitcpio.conf 
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
#MODULES="amdgpu"
MODULES="vfio vfio_iommu_type1 vfio_pci vfio_virqfd amdgpu"
#amdgpu
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

I'm finding no others with this same problem as of kernel 4.11, so I'd be glad for any thoughts or pointers.

Last edited by vectro (2017-08-05 09:46:00)

Morn

Member

Registered: 2012-09-02

Posts: 886

Re: [Solved] AMDGPU issues with FirePro W2100 and Kernel > 4.10

Might be this bug: https://bugs.archlinux.org/task/54175

vectro

Member

Registered: 2016-10-15

Posts: 14

Re: [Solved] AMDGPU issues with FirePro W2100 and Kernel > 4.10

Yeah thanks, I found that shortly after posting. I'm not too satisfied downgrading mesa to patch the issue. Upon more research it seams that AMDGPU is still considered an experimental feature for S.Islands and C.Islands GPUs. I should have followed the asterix on the compatibility chart
I fell back to the default open source radeon driver and things work beautifully. Also according to Phoronix, there's a minor performance gain for S.I and C.I. cards on radeon compared to AMDGPU (linux 4.11).

Morn

Member

Registered: 2012-09-02

Posts: 886

Re: [Solved] AMDGPU issues with FirePro W2100 and Kernel > 4.10

I have had some very mixed results with the radeon driver and software compatibility, particularly shaders in games but there were also glitches with desktop compositors and WebGL rendering. Therefore I am sticking with amdgpu and kernel 4.10.13 for now. Maybe 4.13 will finally fix this bug, who knows.

vectro

Member

Registered: 2016-10-15

Posts: 14

Re: [Solved] AMDGPU issues with FirePro W2100 and Kernel > 4.10

Jesus H christ, the Radeon driver blows! It was working nicely on 4.12, until I started getting daily (hard) crashes and slow video acceleration. No xorg parameters would help. Downgraded back to 4.9.11 and amdgpu. Hope this gets fixed soon.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,033

Re: [Solved] AMDGPU issues with FirePro W2100 and Kernel > 4.10

x86_64 	Core 	linux-lts 	4.9.42-1 	The Linux-lts kernel and modules 	2017-08-12

Vectro, if you do need to go back to 4.9 kernel, atleast use linux-lts .

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

vectro

Member

Registered: 2016-10-15

Posts: 14

Re: [Solved] AMDGPU issues with FirePro W2100 and Kernel > 4.10

Thanks for the tip! I ended up switching to LTS yesterday and it seems to be working nicely with amdgpu. I was glad to find an LTS kernel in the repo. Wasn't satisfied freezing at 4.9.11 and loosing security updates indefinitely.