https://bugzilla.suse.com/show_bug.cgi?id=1231067 https://bugzilla.suse.com/show_bug.cgi?id=1231067#c10 --- Comment #10 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to pallas wept from comment #9)

...

I don't want to test it. I want to fix it. ;-)

But how will be know if it is fixed? We can only see this behaviour, because of the broken driver.

Once we no longer get bug reports about this we can consider people have updated the driver to 550.120 and the driver works.

...

Hmm. Who know. 560.35.03 may suffer from the same issue.

All of the 550 and 560 drivers seem to suffer the same issue.

No, NVIDIA claims 550.120 has fixed that issue. "[...] Our production branch driver 550.120 contains the fix for nvidia-drm to work properly with Linux kernel 6.11, and a future new feature branch release will also contain this fix."

...

So removing fbdev=1 option didn't help?

Sorry for my delay, I wanted to test it, but had to wait until I could risk failure...

560 open driver (cuda repo) Unmodified boots into plasma with bad distortion, corrupted settings, partly unresponsive, totally broken

This is with nvidia_drm.fbdev=1 still enabled and kernel 6.11.

With nvidia_drm.fbdev=1 in the kernel command line (and conf), boots into plasma, without corruption, but with 100% CPU usage and unusably slow

I guess you're now implicitely using nvidia-drm modeset=0 nvidia_drm.fbdev=1 which would be fatal for Wayland. It needs modeset=1. (modeset=0 is the default)

With fbdev=1 removed from conf and dracut -f, boots into plasma, seems normal

Which is options nvidia-drm modeset=1 and makes sense to me.

550 closed driver (nvidia repo) Unmodified is just like 560 With nvidia_drm.fbdev=1 in the kernel command line (and conf), boots into plasma, seems normal

This sounds unexpected. Mabye you didn't run 'dracut -f' after changinge the config?

With fbdev=1 removed from conf and dracut -f, boots into plasma, seems normal

Makes sense.

...

Well, maybe not everybody already switched to Kernel 6.11?

That's a scary thought. I hope nvidia update the driver before all those users have this failure. Thank you for chasing that for us.

I expect all users using 6.11 already see this failure. -- You are receiving this mail because: You are on the CC list for the bug.