I used intel xorg driver (xserver-xorg-video-intel) plus i965-va-driver on Debian Bookworm; everything worked fine, 2D, 3D, video acceleration. After updating to Trixie, intel xorg driver (same setup as bookworm) doesn't provide acceleration. glxinfo shows LLVMpipe instead of Mesa Intel(R) HD Graphics 630 (KBL GT2) (that's the graphic device on my laptop). I switched to modesetting as suggested for years on Debian; 2D, 3D acceleration works fine on modesetting, but as expected, I have screen tearing on videos. I'd prefer to avoid xorg compositors. Wayland is not an option for me due to certain apps I use and still don't work well on it. Any ideas how to have acceleration using intel driver on Trixie, as in Bookworm?

I'm trying to install mesa-git from the unofficial repo in Arch but the install fails. I would just like to know if there is any way around this or is this method just broken? I did find a video talking about this repo from three years ago and some comments from just 3 weeks ago suggest it worked for them. The Video . [tanner@Desktop ~]$ sudo pacman -S mesagit :: There are 24 members in group mesagit: :: Repository mesa-git 1) clang-git 2) compiler-rt-git 3) lib32-libdrm-git 4) lib32-llvm-git 5) lib32-llvm-libs-git 6) lib32-mesa-git 7) lib32-vulkan-intel-git 8) lib32-vulkan-mesa-layer-git 9) lib32-vulkan-mesa-layers-git 10) lib32-vulkan-radeon-git 11) libclc-git 12) libdrm-git 13) lldb-git 14) llvm-git 15) llvm-libs-git 16) llvm-ocaml-git 17) mesa-git 18) opencl-mesa-git 19) vulkan-intel-git 20) vulkan-mesa-git 21) vulkan-mesa-layer-git 22) vulkan-mesa-layers-git 23) vulkan-radeon-git 24) vulkan-swrast-git Enter a selection (default=all): 1-6 9-18 20 22 23 resolving dependencies... looking for conflicting packages... :: llvm-git and llvm are in conflict. Remove llvm? [y/N] y :: lib32-libdrm-git and lib32-libdrm are in conflict. Remove lib32-libdrm? [y/N] y :: libdrm-git and libdrm are in conflict. Remove libdrm? [y/N] y :: lib32-llvm-git and lib32-llvm are in conflict. Remove lib32-llvm? [y/N] y :: lib32-mesa-git and lib32-mesa are in conflict. Remove lib32-mesa? [y/N] y :: mesa-git and mesa are in conflict. Remove mesa? [y/N] y :: lib32-vulkan-radeon-git and lib32-vulkan-radeon are in conflict. Remove lib32-vulkan-radeon? [y/N] y :: vulkan-radeon-git and vulkan-radeon are in conflict. Remove vulkan-radeon? [y/N] y :: libclc-git and libclc are in conflict. Remove libclc? [y/N] y Packages (31) lib32-libdrm-2.4.103-1 [removal] lib32-llvm-11.0.0-2 [removal] lib32-mesa-20.3.2-1 [removal] lib32-vulkan-radeon-20.3.2-1 [removal] libclc-11.0.0-1 [removal] libdrm-2.4.103-2 [removal] llvm-11.0.0-4 [removal] mesa-20.3.2-2 [removal] ocaml-4.11.1-1 ocaml-ctypes-0.17.1-4 ocaml-integers-0.4.0-3 vulkan-radeon-20.3.2-2 [removal] clang-git-12.0.0_r376022.5c951623bc89-1 compiler-rt-git-12.0.0_r376022.5c951623bc89-1 lib32-libdrm-git-2.4.103.r10.gd034db14-1 lib32-llvm-git-12.0.0_r376022.5c951623bc89-1 lib32-llvm-libs-git-12.0.0_r376022.5c951623bc89-1 lib32-mesa-git-1:21.0.0_devel.133039.471fd78e3c5-1 lib32-vulkan-mesa-layers-git-1:21.0.0_devel.133039.471fd78e3c5-1 lib32-vulkan-radeon-git-1:21.0.0_devel.133039.471fd78e3c5-1 libclc-git-1:12.0.0_r376022.5c951623bc89-1 libdrm-git-2.4.103.r10.gd034db14-1 lldb-git-12.0.0_r376022.5c951623bc89-1 llvm-git-12.0.0_r376022.5c951623bc89-1 llvm-libs-git-12.0.0_r376022.5c951623bc89-1 llvm-ocaml-git-12.0.0_r376022.5c951623bc89-1 mesa-git-1:21.0.0_devel.133039.471fd78e3c5-1 opencl-mesa-git-1:21.0.0_devel.133039.471fd78e3c5-1 vulkan-mesa-git-1:21.0.0_devel.132340.296316b5dec-1 vulkan-mesa-layers-git-1:21.0.0_devel.133039.471fd78e3c5-1 vulkan-radeon-git-1:21.0.0_devel.133039.471fd78e3c5-1 Total Download Size: 1.25 MiB Total Installed Size: 2045.37 MiB Net Upgrade Size: 1326.37 MiB :: Proceed with installation? [Y/n] y :: Retrieving packages... error: failed retrieving file 'vulkan-mesa-git-1:21.0.0_devel.132340.296316b5dec-1-x86_64.pkg.tar.zst' from pkgbuild.com : The requested URL returned error: 404 warning: failed to retrieve some files error: failed to commit transaction (failed to retrieve some files) Errors occurred, no packages were upgraded. [tanner@Desktop ~]$ tanner@Desktop ./sssso- -------------- `:osssssss+- OS: EndeavourOS Linux x86_64 `:+sssssssssso/. Kernel: 5.10.4-arch2-1 `-/ossssssssssssso/. Uptime: 2 days, 27 mins -/+sssssssssssssssso+: Packages: 1124 (pacman) `-:/+sssssssssssssssssso+/. Shell: bash 5.1.4 `.://osssssssssssssssssssso++- Resolution: 2560x1440 .://+ssssssssssssssssssssssso++: DE: Plasma 5.20.5 .:///ossssssssssssssssssssssssso++: WM: KWin `:////ssssssssssssssssssssssssssso+++. Theme: Breeze [Plasma], Breeze [GTK2/3] `-////+ssssssssssssssssssssssssssso++++- Icons: breeze [Plasma], breeze [GTK2/3] ..-+oosssssssssssssssssssssssso+++++/ Terminal: konsole ./++++++++++++++++++++++++++++++/:. CPU: AMD Ryzen 5 3600 (12) @ 3.600GHz :::::::::::::::::::::::::------` GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT Memory: 7032MiB / 15973MiB

Currently, glxinfo|grep "OpenGL version" gives OpenGL version string: 4.6 Mesa 18.3.4 And mesa-libGL-devel-18.3.4-12.el17_9.x86_64 got installed by default, but my app needs OpenGL 3.2 support at least. Is possible to install newer mesa to support OpenGL 3.x? If so, how? Thanks in advance!!!

I'm trying to run an app on Fedora 33, but when I run the executable, I get this error:

error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
libGL error: MESA-LOADER: failed to open iris (search paths /usr/lib64/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib64/dri)
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  149 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  52
  Current serial number in output stream:  51

I tried following the thread here: https://www.reddit.com/r/Fedora/comments/hhytvl/libgl_error_mesaloader_failed_to_open_iris/ but haven't gotten anything to work Note that the driver iris_dri.so is present in both /usr/lib/dri and /usr/lib64/dri Any help is appreciated, thanks in advance!

I have been trying to get lutris to work on ubuntu for the last week or so now, but there seems to be some underlying issue with Vulkan and I do not know how to proceed. I get the following error: tue@tue-desktop:~$ vulkaninfo --summary MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid argument MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Invalid argument, continuing without context... MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD /usr/lib/x86_64-linux-gnu/libvulkan_dzn.so. Skipping this driver. MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -4 from call to vkCreateInstance in ICD /usr/lib/x86_64-linux-gnu/libvulkan_gfxstream.so. Skipping this driver. ========== VULKANINFO ========== Vulkan Instance Version: 1.3.275 Instance Extensions: count = 24 ------------------------------- VK_EXT_acquire_drm_display : extension revision 1 VK_EXT_acquire_xlib_display : extension revision 1 VK_EXT_debug_report : extension revision 10 VK_EXT_debug_utils : extension revision 2 VK_EXT_direct_mode_display : extension revision 1 VK_EXT_display_surface_counter : extension revision 1 VK_EXT_headless_surface : extension revision 1 VK_EXT_surface_maintenance1 : extension revision 1 VK_EXT_swapchain_colorspace : extension revision 5 VK_KHR_device_group_creation : extension revision 1 VK_KHR_display : extension revision 23 VK_KHR_external_fence_capabilities : extension revision 1 VK_KHR_external_memory_capabilities : extension revision 1 VK_KHR_external_semaphore_capabilities : extension revision 1 VK_KHR_get_display_properties2 : extension revision 1 VK_KHR_get_physical_device_properties2 : extension revision 2 VK_KHR_get_surface_capabilities2 : extension revision 1 VK_KHR_portability_enumeration : extension revision 1 VK_KHR_surface : extension revision 25 VK_KHR_surface_protected_capabilities : extension revision 1 VK_KHR_wayland_surface : extension revision 6 VK_KHR_xcb_surface : extension revision 6 VK_KHR_xlib_surface : extension revision 6 VK_LUNARG_direct_driver_loading : extension revision 1 Instance Layers: count = 4 -------------------------- VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1 VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1 VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1 VK_LAYER_NV_optimus NVIDIA Optimus layer 1.3.277 version 1 Devices: ======== GPU0: apiVersion = 1.3.277 driverVersion = 550.144.3.0 vendorID = 0x10de deviceID = 0x2204 deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName = NVIDIA GeForce RTX 3090 driverID = DRIVER_ID_NVIDIA_PROPRIETARY driverName = NVIDIA driverInfo = 550.144.03 conformanceVersion = 1.3.7.2 deviceUUID = aee333ba-b8fb-d431-c14e-b6fc5ad3df7a driverUUID = 38474641-f375-59a9-952e-301ac330fdac GPU1: apiVersion = 1.4.305 driverVersion = 0.0.1 vendorID = 0x10005 deviceID = 0x0000 deviceType = PHYSICAL_DEVICE_TYPE_CPU deviceName = llvmpipe (LLVM 19.1.1, 256 bits) driverID = DRIVER_ID_MESA_LLVMPIPE driverName = llvmpipe driverInfo = Mesa 25.0~git2503210600.a801a4~oibaf~n (git-a801a4a 2025-03-21 noble-oibaf-ppa) (LLVM 19.1.1) conformanceVersion = 1.3.1.1 deviceUUID = 6d657361-3235-2e30-7e67-697432353000 driverUUID = 6c6c766d-7069-7065-5555-494400000000 I have tried to search for various parts of the error message, but have not been able to figure out what is wrong or how to fix it. I have tried to update my system and reinstall the drivers, but I do not really know how vulkan works and what exactly I should be looking at in order to fix this, so any insight on how to troubleshoot this would be appreciated.

