nvidia 4070ti + Wayland + Gnome can't boot

grrrl212 · 2025-02-14 10:59:37

hi,

I am trying to boot Gnome (recent version of gnome-shell 1:47.3-1) with Wayland.
I have linux-zen 6.13.1.zen1-1 kernel with headers. Nvidia open drivers 570.86.16-2 with DKMS.

In the recent attempt, I have emptied Modules in the "mkinitcpio.conf".
I've changed in the "/etc/default/grub":

GRUB_CMDLINE_LINUX="nvidia-drm.modeset=1 nvidia-drm.fbdev=1"

and rebuild configuration with grub-mkconfig.

I'm not sure if that was mandatory or not, but I've added to the "/etc/modprobe.d/nvidia.conf"

options nvidia-drm modeset=1
options nvidia-drm fbdev=1

This command shows that fbdev is available.
cat /sys/module/nvidia_drm/parameters/fbdev

__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json eglinfo -B

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

With missing EGL for Wayland, Journalctl showed this lines:

feb 14 09:35:34 Deimos gnome-shell[992]: Failed to create view for Iiyama North America 27" on DP-3: Failed to allocate onscreen framebuffer for /dev/dri/card0: An EGLConfig argument does not name a valid EGL frame buffer configuration.
feb 14 09:35:34 Deimos gnome-shell[992]: Failed to create view for Iiyama North America 23" on DP-2: Failed to allocate onscreen framebuffer for /dev/dri/card0: An EGLConfig argument does not name a valid EGL frame buffer configuration.
feb 14 09:35:34 Deimos gnome-shell[992]: Failed to create view for Sharp Corporation 40" on HDMI-1: Failed to allocate onscreen framebuffer for /dev/dri/card0: An EGLConfig argument does not name a valid EGL frame buffer configuration.

It's the same with both GDM and SDDM.
Other packages installed in the system "egl-gbm 1.1.2-1", "egl-wayland 4:1.1.17-1", "egl-x11 1.0.0-1", "wayland 1.23.1-1", "xorg-xwayland 24.1.4-1 (xorg)".

Earlier in the mkinitcpio.conf, in the Modules I had (nvidia nvidia_modeset nvidia_uvm nvidia_drm), but that does not make any difference.

Gnome + X11 works fine, but my goal is to run the system with multiple monitors and to have on one of them Freesync working correctly.
Nvidia drivers are few years behind from what in regard of what I want.
Even if latest Nvidia drivers 570.86.16 does have stated "Added support for VRR on systems with multiple displays.", Freesync only works if the only active monitor is my main one with Freesync.
Enabling other monitors disables Freesync. Monitor overlay can show me if such signal are sent correctly, since in the overlay refresh rate are fluctuating.

I was trying to figure out what am I missing, but I don't know.
I came to conclusion that I need "other pair of eyes", to look fresh on the issue.

seth · 2025-02-14 22:10:14

Have you tried to globally export _EGL_VENDOR_LIBRARY_FILENAMES ?

For GDM specifically see https://wiki.archlinux.org/title/GDM#Wa … DIA_driver

I came to conclusion that I need "other pair of eyes", to look fresh on the issue.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Probably also your Xorg log, https://wiki.archlinux.org/title/Xorg#General

Sidebar:

Gnome + X11 works fine, but my goal is to run the system with multiple monitors and to have on one of them Freesync working correctly.
Nvidia drivers are few years behind from what in regard of what I want.

And what relevance would the display server have?

grrrl212 · 2025-02-15 09:37:14

Result of: sudo journalctl -b | curl -F 'file=@-' 0x0.st

 http://0x0.st/8Npf.txt

Content from "Xorg.0.log":

 https://0x0.st/8NfZ.txt

I've tried adding these positions to the "/etc/environment" file:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json
VK_LOADER_DRIVERS_SELECT=*nvidia*
_EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json

There was no change.

I was checking that wiki page and I think that I've met all requirements.
Starting from nvidia-utils 560.35.03-5, DRM defaults to enabled.

Command "cat /proc/driver/nvidia/params | sort" shows me both variables to be the same as in wiki:

PreserveVideoMemoryAllocations: 1
TemporaryFilePath: "/var/tmp"

