HI there! This is my first post here and using Linux on an AMD laptop, so pardon me if there are some things that I am not aware of that the rest of y’all are. With that said, let’s start with the questions:
What are some recommended software (preferably GUI) for configuring AMD GPUs?
What configurations and settings are recommended (e.g. GRUB parameters, config files, scripts, etc.)?
Any software that would help improve performance (especially for compute and gaming)?
Trying out UKUU almost broke my system since its kernels had invalid signatures, despite Secure Boot being turned off; are there other methods for getting newer kernels on Ubuntu-based distros besides installing linux-generic-hwe-18.04?
Addendum: Some more questions came up.
Does Linux switch between AMD GPUs dynamically based on demand?
Using glmark2 simultaneously on both iGPU and dGPU using DRI_PRIME yields the same score (449); shoudn’t the dGPU yield better results?
I’m assuming you are using some Ubuntu variant? If so UKUU should JUST WORK, I would suggest pasting a screenshot of the error message here so someone smarter than myself can take a look.
Switching GPUs on Linux with an Nvidia and Intel GPU barely works, and you have to restart your Window Manager/Desktop Environment every time you do, I imagine the support with AMD GPUs to be practically nonexistant.
When in the desktop go to the terminal and paste in
journalctl -b
That command will show you the log of your last boot. You can then just copy everything and paste it here.
if you want to open it in a text editor just put the name of the app before the command. or maybe you put the name of the app before the location path. So for example
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See journald.conf(5) for details.
[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=1000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
Yeah, opening journald logs with text editors was a bad idea since they are apparently in binary form instead of regular text. Seriously, why is it like that? Binary logs are a terrible idea.
Linux in a nutshell, ladies and gentlemen. It isn’t truly YOUR system unless you can completely and inadvertently destroy it by accident with some misguided terminal commands.