The Wreckfest tracking issue is here . ProtonDB entry
The short of it is my ASUS GA401QM runs Wreckfest at full speed. It didn’t always, an update or change or something I have no clue about seems to have made it run at full speed. SO on Ultra settings I get 60+ fps with 25 cars on screen.
My other two PC, including my desktop which should be smoking this game? 25-30 fps…
Reports: these are all fedora 35. Mix of kernel and nvidia driver versions because I’ve been trying various combinations trying to figure out what the cause of the absurd performance drop is.
nvidia-bug-report-dekstop-wayland.log.gz (323.1 KB)nvidia-bug-report-desktop-xorg.log.gz (412.2 KB)nvidia-bug-report-ga401qm-wayland.log.gz (748.2 KB)nvidia-bug-report-ga401qm-xorg.log.gz (522.8 KB)nvidia-bug-report-gx502gw.log.gz (284.9 KB)steam-desktop.log (77.3 KB)steam-ga401qm.log (78.0 KB)steam-gx502gw.log (79.8 KB)
I’d forgotten I did a manual install of the Nvidia drivers on the GA401QM after a fresh install. So these packages are missing from my install:
Installing:
akmod-nvidia x86_64 3:495.46-1.fc35 rpmfusion-nonfree-nvidia-driver 26 k
Installing dependencies:
akmods noarch 0.5.6-28.fc35 fedora 23 k
egl-wayland x86_64 1.1.9-3.fc35 updates 36 k
kmodtool noarch 1-43.fc35 fedora 13 k
libglvnd-egl i686 1:1.3.4-2.fc35 updates 38 k
libglvnd-gles i686 1:1.3.4-2.fc35 updates 30 k
libglvnd-opengl i686 1:1.3.4-2.fc35 updates 40 k
libwayland-server i686 1.19.0-2.fc35 fedora 41 k
mesa-libEGL i686 21.3.4-3.fc35 updates 129 k
mesa-libgbm i686 21.3.4-3.fc35 updates 45 k
nvidia-settings x86_64 3:495.46-1.fc35 rpmfusion-nonfree-nvidia-driver 1.6 M
xorg-x11-drv-nvidia x86_64 3:495.46-1.fc35 rpmfusion-nonfree-nvidia-driver 21 M
xorg-x11-drv-nvidia-kmodsrc x86_64 3:495.46-1.fc35 rpmfusion-nonfree-nvidia-driver 26 M
xorg-x11-drv-nvidia-libs i686 3:495.46-1.fc35 rpmfusion-nonfree-nvidia-driver 24 M
xorg-x11-drv-nvidia-libs x86_64 3:495.46-1.fc35 rpmfusion-nonfree-nvidia-driver 149 M
Of those egl-wayland is what stands out. I will try to replicate this install on my desktop PC.
egl-wayland update was a bug fix to stop apps crashing when using wayland session.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-0526645c86
https://bugzilla.redhat.com/show_bug.cgi?id=2018670
opened 10:08PM - 01 Jun 20 UTC
closed 09:24PM - 23 Nov 21 UTC
Hi!
I'm hitting a segfault while trying to open Evolution (Mail client) under… wayland. I've reported the segfault on the Fedora bugzilla [1] and since it looks like they can't track it down, we decided to report it here.
Here's the stack trace:
```
(gdb) bt full
#0 0x00007ffff3a9c625 in raise () at /lib64/libc.so.6
#1 0x00007ffff3a858d9 in abort () at /lib64/libc.so.6
#2 0x00007ffff3a857a9 in _nl_load_domain.cold () at /lib64/libc.so.6
#3 0x00007ffff3a94a66 in annobin_assert.c_end () at /lib64/libc.so.6
#4 0x00007fffe4109b7d in wlExternalApiLock () at ../src/wayland-thread.c:87
__PRETTY_FUNCTION__ = "wlExternalApiLock"
#5 0x00007fffe410e4ab in wlEglGetInternalHandleExport (dpy=0x5555566dad60, type=13233, handle=0x5555566dad60) at ../src/wayland-eglhandle.c:146
#6 0x00007fffd65574ef in () at /lib64/libEGL_nvidia.so.0
#7 0x00007fffd64deeeb in () at /lib64/libEGL_nvidia.so.0
#8 0x00007fffe410b752 in wl_eglstream_display_bind (data=data@entry=0x5555566cc5c0, wlDisplay=wlDisplay@entry=0x55555649b360, eglDisplay=eglDisplay@entry=0x5555566dad60)
at ../src/wayland-eglstream-server.c:311
wlStreamDpy = 0x555556b69f90
exts = 0x0
env = 0x0
#9 0x00007fffe410a355 in wlEglBindDisplaysHook (data=0x5555566cc5c0, dpy=0x5555566dad60, nativeDpy=0x55555649b360) at ../src/wayland-egldisplay.c:87
res = 0
#10 0x00007fffd65533f3 in () at /lib64/libEGL_nvidia.so.0
#11 0x00007fffd64db775 in () at /lib64/libEGL_nvidia.so.0
#12 0x00007ffff20f5b11 in WS::Instance::initialize(void*) () at /lib64/libWPEBackend-fdo-1.0.so.1
#13 0x00007ffff49c7bf6 in WebKit::WebProcessPool::platformInitializeWebProcess(WebKit::WebProcessProxy const&, WebKit::WebProcessCreationParameters&) (this=this@entry=0x7fffe42ee000, process=
..., parameters=...) at ../Source/WebKit/UIProcess/glib/WebProcessPoolGLib.cpp:119
#14 0x00007ffff489adfa in WebKit::WebProcessPool::initializeNewWebProcess(WebKit::WebProcessProxy&, WebKit::WebsiteDataStore*, WebKit::WebProcessProxy::IsPrewarmed)
(this=<optimized out>, process=..., websiteDataStore=0x7fffe42e4000, isPrewarmed=WebKit::WebProcessProxy::IsPrewarmed::No) at ../Source/WebKit/UIProcess/WebProcessPool.cpp:1044
initializationActivity = {m_ref = std::unique_ptr<WebKit::ProcessThrottler::Activity<(WebKit::ProcessThrottler::ActivityType)0>> = {get() = 0x0}}
parameters = <snip here>
```
If you need any information, i'll gladly help.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1842473
https://src.fedoraproject.org/rpms/egl-wayland/c/6b47b1f764429a22e8cf481f08d6df0d4ec80ccb?branch=f35
As your using Xorg I doubt it is causing your issue.
1 Like
generix
January 24, 2022, 10:45am
#4
The no-working systems are an intel-based hybrid graphics notebook with prime-sync enabled and a nvidia-only desktop. The working system is an amd-based hybrid graphics notebook.
Yes, it makes no difference here.
generix
January 26, 2022, 9:50am
#6
Did you try using gamemode, like one protondb user advised? This also removed performance issues for RDR2.
Yes. Also tried gamescope, including running that as its own session. No difference. Still 3 machines that started off with almost identical installs but give different results on the one game.
generix
January 28, 2022, 9:05am
#8
Did you check top and nvidia-smi while running the game to make sure it’s really using the nvidia gpu?
Sure did. Definitely using the GPU - verified on all 3 machines.
generix
January 28, 2022, 10:07am
#10
Same in-game settings and proton version set?
For sure. I mean all the basic stuff is what I checked. Drivers, kernel, proton, steam, distro updates, same manual nvidia install (and same rpmfusion install after). I don’t really know where to go from here.
Recently released Nvidia driver + 5.16.5 kernel hasn’t fixed this issue.
It’s looking like something is broken at the distro level? I’m not sure where to begin with this. I compared all the relevant installed libs I can think of, including the end results of Nvidia driver install - this all seems to be correct.