Necessary services nvidia-suspend.service, nvidia-hibernate.service, and nvidia-resume.service are enabled.

seth wrote:

And what relevance would the display server have?

It does matter. I can run KDE with Wayland.
With running VRRTest application and forcing 140fps - can see that the Freesync is working properly on the monitor OSD.
With Gnome and X11, I can't achieve such result.

I've found that there are someting weird in my opinion.
These two commands does have very different results.

__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json eglinfo -B

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
eglinfo: eglInitialize failed

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

eglinfo -B

GBM platform:
eglinfo: eglInitialize failed

Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.3.4-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.3.4-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.3.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.3.4-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.3.4-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.3.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Segmentation fault (core dumped)

grrrl212 · 2025-02-15 10:22:08

One more thing -> while running KDE+Wayland, every game that are running from Steam does have 15 fps at max. And it does not matter which Proton version I use.

seth · 2025-02-15 14:38:19

I was checking that wiki page and I think that I've met all requirements.
Starting from nvidia-utils 560.35.03-5, DRM defaults to enabled.

Generally besides the point, GDM has a tendency to high-handedly deny you wayland anyway.
Not currently the case, though - might however become an issue once eglinit doesn't fail.

lut 15 09:05:43 Deimos org.gnome.Shell.desktop[1050]: eglInitialize() failed
lut 15 09:05:43 Deimos org.gnome.Shell.desktop[1050]: EGL setup failed, disabling glamor
lut 15 09:05:43 Deimos org.gnome.Shell.desktop[1050]: Failed to initialize glamor, falling back to sw

1. this is on nvidia-open, what about nvidia?
2. was that already w/ exporting __EGL_VENDOR_LIBRARY_FILENAMES globally ?
3. what happens for "nvidia_drm.fbdev=0"?

VK_LOADER_DRIVERS_SELECT=*nvidia*

Remove that.

It does matter. I can run KDE with Wayland.
With running VRRTest application and forcing 140fps - can see that the Freesync is working properly on the monitor OSD.
With Gnome and X11, I can't achieve such result.

Since both are syncing compositors (gnome forcefully on either wayland or X11) I suppose the problem is rather "gnome" than "nvidia" then…?
I mean, what's the theory? The nvidia modules principally don't support VRR but some userspace implementation can change that?

grep -iEA5 'kwin|mutter|gnome' /usr/share/drirc.d/00-mesa-defaults.conf

At least mesa disables adaptive_sync for kwin_x11 and gnome, but apparently not kwin_wayland

One more thing -> while running KDE+Wayland, every game that are running from Steam does have 15 fps at max.

qdbus6 org.kde.KWin /KWin supportInformation
glxinfo -B

Steam will run on X11 (via xwayland) no matter what, but this sounds as if you're running on software emulation there as well?
Or did you forget to intall lib32-nvidia-utils for 32bit games?
How are the games performing on KDE or gnome on X11?

grrrl212 · 2025-02-15 16:41:36

Yes, I'm running on Nvidia-Open -> local/nvidia-open-dkms 570.86.16-2.

What you mean "exporting __EGL_VENDOR_LIBRARY_FILENAMES globally"??
Isn't that already set as global in the "/etc/environment" file??

grep -iEA5 'kwin|mutter|gnome' /usr/share/drirc.d/00-mesa-defaults.conf

        <application name="KWin Wayland" executable="kwin_wayland">
            <!-- This works around a cursor issue with glthread.
                 See: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7351#note_1581105 -->
            <option name="mesa_glthread_app_profile" value="0"/>
        </application>

--
        <application name="gnome-shell" executable="gnome-shell">
            <option name="adaptive_sync" value="false" />
            <option name="v3d_nonmsaa_texture_size_limit" value="true" />
        </application>
        <application name="Desktop — Plasma" executable="plasmashell">
            <option name="adaptive_sync" value="false" />
--
        <application name="kwin_x11" executable="kwin_x11">
            <option name="adaptive_sync" value="false" />
        </application>
        <application name="ksmserver-logout-greeter" executable="ksmserver-logout-greeter">
            <option name="adaptive_sync" value="false" />
        </application>
