NVidia, could you build 560 rpm versions for opensuse and namely Tumbleweed as alternative? Version of driver is very stable as for me and prevents many people from using it, since no rpms being built, while only this driver normally works with Wayland. Counting recent KDE 6.2 release stability and speed in insane now and flawless.
Thanks in advance.
@amrits
I noticed when the card is in performance state P8, the wayland session can be a bit laggy when scrolling/moving windows and switching desktops. If you start to switch desktops a few times or move things around, it becomes smoother since the P-state increases.
So it needs optimizing.
RTX 4070, KDE 6.1 and 6.2 tested. From what Iāve seen I donāt think kernel module really matters, Iām using the proprietary module (GSP off).
CPU is set to max clock speed, so it isnāt due to different CPU clock speeds.
560.35.03 has been very useful on Arch (Garuda) for some time, well improved performance and usability on Wayland. However it seems that a recent change has caused the driver to crash an provide the āGPU has fallen off the bus messageā. At this point the system is no longer recoverable so it has been difficult to get a capture of the issue. It seems that this coincided with a recent plasma update (Installation of KDE Application Platform 6.7/ 5.15-23.08 seemed to be a trigger in my case). The only fix at the moment is downgrading the Nvidia driver and re-installing the current version until the crash/ corruption happens again.
Looking forward to the next release! Thanks for the good work.
iāam here worried about the DX12 performance on the nvidia side of things , itās unacceptable to have minus 30-50% comparing to dx11 and windows to linux .
Actually I realized I am confusing 2 problems. The problem I refered to is when using s2idle. Not sure the cause.
With the open driver the system goes to sleep(s3) once, but then fails going into sleep mode. Yeah and also ssh-ing in. It is just non-responisve. Only thing that can be done then is power cycle.
Hi folks. I just installed Ubuntu 24.10. The NVIDIA driver 560.35.03 was automatically installed. My NVIDIA card is not working on Wayland and it is working on X11. But when I try to use X11, some apps delay a lot to open, sometimes never open, and open with light theme (since I configured for dark theme). I am using a Lenovo Thinkpad T480 with integrated GPU IntelĀ® UHD Graphics 620 and dedicated GPU NVIDIA GeForce MX150. I am looking for some solution to activate my NVIDIA on Wayland. Tips are welcome.
@shabapiffer I recently experienced a similar problem with 24.04 after the latest GNOME Shell and related updates. This had never happened before. I am also using the 560.35.03 driver. In my case, the problem occurred while/after using a Wayland session, which generally works for me. However, after waking up from suspend, several elements (like window controls/buttons) were not rendered properly, or not rendered at all (This is a common, known issue).
After encountering this issue again, I decided to log out and switch to the Xorg session (which I normally use). However, I then experienced the same issues youāve described: the dark theme didnāt work, and applications like Nautilus and system settings took a long time to open.
What fixed it for me was opening the Tweaks application, selecting the options menu (three lines in the top left corner), and then choosing āReset to Default.ā I had to re-apply my wallpaper and reselect the dark theme, but after that, everything seems to work normally again.
EDIT:
Regarding your issue with Wayland, this is just a guess, but laptops work differently, and the integrated GPU is the primary one, and display is connected to it, what sometimes complicates things. Try 'sudo prime-select nvidia
ā (Install nvidia-prime if itās missing) and see if that helps with Wayland.
Thank you @sorn.denis for you reply. I tried āReset to Defaultā on Tweaks and it didnāt resolve the problem. I also tried āprime-select nvidiaā and nothing changed. On Wayland the NVIDIA card is not activating and on Xorg I am having problems in opening and using the apps. Some curious facts I am able to run DaVinci Resolve on Wayland and the app detects my NVIDIA card. The Kdenlive detects but doesnāt use the NVIDIA card on Wayland and Xorg. The option āIntel (Power Saving Mode)ā is not selectable on NVIDIA Settings. I wrote a full report to linux-bugs@nvidia.com with the nvidia-bug-report.log.gz file attached. While I didnāt receive a answer, I continue looking some solution. Thank you again.
Anyone experiencing crashes 6-10 seconds after log in? Using 560.35 drivers on RTX 2070 on latest TUXEDO OS (22.04), KDE Plasma 6 on Wayland
It seems that the signal from GPU turns off completely. This happens only sometime. Nothing in dmesg or syslog
Any newer versions to come any time soon, nvidia? (especially push of 560 driver series to stable)
Iād say let them fix the bugs then release the driver. Instead of rushing out the driver like i feel they did last time.
Just upgraded to Ubuntu 24.10 which updated my drivers from 550 to 560, and ended up in a very sluggish system. Same issue as above, but also nvidia-smi just outright ends up in a memory leak almost immediately gobbling up heaps of memory before the kernel kills it.
[Mon Oct 14 15:37:38 2024] Out of memory: Killed process 16814 (nvidia-smi) total-vm:54547592kB, anon-rss:26035688kB, file-rss:2256kB, shmem-rss:0kB, UID:1000 pgtables:53388kB oom_score_adj:100
[Mon Oct 14 15:41:44 2024] nvidia-smi invoked oom-killer: gfp_mask=0x440dc0(GFP_KERNEL_ACCOUNT|__GFP_COMP|__GFP_ZERO), order=0, oom_score_adj=200
[Mon Oct 14 15:41:44 2024] CPU: 14 UID: 1000 PID: 18876 Comm: nvidia-smi Tainted: P O 6.11.0-8-generic #8-Ubuntu
[Mon Oct 14 15:41:44 2024] Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
[Mon Oct 14 15:41:44 2024] Hardware name: LENOVO 82JU/LNVNB161216, BIOS GKCN60WW 03/07/2023
[Mon Oct 14 15:41:44 2024] Call Trace:
[Mon Oct 14 15:41:44 2024] <TASK>
[Mon Oct 14 15:41:44 2024] show_stack+0x49/0x60
[Mon Oct 14 15:41:44 2024] dump_stack_lvl+0x5f/0x90
[Mon Oct 14 15:41:44 2024] dump_stack+0x10/0x18
[Mon Oct 14 15:41:44 2024] dump_header+0x46/0x1a6
[Mon Oct 14 15:41:44 2024] oom_kill_process.cold+0xb/0xaf
[Mon Oct 14 15:41:44 2024] ? srso_alias_return_thunk+0x5/0xfbef5
[Mon Oct 14 15:41:44 2024] out_of_memory+0x100/0x2b0
[Mon Oct 14 15:41:44 2024] __alloc_pages_may_oom+0x10b/0x1d0
[Mon Oct 14 15:41:44 2024] __alloc_pages_slowpath.constprop.0+0x41c/0xa10
[Mon Oct 14 15:41:44 2024] __alloc_pages_noprof+0x336/0x360
[Mon Oct 14 15:41:44 2024] alloc_pages_mpol_noprof+0xd5/0x1e0
[Mon Oct 14 15:41:44 2024] ? __mod_memcg_lruvec_state+0xf4/0x220
[Mon Oct 14 15:41:44 2024] alloc_pages_noprof+0x5c/0xd0
[Mon Oct 14 15:41:44 2024] ? srso_alias_return_thunk+0x5/0xfbef5
[Mon Oct 14 15:41:44 2024] pte_alloc_one+0x1d/0x60
[Mon Oct 14 15:41:44 2024] __pte_alloc+0x28/0xb0
[Mon Oct 14 15:41:44 2024] ? set_ptes.isra.0+0x48/0xb0
[Mon Oct 14 15:41:44 2024] do_anonymous_page+0x2ea/0x400
[Mon Oct 14 15:41:44 2024] handle_pte_fault+0x1ad/0x1c0
[Mon Oct 14 15:41:44 2024] __handle_mm_fault+0x3d5/0x7a0
[Mon Oct 14 15:41:44 2024] handle_mm_fault+0xef/0x2d0
[Mon Oct 14 15:41:44 2024] do_user_addr_fault+0x2ff/0x7e0
[Mon Oct 14 15:41:44 2024] exc_page_fault+0x85/0x1c0
[Mon Oct 14 15:41:44 2024] asm_exc_page_fault+0x27/0x30
[Mon Oct 14 15:41:44 2024] RIP: 0033:0x7231948a02ab
[Mon Oct 14 15:41:44 2024] Code: e5 e8 99 5a ff ff 66 0f 1f 84 00 00 00 00 00 31 c0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 66 0f ef c0 0f 11 07 <0f> 11 47 10 0f 11 47 20 48 85 f6 74 1e 8b 06 ba 02 00 00 00 a8 01
[Mon Oct 14 15:41:44 2024] RSP: 002b:00007ffe0ea3fea8 EFLAGS: 00010206
[Mon Oct 14 15:41:44 2024] RAX: 00007230167ffff0 RBX: 00007ffe0ea40160 RCX: 0000722493400010
[Mon Oct 14 15:41:44 2024] RDX: 000000003d66aaaa RSI: 0000000000000000 RDI: 00007230167ffff0
[Mon Oct 14 15:41:44 2024] RBP: 00007ffe0ea40130 R08: 00000000ffffffff R09: 0000000000000000
[Mon Oct 14 15:41:44 2024] R10: 0000000000000022 R11: 0000000000000246 R12: 00007ffe0ea4022c
[Mon Oct 14 15:41:44 2024] R13: 0000000000000001 R14: 00007ffe0ea40162 R15: 0000000000000009
[Mon Oct 14 15:41:44 2024] </TASK>
[Mon Oct 14 15:41:44 2024] Mem-Info:
[Mon Oct 14 15:41:44 2024] active_anon:3375720 inactive_anon:3259462 isolated_anon:0
active_file:31938 inactive_file:51843 isolated_file:0
unevictable:7109 dirty:81 writeback:0
slab_reclaimable:28357 slab_unreclaimable:78488
mapped:65495 shmem:4634 pagetables:41888
sec_pagetables:1320 bounce:0
kernel_misc_reclaimable:0
free:17266 free_pcp:1565 free_cma:0
Can you use refresh rates above 60hz with on 560 ?
Iām on a tuxedo stellaris ( laptop ) with a RTX 4080 .
Everything works as intended on 555.58 but the moment I update to 560 my programs keep crashing.
If I start a game it freezes after a few seconds and I cannot open any gpu accelerated thing anymore.
Okt 14 12:38:43 crashtux kernel: NVRM: GPU at PCI:0000:01:00: GPU-f6cd1b06-0e50-622e-08d9-5b44281bcb65
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 62, pid='<unknown>', name=<unknown>, 2028bf5e 2028b2a4 2029e768 2029e0a4 2029de6c 2029d960 00000000 00000000
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid='<unknown>', name=<unknown>, Ch 0000001e
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid='<unknown>', name=<unknown>, Ch 00000022
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid='<unknown>', name=<unknown>, Ch 00000023
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid='<unknown>', name=<unknown>, Ch 00000025
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid='<unknown>', name=<unknown>, Ch 00000028
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid='<unknown>', name=<unknown>, Ch 0000002c
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid='<unknown>', name=<unknown>, Ch 0000002d
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid='<unknown>', name=<unknown>, Ch 0000002e
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 0000002f
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000030
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000031
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000032
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000033
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000034
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000035
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000036
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000037
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000038
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000039
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 0000003a
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 0000003b
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 0000003c
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 0000003d
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 0000003e
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 0000003f
Okt 14 12:38:43 crashtux kernel: NVRM: Xid (PCI:0000:01:00): 45, pid=6664, name=Ghostrunner2-Wi, Ch 00000040
Okt 14 12:38:45 crashtux /usr/bin/nvidia-powerd[2228]: Failed to get topology status 55
Okt 14 12:38:47 crashtux /usr/bin/nvidia-powerd[2228]: Failed to get topology status 55
Okt 14 12:38:49 crashtux /usr/bin/nvidia-powerd[2228]: Failed to get topology status 55
Okt 14 12:38:51 crashtux /usr/bin/nvidia-powerd[2228]: Failed to get topology status 55
Okt 14 12:38:53 crashtux /usr/bin/nvidia-powerd[2228]: Failed to get topology status 55
Okt 14 12:38:55 crashtux /usr/bin/nvidia-powerd[2228]: Failed to get topology status 55
Okt 14 12:38:55 crashtux systemd[1]: systemd-timedated.service: Deactivated successfully.
Okt 14 12:38:55 crashtux audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Okt 14 12:38:55 crashtux audit: BPF prog-id=71 op=UNLOAD
Okt 14 12:38:55 crashtux audit: BPF prog-id=70 op=UNLOAD
Okt 14 12:38:55 crashtux audit: BPF prog-id=69 op=UNLOAD
Okt 14 12:38:57 crashtux /usr/bin/nvidia-powerd[2228]: Failed to get topology status 55
Okt 14 12:38:59 crashtux /usr/bin/nvidia-powerd[2228]: Failed to get topology status 55
Okt 14 12:39:00 crashtux kernel: NVRM: rpcRmApiAlloc_GSP: GspRmAlloc failed: hClient=0xc1d002ba; hParent=0xbeef00f0; hObject=0xbeef0100; hClass=0x0000c56f; paramsSize=0x00000168; paramsStatus=0x00000062; status=0x00000062
Okt 14 12:39:00 crashtux kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Reset required [NV_ERR_RESET_REQUIRED] (0x00000062) returned from status @ kernel_channel.c:2834
Okt 14 12:39:00 crashtux kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Reset required [NV_ERR_RESET_REQUIRED] (0x00000062) returned from _kchannelSendChannelAllocRpc(pKernelChannel, pChannelGpfifoParams, pKernelChannelGroup, bFullSriov) @ kernel_channel.c:916
Okt 14 12:39:00 crashtux kernel: NVRM: rpcRmApiAlloc_GSP: GspRmAlloc failed: hClient=0xc1d002ba; hParent=0xbeef00f0; hObject=0xbeef0100; hClass=0x0000c56f; paramsSize=0x00000168; paramsStatus=0x00000062; status=0x00000062
Okt 14 12:39:00 crashtux kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Reset required [NV_ERR_RESET_REQUIRED] (0x00000062) returned from status @ kernel_channel.c:2834
Okt 14 12:39:00 crashtux kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Reset required [NV_ERR_RESET_REQUIRED] (0x00000062) returned from _kchannelSendChannelAllocRpc(pKernelChannel, pChannelGpfifoParams, pKernelChannelGroup, bFullSriov) @ kernel_channel.c:916
Okt 14 12:39:00 crashtux kernel: [drm:nv_drm_semsurf_fence_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to lookup gem object for fence context: 0x00000000
happens on both open and closed kernel modules
All good, expect this: Using two NVIDIA GPUs monitor ok in the first gpu, one is always black on second gpu. ( but shows mouse cursor)
The editor for Unreal Engine 5 crashes after some time (seconds to minutes in my case), on Wayland, with driver 560. This issue has already been reported, and is being tracked on 4717891 for 555, but Iām not sure whether it has been mentioned that it also happens on 560, hence my post.
Things seem stable on X11.
Hereās a link to a post on the Unreal Engine forums about it:
Hereās the stack trace:
Caught signal 11 Segmentation fault
libnvidia-glcore.so.560.35.03!UnknownFunction(0xa10857)
libnvidia-glcore.so.560.35.03!UnknownFunction(0xe279e8)
libnvidia-glcore.so.560.35.03!UnknownFunction(0xe0d37f)
libnvidia-glcore.so.560.35.03!UnknownFunction(0xd4b78d)
libUnrealEditor-VulkanRHI.so!VulkanRHI::FFenceManager::WaitForFence(VulkanRHI::FFence*, unsigned long long) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanMemory.cpp:4690]
libUnrealEditor-VulkanRHI.so!FVulkanSwapChain::AcquireImageIndex(VulkanRHI::FSemaphore**) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanSwapChain.cpp:732]
libUnrealEditor-VulkanRHI.so!FVulkanViewport::Present(FVulkanCommandListContext*, FVulkanCmdBuffer*, FVulkanQueue*, FVulkanQueue*, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanViewport.cpp:916]
libUnrealEditor-VulkanRHI.so!FVulkanCommandListContext::RHIEndDrawingViewport(FRHIViewport*, bool, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanRHI.cpp:1184]
libUnrealEditor-RHI.so!FRHICommand<FRHICommandEndDrawingViewport, FRHICommandEndDrawingViewportString2188>::ExecuteAndDestruct(FRHICommandListBase&, FRHICommandListDebugContext&) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/RHI/Public/RHICommandList.h:1295]
libUnrealEditor-RHI.so!FRHICommandListBase::Execute(TRHIPipelineArray<IRHIComputeContext*>&, FRHICommandListBase::FPersistentState::FGPUStats*) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/RHI/Private/RHICommandList.cpp:477]
libUnrealEditor-RHI.so!UE::Core::Private::Function::TFunctionRefCaller<FRHICommandListImmediate::ExecuteAndReset(bool)::$_0, void ()>::Call(void*) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Public/Templates/Function.h:405]
libUnrealEditor-Core.so!TGraphTask<TFunctionGraphTaskImpl<void (), (ESubsequentsMode::Type)0> >::ExecuteTask(TArray<FBaseGraphTask*, TSizedDefaultAllocator<32> >&, ENamedThreads::Type, bool) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Public/Async/TaskGraphInterfaces.h:1235]
libUnrealEditor-Core.so!FNamedTaskThread::ProcessTasksNamedThread(int, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/Async/TaskGraph.cpp:760]
libUnrealEditor-Core.so!FNamedTaskThread::ProcessTasksUntilQuit(int) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/Async/TaskGraph.cpp:650]
libUnrealEditor-RenderCore.so!FRHIThread::Run() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/RenderCore/Private/RenderingThread.cpp:330]
libUnrealEditor-Core.so!FRunnableThreadPThread::Run() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/HAL/PThreadRunnableThread.cpp:25]
libUnrealEditor-Core.so!FRunnableThreadPThread::_ThreadProc(void*) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Private/HAL/PThreadRunnableThread.h:187]
libc.so.6!UnknownFunction(0x9e385)
libc.so.6!UnknownFunction(0x11fb0b)
My system:
Hi Nvidia I know youāre busy taking other peopleās content for use for your AI models but if you get the chance it would be nice if this was fixed.
Donāt know if it helps any, but sometimes this is shown: Failed in glXMakeCurrent.
Unreal Engine 5.4 crashes immediately after selecting āPlay in editorā when using Wayland. X11 works normally.
LoginId:9c24d628f5b84475875e383329604014-000003e8
Caught signal 11 Segmentation fault
libnvidia-glcore.so.560.35.03!UnknownFunction(0xa10857)
libnvidia-glcore.so.560.35.03!UnknownFunction(0xe279e8)
libnvidia-glcore.so.560.35.03!UnknownFunction(0xe0d37f)
libnvidia-glcore.so.560.35.03!UnknownFunction(0xd4b78d)
libUnrealEditor-VulkanRHI.so!VulkanRHI::FFenceManager::WaitForFence(VulkanRHI::FFence*, unsigned long long) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanMemory.cpp:4690]
libUnrealEditor-VulkanRHI.so!FVulkanCommandBufferManager::WaitForCmdBuffer(FVulkanCmdBuffer*, float) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanCommandBuffer.cpp:502]
libUnrealEditor-VulkanRHI.so!FVulkanViewport::WaitForFrameEventCompletion() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanViewport.cpp:278]
libUnrealEditor-VulkanRHI.so!FVulkanViewport::Present(FVulkanCommandListContext*, FVulkanCmdBuffer*, FVulkanQueue*, FVulkanQueue*, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanViewport.cpp:1048]
libUnrealEditor-VulkanRHI.so!FVulkanCommandListContext::RHIEndDrawingViewport(FRHIViewport*, bool, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanRHI.cpp:1184]
libUnrealEditor-RHI.so!FRHICommand<FRHICommandEndDrawingViewport, FRHICommandEndDrawingViewportString2188>::ExecuteAndDestruct(FRHICommandListBase&, FRHICommandListDebugContext&) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/RHI/Public/RHICommandList.h:1295]
libUnrealEditor-RHI.so!FRHICommandListBase::Execute(TRHIPipelineArray<IRHIComputeContext*>&, FRHICommandListBase::FPersistentState::FGPUStats*) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/RHI/Private/RHICommandList.cpp:477]
libUnrealEditor-RHI.so!UE::Core::Private::Function::TFunctionRefCaller<FRHICommandListImmediate::ExecuteAndReset(bool)::$_0, void ()>::Call(void*) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Public/Templates/Function.h:405]
libUnrealEditor-Core.so!TGraphTask<TFunctionGraphTaskImpl<void (), (ESubsequentsMode::Type)0> >::ExecuteTask(TArray<FBaseGraphTask*, TSizedDefaultAllocator<32> >&, ENamedThreads::Type, bool) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Public/Async/TaskGraphInterfaces.h:1235]
libUnrealEditor-Core.so!FNamedTaskThread::ProcessTasksNamedThread(int, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/Async/TaskGraph.cpp:760]
libUnrealEditor-Core.so!FNamedTaskThread::ProcessTasksUntilQuit(int) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/Async/TaskGraph.cpp:650]
libUnrealEditor-RenderCore.so!FRHIThread::Run() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/RenderCore/Private/RenderingThread.cpp:330]
libUnrealEditor-Core.so!FRunnableThreadPThread::Run() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/HAL/PThreadRunnableThread.cpp:25]
libUnrealEditor-Core.so!FRunnableThreadPThread::_ThreadProc(void*) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Private/HAL/PThreadRunnableThread.h:187]
libc.so.6!UnknownFunction(0x9439c)
libc.so.6!UnknownFunction(0x11949b)
running pretty much any wine game on an external monitor on a laptop with a nvidia dgpu makes it spam and fill the journal with
ā[12100.394561] [drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory not appropriate for scanoutā
just endlessly spams it. everything seemingly works tho.
driver 560.35.03, but has been doing it for many version back.
kwin 6.2.1
linux 6.11.3
Wellā¦ ok, but they could release at least something in between to let us test it too. Otherwise it will be released after many months and then people start reporting new bugs.
Similar issue here.