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
Failed to find physical device on Intel #49
Comments
Please provide a stack trace. You can do so by running |
|
Hmm, this is missing debug symbols. Can you try compiling from source? |
Sorry for the delay with the answer. I've compiled gamescope from source. I got segfault as well, but the stack trace isn't the same. Spoiler
|
Can you try the latest commit? 9353ba1 It seems like |
Yeah, I've got |
It means your GPU doesn't support Vulkan, or it may be a Vulkan driver bug. Can you try running |
Here's |
Hmm, we're selecting a queue with compute support and without graphics support: https://github.com/Plagman/gamescope/blob/9353ba11d33c945329dd546433037154ad834bbd/src/rendervulkan.cpp#L472 |
On AMD hw there are two queues: one with gfx support, and another one which is compute-only. We want to select the second one if available so that the game can have exclusive access to the gfx-capable queue. On Intel there's only one queue. In this case we should fallback to the first queue instead of trying to pick the second one. |
Can you check again with latest? I think there's a good chance it'll work on Intel now, but I don't have the hardware to test. |
Got this:
|
Eh, right, we don't handle more than one DMA-BUF planes at all right now. I've tried to add asserts to make it clear what parts of the code assumes 1 plane. Would be nice to plumb that across the compositor, since AMD is eventually going to have these too. |
What client were you trying to run here? |
Battle for Wesnoth |
Does anyone know offhand why DMA-BUFs for what seem like normal clients would have several planes on Intel? Is there some sort of planar encoding we need to feed back into Vulkan when importing? Is this another 'we need modifiers' situation? |
Intel buffers with the CCS modifier will typically use multiple planes. I don't know if things will "just work" once we start supporting multiple planes, but https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1466 doesn't seem too far away from being mergeable. |
Jason mentions INTEL_DEBUG=norbc might help with this. Try setting it for both gamescope and the client, probably. |
It doesn't crash with |
Hello, I believe I am having a related issue, however regardless of when I run INTEL_DEBUG=norbc I am running gamescope 3.7.1 from gamescope on latest aur. however the issue that I am getting right now is
I am unsure as whether or not this is a related issue. I am running sway desktop, and an Braswell CPU. attached are the full text output of running "gamecope -- firefox" (It doesnt work with any game) and vulkan info. |
Above post was using wayland. I tested using sway and KDE behavior is consistent. On X11, I got the same issue as Renom did, but I did not need to use the intel debug. this is on the latest mesa-git so it should now support VK_EXT_image_drm_format_modifier EDIT: More info When running gamescope -l -d... on a fresh boot this is the output Slightly different, now has a new error |
Apologies for not being able to get logs, but running gamescope on intel WORKS when running on a tty directly, This started happening with the latest merge request #166. I can confirm that it did not work before that merge it does NOT work when nested either with wayland or X11, (same issues as before at a close glance). I do not have time to test further. I will get logs when time permits Thanks for all the hard work being put in. |
That's interesting, I certainly wouldn't expect this PR to make things work. I'll investigate and see what has changed since last time I tried. |
My appologies it seems like I spoke early, I ran supertuxkart from a tty; Needless to say it didn't work. Interestingly enough, of the apps I have tried, kate, firefox, and glxgears all failed. However, I was able to run sway, and within Running under wayland (nested) I get this issue
I will do more testing, |
The graphical issues are always the same, a single line of pixels at the top, rest of the screen is blank. or just a blank screen. I can tell that graphics are updating as the line of pixels changes in adherence with movement I know to be happening. here are some tested apps, assume the pixels are the grahical issue unless I specify otherwise. Supertuxkart - Works fine until you get in game, then after a couple of seconds graphical issues. Supertux2 - works fine, bad preformance issues Warzone2100 - works flawlessly from my testing spent about 20min on each graphical backend Firefox - Just crashes MPV - graphical issue Dolphin (File browser) - Graphical issues. VKcube- blackscreen glxgears - blackscreen Sway - low preformance, forced letterboxing |
According to the spec, this is invalid: > If the tiling of the image is VK_IMAGE_TILING_DRM_FORMAT_MODIFIER_EXT, then > the aspectMask member of pSubresource must be > VK_IMAGE_ASPECT_MEMORY_PLANE_i_BIT_EXT This triggers an assertion in anv. References: #49
With this Mesa patch and the latest gamescope commit, I was able to run glxgears inside a nested gamescope session on a CML machine: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10426 |
Seems like there were already a lot of other MRs doing the same thing:
The latest iteration is: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10624 |
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10624 has been merged. |
On the latest mesa-git and latest gamescope X11 seems to work fine, but I can no longer get TTY to work. first elaborating on X11, Both vulkan and Opengl apps seem to work pleasantly, even wine apps have been working on it. preformance is about what I would expect from my machine, (Given it is a celeron N3050 so preformance is not great in most stuff in the first place) I have not done extensive testing, but supertuxkart renders properly and is playable. Wayland and starting from a TTY directly both give this error. I will test past versions of gamescope at my earliest convience.
|
Hello, The last thing I have tested for the regression happened sometime after commit 2bb4907. This was the last commit I could test. if needed I could test more at a later date. As far as X11, Gamescope seems to be consistent and as performant as I would expect. Even during edge case games that make calls directly to GDI seem to work without issue. Wayland Produces the same issue on KDE and Sway. |
Hello, I updated to the new gamescope, tried on wayland, and got it to work a single time. preformance was terrible, and no mouse but it did work. interestingly enough it won't work again no matter what I do, I have only tried on sway, and have no logs. unfortunately I borked my install trying to see if I can get it to work, and wont have time to reinstall for a while. however it was progress regardless and thought it best to inform anyways. |
Latest updates causes intel wayland to work, I have not verified Xorg still works, Framerate seems fine, but I am using a celeron so I get around 15fps either way so it's not a great indicator on intel wayland it seems to be pretty much usable with the hardware I have. unfortunately I do not have other hardware I can test with. TTY still does not work now get an error. drmModeAddGB2WithModifiers failed: Invalid argument |
Running nested on intel seems to run fine in both wayland (sway) and x11 (KDE) however running from TTY results in a black screen and gives this error
|
Ah, this in fact is not an Intel-specific bug. Fixed in c9e8634. |
Closing since Intel should be supported now. Please open separate issues if something doesn't work. |
I'm trying to start gamescope (e.g.
gamescope
command without params), but then I get segfault with the following errors:Any ideas?
The text was updated successfully, but these errors were encountered: