Hi, Thanks for replying back
I uninstalled the 560 driver, I’m back on driver 555 so I can’t provide the logs now. I’m sorry for that.
I’m pretty sure though that the bug is not the same: Different error messages and different causes. The first one happened after running UE for some time. This one happens right after launching UE and seeing the first window, i.e there is no 3d rendering what so ever. I hope someone can replicate this bug and provide some logs.
1 Like
Tried -r1 and everything seems to work now.
I think power management may not yet be implemented for this GPU?
nvidia-smi -a | grep ‘Performance State’:
Performance State : P0
cat /proc/driver/nvidia/gpus/0000:05:00.0/power:
Runtime D3 status: Disabled by default
Video Memory: Active
GPU Hardware Support:
Video Memory Self Refresh: Not Supported
Video Memory Off: Supported
S0ix Power Management:
Platform Support: Not Supported
Status: Disabled
Okay, using Fedora Rawhide with the fixed build Proton Games are working fine, GNOME also is.
Pipewire screen capture works as well.
Direct Scanout is working again but there is a critical regression that can be triggered by having two directly scanned out windows on two monitors; This causes a complete freeze similar to [545.29.06-18.1]Flip event timeout error on startup, shutdown and sometimes suspend. Wayland unusable
lug 24 16:58:55 mattia-desktop kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 1
lug 24 16:58:52 mattia-desktop kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 1
lug 24 16:58:46 mattia-desktop kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to apply atomic modeset. Error code: -11
lug 24 16:58:46 mattia-desktop kernel: [drm:nv_drm_atomic_apply_modeset_config.isra.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to initialize semaphore for plane fence
I tested this in GNOME 47 Alpha but it’s very likely to also be reproducible in 46. Disabling Direct Scanout prevents this issue.
Reproducibility Steps:
- Have a Dual(+?) Monitor System with GNOME on Wayland
- Open a Terminal fullscreened on one monitor
- Open a Terminal fullscreened on another
- Notice the monitors freezing
If you can’t reproduce this you should check if Direct Scanout is being engaged by opening the Looking Glass with ALT+F2, then inputting lg, going into Flags and enabling OPAQUE_REGION.
If a surface is green, then Direct Scanout is NOT engaged; When a surface is fullscreened the green overlay should disappear, if it doesn’t then Direct Scanout isn’t working for other reasons.
EDIT: This issue can be trigger with and without fbdev or the GSP Firmware, I didn’t test the Open Source Kernel Modules yet.
EDIT2: Bug Report for Reference: nvidia-bug-report.log.gz (847.8 KB)
4 Likes
That’s a great tip, I’m on Arch linux with Kernel 6.10 and after updating to egl-wayland 1.1.14 the issues I was seeing have vanished. (official package is at 1.1.13, change “1.1.13” to “1.1.14” in the PKGBUILD)
With egl-wayland 1.1.13 the following issues showed up:
- Electron apps appear blank
- Screen capture appears blank
- Missing characters on firefox text
However, with the egl-wayland 1.1.14 update, the desktop seems to be functioning well.
2 Likes
I wonder if this is causing proton games to crash or not likely? At least on Arch
Game launched with proton experimental: mangohud %command% → black screen.
Game launched with proton experimental: LD_PRELOAD="" gamescope -w 2560 -h 1440 -r 240 --mangoapp %command% → works.
Game launched with wine 9.13 staging: mangohud → works. Even without gamescope.
KDE 6.1.3 Wayland session.
I checked eglinfo, clinfo and vainfo.Everything looks normal. Cuda stuff also working.
If the next version has multi-monitor VRR support it would make a lot of your customers very happy. 🙂
4 Likes
I’m using Arch, and I’d be willing to help test the driver. Where are the most up to date files kept?
Can you help me how to update egl-wayland to 1.1.14 on Arch? Official 560.28.03 installer has 1.1.13.
Compile myself or is there an easier/better version? Also, how do i know which version I have? eglinfo -B doesn’t show that particular version string. (I know I have 1.1.13 but I want to see some log output)
Running Garuda, zen kernel 6.10.0-zen1-2. 3060 Ti FE. KDE Plasma 6.1.3. Wayland.
555 was working perfectly for me after setting modeset=1 and fbdev=1, but 560 is just giving me a black screen in games. This is both with a native Linux game and with Proton games (The Linux game did manage to produce audio, but the Proton ones wouldn’t). I guess I’ll try seeing if removing one or both modprobe options helps.
Edit:
- Removing either modeset=1 or fbdev=1 makes it so I am unable to even log in to KDE (black screen with just the mouse cursor, same issue I had in 555 but did not have in 550).
- Adding NVreg_EnableGpuFirmware=0 had no effect
- However, KDE in X11 works fine, even with none of the options. And even games work.
Edit 2:
Noticed an oddity. If I add nvidia_drm.modeset=1 to GRUB_CMDLINE_LINUX, KDE + Wayland works, even without fbdev=1. But if I am setting it with /etc/modprobe.d/nvidia.conf I need to have both or KDE + Wayland doesn’t work. (Games still don’t work when setting the options via grub)
Would be great if 560 would use the newer egl-wayland 1.1.14!
i tried 560 again + compiled egl-wayland 1.1.14 version. no problems in x11 anymore (weird that the install kinda failed before)
wayland also runs. still getting the freeze in KDE though (487728 – With NVIDIA GPU, Plasma panel/widgets freeze randomly with explicit sync, can be unfrozen by going into overview)
Zamundaaa said:
I looked into this, and it’s hanging in the NVidia driver, which waits for KWin to release a buffer that will only be released once the window is shown. This will need to be fixed in the driver
I installed 1.1.14 to /usr/local/lib and still have issues with proton, how can I be sure it’s loading this and not 1.1.13? Should I remove it from /usr/lib
Can confirm. Just tested in a couple wlroots based compositors as well and they worked. KWin is the only one giving me problems.
OS: Arch Linux - 6.10.0-arch1-2
Desktop: Hyprland Desktop Environment (same behavior was observed in GNOME)
GPU: 3080ti
Will attach a bug report when I have a moment to reinstall 560 and check again.
1 Like
Can confirm firefox v.128.02 hardware acceleration fails on 560 beta release, wayland, with all settings workable on previous 555 beta release
can confirm gamescope still works to launch games, but vrr does not seem to work atleast not with gamescope
Please use sudo nvidia-bug-report.sh to report issues and also report the distro and any other logs so we can get issues fixed and reported properly.
PlasmaShell freezes randomly. Using plasmashell --replace shows a libEGL error.
libEGL warning: egl: failed to create dri2 screen
Reading the thread seems it’s something related to egl-wayland. Using the 1.1.14 version fixed it, however Proton is still unable to run some games directly.
1 Like
Filed a bug to track this NV Bug #4769138. I can reproduce the crash at launch on Wayland with Unreal Engine Editor 5.3.0. I did not see the same crash on X11. Please share the crash logs when possible to confirm. Thank you
2 Likes
Thank you for reporting this issue. I have filed a bug to track this at NVBug #4769163. I haven’t managed to reproduce this issue. I will repeat the testing and reach out to you for additional information.
3 Likes