I'm trying to create a ubuntu noble container (it has to be ubuntu noble due to another software's compatibility constraints) with a gui capable of running Gazebo, a robot simulation. For Gazebo, I need a working OpenGL setup (using mesa). As of now, though, my attempts to verify my setup with glxinfo fail due to some odd error:

root@554bf70792e2:/# glxinfo
name of display: :1
Error: couldn't find RGB GLX visual or fbconfig

I've done a ton of searching online and tried many solutions but none of them seemed to work. Can anyone help me out? # Further context: I'm running this on an apple silicon macbook (M3). Dockerfile:

FROM --platform=linux/arm64 ubuntu:noble

# ---------- Set Up VNC Server ----------

# Install Necessary Debian Packages
ENV DEBIAN_FRONTEND=noninteractivex
RUN apt update && \
    apt upgrade -y && \
    apt install -y xfce4 xfce4-goodies tightvncserver dbus-x11

# Add vncuser
RUN useradd -m vncuser && echo "vncuser:password" | chpasswd

# Switch to vncuser
USER vncuser

# Set up VNC password

RUN mkdir -p ~/.vnc && \
    echo "password" | vncpasswd -f > ~/.vnc/passwd && \
    chmod 600 ~/.vnc/passwd

# Set the default desktop environment to XFCE
RUN echo "#!/bin/bash\nXvfb :1 -screen 0 1280x720x24 &\nstartxfce4 &" > ~/.vnc/xstartup && \
    chmod +x ~/.vnc/xstartup && \
    touch ~/.Xauthority

# Switch back to root
USER root

# Expose VNC port
EXPOSE 5901

# Set environment variables
ENV DISPLAY=:1 \
    XDG_RUNTIME_DIR=/tmp/runtime-root \
    LIBGL_ALWAYS_SOFTWARE=1

# Mesa and other libraries
RUN apt update && apt install -y \
    libgl1-mesa-dri \
    libglx-mesa0 \
    libegl-mesa0 \
    mesa-vulkan-drivers \
    libosmesa6 \
    mesa-utils \
    xvfb \
    pciutils

vnc-start.sh:

su - vncuser -c "
export USER=vncuser
export DISPLAY=:1
vncserver -geometry 1280x720 -depth 24 :1
xhost +"

docker-compose.yml:

services:
  gprp:
    build: .
    container_name: gprp
    command: tail -f /dev/null
    ports:
      - "5901:5901"
    volumes:
      - .:/workspace

To start the container, I run docker-compose build and docker-compose up -d, then (within the container) run vnc-start.sh and glxinfo.

I am running Debian with kernel 6.5-asahi on an Apple M1 MacBook Air. Although I have kernel 6.9 installed, if I boot into it Mesa goes into software acceleration mode. apt upgrade gives

The following packages have been kept back:
  libegl-mesa0 libgbm-dev libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0 libosmesa6   
  lsp-plugins-lv2 lsp-plugins-r3d-glx m1n1 mesa-va-drivers mesa-vdpau-drivers
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.

apt full-upgrade gives

The following packages will be REMOVED:
  linux-image-asahi u-boot-asahi
The following packages have been kept back:
  libegl-mesa0 libgbm-dev libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0 libosmesa6
  lsp-plugins-lv2 lsp-plugins-r3d-glx m1n1 mesa-va-drivers mesa-vdpau-drivers
0 upgraded, 0 newly installed, 2 to remove and 12 not upgraded.

Here's my dpkg -l | grep mesa

ii  libegl-mesa0:arm64                               23.0.0-202310051950                       arm64        free implementation of the EGL API -- Mesa vendor library
ii  libegl1-mesa-dev:arm64                           24.2.0-20240527+cy8aer0                   arm64        free implementation of the EGL API -- development files
ii  libgl1-mesa-dev:arm64                            24.2.0-20240527+cy8aer0                   arm64        transitional dummy package
ii  libgl1-mesa-dri:arm64                            23.0.0-202310051950                       arm64        free implementation of the OpenGL API -- DRI modules
ii  libglapi-mesa:arm64                              23.0.0-202310051950                       arm64        free implementation of the GL API -- shared library
ii  libglu1-mesa:arm64                               9.0.2-1.1                                 arm64        Mesa OpenGL utility library (GLU)
ii  libglu1-mesa-dev:arm64                           9.0.2-1.1                                 arm64        Mesa OpenGL utility library -- development files
ii  libglx-mesa0:arm64                               23.0.0-202310051950                       arm64        free implementation of the OpenGL API -- GLX vendor library
ii  libosmesa6:arm64                                 23.0.0-202310051950                       arm64        Mesa Off-screen rendering extension
ii  mesa-common-dev:arm64                            24.2.0-20240527+cy8aer0                   arm64        Developer documentation for Mesa
ii  mesa-utils                                       8.5.0-1                                   arm64        Miscellaneous Mesa utilities -- symlinks
ii  mesa-utils-bin:arm64                             8.5.0-1                                   arm64        Miscellaneous Mesa utilities -- native applications
ii  mesa-va-drivers:arm64                            23.0.0-202310051950                       arm64        Mesa VA-API video acceleration drivers
ii  mesa-vdpau-drivers:arm64                         23.0.0-202310051950                       arm64        Mesa VDPAU video acceleration drivers

How can I cleanly upgrade mesa without screwing the system? These versions of Mesa are from a 3rd party repo, which also contains the linux-image-asahi which is odd that they conflict. The versions of Mesa I am trying to upgrade are from the repo, not from deb.debian.org, and I've set a very high pin priority to the 3rd party repos in apt The 3rd party repos are

deb https://git.g3la.de/api/packages/repos/debian  testing main
deb https://thomas.glanzmann.de/asahi  testing main

As an example of manually installing one of the replacement packages:

nick@MacBook:~$ sudo apt install libegl-mesa0
[sudo] password for nick: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libegl-mesa0 : Depends: libc6 (>= 2.38) but 2.36-9+deb12u7 is to be installed
                Depends: libgbm1 (= 24.2.0-20240527+cy8aer0) but 23.0.0-202310051950 is to be installed
                Depends: libglapi-mesa (= 24.2.0-20240527+cy8aer0) but 23.0.0-202310051950 is to be installed
                Depends: libx11-xcb1 (>= 2:1.8.7) but 2:1.8.4-2+deb12u2 is to be installed
E: Unable to correct problems, you have held broken packages.

