[solved]vulkan games black screen, only sound

[The Main Man]

vkcube was fixed in 181.

Right, after emerging 9999 vkcube is working.

I really appreciate you testing this out with me. Ive now installed all 9999 packages again and reverted from using stable packages.

No worries, I was always curious about Sway and Wayland in general, this was a perfect chance to finally test it.

Forgot to say in previous post that of course my first goal was to try l4d2, but I couldn't launch Steam, it was complaining about having problems locating X display and I couldn't bother with that then.
I got it to work now, thing is I have Steam installed via flatpak, so I don't have any x32 libs actually on my system, and the trick with Wayland was to disable Wayland socket in Steam in order for it to launch.
l4d2 works with -vulkan

Now, I understand that it's not actually regularly installed Steam, like in your case, but I like it this way and will not change it.
I'll leave Sway installed, I have to test other stuff but if all goes well there's a pretty good chance of me moving to it, so feel free to ask anything for me to try, except installing x32 libs and Steam in non-flatpak way

[shoober420]

I did install Steam manually, with all native 32bit libs, but unfortunately i get the same behavior even with the runtime enabled. when you say disable wayland socket, do you mean launch Steam and Steam games with “SDL_VIDEODRIVER=x11”?

I added to the gentoo wiki files for manual installation if you want to disable the runtime and launch steam natively.

https://github.com/shoober420/rootscrip ... s/steamset
https://github.com/shoober420/rootscrip ... e/steamuse

[The Main Man]

In flatpak configuration for Steam package if I enable Wayland it won't start, only if I disable it.
In X11 that doesn't matter but on Wayland it does.
You can see what I mean in this screenshot.
Don't know about "SDL_VIDEODRIVER=x11"

[shoober420]

after manually installing the amdgpu-pro drivers and using them, vulkan is borked on my system. i used to be able to run vkcube. now no matter if i uninstall vulkan-* packages and restart from the top like i did prior, vkcube crashes sway or renders a black screen like mentioned.

ive come up with a reinstall list that SHOULD start from scratch if your use flags are set, or unset in this matter.

emerge -av "vulkan-headers vulkan-loader vulkan-tools glslang mesa wlroots sway xf86-video-ati"

there is also vulkan-tools 32bit i installed recently, which might be why vkcube never runs anymore. i also dont know how to launch 64bit vkcube and 32bit vkcube when both libs are installed

this whole thing is pretty wild. because of how many different debugging things ive tried, i feel like i cant go back to the start of before all the debugging was tried. i cant seem to get consistent results. this vulkan fiasco is driving me pretty crazy lolol

@kajzer
Here is a flatpack of proton if you’re interested. proton broke on sway after 5.13 apparently
https://github.com/flathub/com.valvesof ... .Proton-GE

[The Main Man]

Yeah, I'm using flatpak GE version anyway, regardless of Sway
I find it much better than stock Proton

[The Main Man]

Oh, and I had to abandon Sway and Wayland, I was starting to configure it, setting up Waybar and tweaking WM, and I was watching some videos with mpv, what happened was after few minutes of watching the monitor would turn off for some reason, you could hear the audio still running but nothing except hard reset would help that situation. When it happened 3 times I decided to let it go, that doesn't happen in X11, too bad as I was starting to like it. Could be Vulkan related as mpv is using vulkan, I guess I could have tried to turn it off for mpv and see if it would happen again but I just quickly reverted back to X and that was it, I might try it again soon.

[shoober420]

i’m using GE as well, but non-flatpak

so wait you actually did get vulkan working then?

[The Main Man]

vkcube worked after I emerged 9999 version
l4d2 worked with -vulkan under Wayland

So I guess it was working but like I said, was getting crashes, don't know if that's Vulkan related though

[shoober420]

ok, i think i figured out how to start from scratch

1. "emerge -Cav vulkan-loader vulkan-headers vulkan-tools"

2. "rm -rf /usr/lib/libvulkan*"
"rm -rf /usr/lib64/libvulkan*"

step 2 removes the preserved libs that get left over, which is probably why i couldnt get consistent results

after that using the vulkanusedebug file in my package.use folder (https://github.com/shoober420/rootscrip ... anusedebug), im now able to easily tweak and change use flag settings for vulkan-tools and vulkan-loader.

now im emerging "vulkan-tools vulkan-loader vulkan-headers", with the wayland flag disabled, to test X

trying to launch vkcube now gets this error:

Code: Select all

@gentoo:~$ vkcube                                                                                                                                                                              
vkEnumerateInstanceExtensionProperties failed to find the VK_KHR_surface extension.                                                                                                            

Do you have a compatible Vulkan installable client driver (ICD) installed?
Please look at the Getting Started guide for additional information.

getting further i guess? lolol, at least its something different. im feeling a bit better

recompiling vulkan packages with wayland flag enabled on vulkan-loader

still the same error as above

going into the /usr/lib directories again shows that libvulkan_radeon.so is missing from both lib32 and lib64

this is provided by mesa, so recompiling mesa and restarting sway

i still get a black screen when launching vkcube

as the final straw, im installing stable mesa and llvm and retrying after they are finished compiling

[The Main Man]

I've decided to try it again but this time without wayland in make.conf
Just emerged sway and waybar and whatever use flags were needed to change for that to emerge
I have no crashes with mpv and everything works fine under xwayland it seems, including vulkan and vkcube , also l4d2 runs with -vulkan

Now, mesa had to be wayland in order for sway to work, so that's not the reason why mpv was crashing, could be vulkan or wayland use flag, or maybe it is mesa but with wayland combined
It's not that easy to test since the crash doesn't happen right away but depends, 5-15 mins maybe, not in the mood to bother with that now
I guess I'll put wayland in make.conf and then cut down wayland from mpv , then vulkan etc. until I figure it out

@shoober420, you didn't mention (I think, maybe I missed it) if you're running pure wayland or do you have X as well, or if you have X (on something else than Sway) did you try l4d2 there with -vulkan and if that worked
I'm on Xmonad and I can go back and forth with Sway and Xmonad if needeed
But this time I think I'll got it right with Sway and move permanently to it
Like I said, right now I run basically everything under XWayland, so I don't really know why are you having so much trouble with vulkan, trying to say that it should work for you just fine with -wayland
atm I have wayland enabled just in xorg-server, mesa and gtk+ , Sway needed those to be wayland, or wayland needed those, whatever

[The Main Man]

So I did update the system with wayland in make.conf
Crashes happened with Firefox as well, when watching videos.
Seems like the mesa was the problem, I was on stable mesa, when I emerged the latest version it didn't happen anymore.

Wayland likes the latest and greatest it seems

[Zucca]

Rolling with stable wayfire and firefox here. No problems. ;)

[The Main Man]

That's a different beast , I didn't try wayfire :O

But true story, mesa 21.0.3 -> crashes, mesa 21.1.3 -> no crashes, while watching videos after few minutes (I have in log actual errors)
I was happy with stable mesa until now.
I'm on stable gentoo, very few packages I have unmasked, firefox and some fonts (they demanded to be unstable), youtube-dl and mpv
Even Vulkan is stable, luckily I didn't had to unmask that one

[shoober420]

i cant seem to get vulkan back to a half working state like it was. amdgpu-pro messed up everything. i dont even know where to start now. i can provide as much information as needed, like logs or console output for system info. i just cant get it back to work. how can i attempt to diagnose this thing?

[shoober420]

i finally think i got a lead. so when i was downgrading to stable packages, emerge wanted to install two packages i didnt have. one was "wayland-scanner 32bit" and another and very important package, Xwayland. i wasnt sure how gentoos xorg structure worked, but i can see they did indeed split Xwayland like most other distros.

@kajzer
do you have both xorg-server and Xwayland installed or just Xwayland?

[The Main Man]

I don't have xwayland package installed at all, never had, when I said Xwayland I meant wayland USE flag for xorg-server enabled, that part is little different in gentoo than in other distros
Sorry for the confusion

[wwdev16]

shoober420,

Maybe these will be helpful:

Code: Select all

