6.13-rc1 graphics fail
Attachments:
As reported on mailing list(s)
6.12.1 on same system with same userspace works fine (as did 6.12) while 6.13-rc1 boots, but without working graphics using gnome with wayland.
Laptop is raptor lake with Intel XE (lspci attached). No kernel errors are logged, but GDM fails, leading to frozen screen with some messages logged most notable seems to be quite a few of this one:
Failed to ensure KMS FB ID on /dev/dri/card1 drmModeAddFB2WithModifiers failed: Invalid argument
which does not happen with 6.12.
I can switch to different VTs but GDM appears hung.
This is my primary machine so will take some time before I can bisect but thought it best to share sooner than later. Maybe this rings a bell to someone? Or does userspace GDM need to be changed to work with 6.13?
regards
gene
Larger journal attached along with lspci and kernel config. Some possibly relevant additional log bits:
-- journal --
gnome-shell[1380]: Thread 'KMS thread' will be using high priority scheduling
gnome-shell[1380]: Device '/dev/dri/card1' prefers shadow buffer
gnome-shell[1380]: Added device '/dev/dri/card1' (i915) using atomic mode setting.
gnome-shell[1380]: Created gbm renderer for '/dev/dri/card1'
gnome-shell[1380]: GPU /dev/dri/card1 selected primary from builtin panel presence
gnome-shell[1380]: Obtained a high priority EGL context
gnome-shell[1380]: Running GNOME Shell (using mutter 47.2) as a Wayland display server
/usr/lib/gdm-wayland-session[1367]: dbus-daemon[1367]: [session uid=120 pid=1367] Activating service name='org.freedesktop.impl.portal.desktop.gnome' requested by ':1.39' (uid=120 pid=1777 comm="/usr>
gnome-shell[1380]: Failed to ensure KMS FB ID on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument
meta_frame_native_release: assertion '!frame_native->kms_update' failed-- journal --
--