Description of problem: When using jetson-tk1 (armhfp) and maybe other aarch64 related devices (yet to be confirmed) the software rendering is used instead of the nouveau accelerated GPU. Version-Release number of selected component (if applicable): mesa-libGL-21.0.0~rc5-3.fc34.armv7hl How reproducible: always Steps to Reproduce: 1. run gnome-shell on jetson-tk1* devices. 2. 3. Actual results: it uses the LLVM software rendering Expected results: It should have used the GPU accelerated by nouveau Additional info: This used to work previously. journalctl -b _COMM=gnome-shell -o cat Adding device '/dev/dri/card0' (tegra) using non-atomic mode setting (using atomic mode setting not allowed). Adding device '/dev/dri/card1' (nouveau) using non-atomic mode setting. nvc0_screen_create:1093 - Error creating SW object: -22 failed to create GPU screen Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 11.1.0, 128 bits)), falling back to CPU copy path nvc0_screen_create:1093 - Error creating SW object: -22 Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 11.1.0, 128 bits)), falling back to CPU copy path Integrated GPU /dev/dri/card0 selected as primary Disabling DMA buffer screen sharing for driver 'tegra'. Using public X11 display :1024, (using :1025 for managed services) Using Wayland display name 'wayland-0' Skipping parental controls support as it’s disabled Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Will monitor session c2 Unable to connect to ibus: Impossible de se connecter : Connexion refusée Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Failed to set hardware cursor (drmModeSetCursor failed: Argument invalide), using OpenGL from now on Registering session with GDM Adding device '/dev/dri/card0' (tegra) using non-atomic mode setting (using atomic mode setting not allowed). Adding device '/dev/dri/card1' (nouveau) using non-atomic mode setting. nvc0_screen_create:1093 - Error creating SW object: -22 failed to create GPU screen Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 11.1.0, 128 bits)), falling back to CPU copy path nvc0_screen_create:1093 - Error creating SW object: -22 Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 11.1.0, 128 bits)), falling back to CPU copy path Integrated GPU /dev/dri/card0 selected as primary Disabling DMA buffer screen sharing for driver 'tegra'. Using public X11 display :0, (using :1 for managed services) Using Wayland display name 'wayland-0' Skipping parental controls support as it’s disabled Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Will monitor session c3 Telepathy is not available, chat integration will be disabled. Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Failed to set hardware cursor (drmModeSetCursor failed: Argument invalide), using OpenGL from now on GNOME Shell started at Wed Mar 10 2021 09:05:47 GMT+0100 (heure normale d’Europe centrale) Registering session with GDM
might attaching the output of dmesg?
Nothing is written in dmesg after changing from multi-user to graphical Also worth to mention that I'm using a downstream kernel (basically linux-next 20210302 with grate patches from github.com/grate-driver/linux) Using a fedora kernel (5.11.5) I'm experiencing this page fault: 1937129 I've just reproduced with linux-next 20210302 (without grate), the same failure occurs.
(In reply to Nicolas Chauvet (kwizart) from comment #2) > Nothing is written in dmesg after changing from multi-user to graphical > irrelevant as it might point out to something going wrong earlier. > Also worth to mention that I'm using a downstream kernel (basically > linux-next 20210302 with grate patches from github.com/grate-driver/linux) > > Using a fedora kernel (5.11.5) I'm experiencing this page fault: 1937129 > > I've just reproduced with linux-next 20210302 (without grate), the same > failure occurs.
Created attachment 1762377 [details] dmesg with "grate kernel" based on linux-next 20210302
Seems like kernel 5.10.6 is the last known good kernel with me: - Doesn't have the page fault (see rhbz#1937129) - Correctly allow userspace to use GL_VENDOR=NVIDIA and GL_RENDERER=tegra (instead of LLVM) Still checking previously built kernel to start bisecting...
Bisection started between v5.10 and v5.11-rc1
with 5.14-rc5 as a base + tegra-next + tegra-drm-next + tegra-drm-fixes (scheduled for next) + PM patches (scheduled for 5.16, but optionals). And using libdrm scheduled for the new tegra uABI... I have no issue anymore to have a graphical display using Wayland on workstation Spin (jetson-tk1).
I confirm that current fedora kernel and f35 userspace works under wayland. Xorg would requires the newer 21 release as it relies upon drm modifier support (or some others features only in xserver 21).