I'm running FreeBSD 14.1 right now and I suspect that the Mesa libs that I have installed on the system are bugged or maybe I have some misconfiguration,because when I do : # glxinfo | grep Mesa I get the error that you see on the title and smplayer/mpv/vlc doesn't work at all. Anyway,this is the context in which the error happens : I have 3 GPUS : 1) 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] 2) 01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] 01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller 3) 02:00.0 VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] 02:00.1 Audio device: NVIDIA Corporation TU102 High Definition Audio Controller 02:00.2 USB controller: NVIDIA Corporation TU102 USB 3.1 Host Controller 02:00.3 Serial bus controller: NVIDIA Corporation TU102 USB Type-C UCSI Controller I'm not using any xorg.conf. nano /etc/rc.conf : kld_list="nvidia-modeset nvidia-drm linux i915kms ext2fs" nano /boot/loader.conf : pptdevs="1/0/0 1/0/1 2/0/0 2/0/1 2/0/2 2/0/3 4/0/0" hw.nvidiadrm.modeset=1 This is where the problem is : [marietto@marietto ~]==> glxinfo | grep Mesa X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 24 (X_GLXCreateNewContext) Value in failed request: 0x0 Serial number of failed request: 50 Current serial number in output stream: 51 I've installed the following packages : # pkg install xf86-video-intel nvidia-drm-kmod drm-kmod nvidia-driver I've also tried to check if I had the same error by removing the xf86-video-intel and using the i915kms driver with Xorg : # pkg remove xf86-video-intel # nano /etc/X11/xorg.conf Section "Device" Identifier "Intel Graphics" Driver "i915kms" EndSection But I've got the same error. Maybe it is a Mesa bug. What's one consequence of this "bug" ? this one : ==> scrcpy --tcpip=192.168.1.3:5555 scrcpy 2.7 INFO: Connecting to 192.168.1.3:5555... INFO: Connected to 192.168.1.3:5555 /usr/local/share/scrcpy/scrcpy-server: 1 file pushed, 0 skipped. 34.1 MB/s (71200 bytes in 0.002s) [server] INFO: Device: [samsung] samsung SM-N9005 (Android 9) [server] WARN: Audio disabled: it is not supported before Android 11 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 147 Current serial number in output stream: 148

I'm new to Arch, coming from Ubuntu I have very recently installed EndeavourOS\ today I installed Steam, but my windows are \ Looking for some solution I notice that often the finger is pointed at glxinfo so I run

[yakforward@yoga-720 ~]$ sudo pacman -S vulkan-intel
[sudo] password for yakforward: 
warning: vulkan-intel-21.2.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)         Old Version  New Version  Net Change

extra/vulkan-intel  21.2.1-1     21.2.1-1       0,00 MiB

Total Installed Size:  9,99 MiB
Net Upgrade Size:      0,00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [----------------------] 100%
(1/1) checking package integrity                   [----------------------] 100%
(1/1) loading package files                        [----------------------] 100%
(1/1) checking for file conflicts                  [----------------------] 100%
:: Processing package changes...
(1/1) reinstalling vulkan-intel                    [----------------------] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Checking which packages need to be rebuilt
[yakforward@yoga-720 ~]$ glxinfo | grep -i vulkan
bash: glxinfo: command not found

this is my neofetch

./o.                  yakforward@yoga-720 
                   ./sssso-                ------------------- 
                 `:osssssss+-              OS: EndeavourOS Linux x86_64 
               `:+sssssssssso/.            Host: 80X6 Lenovo YOGA 720-13IKB 
             `-/ossssssssssssso/.          Kernel: 5.13.13-arch1-1 
           -/+sssssssssssssssso+:        Uptime: 1 hour, 29 mins 
         `-:/+sssssssssssssssssso+/.       Packages: 1080 (pacman), 7 (snap) 
       `.://osssssssssssssssssssso++-      Shell: bash 5.1.8 
      .://+ssssssssssssssssssssssso++:     Resolution: 1920x1080 
    .:///ossssssssssssssssssssssssso++:    DE: GNOME 40.4 
  `:////ssssssssssssssssssssssssssso+++.   WM: Mutter 
`-////+ssssssssssssssssssssssssssso++++-   WM Theme: Adwaita 
 ..-+oosssssssssssssssssssssssso+++++/   Theme: Adwaita-dark [GTK2/3] 
   ./++++++++++++++++++++++++++++++/:.     Icons: Adwaita [GTK2/3] 
  :::::::::::::::::::::::::------`       Terminal: gnome-terminal 
                                           CPU: Intel i5-7200U (4) @ 3.100GHz 
                                           GPU: Intel HD Graphics 620 
                                           Memory: 2380MiB / 7675MiB

do you have any suggestion? Thank you

I've got 6700S laptop GPU that has 100W power limit provided by ASUS' custom design or whatever. On Windows it uses 100W power limit just fine. But on Linux with **amdgpu** it starts for a couple of seconds with 100W after system boot and by ~25th second it turns it down to 80W which is its vanilla power limit. The value is confirmed by cat /sys/class/drm/card0/device/hwmon/hwmon4/power1_cap. I've tried several kernels: 6.2, 6.5, 6.7. Also I tried several mesa versions: 23.1, 24.1. Also I manually upgraded **linux-firmware** for **amdgpu** specifically - no luck. Dmesg shows this output when 100W to 80W change happens (supposedly): [ 22.496680] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 22.513799] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 22.513802] amdgpu 0000:03:00.0: amdgpu: SMU is resuming... [ 22.513806] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b2f00 (59.47.0) [ 22.513810] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched [ 22.565134] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully! Where should I dig to allow this GPU to have power1_cap_max to be 100W? UPD: It seems like this happens when this GPU is being sent to low-power state and then it resumes. By default it boots with 100W limit just fine. Then it's being suspended (or smth) due to inactivity - iGPU is used. When the system needs this GPU back it resumes it and then it overrides the limit!

