-
Notifications
You must be signed in to change notification settings - Fork 185
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
Support for NVIDIA's proprietary driver #151
Comments
Maybe. They'd need to add support for Vulkan DMA-BUF extensions too. We still have some code that assumes Mesa (see #51) and AMD hardware (see #49). We'll need to clean these up. Keep in mind that because the driver is proprietary, it makes the gamescope work a lot more difficult. We've been routinely sending RADV and amdgpu patches upstream to fix bugs, and reading the source code for troubleshooting. This isn't possible with a proprietary driver. |
Current build from git fails on Nvidia proprietary driver. On my laptop:
Since #51 and #49 are closed, and mesa 21.2.1 changes, what needs to happen to get Nvidia working? |
They need to implement |
Should this work already? |
While NVIDIA is missing in the link above, no, this won't work. |
This comment was marked as off-topic.
This comment was marked as off-topic.
I thought that they did cause of the link, thanks for the info! |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Is there any hope for NVIDIA to implement this? |
This place isn't NVIDIA support. If you'd like to know their plans, email them, and maybe share any response here if it's relevant to closing this issue. Who knows, might actually push them into action if enough people complain To actually be a bit helpful: Nvidia have slowly been adding bits of support for Wayland-related features to the proprietary driver, but it's also been like half a decade since the move to Wayland started, so who knows. Their message is obviously, in the future, don't buy nvidia if you're planning to use a Linux desktop. You can try the FOSS driver (nouveau) if you're desperate, but it'll most likely run ridiculously slowly compared to the proprietary one. I'm personally sticking to X until I either buy a new GPU or nvidia see the light. All that said, little bit rude to ping everybody watching this issue with nvidia rants/questions, for future readers, please just click the subscribe button and wait for someone to share some news. Until there's a comment with news, people here know as much as you do, and we're all as annoyed by the proprietary software from this vendor as you are. |
My next GPU definitely won't be NVIDIA. But I can't get a GPU until supply chain gets fixed up and miners calm down. |
Seams an official Nvidia employee says gamescope required vulkan extensions soon™ |
It seems, nvidia has added support for this with their most recent driver here. |
Yup. Closing since there's nothing more to be done on the gamescope side. |
This means NVIDIA GPU should automatically work now? |
well that's not a gamescope issue |
Just to confirm, has anyone got this working on the aforementioned beta driver, or the recently release 515.48.07? (I haven't 😅) |
@nrdxp I got it working by using gamescope-git (Arch) |
Were you able to get it working with fullscreen? For me it's only working in borderless and windowed modes with 515.48.07. If I launch in fullscreen or switch to fullscreen after launching, gamescope output goes black and I have to terminate it, at which point it freezes everything for about 10 seconds. |
@SingerJonathan Nope, using the -f flag, renders the first frame and then gamescope hangs. |
Now that NVIDIA's proprietary driver is about to land support for GPU-accelerated XWayland[1], could we see gamescope supporting it?
[1] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/587
The text was updated successfully, but these errors were encountered: