Farlight84 crash issue after system update

Hello Garuda users.
i was facing a problem to launchin farlight 84 game on steam but in i wlready played this game on this same system just some days ago idk what to do

command:

╭─alex@SoulHunter in ~
╰─λ garuda-inxi
System:
Kernel: 6.4.12-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4ffdc21e-d8b6-4c1f-b1fb-883626b7e4ab rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: A320M-S2H v: N/A
serial: <superuser required>
Mobo: Gigabyte model: A320M-S2H-CF v: x.x serial: <superuser required>
UEFI: American Megatrends v: F53 date: 01/05/2021
CPU:
Info: model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 type: MCP
arch: Zen level: v3 note: check built: 2017-19 process: GF 14nm
family: 0x17 (23) model-id: 0x11 (17) stepping: 0 microcode: 0x8101016
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
desc: 1x4 MiB
Speed (MHz): avg: 2813 high: 3692 min/max: 1600/3500 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2954 2: 1654
3: 2953 4: 3692 bogomips: 27947
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series]
vendor: Gigabyte driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 07:00.0
chip-ID: 1002:15dd class-ID: 0300 temp: 54.0 C
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.0
compositor: kwin_x11 driver: gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: 24HC1QR serial: <filter>
built: 2020 res: 1920x1080 hz: 120 dpi: 82 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 600mm (23.6") ratio: 16:9, 15:9
modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.6 renderer: AMD Radeon Vega 8 Graphics
(raven LLVM 15.0.7 DRM 3.52 6.4.12-zen1-1-zen) direct-render: Yes
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 07:00.1
chip-ID: 1002:15de class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 07:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.4.12-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.78 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8168 v: 8.051.02-NAPI modules: r8169 pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Drives:
Local Storage: total: 585 GiB used: 167.25 GiB (28.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT3500SC 6
CTB5029G21Y034 size: 465.76 GiB block-size: physical: 512 B logical: 512 B
speed: 3.0 Gb/s tech: HDD rpm: 7200 serial: <filter> fw-rev: A52B
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 model: SSD 128GB size: 119.24 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter>
fw-rev: XKR scheme: GPT
Partition:
ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
used: 29.87 GiB (25.1%) 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: 118.95 GiB size: 118.95 GiB (100.00%)
used: 29.87 GiB (25.1%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
used: 29.87 GiB (25.1%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
used: 29.87 GiB (25.1%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 13.59 GiB used: 3.58 GiB (26.4%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 54.5 C mobo: N/A gpu: amdgpu temp: 54.0 C
Fan Speeds (rpm): N/A
Info:
Processes: 339 Uptime: 3h 13m wakeups: 0 Memory: total: 16 GiB note: est.
available: 13.59 GiB used: 9.13 GiB (67.2%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 15.0.7
Packages: pm: pacman pkgs: 1538 libs: 465 tools: octopi,paru Shell: fish
v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.29
Garuda (2.6.16-1):
System install date:     2023-08-28
Last full system update: 2023-08-28 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

here you can find the logs of steam

please help me to fix it

This means that a reboot is pending after the latest update.
Most likely not related to your issue, but you never can say.
What was updated in the latest update? If you check the pacman logs you could try to understand if something important changed.
You could maybe test the linux-lts kernel.

sudo pacman -S linux-lts linux-lts-headers

Then select it at the next boot in the GRUB under Advanced Options.

1 Like

nothing changes i booted with xanmod kernel and here is the logs
the problem is still exist.

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