--
        <application name="mutter" executable="mutter">
            <option name="adaptive_sync" value="false" />
            <option name="v3d_nonmsaa_texture_size_limit" value="true" />
        </application>
        <application name="muffin" executable="muffin">
            <option name="adaptive_sync" value="false" />
--
        <application name="gnome-shell" executable="gnome-shell">
            <option name="glx_extension_override" value="-GLX_OML_sync_control -GLX_SGI_video_sync" />
        </application>
        <application name="cinnamon" executable="cinnamon">
            <option name="glx_extension_override" value="-GLX_OML_sync_control -GLX_SGI_video_sync" />
        </application>
--
        <application name="GNOME Shell" executable="gnome-session-check-accelerated-helper">
            <option name="r300_nohiz" value="true" />
            <option name="r300_nozmask" value="true" />
        </application>
        <application name="GNOME Shell" executable="gnome-shell">
            <option name="r300_nohiz" value="true" />
            <option name="r300_nozmask" value="true" />
        </application>
        <application name="KWin" executable="kwin_opengl_test">
            <option name="r300_nohiz" value="true" />
            <option name="r300_nozmask" value="true" />
        </application>
        <application name="KWin" executable="kwin">
            <option name="r300_nohiz" value="true" />
            <option name="r300_nozmask" value="true" />
        </application>
        <application name="Unigine Tropics" executable="Tropics">
            <option name="r300_ffmath" value="true" />

qdbus6 org.kde.KWin /KWin supportInformation

KWin Support Information:
The following information should be used when requesting support on e.g. https://discuss.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like https://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 6.2.5
Qt Version: 6.8.2
Qt compile version: 6.8.2
XCB compile version: 1.17.0

Operation Mode: Xwayland

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_GLX: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12401004
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.breeze
Theme: Breeze
Plugin recommends border size: None
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,400,0,0,0,0,0,0,0,0,0,0,1
smallSpacing: 2
largeSpacing: 10

Output backend
==============
Name: DRM
Atomic Mode Setting on GPU 0: true

Cursor
======
themeName: breeze_cursors
themeSize: 24

Options
=======
focusPolicy: ClickToFocus
xwaylandCrashPolicy: 1
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: true
placement: 5
activationDesktopPolicy: SwitchToOtherDesktop
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
edgeBarrier: 100
cornerBarrier: 1
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: MouseRaise
commandActiveTitlebar2: MouseNothing
commandActiveTitlebar3: MouseOperationsMenu
commandInactiveTitlebar1: MouseActivateAndRaise
commandInactiveTitlebar2: MouseNothing
commandInactiveTitlebar3: MouseOperationsMenu
commandWindow1: MouseActivateRaiseAndPassClick
commandWindow2: MouseActivateAndPassClick
commandWindow3: MouseActivateAndPassClick
commandWindowWheel: MouseNothing
commandAll1: MouseUnrestrictedMove
commandAll2: MouseToggleRaiseAndLower
commandAll3: MouseUnrestrictedResize
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: true
glStrictBindingFollowsDriver: true
glPreferBufferSwap: AutoSwapStrategy
glPlatformInterface: 2
windowsBlockCompositing: true
allowTearing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 75
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Number of Screens: 3

Screen 0:
---------
Name: HDMI-A-1
Enabled: 0
Screen 1:
---------
Name: DP-2
Enabled: 1
Geometry: 2560,0,1920x1080
Scale: 1
Refresh Rate: 60000
Adaptive Sync: incapable
Screen 2:
---------
Name: DP-3
Enabled: 1
Geometry: 0,0,2560x1440
Scale: 1
Refresh Rate: 165153
Adaptive Sync: automatic

Compositing
===========
Compositing is active
Compositing Type: QPainter

Loaded Effects:
---------------
outputlocator
zoom
screenedge
highlightwindow
kscreen

Currently Active Effects:
-------------------------

Effect Settings:
----------------
outputlocator:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
focusTrackingEnabled: false
textCaretTrackingEnabled: false
focusDelay: 350
moveFactor: 20
targetZoom: 1

screenedge:

highlightwindow:

kscreen:


