-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gamescope doesn't run on NVIDIA #497
Comments
Try (1st line of logs complains about it): |
Using gamescope-git on my archlinux build it does work. |
@LethalManBoob I guess better to put this report into #492, instead of this issue. |
Seems like the same issue here.
Arch, everything is up to date. |
Yes, also facing same issue, same settings and nvidia drivers, same distro. |
Also having this issue with an NVIDIA GeForce RTX 2060 Mobile on Arch Linux running master Edit: not the same, I actually get
|
Same issue here, also with mobile GPU. vulkan: selecting physical device 'NVIDIA GeForce RTX 3050 Laptop GPU' Up-to-date arch. |
That version is too old, it's missing the NVIDIA fixes. |
Configuration like in my post above (Laptop GPU, using NVIDIA Prime), except: Gamescope git Version from 18.05.2022 gamescope -Y -- glxgears Update: Ran the same command with prime-run: |
Seems like the same as this bug #498 |
If anyone wonders. The chaotic aur version of gamescope-git is what I used. Usually chaotic aur is more up to date than the -git foundi n the normal aur |
Was testing, like suggested from Samsagax, but with -Y flag because of Nvidia GPU: Still same error like in my last post: And: Window with Gears is NOT showing Setup is still the same, like in my last post: (Gamescope git Version from 18.05.2022, Nvidia 3050 Laptop GPU) Full ouput: vulkan: selecting physical device 'NVIDIA GeForce RTX 3050 Laptop GPU' |
Getting a segmentation fault when trying to test gamescope on an Nvidia GTX 1070TI. Graphics card: NVIDIA GTX 1070TI $> gamescope -W 1920 -H 1080 -- glxgears
|
Try disabling mangohud? |
Dont think the error message has anything to do with mangohud.
|
515.48 still the same issue on X11, regardless of mangohud.
|
I believe to get past that error you need to use the gamescope-git package, right now. The last comment I saw you make mentioned |
It's also failing for me:
Versions:
|
I had this issue too, switching to the I have a GTX 1060 6gb and it seems to work. |
I suspect this might be a driver issue, but here goes.
|
gamescope-git with mangohud systemwide:
And without mangohud it opens the window and freezes until manually killed:
It does work in wayland tho. |
i got it working under steam but when i use it in terminal it doesnt work on bottles flatpak i get: on lutris its greyed out running optimus with intel |
weirdly enough it runs with ENABLE_VKBASALT=1
but it locks cursor inside the window and stutters from time to time |
I am seeing the same output as @severinkaderli after removing Optimus Manager from my system. I am on Garuda and just replaced their |
Optimus setups are a different kind of animal (and they seem to be forgotten by NV). Try the suggested variables setting in #498 I managed to get it working on the nested case. |
The referenced variables are set by the prime-run script that I mentioned. Gamescope actually runs through my intel iGPU if I don't set those variables, except for the color corruption referenced in #356, but crashes entirely if I try to run on Nvidia via prime. |
Having the same issue on Fedora, but using Wayland. Works fine under X11. |
As explained here, I have tried NVIDIA driver 515.57 on Wayland (GNOME 42, GBM backend) with both the latest gamescope git and a specific commit that was said to work. Neither works. I get the "DRM format 0x3231564E" error as everyone else. This is some kind of regression. That exact format was supported by NVIDIA on an earlier gamescope build or earlier NVIDIA driver. Not sure if the regression is in NVIDIA driver or in gamescope. I've already verified that the modeset flag is set: You can see some other user's log here which shows that the exact format WAS supported in whatever NVIDIA driver and gamescope version they used back then: #492 (comment) (Or perhaps they were running it on X11 and it's Wayland version that's broken? No idea.) |
In my case I am trying to run in Wayland, but I have verified that it is broken in X11 (bspwm) as well |
this is what it currently prints here.
and if i leave it "running" long enough it begins spamming |
Some people should check their commands. Also
EDIT: debug helper example (while running gamescope) $ lsof | grep egl- | awk '{print $1" "$2" "$NF}' | sort -u
firefox-b 16547 /usr/lib64/libnvidia-egl-gbm.so.1.1.0
Xwayland 18483 /usr/lib64/libnvidia-egl-gbm.so.1.1.0 EDIT2:
I noticed gamescope will not completely exit if command has failed. |
I see, thanks, it does load now (gamescope -- vkcube) but I'm unable to interact with the window (eg. resizing it) as it causes the system to hang for a bit and I have to force the program to quit
It also spammed the logs with When running the command one time, it displayed the first image of the vkcube fullscreen, froze and hung the entire system for ~5 minutes until I was put back at the login menu |
@PikaDevs
Same for me with But I was able to switch to next plasma virtual desktop and kill it via xterm. Usually using them instead of Alt+TAB. |
I see, thanks, it just seems that gamescope isn't really useable for me in it's current state with NVIDIA gamescope --nested-height 1440 --nested-width 2560 --output-height 2160 --output-width 3840 --filter fsr --fsr-sharpness 15 -- I assume since there's no fullscreen that's why the current output is 1440 by 2560, which makes no difference as to just running it at that resolution |
I've managed to fix |
lol $ grep '\-7' /usr/include/vulkan/vulkan_core.h
VK_ERROR_EXTENSION_NOT_PRESENT = -7, Which is either EDIT: well, the |
Anyone else having it crash every other boot? I can make gamescope work fullscreen on kde but ever other boot it just fails even if i close all running gamescope tasks |
Here's a weird one: I'm on Fedora 38, KDE. I just built the Gamescope binary, and i tried it out with vkcube. I get a black window and then it crashes, but I have to kill it with
Trying it with a native Ren'Py game, I get a black window and it crashes:
So I tried it over Wine, and I don't get a window at all. It just dies immediately:
And here's the really weird part. I added the Ren'Py game and Windows game to Lutris with DXVK and Gamescope enabled, and they...work fine?
I tried passing |
Gamescope hasent worked for me in months. Boots to empty screen.
|
@LethalManBoob to build from my branch:
|
@sharkautarch i tried your fix branch, but:
|
@Rdeisenroth Nvidia is one heck of a weird gpu on linux, amirite! See: and see: |
This comment was marked as outdated.
This comment was marked as outdated.
@LethalManBoob
I assume you're running on wayland?
hmmm that probably isn't supposed to happen normally????
hmmm maybe this line, plus the quoted line above it could just be due to a previous gamescope session that didn't exit properly???? Can you confirm that you still get said lines in your terminal after following these steps and then re-running gamescope:
What version is your nvidia driver? is it 545 or 535? |
@sharkautarch
Absolutely. I regret my RTX 4080. Should've bought AMD. But i do need some of the proprietary features of team green 😢
Hmm idk i can't get it to work with 545, it always freezes after a while. I will test 535 and other WMs tomorrow. I am using Hyprland with |
updated
|
@LethalManBoob Are you using nvidia driver version 545? I wonder if the issue w/ nvidia-fix not working is an issue of nvidia+gamescope being used w/ a wayland DE? @akay you said that I'm using nvidia dkms 535 on xfce (x11) and the |
I use Sway, so Wayland on wlroots:
|
545.29.06 wayland kde plasma |
Yeah, so it seems like nvidia 545 might not work well w/ gamescope |
nvidia-fix needs a fix for nvidia B) |
well, since the bug that necessitated the
|
Has anyone had a chance to test if the newly nvidia driver 550.54.14 has solved this issue? https://www.nvidia.com/Download/driverResults.aspx/218826/en-us/ |
i just tested to run it on 550.40.07 with gamescope-git rebuilt, havent tried it in a while and vkcube shows now. this is on a prime/optimus setup |
This comment was marked as outdated.
This comment was marked as outdated.
Same issue, i have set nvidia modeset and setcap using gamescope vkcube
nvidia-smi
|
I'm trying to run glxgears inside gamescope:
gamescope -W 1920 -H 1080 -- glxgears
and I get the following output:
The kernel parameter:
nvidia-drm.modeset=1
is set.Graphics card: NVIDIA GeForce 940MX
NVIDIA version: 515.43.04
Gamescope version: 3.11.31.beta4.r6.g97288b8-1
Distribution: Archlinux
The text was updated successfully, but these errors were encountered: