current64 - Glamor does not load

 

Seem i always issue with mesa / DRI3 / amdgpu, need to continue investigate

If understand could be related to use gles instead gles2 only, i try with -Ddri3=enabled without success but we have -Dgles1=enabled -Dgles2=enabled
https://forums.gentoo.org/viewtopic-t-1070956-start-0.html
https://wiki.gentoo.org/wiki/Radeon#Troubleshooting

 https://forum.slitaz.org/topic/usage-of-slitaz-40-rolling/page/33#post-52894

 

 Troubleshooting

Debug tools

It might be helpful to install the package x11-apps/mesa-progs, which provides the packages glxgears and glxinfo.

Glamor does not load

If you see errors like "glamor detected, failed to initialize EGL.", then try enabling USE="gbm egl gles2 llvm" in the mesa builds.
If you see errors like "Failed to link: error: fragment shader lacks `main'", then make sure the glamor package has been built with USE="-gles".
On cards that are supported by radeonsi (starting at Southern Island, see the feature matrix) make sure to not only specify "radeon" but also "radeonsi" as the driver.

 

----

glamor X acceleration enabled on AMD RENOIR (DRM 3.40.0, 5.10.215-slitaz64, LLVM 13.0.0)

AIGLX: Loaded and initialized radeonsi

$ grep glamor /var/log/Xorg.0.log
[ 1863.979] (II) Loading sub module "glamoregl"
[ 1863.979] (II) LoadModule: "glamoregl"
[ 1863.979] (II) Loading /usr/lib/X11/modules/libglamoregl.so
[ 1863.981] (II) Module glamoregl: vendor="X.Org Foundation"
[ 1863.996] (II) modeset(0): glamor X acceleration enabled on AMD RENOIR (DRM 3.40.0, 5.10.215-slitaz64, LLVM 13.0.0)
[ 1863.996] (II) modeset(0): glamor initialized
[ 1864.050] (WW) modeset(0): DRI2: glamor lacks support for pixmap import/export

$ glxinfo -B | head
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD RENOIR (DRM 3.40.0, 5.10.215-slitaz64, LLVM 13.0.0) (0x1638)
Version: 21.3.5
Accelerated: yes
Video memory: 512MB
Unified memory: no

$ grep -A8 AIGLX /var/log/Xorg.0.log
[ 1864.056] (II) AIGLX: Loaded and initialized radeonsi
[ 1864.056] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1864.056] (II) Initializing extension XFree86-VidModeExtension
[ 1864.056] (II) Initializing extension XFree86-DGA
[ 1864.056] (II) Initializing extension XFree86-DRI
[ 1864.056] (II) Initializing extension DRI2
[ 1864.056] (II) modeset(0): Damage tracking initialized

glxgears-amd.png 8 months old

https://forum.slitaz.org/topic/uefi-only-laptop-trouble-booting/page/6#post-52274

make sure we had a working version. 

 

https://forum.slitaz.org/topic/usage-of-slitaz-40-rolling/page/34#post-52896

 

 

 

current64 - glamor error

 

(EE) AMDGPU(0): eglGetDisplay() failed
(EE) AMDGPU(0): glamor detected, failed to initialize EGL.
(WW) AMDGPU(0): amdgpu_glamor_pre_init returned FALSE, using ShadowFB

slitaz-current-core64.iso 2024-Dec-20 13:04:40 96.1M

latest ISO failed.

----

tux@slitaz:~$ uname -a
Linux slitaz 5.10.221-slitaz64 #2 SMP Wed Dec 18 13:36:29 Europe 2024 x86_64 GNU/Linux

tux@slitaz:~$ tazpkg

SliTaz package manager - Version: 944
================================================================================
  Installed packages:    317
  Installed files:       7024
  Blocked packages:      0
  Upgradeable packages:  0

  Repository:            Main
  Last recharge:         Today at 12:11.
  Database timestamp:    12/20/2024 11:09
  Mirrored packages:     1631
================================================================================

tux@slitaz:~$ X -version

X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
Build Operating System: SliTaz GNU/Linux
Current Operating System: Linux slitaz 5.10.221-slitaz64 #2 SMP Wed Dec 18 13:36:29 Europe 2024 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.221-slitaz64 root=/dev/null autologin lang=en_US kmap=us
Build Date: 18 December 2024  08:49:48PM
 
Current version of pixman: 0.40.0
    Before reporting problems, check http://www.slitaz.org/
    to make sure that you have the latest version.