I want to run Davinci Resolve on my Arch Linux system with a AMD 7900 XTX GPU. Currently Resolve does not even start (process exits immediately after start). Here are the outputs:

$ ./resolve
ActCCMessage Already in Table: Code= c005, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode= 0, Level= 0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode= 0, Level= 0, CmdKey= -1, Option= 0
18.6.4.0006 Linux/Clang x86_64
Main thread starts: 37006000
0x7efd37006000 | Undefined | INFO | 2023-12-09 05:35:11,591 | --------------------------------------------------------------------------------
0x7efd37006000 | Undefined | INFO | 2023-12-09 05:35:11,591 | Loaded log config from /home/vankurt/.local/share/DaVinciResolve/configs/log-conf.xml
0x7efd37006000 | Undefined | INFO | 2023-12-09 05:35:11,591 | --------------------------------------------------------------------------------

I also tried davinci-resolve-checker, to see if I have the correct Open CL and GPU packages installed. Here's what it says:

DaVinci Resolve checker 5.2.5
Installed DaVinci Resolve package: davinci-resolve-studio 18.6.4-1
Chassis type: desktop
Installed OpenCL drivers:
opencl-rusticl-mesa 1:23.2.1-2
rocm-opencl-runtime 5.7.1-1
Presented GPUs:
Navi 31 [Radeon RX 7900 XT/7900 XTX] (kernel driver in use: amdgpu)
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.6, DRM 3.54, 6.6.4-arch1-1)
clinfo detected platforms and devices:
AMD Accelerated Parallel Processing (roc) (number of devices: 1)
AMD Radeon RX 7900 XTX
rusticl (number of devices: 0)

All seems good. You should be able to run DaVinci Resolve successfully.

Has anyone been able to run Davinci Resolve with a AMD 7900 XTX? Are there any other packages I need to install? Is there anything else I can try?

In a fresh Arch Linux Installation with Gnome occurring display errors on specific applications. I have reinstalled Arch Linux (archlinux-2024.01.01-x86_64.iso) due to display errors after an update using "pacman -Syu" on January 2, 2024. On Apps like Console, Nautilus: - The application window flickers. - In particular, the window-backgroundcolor is missing and the controls ("X" for close) are missing. - There are streaks when moving the window. Unfortunately, the same display errors also occur in the fresh installation. With other applications, such as Gnome-Optimizations or Firefox, these display errors do not occur. What I have done so far Alternatively, I installed Arch Linux with Cinnamon and did not get these display errors. However, I would like to get Gnome working again. System: - Notebook: Lenovo B560 (Family: IDEAPAD) - Processor: Pentium P6100, 2 GHz - RAM: 3 GB - Graphic: Intel integrated Graphic Controller, rev. 02 - Kernel Driver in use: i915 Until this update attempt, this system worked flawlessly. Does anyone have an idea how I can solve this problem?Until this update attempt, this system worked flawlessly Best Regards

This image from Wikipedia illustrates the so-called "linux graphics stack". Suppose I buy a laptop that is so new that there exists no dedicated device driver for its GPU. Hence, the graphic quality is bad until one day some decent developer creates an excellent free driver and by updating my linux distro I notice that the graphic quality has become superb and flawless. My question is: how has the update changed the graphics stack? In particular, I'd like to know if the new graphics driver is merely run in user-space or at least some part of it is run in kernel-space. By the way, I'm not a very advanced linux user. Please keep that in mind. :)

Found out that Hardware Acceleration when using a AMD Ryzen 9 5900HX will cause video lockups or system reboots. Using a Minisforum HX90 computer. Using open-source drivers and admgpu. No error msg, justs locks up or reboots. All drivers, OS and software updated and current. Been using Linux for a while, but have not run into this type of problem before and have not studied Arch Linux internals. How do I disable this feature from AMDgpu. Thanks.

