How to activate ray tracing support on Manjaro?


I’m runing a NVidia RTX 2060 on Manjaro 22.0.3 with kernel 6.1.11-1.

Here’s what I got regarding the drivers :

   ~  mhwd -li  :heavy_check_mark:

> Installed PCI configs:
                  NAME               VERSION          FREEDRIVER           TYPE
          video-nvidia            2021.11.04               false            PCI
           video-linux            2018.05.04                true            PCI

Warning: No installed USB configs!

I’m just wondering something :

I can’t manage to have Ray Tracing on my latest video games, like Returnal I just bought and playing on steam/epic.

Do you know what I should do to improve performance and activate rtx support ?

Thanks !

Isn’t that something that you change in the game’s graphics settings?

1 Like

Why do you have both open source and proprietary driver installed? Provide proper system information.

Which one? There is no general “do that” for things to work. Depending how you start the game and from where, this is not the same.

Ray Tracing will be available only if you launch game properly, but first things first, provide system information.

It may, but Ray Tracing will not be available anyway as all graphics cards are seen as AMD card in Proton, without forcing some settings at launch time.

TLDR; launch options in Steam with latest Proton


Hello all and thanks for the help !
First of all, regarding the Ydar comment : yeah I can’t change it on the game, ray tracing seems not to be activated:

As you can see it’s grey and when I start a game on Win11, it’s not and I can activate it.

And for Omano (sorry I don’t know how to embed a part of your messages)

I launch it with steam, but it launches Epic (I think Returnal needs Epic Game Launcher to start)