tux@slitaz:~$ egrep 'failed|disabled|glamor|DRI[23]|GLX' /var/log/Xorg.0.log
[    20.643] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    20.670] (II) Loading sub module "glamoregl"
[    20.670] (II) LoadModule: "glamoregl"
[    20.670] (II) Loading /usr/lib/X11/modules/libglamoregl.so
[    20.671] (II) Module glamoregl: vendor="X.Org Foundation"
[    20.672] (EE) AMDGPU(0): eglGetDisplay() failed
[    20.672] (EE) AMDGPU(0): glamor detected, failed to initialize EGL.
[    20.672] (WW) AMDGPU(0): amdgpu_glamor_pre_init returned FALSE, using ShadowFB
[    20.675] (==) AMDGPU(0): DRI3 disabled
[    20.675] (WW) AMDGPU(0): Direct rendering disabled
[    20.675] (II) AMDGPU(0): 2D and 3D acceleration disabled
[    20.686] (II) Initializing extension DRI3
[    20.686] (II) Initializing extension GLX
[    20.686] (II) AIGLX: Screen 0 is not DRI2 capable
[    20.689] (II) IGLX: Loaded and initialized swrast
[    20.689] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    20.689] (II) Initializing extension DRI2

https://forum.slitaz.org/topic/usage-of-slitaz-40-rolling/page/33#post-52895

 

current64 - xfce4-settings-editor - Settings Editor

xfce4-settings-editor - Settings Editor

Panels can be configured and populated with items and these configurations
are also stored in
$HOME/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml
but when xfce4-panel is restarted, as with logout and new login,
this configuration is lost!

Try!

Accessing Configuration Data

xfce4-settings-editor - Settings Editor
Monitoring Channel Changes

XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon

xfconf - Configuration Storage System

Xfconf is a hierarchical (tree-like) configuration system where the immediate child nodes of the root are called “channels”. All settings beneath the channel nodes are called “properties.”

Accessing Configuration Data
Settings stored in Xfconf can be accessed in numerous ways:
From within applications of Settings Manager. Most of the time, settings stored in Xfconf and configuration options presented in the GUI are tightly coupled. It means that any action of the GUI settings is automatically and immediately propagated to the configuration system and vice-versa. See also: Settings Daemon.

From Command Line Interface (CLI) using xfconf-query.

From GUI. Settings, which are not exposed in configuration dialogs, can be browsed and manipulated using Settings Editor.

If everything else fails, settings can be edited manually. Xfconf stores all its data in XML files, which can be edited when Xfconf is not running. Be very careful when using this option, as it is easy to make the file unparseable or inconsistent.

https://docs.xfce.org/xfce/xfconf/start

xfce4-settings-editor - Settings Editor

The xfce4-settings-editor is a tool for editing ALL settings within xfconf. It is the graphical counterpart of xfconf-query. Both xfconf-query and the xfce4-settings-editor can be used to perform maintenance on the xfconf property database.

[..]

Monitoring Channel Changes

If you right-click a channel, you can Monitor... a channel for changes. This is useful for debugging in some cases and gives you some insight in the activity of a channel.

https://docs.xfce.org/xfce/xfce4-settings/editor

xfce4-settings - Settings Daemon

Debugging

If you have problems with settings and wonder which and if the settings are applied, you can run the daemon in debugging mode. You can do with with the following command in a terminal:
XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon

https://docs.xfce.org/xfce/xfce4-settings/xfsettingsd

https://forum.slitaz.org/topic/warning-xfce4-cooking#post-52823

current64 - amdgpu-glamoregl

 amdgpu-glamoregl

(EE) AMDGPU(0): eglGetDisplay() failed
(EE) AMDGPU(0): glamor detected, failed to initialize EGL.
(WW) AMDGPU(0): amdgpu_glamor_pre_init returned FALSE, using ShadowFB

(==) AMDGPU(0): DRI3 disabled
(WW) AMDGPU(0): Direct rendering disabled
(II) AMDGPU(0): 2D and 3D acceleration disabled
(II) AIGLX: Screen 0 is not DRI2 capable
(II) IGLX: Loaded and initialized swrast

tux@slitaz:~$ egrep 'failed|disabled|glamor|DRI[23]|GLX' /var/log/Xorg.0.log
[ 25.186] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 25.220] (II) Loading sub module "glamoregl"
[ 25.220] (II) LoadModule: "glamoregl"
[ 25.220] (II) Loading /usr/lib/X11/modules/libglamoregl.so
[ 25.222] (II) Module glamoregl: vendor="X.Org Foundation"
[ 25.222] (EE) AMDGPU(0): eglGetDisplay() failed
[ 25.223] (EE) AMDGPU(0): glamor detected, failed to initialize EGL.
[ 25.223] (WW) AMDGPU(0): amdgpu_glamor_pre_init returned FALSE, using ShadowFB
[ 25.230] (==) AMDGPU(0): DRI3 disabled
[ 25.230] (WW) AMDGPU(0): Direct rendering disabled
[ 25.230] (II) AMDGPU(0): 2D and 3D acceleration disabled
[ 25.240] (II) Initializing extension GLX
[ 25.240] (II) AIGLX: Screen 0 is not DRI2 capable
[ 25.244] (II) IGLX: Loaded and initialized swrast
[ 25.244] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 25.244] (II) Initializing extension DRI2

https://forum.slitaz.org/topic/usage-of-slitaz-40-rolling/page/33#post-52819