Getting stutters in Elden Ring when playing on Garuda

Bottom line up front: Elden Ring doesn't stutter at all when I use Nobara Linux, and stutters a bunch on Garuda Linux. I'm not sure what settings, options, etc are different between the two that'd be causing the game to stutter on one distro and not the other. I'd prefer to use Garuda but I'm not sure how to make it run like Nobara as I'm still a novice when it comes to linux.

If you want additional information or if there’s a better place for me to post this, please let me know. I’m sorry for lacking additional detail that may be helpful. I’m still new to figuring some of this stuff out and I’m not sure what’s relevant or not. I’m also new to posting for tech support in general so I’m not entirely sure what to ask or where to ask it. Any linux wisdom provided here would be greatly appreciated.

Here's my output from the require command:

System:
Kernel: 5.17.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3293a743-89eb-4b37-bc76-c02166704002 rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3
Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X570 AORUS ELITE WIFI v: -CF
serial: <superuser required>
Mobo: Gigabyte model: X570 AORUS ELITE WIFI v: x.x
serial: <superuser required> UEFI: American Megatrends LLC. v: F35
date: 07/08/2021
CPU:
Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3
family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 3650 high: 4549 min/max: 2200/4950 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3597 2: 3588
3: 3596 4: 3599 5: 4549 6: 3599 7: 3618 8: 3595 9: 3599 10: 3597 11: 3599
12: 3804 13: 3591 14: 3592 15: 3597 16: 3624 17: 3688 18: 3599 19: 3596
20: 3596 21: 3598 22: 3596 23: 3596 24: 3591 bogomips: 177589
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: always-on, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Vega 20 [Radeon VII] driver: amdgpu v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1 empty: DP-2,DP-3
bus-ID: 0b:00.0 chip-ID: 1002:66af class-ID: 0300
Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.1
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
s-diag: 1055mm (41.54")
Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left
model: LG (GoldStar) 27GK750F serial: <filter> built: 2019 res: 1920x1080
hz: 60 dpi: 92 gamma: 1.2 size: 531x298mm (20.91x11.73")
diag: 685mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: right model: Acer GN246HL
serial: <filter> built: 2018 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2
size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
OpenGL:
renderer: AMD Radeon VII (vega20 LLVM 13.0.1 DRM 3.44 5.17.9-zen1-1-zen)
v: 4.6 Mesa 22.0.4 direct render: Yes
Audio:
Device-1: AMD Vega 20 HDMI Audio [Radeon VII] driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0b:00.1
chip-ID: 1002:ab20 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: SteelSeries ApS Arctis 7 type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-3.3:7 chip-ID: 1038:12ad
class-ID: 0300
Sound Server-1: ALSA v: k5.17.9-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0
chip-ID: 8086:24fb class-ID: 0280
IF: wlp4s0 state: up mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: Gigabyte driver: igb
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp5s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 3-5:2 chip-ID: 8087:0aa7 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 6.36 TiB used: 2.31 TiB (36.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: HP model: SSD EX920 512GB
size: 476.94 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: SVN163
temp: 24.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1B6Q scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SSD PLUS 480GB
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 04RL scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT2000MX500SSD1
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 023 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Crucial model: CT2000MX500SSD1
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 023 scheme: MBR
Partition:
ID-1: / raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 33.18 GiB (7.4%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 33.18 GiB (7.4%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 33.18 GiB (7.4%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 33.18 GiB (7.4%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.35 GiB used: 1.8 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 16.8 C mobo: 16.8 C gpu: amdgpu temp: 39.0 C
mem: 40.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 880
Info:
Processes: 461 Uptime: 1h 52m wakeups: 0 Memory: 31.35 GiB
used: 7.69 GiB (24.5%) Init: systemd v: 251 tool: systemctl Compilers:
gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1940 lib: 528 Shell: fish
v: 3.4.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.16
Garuda (2.6.3-2):
System install date:     2022-05-22
Last full system update: 2022-05-22 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:

While I don't own the game, poking around on the web it looks like a recent patch has messed with how playable the game is for a lot of people. Strangely enough, Steam Deck owners only really complain about more load times recently. Since Nobara Project uses a kernel patched with Steam Deck support (among a ton of other things), it might be a kernel related issue given what people say how it runs and what kernels they are running (check https://www.protondb.com/app/1245620 ).

My other hunch is that you might have better luck running running the game under a forced compatibility mode in Steam with Proton GE (since the person behind Nobara Project also works on that version of Proton and it usually gives you a bit more frame rate).

Also don't forget to restart your machine. "↻" tells me that you need to.

4 Likes

For me it was helping to play on borderless window instead of fullscreen .. since that no more stutters
i play with proton 7.02

4 Likes

Nobara uses development version of Mesa. Perhaps upgrading to that could help.
https://wiki.archlinux.org/title/AMDGPU#Experimental

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.