Here are my system information :slight_smile:

  Kernel: 6.1.11-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=037b75f4-def3-442d-810c-672ffa1a1eb5 rw nouveau.modeset=0 quiet
  Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
  Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING PLUS (MS-7C56) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 1.80
    date: 12/30/2021
  Message: No system battery data found. Is one present?
  RAM: total: 31.27 GiB used: 16.11 GiB (51.5%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
  Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 32 MiB
    desc: 1x32 MiB
  Speed (MHz): avg: 3007 high: 3954 min/max: 2200/4850 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3615 2: 2948
    3: 2955 4: 2888 5: 3954 6: 2993 7: 3150 8: 2879 9: 2880 10: 2878 11: 2877
    12: 2200 13: 3644 14: 2200 15: 3180 16: 2880 bogomips: 121650
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms extapic
    extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
    hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt
    pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor
    svm svm_lock syscall tce topoext tsc tsc_scale umip v_spec_ctrl
    v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq wbnoinvd wdt
    x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: ASUSTeK
    driver: nvidia v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
    status: current (as of 2023-02) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 2b:00.0 chip-ID: 10de:1f08 class-ID: 0300
  Device-2: Microdia Webcam Vitade AF type: USB driver: uvcvideo
    bus-ID: 1-9:6 chip-ID: 0c45:6366 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.7 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 81 s-size: 602x343mm (23.70x13.50")
    s-diag: 693mm (27.28")
  Monitor-1: DP-0 res: 1920x1080 hz: 60 dpi: 82
    size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce RTX
    2060/PCIe/SSE2 direct-render: Yes
  Device-1: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 2b:00.1 chip-ID: 10de:10f9 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 2d:00.4 chip-ID: 1022:1487 class-ID: 0403
  Sound API: ALSA v: k6.1.11-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.21 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.65 running: yes
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 2a:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp42s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
  Message: No bluetooth data found.
  Message: No logical block device data found.
  Message: No RAID data found.
  Local Storage: total: 2.96 TiB used: 222.7 GiB (7.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 33.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 2B6Q scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD10EZRX-00A8LB0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: N/A serial: <filter> rev: 1A01
    scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 850 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 2B6Q scheme: GPT
  Message: No optical or floppy data found.
  ID-1: / raw-size: 931.22 GiB size: 915.53 GiB (98.32%)
    used: 222.7 GiB (24.3%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 037b75f4-def3-442d-810c-672ffa1a1eb5
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: NO_LABEL uuid: 9AA3-93B9
  Alert: No swap data was found.
  ID-1: /dev/sda1 maj-min: 8:1 size: 500 MiB fs: ntfs label: N/A
    uuid: B4FC7F32FC7EEE4C
  ID-2: /dev/sda2 maj-min: 8:2 size: 300 MiB fs: vfat label: N/A
    uuid: 1D0C-20B8
  ID-3: /dev/sda3 maj-min: 8:3 size: 930.06 GiB fs: ntfs label: N/A
    uuid: DE6C66296C65FD21
  ID-4: /dev/sda4 maj-min: 8:4 size: 684 MiB fs: ntfs label: N/A
    uuid: C4C2233FC2233558
  ID-5: /dev/sdb1 maj-min: 8:17 size: 931.51 GiB fs: ntfs label: HDD
    uuid: B68E78D48E788E9D
  ID-6: /dev/sdc1 maj-min: 8:33 size: 300 MiB fs: vfat label: NO_LABEL
    uuid: A66A-3039
  ID-7: /dev/sdc2 maj-min: 8:34 size: 232.59 GiB fs: ext4 label: SSD
    uuid: 4f6e9318-4b89-4973-8ef0-7d4b30ec6adf
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-2:2 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-2.3:9 info: Microsoft Xbox360 Controller
    type: <vendor specific> driver: xpad interfaces: 4 rev: 2.0 speed: 12 Mb/s
    power: 500mA chip-ID: 045e:028e class-ID: ff00 serial: <filter>
  Device-2: 1-5:3 info: Logitech Illuminated Keyboard type: Keyboard,Mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 300mA
    chip-ID: 046d:c318 class-ID: 0300
  Device-3: 1-7:5 info: Micro Star MYSTIC LIGHT type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 500mA
    chip-ID: 1462:7c56 class-ID: 0300 serial: <filter>
  Device-4: 1-9:6 info: Microdia Webcam Vitade AF type: Video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 0c45:6366 class-ID: 0e02 serial: <filter>
  Device-5: 1-10:7 info: Logitech G402 Gaming Mouse type: Mouse,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 300mA
    chip-ID: 046d:c07e class-ID: 0300 serial: <filter>
  Hub-3: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-4: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-5: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-6: 5-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-7: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  System Temperatures: cpu: 65.4 C mobo: N/A gpu: nvidia temp: 49 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
  Processes: 417 Uptime: 19h 0m wakeups: 0 Init: systemd v: 252
  default: graphical tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7
  Packages: 1334 pm: pacman pkgs: 1327 libs: 355 tools: pamac pm: flatpak
  pkgs: 0 pm: snap pkgs: 7 Shell: Zsh v: 5.9 default: Bash v: 5.1.16
  running-in: konsole inxi: 3.3.25

I pasted the code you provided in Steam and it works ! Thanks ! But it’s really slow and stuttering tho.
I’m gonna check on the configuration setup.

Thanks a lot.

Yeah it’s working but the framrate is really low on “medium” pressets, and I checked I have the recommanded configuration to play on “high” pressets.
Maybe there’s something I should do with Proton to improve the performance ?

So you launch it through Steam.

Running the game through Proton is not the same that playing on Windows, especially if you enable advanced features like Ray Tracing, you will not get same performance as on Windows.

There is a feature for Proton game called Shader Pre Caching in Steam, it grabs and compiles shaders ahead of time for Proton so it does less/no stuttering when you need them in game. The shader stuttering should calm itself at some point if you stay in same area of game though without shader pre caching enabled.

If you have low framerate then, it is because you need to tune the game settings. The 2000 Nvidia series are almost a joke when it comes to Ray Tracing, I consider them a proof of concept, especially the 2060. The functionality is there, the power is not.

Honestly I wouldn’t bother enabling Ray Tracing under Proton. You show you have 35 FPS in the menu without Ray Tracing on High settings, I don’t know where you get the impression you could then enable Ray Tracing and have an acceptable experience.

I would set it to Medium @ 1080p without Ray Tracing, using DLSS maybe if it improves performance, or maybe using a startup option to use AMD FSR from Proton, I don’t know at this point you need to tinker a bit I don’t have the game. and Returnal (1649240) · Issue #6538 · ValveSoftware/Proton · GitHub can be information source

select the part of my message you want, click QUOTE.

PS: you can remove the video-linux driver from MHWD, as it appears you have correctly installed the proprietary driver from Manjaro repositories (so I don’t know why video-linux is still present, weird).

Okay thanks a lot I’ll try all this :slight_smile:

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