Loaded Plugins:
---------------
BounceKeysPlugin
KeyNotificationPlugin
StickyKeysPlugin
buttonsrebind
eis
krunnerintegration
nightlight
screencast

Available Plugins:
------------------
BounceKeysPlugin
KeyNotificationPlugin
StickyKeysPlugin
buttonsrebind
eis
krunnerintegration
nightlight
screencast

glxinfo -B

name of display: :1
display: :1  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: llvmpipe (LLVM 19.1.7, 256 bits) (0xffffffff)
    Version: 24.3.4
    Accelerated: no
    Video memory: 31699MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 25 MB, largest block: 25 MB
    VBO free aux. memory - total: 27492 MB, largest block: 27492 MB
    Texture free memory - total: 25 MB, largest block: 25 MB
    Texture free aux. memory - total: 27492 MB, largest block: 27492 MB
    Renderbuffer free memory - total: 25 MB, largest block: 25 MB
    Renderbuffer free aux. memory - total: 27492 MB, largest block: 27492 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 4293234955 MB
    Total available memory: 4293266655 MB
    Currently available dedicated video memory: 25 MB
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 24.3.4-arch1.1
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 24.3.4-arch1.1
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.3.4-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

I've tested option "nvidia-drm.fbdev=0", but I only kept that in the Grub configuration as a parameter for kernel.
I've added comment symbols in "/etc/modprobe.d/nvidia.conf", so it's disabled there.
What you think - it does matter "nvidia-drm" or "nvidia_drm"?? That underscore??

Still I can't login into Gnome+Wayland.
In the Kde+Wayland, nothing changed - 15fps.
Then I've went to KDE+X11 - works as good as Gnome+X11 -> 105fps in tested game.
And it's kinda funny - because Freesync works literally the same in Gnome+X11 - only with one monitor running.

And yes - I guess it can be called emulation. Steam from Valve are using Proton, which is based on Wine application.
They are adding another logical layer called DXVK for DirectX 11 titles, and VKD3D for DirectX 12 titles.
These layers "translate" DirectX instructions into Vulkan API.
I don't use any other software, because I don't need it.

I will keep SDDM anyway.

I've checked - I do have "lib32-nvidia-utils" installed in my system.

About VRR and Nvidia drivers 570.86.16:

Added support for VRR on systems with multiple displays. 

source
https://www.nvidia.com/en-us/drivers/details/240524/

Last edited by grrrl212 (2025-02-15 16:42:46)

seth · 2025-02-16 10:29:56

1. the question was whether the global environment was already applied at the time of that gdm failure, however you should add it via /etc/profile.d in case GDM is too early for pam here.
2. glxinfo shows that kwin/wayland (assuming the output is from there) is running in software emulation and the supportInformation look the same.
YOU ARE NOT RUNNING KDE/WAYLAND ON THE NVIDIA DRIVER!
3. nvidia_drm and nvidia-drm are equivalent, dash/underscore are treated as equivalents here, the kernel commandline parameter will take precedence over modprobe.conf and the latter can apply too late when the module is in the initramfs, but the config isn't. For testing prurposes, rely on the kernel parameter and "cat /proc/cmdline" is authorative on what's actually applied there
4. I know what the grep prints, it was for you as illustration of the status quo of mesa's client specific VRR configuration

Put the __EGL_VENDOR_LIBRARY_FILENAMES export iont /etc/profile.d, see whether that makes GDM happy - but I'd not expect any difference between X11 and wayland wrt. the VRR situation once you're actually running gnome/kde on wayland and the nvidia drivers.

grrrl212 · 2025-02-16 11:33:33

I've created appropriate script file under "/etc/profile.d", and I've cleaned "/etc/environment". GDM are starting, but available options are only X11 variants.

Later I was looking into filed "/etc/gdm/custom.conf", since there are "WaylandEnable=false" option.
Without comment mark, GDM does start just like I've said earlier - with only X11 options.
But when I have commented that line, when the system is booting after GRUB, when it tries to run GDM, it freezes completely. I can't switch to other TTY terminals.
I tried to skip login manager, by putting "3" in the kernel parameters, and after logging in the TTY and running "gnome-shell --wayland", it does freeze the same way.