https://en.wikipedia.org/wiki/Direct_Rendering_Manager
https://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure
https://en.wikipedia.org/wiki/Mesa_(computer_graphics)
https://mesamatrix.net/

When you make changes in the kernel for drm, you need to at least rebuild
media-libs/mesa and x11-libs/libdrm for X api usage (even w/o xorg-server).
These packages use the VIDEO_CARDS variable. Note that they don't always support
the same cards, e.g. on arm64 I need to have vc4 and v3d for libdrm, while mesa
only uses vc4. You may also want to see what dmesg has to say:

Code: Select all

dmesg | egrep 'drm|kms|fb|gpu'

There seem to be many ways (e.g. opengl, gles, egl, vulkan) to access the accelerated
3d ops. So for your game you need to be sure you have the right api available. Using
lddtree (provided by app-misc/pax-utils) on the game binary may provide clues as to
what you need. mesamatrix.net will give you and idea if your driver supports the
apis you want.

[shoober420]

ive tried to create a sort of graphics layer rebuild string thing i can use after i make USE flag changes. i got this so far.

Code: Select all

emerge -av mesa libdrm glslang xf86-video-ati xf86-video-amdgpu vulkan-loader vulkan-headers vulkan-tools xorg-server wlroots sway

i checked all the .so libs using lddtree in the l4d2 directory, and i have all the required libs installed, especially the vulkan libs (do keep in mind l4d2 launches for me in opengl mode). i still get a blackscreen. what im going to do is try out the amdvlk open source vulkan drivers and see if i can get those to work.

i made the big mistake while building this system to benchmark only CSGO, and assume that this would mean my system is working. i should have also included a vulkan game before slapping all these 9999 packages into the environment. if worst comes to worst, i can just start over again, and use a vulkan game to benchmark instead of CSGO.

an interesting thing i should note, is on my arch/obarun install with the same hardware (i just swapped the nvme out and put gentoo on another nvme), i had all x11 programs running with only the new xwayland package, and didnt need to install the traditional xorg-server package. i only used the traditional xorg-server package on my nvidia/x11 machine, and xwayland/sway/wlroots on the arch/obarun machine. it appears that wlroots is force pulling xorg-server, even though the standalone xwayland package should suffice, since xwayland is only needed if youre using wayland. im going to tweak the wlroots ebuild so it force pulls xwayland instead and see if it still runs, at least the buggy same as traditional xorg-server package.

[shoober420]

so xorg-server gets pulled in by the xorg-3 eclass, and i literally, am just not even.

so xwayland is literally useless by itself, and isnt standalone whatsoever. i have no idea why its even a thing. im just going to revert all those changes and try to install amdvlk.

[The Main Man]

It is standalone, i Just switched to it yesterday, removed xorg-server and related files completely.

[shoober420]

it must be the xf86-video-ati/amdgpu 9999 packages forcing the install of xorg-server, since they are linked to the xorg-3.eclass. i'll have to try and tweak it again and try to get xwayland only.

[The Main Man]

Yeah but you don't need those drivers, they are not used in Wayland anyway
Kernel video drivers are used

[Anon-E-moose]

Any xf86* will likely pull in xorg server/driver

As kajzer said, wayland doesn't need or use the xorg stuff, it uses a combo of the hardware/kernel and mesa.

wlroots will be happy with xorg-server 1.20.11-r1 w/the wayland use flag, as the ebuild pulls in xwayland when it sees the wayland flag.

[shoober420]

i narrowed down what package was pulling xorg-server specifically, and its wlroots-9999. also, its a dependency for "0.13" and "0.14" version of wlroots. are you using "emerge -Cav" to force uninstall xorg-server and xorg-drivers since its required by wlroots?

i also managed to get xorg-server to install without xorg-drivers by using the -xorg flag. rebuilding with xorg-drivers, xf86-video-ati, and xf86-video-amdgpu uninstalled and -xorg globally set still produces a black screen for vulkan games.

[The Main Man]

You need to make custom ebuild for wlroots, and replace xorg-server with x11-base/xwayland
Check this thread, I went through all of that few days ago