Hi Community,
I have a Radeon RX550 4GB, and i dont have the Backend Rendering in the Monitor and Display / Compositor settings!
When i run the cmd `glxinfo | grep “OpenGL version”
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.1`
Question comes down to if i must remove the Mesa driver since i have installed the amdgpu-pro drivers, and how do i correctly do that?
Why? They are inferior to the the open source AMDGPU kernel driver.
Tip: If you don’t know why I said, that, you have not done enough research. 
Are you suggesting that i should remove all the amdgpu-pro drivers?
I did my research on internet when i installed Manjaro for first time, the Backend rendering setting was not optional, so i found out that i needed the amdgpu-pro drivers to get that option !
Okey so now what do i do? and how do i do it?
Graphics:
Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X]
driver: amdgpu v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm
built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-2
empty: HDMI-A-1,HDMI-A-3,HDMI-A-4 bus-ID: 03:00.0 chip-ID: 1002:699f
class-ID: 0300 temp: 37.0 C
Display: x11 server: X.Org v: 21.1.6 compositor: kwin_x11 driver: X:
loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 444x277mm (17.48x10.91")
s-diag: 523mm (20.6")
Monitor-1: HDMI-A-2 mapped: HDMI-A-1 model: HP L2245w serial: <filter>
built: 2009 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.1 renderer: AMD Radeon RX 550 / 550 Series
(polaris12 LLVM 14.0.6 DRM 3.42 5.15.85-1-MANJARO) direct render: Yes
mhwd -l && mhwd -li ✔
> 0000:03:00.0 (0300:1002:699f) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
> 0000:05:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
network-r8168 2016.04.20 true PCI
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
Warning: No installed USB configs!
journalctl --boot=0 --priority=3 --no-pager ✔
Dec 30 21:19:48 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:48 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:48 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:48 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:48 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:48 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:48 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:48 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:48 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:48 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:48 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:48 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:49 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:49 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:49 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:49 core bluetoothd[931]: src/plugin.c:plugin_init() Failed to init vcp plugin
Dec 30 21:19:49 core bluetoothd[931]: src/plugin.c:plugin_init() Failed to init mcp plugin
Dec 30 21:19:49 core bluetoothd[931]: src/plugin.c:plugin_init() Failed to init bap plugin
Dec 30 21:19:49 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:49 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:49 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:49 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:49 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:50 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:50 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:50 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:50 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:50 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:50 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:50 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:50 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:50 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:51 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:51 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:52 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:52 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:52 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:52 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:52 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:52 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:52 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:52 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:52 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:53 core kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Dec 30 21:19:53 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:53 core kernel: EDAC sbridge: Couldn't find mci handler
Dec 30 21:19:53 core kernel: EDAC sbridge: Failed to register device with error -19.
Dec 30 21:19:58 core systemd[1]: Failed to start pkgfile database update.
Dec 30 21:24:41 core konsole[2477]: kf.xmlgui: Shortcut for action "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Dec 30 21:24:41 core konsole[2477]: kf.xmlgui: Shortcut for action "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Dec 30 22:07:01 core crond[932]: (root) CAN'T OPEN (/etc/crontab): No such file or directory
Display: x11 server: X.Org v: 21.1.6 compositor: kwin_x11 driver: X:
loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: :0 screens: 1
sudo lshw -c memory ✔
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 5.11
date: 03/04/2022
size: 64KiB
capacity: 8MiB
capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
*-memory
description: System Memory
physical id: 56
slot: System board or motherboard
size: 32GiB
*-bank:0
description: DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
vendor: Undefined
physical id: 0
serial: 321640CE
slot: DIMM_A1
size: 8GiB
width: 72 bits
clock: 2667MHz (0.4ns)
*-bank:1
description: DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
vendor: Undefined
physical id: 1
serial: 321640CD
slot: DIMM_B1
size: 8GiB
width: 72 bits
clock: 2667MHz (0.4ns)
*-bank:2
description: DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
vendor: Undefined
physical id: 2
serial: 6C440EC3
slot: DIMM_C1
size: 8GiB
width: 72 bits
clock: 2667MHz (0.4ns)
*-bank:3
description: DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
vendor: Undefined
physical id: 3
serial: 6C440ED0
slot: DIMM_D1
size: 8GiB
width: 72 bits
clock: 2667MHz (0.4ns)
*-cache:0
description: L1 cache
physical id: 62
slot: CPU Internal L1
size: 1152KiB
capacity: 1152KiB
capabilities: internal write-back
configuration: level=1
*-cache:1
description: L2 cache
physical id: 63
slot: CPU Internal L2
size: 4608KiB
capacity: 4608KiB
capabilities: internal write-back unified
configuration: level=2
*-cache:2
description: L3 cache
physical id: 64
slot: CPU Internal L3
size: 45MiB
capacity: 45MiB
capabilities: internal write-back unified
configuration: level=3
Alright, fair enough. I just meant AMDGPU outperforms AMDGPU-PRO in general and the latter should not be used in most cases.
Tip: Most users do not need these proprietary drivers.
AMDGPU PRO OpenGL is a proprietary, binary userland driver, which works on top of the open-source amdgpu kernel driver. From Radeon Software 18.50 vs Mesa 19 benchmarks article: When it comes to OpenGL games, the RadeonSI Gallium3D driver simply dominates the proprietary AMD OpenGL driver. Users of graphic cards other than Radeon Pro are advised to use the amdgpu graphics stack. Mostly used because of lacking compatibility layers that some software relies on.
When you say, “backend rendering”, do you mean AMD Radeon™ ProRender?
Either way, sharing more details about why you need that feature will help us help you.
When you say, “backend rendering”, do you mean AMD Radeon™ ProRender?
In Backend Rendering in the Monitor and Display Settings
Your quote is enveloping your entire reply. Might want to edit that.
Tip: I don’t use KDE. Maybe I’m not the best person to answer this. 
There is no “Backend Renderer” option in the Display and monitor section anymore. It is auto-selected by Plasma at this point, I believe.
What got me wondering is that i also was shocked over that i could not choose Crisp option in Scale method like i have always, and the second that back-end rendering in the monitor and display settings!