Is there any special configuration required to get glamor working with the GPU instead of swrast?

[kfoxirl]

Hi guys, clean install of xrdp but I cant seem to get the glamor piece working. Is there any special configuration required to get glamor working with the GPU instead of swrast?

My Xorg.conf
https://termbin.com/vx8l

[matt335672]

• Is xorgxrdp compiled with --enable-glamor?
• Is your hardware on the whitelist?

In your config:-

    Option "DRMAllowList" "amdgpu i915 msm radeon"

Looking at the sources, you should get something like the following logged in the xorg log file.

rdpPreInit: name [. . .]

[kfoxirl]

• Is xorgxrdp compiled with --enable-glamor?

  • Is your hardware on the whitelist?

In your config:-

    Option "DRMAllowList" "amdgpu i915 msm radeon"

Looking at the sources, you should get something like the following logged in the xorg log file.

rdpPreInit: name [. . .]

I'm sure about the Whitelist as this is a WSL instance, but if it helps I did have it working before on a different instance on an older version of XRDP.

I did build with --enable-glamor, and this is what I see for that value "rdpPreInit: name [vkms]"

But these lines kind of suggest to me that I'm using sw rasterizer.
[ 2722.420] (II) AIGLX: Screen 0 is not DRI2 capable
[ 2722.633] (II) IGLX: Loaded and initialized swrast
[ 2722.633] (II) GLX: Initialized DRISWRAST GL provider for screen 0

[matt335672]

@kfoxirl - can you post your xorgxrdp log file?

I must warn you this isn't really my area of expertise. I'm happy to trace the log messages against the sources though, and see if we can get something sorted out.

[kfoxirl]

Got it sorted Matt. I am not 100% sure what the fix was, but I used an old xorgxrdp-glamor AUR package and then used the configuration files from that with my build and now I get glamor :) Thanks for the help!

…

On Mon, Feb 3, 2025 at 4:45 AM matt335672 ***@***.***> wrote: @kfoxirl <https://github.com/kfoxirl> - can you post your xorgxrdp log file? I must warn you this isn't really my area of expertise. I'm happy to trace the log messages against the sources though, and see if we can get something sorted out. — Reply to this email directly, view it on GitHub <#361 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFMBKZUNRTXDDLCRPSUO2TL2N43EDAVCNFSM6AAAAABWJOJKMOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBTHEZTANA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Regards Karl Fox US2003120104

[matt335672]

Thanks for the update!

[adworacz]

So I just ran into this on Debian 13 (Trixie).

I checked journalctl -b, looking for the rdpPreInit line. I found the following:

Sep 19 15:36:08 crystal xrdp-sesman[970]: rdpPreInit: /dev/dri/renderD128 open failed

I did an ls -l on /dev/dri/renderD128 and noticed that it was owned by the render group:

crw-rw----+ 1 root render 226, 128 Sep 19 16:09 /dev/dri/renderD128

So I added my user to said group with sudo usermod -a -G render $USER.

Rebooted

Logged in with RDP, and BAM - KDE's "About this System" went from showing llvmpipe to Intel HD Graphics 500.

CPU usage is way down, since this is a tiny little Celeron.

Hope this helps others!