Our application needs Opengl 3.1 support or higher. The RHEL7.9 VM (thru VMware, with the VMware SVGA II adapter) we use, provides the following for glxinfo | grep version: - server glx version string: 1.4 - client glx version string: 1.4 - GLX version: 1.4 - Max core profile version: 0.0 - Max compat profile version: 2.1 - Max GLES1 profile version: 1.1 - Max GLES profile version: 2.0 - OpenGL version string: 2.1 Mesa 18.3.4 - OpenGL shading language version string: 1.20 - OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.3.5 - OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 The Wiki for Mesa (https://en.wikipedia.org/wiki/Mesa_(computer_graphics)) shows 18.x supports OpenGL 4.6 / OpenGL ES 3.2, I am trying to figure out how to configure the default driver in RHEL7 to support that instead of the 2.1/2.0 it shows in glxinfo. (Why would Red Hat set it up by default for OpenGL 2.1 / OpenGL ES 2.0?) Update: The underlying hardware is one of a bunch of Dell PowerEdge R730/R740/R830/R840 all of 2015-2017 vintage. The CPUs on them are Xeon Platinum 8620, a few Xeon Gold something-something, and a few other flavors of Xeon Platinum. (Some of them we have Nvidia Tesla M10/M60/P40 graphics accelerators, we are trying to do away with) I asked the Lab Ops manager a couple hours ago what the iGPU capability on those are, and his response "that is a good question". The CPUs on them are Xeon Platinum 8620, a few Xeon Gold something-something, and a few other flavors of Xeon Platinum. The interesting thing is that my RHEL8 VM gave me satisfactory glxinfo data, ie. OpenGL 4.6 and OpenGL ES 3.2. I may have to get the VMs on the same cluster with the same underlying servers to truly be able to tell if the actual physical hw can really do those versions. Update2: Both RHEL7 and RHEL8 VM are running on the same cluster of three PowerEdge R730's with Xeon ES-2690 v4 cpus (and identical config across the three servers). Here is the glxinfo | grep version for the RHEL8 VM: server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 Max core profile version: 4.5 Max compat profie version: 4.5 Max GLES1 profile version: 1.1 Max GLES profile version: 3.2 OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.1.5 OpenGL core profile shading language version string: 4.50 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.1.5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 GL_EXT_shader_implicit_conversions, GL_EXT_shader_integer_mix, So the RHEL8 driver on the same hardware can support 4.5/ES 3.2, but the RHEL7 drops back to 2.1.

I'm using virt-manager and set "3D Acceleration" as per what was recommended, but I'm getting this error: > qemu_gl_create_compile_shader: compile vertex error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES This tells me that my GPU is too old for that, which doesn't adds up since my GPU does support OpenGL ES up to 2.0. Anyway, I do need 3D acceleration so some guests won't get sluggy, and my best bet would be to force virt-manager to use the hosts' llvmpipe renderer, which allows a higher OpenGL ES support. Anyone knows how I can do that with virt-manager? PS: If this can't be done like that, I'll probably have to use an older QEMU version that had lower OpenGL ES requirements. Does anyone knows what are those QEMU versions? All I know is that QEMU 2.5 is the very first to support VirGL ( https://docs.mesa3d.org/drivers/virgl.html ), but that wouldn't be a great idea to go that old, there must be some later versions that can still make use of OpenGL (not ES, still can't understand why, as support is worse than regular OpenGL) 2.0. PS2: I did try to add

=1

in front of virt-manager and ran them in a terminal, but it did nothing. Another thing I've noticed is changing the Spice Display's xml to the right rendernode (was set to

/dev/dri/by-path/pci-0000:01:00.0-render

) might do the trick, so where's the correct path to llvmpipe then?

I need OpenGL 4.5 to be supported by my graphics card's driver, and as far as I know Mesa is actually able to run it. glxinfo gives me this: $ glxinfo | grep "OpenGL" OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 13.0.6 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.0.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 OpenGL ES profile extensions: So this means it can only run OpenGL 3.0. So I tried to update it, but I ran into several problems: If I try to update it through apt, i.e. sudo apt-get upgrade libgl1-mesa-dri -t testing, it is broken: $ sudo apt-get upgrade libgl1-mesa-dri -t testing Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsnmp30 : Depends: libsensors4 (>= 1:3.0.0) but it is not going to be installed mesa-va-drivers : Depends: libsensors4 (>= 1:3.0.0) but it is not going to be installed mesa-va-drivers:i386 : Depends: libsensors4:i386 (>= 1:3.0.0) but it is not going to be installed E: Broken packages Okay, but: $ apt-cache policy libsensors4 libsensors4: Installed: 1:3.4.0-4 Candidate: 1:3.4.0-4 Version table: *** 1:3.4.0-4 900 900 http://ftp.ru.debian.org/debian stretch/main amd64 Packages 100 /var/lib/dpkg/status So it depends on the lib version >=1:3.0.0, but I have version 1:3.4.0-4, which is really strange. Generally, I don't understand how should I upgrade Mesa. If using apt, I don't know which packages should I update. If from source, I don't know how will it interact with apt and if it won't be reverted by an update. I am using Debian 9 Stretch, and my graphics card is Intel HD Graphics 5000.

Since I cannot precisely tell what upgrade (possibly nvidia-drivers from 340 to 470 or mesa 20 to 22 or even xorg-server 1.20 to 21) or following the first time I ran glxgears after upgrading ? :
I (not systematically though) can see, superposed on the upper left corner of the window of applications such as *vlc* or *chromium*, some report very similar to the one I would get running *glxgears* as one can see below on some screen capture of vlc upper-left window corner : Is this a bug ? a misconfiguration problem ? a feature ? Whatever : How can I just get rid of this ? ---------- **EDIT 1 :** Would that be the *Graphics API Visual Indicator * ?
I'd be surprised since its display is not systematic and I made sure the __GL_SHOW_GRAPHICS_OSD environment variable is not set. ---------- BTW : Running a KDE-Plasma desktop, I know it offers the possibility to display informations regarding the frame rate but I do not think this very question related since this option is not set and the display of this information is radically different.

As a Linux fan, I want to get into OpenGL development as a hobby of mine. I know that OpenGL is just an API that the GPU vendors must implement. Some GPU vendors' OpenGL/Vulkan implementations are proprietary, whilst some are open source (like Intel). Because I like open source, I want to make sure I don't use anything proprietary when I develop stuff, so how would I go about checking whether or not my GPU is currently using Mesa for rendering? The reason I am asking is because I've gotten mixed messages online, as I have heard that you can apparently still have Mesa installed but the GPU will be using something else that is proprietary, which is why I wanted to ask this question. Any help would be appreciated.

I am trying to get the Intel integrated GPU working with my Parabola (Arch variant) desktop PC. According to lspci, the GPU is: 00:02.0 Display controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) I have reconfigured my xorg.conf files to point to it; however, when I run startx, I get the following error in the Xorg log file: [ 1611.090] (II) Initializing extension GLX [ 1611.101] (EE) AIGLX error: dlopen of /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory) [ 1611.101] (EE) AIGLX error: unable to load driver i965 So, it seems to not be able to find the i965 driver for the GPU. Looking in /usr/lib/dri verifies that the driver file is not there: # ls /usr/lib/dri crocus_dri.so iris_dri.so nouveau_dri.so r600_dri.so swrast_dri.so vmwgfx_dri.so d3d12_dri.so kms_swrast_dri.so r300_dri.so radeonsi_dri.so virtio_gpu_dri.so zink_dri.so *However*, if I check the file list for the mesa package I have installed, it says the file should be installed: # pacman -Fl mesa | grep dri mesa usr/include/GL/internal/dri_interface.h mesa usr/lib/dri/ mesa usr/lib/dri/i915_dri.so mesa usr/lib/dri/i965_dri.so mesa usr/lib/dri/iris_dri.so mesa usr/lib/dri/kms_swrast_dri.so mesa usr/lib/dri/nouveau_dri.so mesa usr/lib/dri/nouveau_vieux_dri.so mesa usr/lib/dri/r200_dri.so mesa usr/lib/dri/r300_dri.so mesa usr/lib/dri/r600_dri.so mesa usr/lib/dri/radeon_dri.so mesa usr/lib/dri/radeonsi_dri.so mesa usr/lib/dri/swrast_dri.so mesa usr/lib/dri/virtio_gpu_dri.so mesa usr/lib/dri/vmwgfx_dri.so mesa usr/lib/pkgconfig/dri.pc mesa usr/share/drirc.d/ mesa usr/share/drirc.d/00-mesa-defaults.conf **However**, if I check the mesa package tar archive, that driver file is clearly not present: # tar -tf mesa-22.2.1-1-x86_64.pkg.tar.zst | grep dri usr/include/GL/internal/dri_interface.h usr/lib/dri/ usr/lib/dri/crocus_dri.so usr/lib/dri/d3d12_dri.so usr/lib/dri/iris_dri.so usr/lib/dri/kms_swrast_dri.so usr/lib/dri/nouveau_dri.so usr/lib/dri/r300_dri.so usr/lib/dri/r600_dri.so usr/lib/dri/radeonsi_dri.so usr/lib/dri/swrast_dri.so usr/lib/dri/virtio_gpu_dri.so usr/lib/dri/vmwgfx_dri.so usr/lib/dri/zink_dri.so usr/lib/pkgconfig/dri.pc usr/share/drirc.d/ usr/share/drirc.d/00-mesa-defaults.conf So, what's going on here then? Is 'i965_dri.so' supposed to be provided with mesa, or am I supposed to get it from somewhere else? If it is supposed to be there, I should probably file an issue report?