[solved]vulkan games black screen, only sound

The Main Man · Posted: Wed Jun 30, 2021 12:02 pm Post subject:

Yeah but if he wants to remove xorg-server (and I think he does) then the custom ebuild for wlroots is needed.

shoober420 · Apprentice Joined: 22 May 2017 Posts: 223

Anon-E-moose · Posted: Wed Jun 30, 2021 7:14 pm Post subject:

shoober420 · Apprentice Joined: 22 May 2017 Posts: 223

Anon-E-moose · Posted: Wed Jun 30, 2021 7:49 pm Post subject:

shoober420 · Apprentice Joined: 22 May 2017 Posts: 223

wlroots wants xorg-server with the wayland use flag set, not the literal xwayland package, which gets pulled in naturally. it wants/needs both packages technically if you want X support (on stable)
_________________
https://www.github.com/shoober420
https://bandcamp.com/shoober420
https://steamcommunity.com/id/shoober420

The Main Man · Posted: Wed Jun 30, 2021 9:08 pm Post subject:

I told you in my previous post, you need custom ebuild for wlroots to change that.

But I'm afraid that all won't solve your problem, it's much deeper, you messed up some use flags most likely.
In make.conf have both X and wayland, and vulkan as well, check your package.use what you have set there, but I guess the problem is in mesa, what flags you have set for it ?
Here's mine

Ionen · Developer Joined: 06 Dec 2018 Posts: 2729

ebuilds migration will likely wait until both xwayland and -r1 are stable.

Using split xwayland is very new right now and still due for some changes (Edit: new version soon'ish too -- there's a release candidate that should allow nvidia acceleration, whereas xorg-server pretty much never do releases).

shoober420 · Apprentice Joined: 22 May 2017 Posts: 223

The Main Man · Posted: Wed Jun 30, 2021 9:31 pm Post subject:

Yeah I don't know what zink does, maybe try without that use flag

for vkcube you need >=181 of vulkan-tools, otherwise it doesn't work for me either, maybe you forgot info about that
I made a bug report about that few hours ago btw

shoober420 · Apprentice Joined: 22 May 2017 Posts: 223

zink has no effect on the blackscreen unfortunately

i meant official stable (which is 182 or 183 now?), not gentoo stable lolol, so i found something that i really think is it. libdrm wasnt compiled with libkms flag. and i think kms is needed for kernel video things, so im rebuilding my graphics layer and seeing if libkms fixes it

dang it didnt work. im really running out of ideas. if i install flatpak-proton-ge and it works, i guess that means its not my system settings then right? so maybe we could narrow it down if flatpak-proton-ge works?

could i also see your use flag set for libdrm?
_________________
https://www.github.com/shoober420
https://bandcamp.com/shoober420
https://steamcommunity.com/id/shoober420

The Main Man · Posted: Wed Jun 30, 2021 11:05 pm Post subject:

I don't think installing proton from flatpak would affect regular steam install, try installing flatpak steam first

I don't have kms

Ionen · Developer Joined: 06 Dec 2018 Posts: 2729

The Main Man · Posted: Thu Jul 01, 2021 12:01 am Post subject:

@shoober420,

try to run vkmark, it's a benchmark for Vulkan, does some tests, I just did it and it works, maybe it's just a steam problem for you, since you managed to run vkcube at some point
I had to install two deps for this , glm and assimp
https://github.com/vkmark/vkmark

So, steps to build and run this would be :
git clone https://github.com/vkmark/vkmark
cd vkmark
meson build
ninja -C build
sudo ninja -C build install

then just run vkmark

The Main Man · Posted: Thu Jul 01, 2021 12:47 am Post subject:

shoober420 · Apprentice Joined: 22 May 2017 Posts: 223

ok...so i dont even...but its working lolol. ITS WORKING!!!!!!!!!!!!! w00t!!

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

so i first tried installing the amdvlk from the guru overlay (https://data.gpo.zugaina.org/guru/media-libs/amdvlk/), which wouldn’t compile, even with default build flags

i then tried to do the amdgpu-pro drivers again, messing specifically with "VK_ICD_FILENAMES" launch option for both steam and l4d2, as instructed on the gentoo wiki (https://wiki.gentoo.org/wiki/AMDGPU-PRO#Use_AMDGPU-PRO_Vulkan_drivers_for_specific_games), but would have an immediate crash when launching l4d2

everything didnt work lolol. so then, i just reverted everything again like i usually do, removing "VK_ICD_FILENAMES" from l4d2 launch options and my steam script, and launched l4d2 again because yeah, and it worked.

i literally....i dont even

whatever

you know clark griswald from christmas vacation when he was trying to get his christmas lights to turn on and figure out why they wouldn’t work? that was literally me except the l4d2 mr valve guy intro screen.
_________________
https://www.github.com/shoober420
https://bandcamp.com/shoober420
https://steamcommunity.com/id/shoober420

shoober420 · Apprentice Joined: 22 May 2017 Posts: 223

so i actually really really figured out what it was. enabling the "-flto=auto" flag on the mesa package will break vulkan games, and make them black screen. what a wacky thing, i made a bug report on the mesa gitlab about it.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/5017
_________________
https://www.github.com/shoober420
https://bandcamp.com/shoober420
https://steamcommunity.com/id/shoober420

Ralphred · Guru Joined: 31 Dec 2013 Posts: 506

Anon-E-moose · Posted: Fri Jul 02, 2021 3:08 pm Post subject:

Hu · Administrator Joined: 06 Mar 2007 Posts: 21770

Maybe. They might also take the position that -flto=auto is a valid build configuration and try to track down what part of Mesa is miscompiled when this is set. We don't know yet whether this is a gcc bug (producing incorrect assembly from a correct C program) or a Mesa bug (invalid C that happens to produce the good result without -flto=auto, and the bad result with it). Without a more minimal test case, I wouldn't rate it as a worthwhile use of my time if I were the developer, but maybe shoober420 will get lucky and a Mesa developer will be bored enough, or determined enough, to hunt this down.

shoober420: could you isolate an easier test for the Mesa developers? Ideally, you could find or make a trivial Vulkan program that just displays a spinning object (like glxgears does for OpenGL) and reproduces the problem.

shoober420 · Apprentice Joined: 22 May 2017 Posts: 223

Ironically, i made a similar issue on the xorg gitlab about a build option breaking functionality.

https://gitlab.freedesktop.org/xorg/xserver/-/issues/1181

I bisected and provided as much as a i could at the time, but ran into this issue which stalled me from debugging that any further. Unfortunately, that particular use case and my wacky environment make it hard to reproduce the bug for the dev, so i’m going to get legit .core files for him soon now.

Considering it’s reproducible in any vulkan instance, like vkcube, l4d2, and proton+dxvk, i’m sure the mesa devs can reproduce this one easy, unless the issue stems way deeper like the xorg bug i just posted.

Also considering that LTO is being enabled by default on certain distros, like ubuntu, is another reason they would consider.
_________________
https://www.github.com/shoober420
https://bandcamp.com/shoober420
https://steamcommunity.com/id/shoober420