gupax libEGL warning: DRI3 error: Could not get DRI3 device

[nova2moon]

OS & Version:

Operating System: Ubuntu 24.04.4 LTS              
          Kernel: Linux 6.17.0-1023-oem
    Architecture: x86-64

Bug

Noticed these errors during startup :

[INFO] [0.210] [<redacted>:0] Skipping auto-XMRig-Proxy...                                          ???????? 
[INFO] [0.210] [<redacted>:0] Skipping auto-xmrig...                                                ???????  
[INFO] [0.210] [<redacted>:0] Skipping auto-xvb...                                                  ???????  
[INFO] [0.210] [<redacted>:0] /*************************************/ Init ... OK /*****************?????????*/                                                                               
[INFO] [0.210] [<redacted>:0] after daemon                                                          ??????   
[INFO] [0.210] [<redacted>:0] init_options() ... OK                                                 ???????  
[INFO] [0.210] [<redacted>:0] starting Gupax with renderer: wgpu                                    ???????? 
[INFO] [0.210] [<redacted>:0] Both the glow and wgpu renderers are available. Using wgpu.           ?????????
[WARN] [0.212] [/home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/winit-0.30.13/src/?????????/x11/xdisplay.rs:118] error setting XSETTINGS; Xft options won't reload automatically                                                                                                
[WARN] [0.220] [/home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/winit-0.30.13/src/?????????/x11/util/randr.rs:24] XRandR reported that the display's 0mm in size, which is certifiably insane                                                                                   
[INFO] [0.220] [/home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/winit-0.30.13/src/?????????/x11/window.rs:192] Guessed window scale factor: 1                               
libEGL warning: DRI3 error: Could not get DRI3 device                                               
libEGL warning: Ensure your X server supports DRI3 to get accelerated rendering                     
vulkan: No DRI3 support detected - required for presentation                                        
Note: you can probably enable DRI3 in your Xorg config                                              
[INFO] [0.268] [<redacted>:0] There were 3 available wgpu adapters: {backend: Vulkan, device_type: I????????? "AMD Radeon Graphics (RADV PHOENIX)", driver: "radv", driver_info: "Mesa 25.2.8-0ubuntu0.24.04.1", vendor: AMD (0x1002), device: 0x1900, pci_bus_id: "0000:c6:00.0", subgroup_size: 32..=64, transient_saves_memory: false}, {backend: Vulkan, device_type: Cpu, name: "llvmpipe (LLVM 20.1.2, 256 bits)", driver: "llvmpipe", driver_info: "Mesa 25.2.8-0ubuntu0.24.04.1 (LLVM 20.1.2)", vendor: Mesa (0x10005), subgroup_size: 8..=8, transient_saves_memory: false}, {backend: Gl, device_type: Cpu, name: "llvmpipe (LLVM 20.1.2, 256 bits)", driver_info: "4.5 (Core Profile) Mesa 25.2.8-0ubuntu0.24.04.1", vendor: Mesa (0x10005), subgroup_size: 4..=128, transient_saves_memory: false}        

looking at CPU flags, shows there is support(?):

$ grep -o pdpe1gb /proc/cpuinfo
pdpe1gb
pdpe1gb
pdpe1gb
pdpe1gb
pdpe1gb

Hardwhare is:

8-core AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (-MT MCP-)

amdgpu is loaded fine, maybe this will help?:

$ modinfo amdgpu |grep -i version
srcversion:     F4E119C8AEF459401531B5B
vermagic:       6.17.0-1023-oem SMP preempt mod_unload modversions 

Steps

Steps to reproduce the behavior:

1. Just launch gupax on ubuntu 24.04 (no standard GUI, setup as server with remove VNC)

Trying to understand HOW to avoid these (maybe somehow enable DRI??) based on glxinfo (if "direct rendering" is YES, then DRI is enabled:

$ glxinfo -B 
name of display: :2
display: :2  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: llvmpipe (LLVM 20.1.2, 256 bits) (0xffffffff)
    Version: 25.2.8
    Accelerated: no
    Video memory: 90044MB
    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: 0 MB, largest block: 0 MB
    VBO free aux. memory - total: 81534 MB, largest block: 81534 MB
    Texture free memory - total: 0 MB, largest block: 0 MB
    Texture free aux. memory - total: 81534 MB, largest block: 81534 MB
    Renderbuffer free memory - total: 0 MB, largest block: 0 MB
    Renderbuffer free aux. memory - total: 81534 MB, largest block: 81534 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 0 MB
    Total available memory: 90044 MB
    Currently available dedicated video memory: 0 MB
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 20.1.2, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 25.2.8-0ubuntu0.24.04.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 25.2.8-0ubuntu0.24.04.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 25.2.8-0ubuntu0.24.04.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Any tips welcomed.

[Cyrix126]

please don't copy/paste llm output if you don't understand it. pdpe1gb has nothing to do with the issue.
If your machine is a VM, you will not be able to get hardware acceleration. The warning is normal in this case.

[nova2moon]

1. This is not a VM, it's a physical AMD machine w/GPU, as posted above: 8-core AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (-MT MCP-)
2. It's a human driving requests and trying to not paste things that are not relevant, to my understanding if glxinfo shows there is no direct rendering support that might affect x11/DRI and thus contribute, sorry if not relevant..
3. Anyway to debug/understand further?

As general note I'd like to say that I'm totally understanding that due to nature of this amazing tool, all these "issues" are finding themselves here but in fact they really belong to the respective projects, i.e. p2pool, xmrig, monerod, etc. so, rest assured I'm very appreciative for your insight, and looking forward to help improve integration/quality for longer term..

And that too was not AI :) :) time will tell..