After your comment I've double checked what does GLXINFO prints in my terminals. Both "Gnome+X11" and "KDE+wayland".
I must admit that I overlooked that and that's true - KDE is not using Nvidia proprietary drivers.

Maybe these Nvidia drivers does not 'like' Wayland, since 570.86.16 are in beta stage.

grrrl212 · 2025-02-16 13:42:14

I've updated these packages to versions from Aur/Git:

local/egl-wayland-git 1.1.17.r3.g26ba0e3-1
    EGLStream-based Wayland external platform (git version)
local/lib32-egl-wayland-git 1.1.17.r3.g26ba0e3-1
local/wayland-docs-git 1.23.0.r37.g1ab6b69-1
    A computer display server protocol (git version) (documentation)
local/wayland-git 1.23.0.r37.g1ab6b69-1
    A computer display server protocol (git version)
local/wayland-git-debug 1.23.0.r37.g1ab6b69-1
    Detached debugging symbols for wayland-git

There was change in libraries.
New file "/usr/share/glvnd/egl_vendor.d/10_nvidia_wayland.json":

{
    "file_format_version" : "1.0.0",
    "ICD" : {
        "library_path" : "libnvidia-egl-wayland.so.1"
    }
}

_EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia_wayland.json eglinfo -B

GBM platform:
eglinfo: eglInitialize failed

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.3.4-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.3.4-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.3.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 24.3.4-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 24.3.4-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 24.3.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen

But it's still pointing Mesa Project.

seth · 2025-02-16 15:30:42

GDM are starting, but available options are only X11 variants.

For GDM specifically see https://wiki.archlinux.org/title/GDM#Wa … DIA_driver
Mask that udev rule.

I've updated these packages to versions from Aur/Git:

Undo that! Previously eglinfo at least used the nvidia device on explicit request.

But when I have commented that line, when the system is booting after GRUB, when it tries to run GDM, it freezes completely. I can't switch to other TTY terminals.
I tried to skip login manager, by putting "3" in the kernel parameters, and after logging in the TTY and running "gnome-shell --wayland", it does freeze the same way.

Do you have the system journal for that boot or did you reboot w/ the power button?

https://archlinux.org/packages/extra/x86_64/nvidia/ - where is 570.86.16 "in beta stage"?

grrrl212 · 2025-02-16 20:06:31

I've reverted changes in "/etc/profile.d/" so the global __EGL_VENDOR_LIBRARY_FILENAMES points earlier json file.
And I've downgraded packages from this list.

Journal:

https://0x0.st/8N0d.txt

I've picked last 4 minutes from the journal.
GDM is not starting. I see only simple console pointer that is not blinking.
But I was able to switch to tty6 and generate log from journal.

Only thing that I've added is a symbolic link:

lrwxrwxrwx 1 root root 9 2024-01-23  /etc/udev/rules.d/61-gdm.rules -> /dev/null

It's that you've meant, about masking udev rule??

And yes - according to Nvidia website 570.86.16 are beta drivers.

https://www.nvidia.com/en-us/drivers/details/240524/

seth · 2025-02-16 21:42:33

Skip GDM, only boot the multi-user.target (2nd link below), make sure __EGL_VENDOR_LIBRARY_FILENAMES points at the correct file and "eglinfo | grep NVIDIA" confirms its use.
From there try to start gnome/wayland manually, https://wiki.archlinux.org/title/GNOME#Wayland_sessions
The suggestion there will lead to a degenerated session, https://bbs.archlinux.org/viewtopic.php … 9#p2220539
But that's besides the point as we're only trying to make it run on the nvidia chip for now.

according to Nvidia website 570.86.16 are beta drivers

