You are not logged in.

#1 2024-09-16 11:19:29

mewt
Member
Registered: 2008-06-24
Posts: 36

Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

I upgraded from linux-6.10.10.arch1-1 and nvidia 560.35.03-6 to linux 6.11.arch1-1 and nvidia 560.35.03-7 which caused a number of strange graphical issues/

1) Hyprland - stuttering / jerky mouse movement, overall slow performance, graphical glitches in terminal (tested with htop). No logs in journalctl
2) waybar - showing incorrect workspace numbers (2/3 instead of 1/2). Trying to move to workspace 1 hid mouse
3) Kwin - stopped loading with black screen and mouse cursor only. journalctl logs as follows:

Sep 16 12:40:15 Minas-tirith kwin_wayland[2729]: kwin_scene_opengl: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Sep 16 12:40:15 Minas-tirith kwin_wayland[2729]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Sep 16 12:40:15 Minas-tirith kwin_wayland[2729]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Sep 16 12:40:15 Minas-tirith kernel: [drm] [nvidia-drm] [GPU ID 0x00002600] Framebuffer memory not appropriate for scanout
Sep 16 12:40:15 Minas-tirith kernel: [drm] [nvidia-drm] [GPU ID 0x00002600] Framebuffer memory not appropriate for scanout
Sep 16 12:40:15 Minas-tirith kwin_wayland[2729]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Sep 16 12:40:15 Minas-tirith kwin_wayland[2729]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Sep 16 12:40:15 Minas-tirith kwin_wayland[2729]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument

downgrading to the previous versions resolved all issues with plasma and hyprland (and waybar) all loading correctly and functioning as expected.

Offline

#2 2024-09-17 11:33:43

ziggybeans
Member
Registered: 2021-04-20
Posts: 3

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

Same here. Was running 6.10.10 with Nvidia 560.35.03 and everything was fine. Upgraded only my kernel to 6.11.0. Now hyprland consumes 100% CPU on all cores, screen is very laggy, waybar shows wrong workspace, and hyprctl is showing a new phantom monitor causing things to render off screen.

Reverting to Linux 6.10.10 resolves the issues.

Last edited by ziggybeans (2024-09-17 11:34:18)

Offline

#3 2024-09-17 16:36:48

snx9
Member
Registered: 2024-05-02
Posts: 6

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

Same here.  Have not tested much with cpu usage, but get the phantom monitor.

The phantom screen appears on gnome also. The reason seems to be that simpledrm is initialized so the system sees 2 gfx cards.
I can get simpledrm to not init and the phantomscreen goes away by adding this to the kernel options: initcall_blacklist=simpledrm_platform_driver_init

However there is no display until gdm launches and no boot logo and trying to switch to a VT gives a black screen.

I Tested with the cachyos 6.11 kernel from aur and there non of these issues appear afaik.

Offline

#4 2024-09-18 00:48:08

huyizheng
Member
Registered: 2018-05-15
Posts: 21

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

This is because kernel 6.11 changed some `fbdev` related header file name, so the compiled `nvidia_drm` module does not have `fbdev` parameter. So `simpledrm` cannot be automatically disabled.
Apply this PR, and rebuild the kernel module, can fix this issue:
https://github.com/NVIDIA/open-gpu-kern … s/pull/692

Offline

#5 2024-09-18 13:21:49

snx9
Member
Registered: 2024-05-02
Posts: 6

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

huyizheng wrote:

This is because kernel 6.11 changed some `fbdev` related header file name, so the compiled `nvidia_drm` module does not have `fbdev` parameter. So `simpledrm` cannot be automatically disabled.
Apply this PR, and rebuild the kernel module, can fix this issue:
https://github.com/NVIDIA/open-gpu-kern … s/pull/692

Cheers i just tested that PR and it fixed the issue with the phantom screen and simpledrm that was not disabled.

Offline

#6 2024-09-18 18:46:25

pbo
Member
Registered: 2021-09-20
Posts: 9

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

just to add the same thing with:
linux-zen 6.11.zen1-1
nvidia-dkms 560.35.03-2

