What desktop environment or wm are you using? Are you using a login manager or launching your session from tty?
I’ve had similar issues in the past but in my case I had to configure things so that when I log in it sets environment variables correctly and have my sway config start up xdg-desktop-portal correctly.
I’ve also had situations where specifically xdg-desktop-portal-gtk was causing problems so id uninstall that while keeping the other xdg-desktop-portal-* packages, so it could be one of those causing it
Some annoyances exist though, like trying to use hardware en(!)coding while retaining the mesa drivers for gaming. HW Enc. is only available with the proprietary amdgpu-pro drivers, which are no good for gaming. You can work around that by using distrobox to setup an arch container on any distro and then using the AUR to install the proprietary drivers and obs in that container. That way, the rest of the system still runs on mesa, but obs loads with hardware encoding support. You can then export obs using distrobox-export -app obs-studio to make it available on the rest of your system like any other app. On nvidia, you install the proprietary drivers anyway, so obs will let you encode on hardware right away.
Hmm, I’ve just tried a fresh install of Manjaro and it’s exhibiting the same problems as Pop. It could be something to do with my setup? Or maybe there’s some other Linux fuckery going on? It’s strange though, since Windows works just fine.
What kind of problems are you seeing? The only issue I had was stuttering but I fixed that with corectrl. I have an AMD GPU and running Wayland if that helps.
When launching SteamVR my headset turns on but all I see is a grey screen. In the left eye there’s a very glitchy image of my desktop that flickers rapidly. Disabling asynchronous reprojection fixes the flickering desktop but the view is still completely grey.
Also, my base stations don’t wake up when launching SteamVR. Trying to scan for them results in it find them but being unable to connect (with an unhelpful error message that says “failed to connect” or something along those lines). I assume the lack of base station connectivity is causing the grey screen in the headset, but I’m not sure how to get them to connect.
I’ve tried using lh.py to get them to wake up, but there’s some Bluetooth error that happens that I haven’t figured out yet: bluepy.btle.BTLEManagementError: Failed to execute management command ‘le on’ (code: 17, error: Invalid Index). I read somewhere that this might be because the Index’s Bluetooth chip doesn’t work on Linux and that I may have to buy a separate Bluetooth adapter :/
I’ve followed the Bluetooth instructions but now SteamVR crashes on launch.
I get a 109 error on the 1.14 Linux branch (no change from before).
On the beta branch it crashes as soon as I launch it (nothing specific, just a message saying SteamVR is disabled because it crashed and a Retry button). Upon retrying my entire system froze and I had to hard reset. Upon rebooting and trying again it broke the window manager so now I have no window chromes (if that’s what you call them on Linux? the top bar and title and min/max/close buttons) so I had to reboot again.
On the stable branch it seems to now work but there’s a very noticeable delay in my head movements, which is very nauseating. Disabling asynchronous reprojection seemed to slightly improve this, but it’s still noticeable.
If I can’t find a fix for that, it seems like Linux VR is still a pipe dream for me. But in any case, thanks for your help so far!
Regarding the lag, to fix that I had to make sure the gpu was using it’s full capacity which I managed to do by using the Corectrl app to add a SteamVR profile and setting it to max. Without it I would see the same issue where it didn’t move fast enough with my head movement.
It seems CoreCtrl doesn’t support Nvidia GPUs, which is unfortunate. I did also attempt to set PowerMizer mode to Maximum Performance in nvidia-settings but that didn’t help. I suppose I’ll need an AMD card to have a good Linux VR experience?
I was having similar problems on a fresh arch install with multiple apps taking upwards of 15 seconds to launch, and the “fix” ended up being to uninstall one or more of the “portal” packages (there are several with names like xdg-desktop-portal-gtk). gitlab.gnome.org/GNOME/…/74 and bbs.archlinux.org/viewtopic.php?id=285334 for more info.
Could be completely unrelated, but it might be worth a try.
Exciting that the team at ChimeraOS was able to get some initial support for the ROG Ally so quickly.
AMD employs developers to directly contribute to Linux, so basic support for the SoC was just a matter of time anyway. However, Asus does funky stuff, so the experience seems to be not excellent right now: “Issue: Wi-Fi, Bluetooth, Audio, or extra keys stop working. This can happen after the system goes into suspend, after booting to Linux after being in the BIOS, or may occur randomly after a few successful boots.” github.com/…/Device-Specific-Configurations#asus-…
I had a 5700xt prior to my current 3060 and I’m very tempted to switch back so I can get rid of nvidia’s drivers, getting Wayland functional has been a disaster for me.
I just switched them like a couple weeks ago to give macOS another go, so I’m just being lazy 😅
I’m so mad at myself for impulse buying the rtx 3080… can’t wait to switch to team red completely in a couple of years. Or do you think someone is willing to swap their AMD for my nVidia card? 😂
I don’t know how you all manage to have so much trouble. The only issue of note I’ve had with nVidia is the machine not hibernating by itself. Apart from that, it’s always worked without much fuss for the last fifteen years (not sure what I used before that).
My Nvidia card is rock solid under Wayland. As long as I’m not running something needing 3d acceleration. Using it with 3d acceleration I have to be very careful. If the viewport moves too fast etc. Nvidia just shits the bed. Then I have to drop to terminal and reset my desktop session quickly before it hard locks the system. It’s very annoying and reproducible. So much so that I’m replacing a 1650 with a 6400 with less vram.
Same here. I keep shaking my head in disbelief when I read all this “you need this custom niche distro if you want nvidia without problems” posts, and then look at my totally uncustomized Debian Stable PC, on which I’ve been playing modern games for many years now. :)
Really, the only trouble I’ve had was not Nvidia related at all - in the very beginning when Steam Linux client was released, Debian had too old glibc, and I had to resort to LD_LIBRARY_PATH/LD_PRELOAD tricks with glibc snatched from an Ubuntu package. But next Debian release fixed even that, and it’s been smooth sailing ever since.
I just bought a Samsung G9 Neo (5120x1440), and Ubuntu just worked resolution-wise. Had to switch the monitor to 120hz instead of 240 because otherwise Ubuntu would only allow 60. For the rest all is well. GTX1660Ti. I’m actively looking to upgrade that card now though, with an RTX4060Ti being the prime candidate. I wondered whether i should choose AMD instead, but the doubt was too much. 😅
There’s FSR2 which is similar to DLSS without frame gen They’re also developing FSR3 which will apparently give “up to a 2x increase” of frames by also using frame gen.
A pro of FSR is that it’s open source so it’s easier for developers to put it in their games themselves.
Same here, experience got worse after upgrading the monitor.
I went from a somewhat matched pair of 1080p 75Hz monitors, one of which was ultrawide (2560 width) to upgrading my ultrawide to a 3440x1440 160hz panel.
That upgraded panel suffered every step of the way in Linux.
I absolutely cannot get 160Hz consistently if I have both monitors running. On KDE X11, compositor drops the rate to 75FPS to even things out (except the mouse lol). On KDE Wayland it works properly in this regard, but we all know how Wayland is on NVIDIA right now.
GNOME is a similar story as KDE Wayland, with an added bonus of stuttering.
I’m not losing hope, though. It’s gonna catch up to AMD but man does it stink to use lol
The only other reason I really have to use X11 is because the hardware video decoding in the browser doesn’t work in Wayland with NVIDIA. Most of the apps are actually becoming more and more stable.
Had the same problem after upgrading from 37 to 38. Its an nvidia problem
1 - Boot an older kernel OR Drop to a TTY (Ctrl + Alt + F3) OR Boot into runlevel 3 (on grub, press ‘e’ when the list of kernels show, look for the line with quite splash nvidia-drm.modeset=1 and add the number 3 there, then Ctrl + X to boot) 2 - Login on your terminal and dkms status. If you see something like /var/dkms/nvidia/525.116.03/source/dkms.conf does not exist, remove the entire directory of the failed version rm -rf /var/dkms/nvidia/525.116.03 3 - sudo dkms autoinstall 4 - reboot if no errors and profit, otherwise rinse and repeat step 2-3
PS: If dkms tells you nothing at all (after the upgrade): remove the drivers /etc/nobara/scripts/cosmo-nvidia-wizard/remove.sh
reinstall them /etc/nobara/scripts/cosmo-nvidia-wizard/install.sh
If your dkms status is ok, you probably have a mismatch in your initramfs and root. just sudo dracut -f --regenerate-all and reboot
it was an nvidia driver problem, i have resolved the issue by editing the boot in grub by pressing e and setting ‘nomodeset quiet’ and reinstalling the propriety drivers upon boot
linux_gaming
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.