'key, did you try using the 565xx drivers?
(YOU'll have to use the dkms package or downgrade the kernel to the exact version the nvidia driver package was built for)

grrrl212 · 2025-02-17 07:25:49

I've downgraded the Kernel to 6.12.8.
With drivers 565.77, after logging in from SDDM, monitor turns black, and it acts like there's no signal from PC - blue power dot from monitor turns orange and I see notification from OSD about no signal.

While logging by "multi-user.target", take a look here:

PC froze completely. Only power button was useful.

With drivers 565.57 these are result:

I was trying to run manually dbus - "dbus-launch", but there was no change.

Take a look on that image too:

I noticed one thing about services.
To be sure I was installing drivers back and forth.
Nvidia-utils package with version "565.77" adds these services for hibernation and suspend.
And that version started freezing PC. And it acts the same with "570" series drivers.

Is that possible that I have some issue with power management?

seth · 2025-02-17 08:52:12

Nvidia-utils package with version "565.77" adds these services for hibernation and suspend.

They do only apply when entering S2/3/4 states (ie. sleep the system)
Did the dkms modules actually build for the 565xx drivers?
I should probably have mentioned that, but you need to downgrade the kernel module, nvidia-utils and the threee egl-* packages it depends on (otherwise this will not work)

However, first and for 570xx and the not-GDM situation

With drivers 565.77, after logging in from SDDM, monitor turns black, and it acts like there's no signal from PC - blue power dot from monitor turns orange and I see notification from OSD about no signal.

Try to add "nvidia_drm.fbdev=0" to the kernel parameters and

PC froze completely. Only power button was useful.

Probably not: https://wiki.archlinux.org/title/Keyboa … el_(SysRq) - nb. you'll have to explicitly enable the feature first (if REISUB works you'll get a useful journal for the previous boot)

grrrl212 · 2025-02-17 10:08:18

Both Kernels are installed with appropriate headers to version 6.12.8.

I've installed these packages to version 565.77:
- nvidia-utils
- lib32-nvidia-utils
- opencl-nvidia
- lib32-opencl-nvidia
- nvidia-open-dkms
- nvidia-settings

To be able to catch details in journal.
I've passed command:

 echo "1" > /proc/sys/kernel/sysrq

after logging in the tty and trying to run Gnome-Session with Wayland:

 Alt+SysRq+e

Worked like a charm.
I was able to login again in tty, and I've picked last 4 min from Journal.
Results:

 https://0x0.st/8NhA.txt

I did the same with fbdev=0.
Results:

 https://0x0.st/8Nhm.txt

By the way, DKMS was building properly the modules in both cases - 565.57 and 565.77.

In the archive (archive.archlinux.org) there are only one package from pretty similar date to the packages I mentioned above.
It's EGL-Wayland with version 1.1.16.

These two remain the same - because it's only version available.

egl-x11-1.0.0-1-x86_64.pkg.tar.zst                 13-Dec-2024 07:06     37K
egl-x11-1.0.0-1-x86_64.pkg.tar.zst.sig             13-Dec-2024 07:06     119

egl-gbm-1.1.2-1-x86_64.pkg.tar.zst                 19-Sep-2024 07:35     12K
egl-gbm-1.1.2-1-x86_64.pkg.tar.zst.sig             19-Sep-2024 07:35     566

Last edited by grrrl212 (2025-02-17 10:30:05)

grrrl212 · 2025-02-19 12:50:22

Thank you for your help Seth.
But I decided to take experimental step -> I've formatted drive and installed EndeavourOS.

Good news is that the Wayland as a background for desktop, with Nvidia drivers works really well.
Variable refresh rate does work on my main monitor when all connected monitors are turned on.
But... I've found pretty quickly that the controller support is in really bad state.

X11 works literally the same just like before the format. VRR only works with one monitor turned on.

EndeavourOS is Arch Linux based - so I should be able to install the same things in clean Arch too.

I've created package list before doing format -> I don't know if such knowledge will help me or not.

grrrl212 · 2025-02-19 13:20:34

I will share some data for comparison.

Installed EGL packages:

local/egl-gbm 1.1.2-1
    The GBM EGL external platform library
local/egl-wayland 4:1.1.17-1
    EGLStream-based Wayland external platform
local/egl-x11 1.0.0-1
    NVIDIA XLib and XCB EGL Platform Library
    
local/egl-wayland 4:1.1.17-1
    EGLStream-based Wayland external platform
local/lib32-wayland 1.23.1-1
    A computer display server protocol
local/wayland 1.23.1-1
    A computer display server protocol
local/xorg-xwayland 24.1.5-1 (xorg)
    run X clients under wayland

Printenv:

SHELL=/bin/bash
SESSION_MANAGER=local/deimos:@/tmp/.ICE-unix/1405,unix/deimos:/tmp/.ICE-unix/1405
COLORTERM=truecolor
XDG_MENU_PREFIX=gnome-
TERM_PROGRAM_VERSION=47.1
LC_ADDRESS=pl_PL.UTF-8
LC_NAME=pl_PL.UTF-8
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
DESKTOP_SESSION=gnome
LC_MONETARY=pl_PL.UTF-8
EDITOR=nano
PWD=/home/batman
LOGNAME=batman
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_TYPE=wayland
SYSTEMD_EXEC_PID=4446
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.UC0J22
MOTD_SHOWN=pam
GDM_LANG=pl_PL.UTF-8
HOME=/home/batman
USERNAME=batman
LC_PAPER=pl_PL.UTF-8
LANG=pl_PL.UTF-8
XDG_CURRENT_DESKTOP=GNOME
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/app.slice/app-dbus\x2d:1.2\x2dorg.gnome.Console.slice/dbus-:1.2-org.gnome.Console@0.service/memory.pressure
VTE_VERSION=7803
WAYLAND_DISPLAY=wayland-0
INVOCATION_ID=a288a8bedf684215a4f886459db792b8
MANAGERPID=1330
GNOME_SETUP_DISPLAY=:1
XDG_SESSION_CLASS=user
TERM=xterm-256color
LC_IDENTIFICATION=pl_PL.UTF-8
USER=batman
DISPLAY=:0
SHLVL=1
LC_TELEPHONE=pl_PL.UTF-8
LC_MEASUREMENT=pl_PL.UTF-8
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
LC_TIME=pl_PL.UTF-8
JOURNAL_STREAM=9:54068
BROWSER=firefox
PATH=/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
GDMSESSION=gnome
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MAIL=/var/spool/mail/batman
LC_NUMERIC=pl_PL.UTF-8
TERM_PROGRAM=kgx
_=/usr/bin/printenv

__EGL_VENDOR_LIBRARY_FILENAMES is not set in this system.

eglinfo -B -> status from Gnome + Wayland

GBM platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 570.86.16
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

I've changed one thing - installed nvidia-open-dkms 570.86.16-2.
Works just fine with both kernels.

glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 12282 MB
    Total available memory: 12282 MB
    Currently available dedicated video memory: 10981 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 570.86.16
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Arch Linux

#1 2025-02-14 10:59:37

nvidia 4070ti + Wayland + Gnome can't boot

#2 2025-02-14 22:10:14

Re: nvidia 4070ti + Wayland + Gnome can't boot

#3 2025-02-15 09:37:14

Re: nvidia 4070ti + Wayland + Gnome can't boot

#4 2025-02-15 10:22:08

Re: nvidia 4070ti + Wayland + Gnome can't boot

#5 2025-02-15 14:38:19

Re: nvidia 4070ti + Wayland + Gnome can't boot

#6 2025-02-15 16:41:36

Re: nvidia 4070ti + Wayland + Gnome can't boot

#7 2025-02-16 10:29:56

Re: nvidia 4070ti + Wayland + Gnome can't boot

#8 2025-02-16 11:33:33

Re: nvidia 4070ti + Wayland + Gnome can't boot

#9 2025-02-16 13:42:14

Re: nvidia 4070ti + Wayland + Gnome can't boot

#10 2025-02-16 15:30:42

Re: nvidia 4070ti + Wayland + Gnome can't boot

#11 2025-02-16 20:06:31

Re: nvidia 4070ti + Wayland + Gnome can't boot

#12 2025-02-16 21:42:33

Re: nvidia 4070ti + Wayland + Gnome can't boot

#13 2025-02-17 07:25:49

Re: nvidia 4070ti + Wayland + Gnome can't boot

#14 2025-02-17 08:52:12

Re: nvidia 4070ti + Wayland + Gnome can't boot

#15 2025-02-17 10:08:18

Re: nvidia 4070ti + Wayland + Gnome can't boot

#16 2025-02-19 12:50:22

Re: nvidia 4070ti + Wayland + Gnome can't boot

#17 2025-02-19 13:20:34

Re: nvidia 4070ti + Wayland + Gnome can't boot

Board footer