using nvidia_drm.modeset=1 and nvidia_drm.fbdev=1 : simpledrm load anyway and got an error about fbdev unknown parameter, tty is at 1024x768 and can't start wayland.
using initcall_blacklist=simpledrm_platform_driver_init : simpledrm isnt loaded, tty is black with [drm] User-defined mode not supported: "1920x1080" , but if I enter login, password and launch Hyprland blindy it works.

Online

#7 2024-09-23 10:13:25

mewt
Member
Registered: 2008-06-24
Posts: 36

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

huyizheng wrote:

This is because kernel 6.11 changed some `fbdev` related header file name, so the compiled `nvidia_drm` module does not have `fbdev` parameter. So `simpledrm` cannot be automatically disabled.
Apply this PR, and rebuild the kernel module, can fix this issue:
https://github.com/NVIDIA/open-gpu-kern … s/pull/692

Do we know when this fix will be made available in testing ? Last refresh seems to still give the same version of nvidia package

Offline

#8 2024-09-28 13:33:59

snx9
Member
Registered: 2024-05-02
Posts: 6

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

Fix for this seems to be in the testing repos now: https://gitlab.archlinux.org/archlinux/ … equests/12

Seems to work nice here and the phantom screen is gone.

Offline

#9 2024-10-01 18:44:44

mewt
Member
Registered: 2008-06-24
Posts: 36

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

I upgraded to 560.35.03-9 and linux 6.11.1.arch1-1 and the issue persists for me, including the missing desktop 1

Offline

#10 2024-10-01 18:49:46

Dividebysandwich
Member
Registered: 2024-10-01
Posts: 3
Website

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

Same as mewt here. The reason why desktop1 is missing is that the hdmi output is always active, regardless of whether something is plugged in or not. Using hyprctl to disable hdmi works, but doesn't solve the stutter/glitches. downgrading nvidia and kernel fixes the issue.

Offline

#11 2024-10-01 19:10:18

zebulon
Member
Registered: 2008-10-20
Posts: 372

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

Unfortunately the problem just made its way to the [core] repo, with kernel 6.11.1 and nvidia-dkms 560.35.03-4 leading to broken Plasma Wayland.

Last edited by zebulon (2024-10-01 19:10:42)

Offline

#12 2024-10-01 19:13:51

mewt
Member
Registered: 2008-06-24
Posts: 36

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

Does someone have an account to the gitlab that can re-open the issue ? I don't have an account and registrations aren't open it seems.

Offline

#13 2024-10-04 16:57:33

piratebill
Member
From: Sol System
Registered: 2011-10-20
Posts: 136

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

Currently away from my arch box until tomorrow. Once I verify its borked (which from what I'm reading it should be once I update) I can log into gitlab and try to re-open it

Offline

#14 2024-10-06 19:19:48

piratebill
Member
From: Sol System
Registered: 2011-10-20
Posts: 136

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

Updated to 6.11, but no issues. Gaming in wayland was the same as it was before

Offline

#15 2024-10-08 13:42:31

jslay
Member
Registered: 2024-05-20
Posts: 6

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

I am having the black screen issue as well on 6.11 + wayland

Seems like NVIDIA is aware. https://forums.developer.nvidia.com/t/d … ove/307920

Last edited by jslay (2024-10-08 13:43:06)

Offline

#16 2024-10-14 16:17:55

rek2
Member
Registered: 2015-02-12
Posts: 39

Re: Upgrade to Kernel 6.11.arch1-1 and nvidia 560.35.03-7 regression

I am having similar problem when upgrading from 560.35.03-4 to whatever I even tried -10 from test etc I am using the propietary drivers because my card GTX1080ti is not supported under the open ones sad and in my case it gets stuck on boot right after systemd-udev or similar
then I have to each time boot from usb, run cryptsetup mount do changes and so on... I did it for each of them with no luck.... does anyone have a workaround to at least boot? I tried going into edit mode on boot and remove nvidia_drm.modeset=1 and also same issue sad

Last edited by rek2 (2024-10-14 16:27:56)

Offline

Board footer

Powered by FluxBB