Bug 1227110 - OpenGL/Vulkan hardware acceleration not available after update to TW 20240624
Summary: OpenGL/Vulkan hardware acceleration not available after update to TW 20240624
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Upgrade Problems (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-26 21:21 UTC by Pavel Urusov
Modified: 2024-07-16 16:38 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Urusov 2024-06-26 21:21:11 UTC
After update to openSUSE Tumbleweed 20240624, no OpenGL or Vulkan hardware acceleration is available on my system with an AMD RX560 GPU.

Output of `glxinfo -B`:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: llvmpipe (LLVM 18.1.6, 256 bits) (0xffffffff)
    Version: 24.1.1
    Accelerated: no
    Video memory: 31852MB
    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: 31 MB, largest block: 31 MB
    VBO free aux. memory - total: 29196 MB, largest block: 29196 MB
    Texture free memory - total: 31 MB, largest block: 31 MB
    Texture free aux. memory - total: 29196 MB, largest block: 29196 MB
    Renderbuffer free memory - total: 31 MB, largest block: 31 MB
    Renderbuffer free aux. memory - total: 29196 MB, largest block: 29196 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 4293901243 MB
    Total available memory: 4293933095 MB
    Currently available dedicated video memory: 31 MB
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 18.1.6, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 24.1.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.1.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.1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Output of `inxi -GSaz`:

System:
  Kernel: 6.9.5-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.3.0
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.9.5-1-default
    root=UUID=1b04871b-19af-4656-b838-b6dd768d39e4 splash=silent
    resume=/dev/disk/by-uuid/e1ddb037-4568-42f0-96be-53efd696200d
    mitigations=auto quiet security=apparmor
  Desktop: KDE Plasma v: 6.1.0 tk: Qt v: N/A info: frameworks v: 6.3.0
    wm: kwin_x11 tools: avail: swaylock,xscreensaver vt: 2 dm: SDDM
    Distro: openSUSE Tumbleweed 20240624
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: ASRock driver: i915 v: kernel
    alternate: xe arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports:
    active: none empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:4680 class-ID: 0380
  Device-2: AMD Baffin [Radeon RX 550 640SP / 560/560X] vendor: Sapphire
    driver: amdgpu v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm
    built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 8 ports:
    active: DP-2,HDMI-A-3 empty: DVI-D-1 bus-ID: 01:00.0 chip-ID: 1002:67ff
    class-ID: 0300 temp: 52.0 C
  Display: x11 server: X.Org v: 21.1.12 with: Xwayland v: 24.1.0
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
    alternate: intel gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x2160 s-dpi: 96 s-size: 1354x571mm (53.31x22.48")
    s-diag: 1469mm (57.85")
  Monitor-1: DP-2 pos: primary,left model: LG (GoldStar) Ultra HD
    serial: <filter> built: 2018 res: 3840x2160 hz: 60 dpi: 163 gamma: 1.2
    size: 600x340mm (23.62x13.39") diag: 690mm (27.2") ratio: 16:9 modes:
    max: 3840x2160 min: 640x480
  Monitor-2: HDMI-A-3 mapped: HDMI-3 pos: right model: Idek Iiyama PL1780
    serial: <filter> built: 2019 res: 1280x1024 hz: 60 dpi: 96 gamma: 1.2
    size: 338x270mm (13.31x10.63") diag: 433mm (17") ratio: 5:4 modes:
    max: 1280x1024 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris drv: amd radeonsi platforms: device: 0
    drv: iris device: 1 drv: radeonsi device: 2 drv: swrast surfaceless:
    drv: iris x11: drv: swrast inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 24.1.1 glx-v: 1.4
    direct-render: yes renderer: llvmpipe (LLVM 18.1.6 256 bits)
    device-ID: ffffffff:ffffffff memory: 30.38 GiB unified: yes
  API: Vulkan v: 1.3.283 layers: 6 device: 0 type: discrete-gpu name: AMD
    Radeon RX 560 Series (RADV POLARIS11) driver: N/A device-ID: 1002:67ff
    surfaces: N/A device: 1 type: integrated-gpu name: Intel UHD Graphics 770
    (ADL-S GT1) driver: N/A device-ID: 8086:4680 surfaces: N/A

I don't have any Packman repositories enabled.

System information:

Operating System: openSUSE Tumbleweed 20240624
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.5-1-default (64-bit)
Graphics Platform: X11
Memory: 31.1 GiB of RAM
Graphics Processor: llvmpipe
Comment 1 Pavel Urusov 2024-06-26 21:22:19 UTC
Also forgot to add that due to the 3D acceleration being not available, KDE Plasma (Wayland) session is not available.
Comment 2 hui 2024-06-27 12:21:25 UTC
Update your system to the latest snapshot and make sure that you have the latest Mesa packages from ONE source (either openSUSE or packman). This issue should alreday be already fixed...
Comment 3 Chenzi Cao 2024-07-16 16:37:33 UTC
Hi Pavel, would you please take a look at comment 2 and see whether the issue is fixed or not please? Thanks.
Comment 4 Pavel Urusov 2024-07-16 16:38:35 UTC
Hi, yes the issue has been fixed in the next update, thank you very much!