-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
amdgpu/msm: xorgxrdp
v0.10.2 does not work for hardware acceleration, but v0.10.1 does!
#341
Comments
Could be #322 Have a look in the xorgxrdp log file. |
Is this right ? 'glxinfo | Accelerated' Looks like a typo to me. |
I am facing an issue where I do not see the effects of acceleration. Am i suppose to see Xorg and gnome processes be listed in I am using your nvenc branch, built with
My /etc/X11/xrdp/xorg.conf, adding nvidia to Module and nvidia to DRMAllowList
|
@auggie246 You should be using /etc/X11/xrdp/xorg_nvidia.conf, not /etc/X11/xrdp/xorg.conf. You will need to edit /etc/xrdp/sesman.ini to change that. You should also turn on accel_issist too. |
Thanks i finally got everything working. However dynamic scaling is not working and mouse is limited to work in a very small region (green being the max point, black being where i was right clicking) This is my xorg_nvidia.conf
|
@auggie246 I know about the dynamic resizing and am working on it. You must be using a GRID GPU, if you change the |
Hi, this change also broke "msm" (definitely not easy to narrow down that this was the reason without a bit of tracing thru Xorg / xrdp) and now debian unstable ships this xorg new version, so by default anybody on debian unstable on arm64 laptops will hit this (I believe in just the past few days this xorgxrdp version went out). I can report that "msm" has worked with glamor for a while (past few years at least), so it would be fantastic if msm could be added to this list here like this: (or whatever else should be in here) : Option "DRMAllowList" "nvidia amdgpu i915 radeon msm" Just tested and this fixes latest xorgxrdp + msm. |
@jsorg71 - thoughts about adding msm to the approved drivers list? From what I can see, this is part of the Snapdragon SoC |
@matt335672 |
You're right. It is a typo. I fixed it. |
That's a good point @ChipZhang. A lot of our users may be using I've edited the release note for 0.10.2 to make this clearer:- https://github.com/neutrinolabs/xorgxrdp/releases/tag/v0.10.2 @metalefty - please be aware I've added this to the v0.10.2 known issues. |
Hi thanks for working on this, and I appreciate your work on xrdp over the years I definitely use it a ton. Yea it looks like initially there was a report that some nvidia users using glamor were getting a black screen -- which I believe means it was failing to fall back to swrast when Xorg started. (feels like a bug on that platform, but not sure). So given that this (I think) was coming from reports of specific drivers having problems, if we used a Disallowlist -- that'd probably avoid lots of people discovering this in the next 1-2 months as they discover that xrdp + gpu acceleration is broken on their platform / come here complaining etc. And if particular users want to disallow their nvidia gpu or whatever because it is not falling back to swrast or they have bugs with their driver, then they can do that by putting "nvidia" in the Disallowlist. Putting a big list by default I think will likely still end up missing some driver or some strange combination of things like somebody who is trying to get new drivers working etc. I can make a quick patch to send if you want as well to help out. |
I ended up making a patch anyway with a DRMDisallowList in case its useful and verified it works, lemme know and I'll send over. |
Thanks for the offer @gaberowe It's early days for the allow list, and (personally) I still think it's a preferred approach. Since you've offered us code however (which is always nice) I feel I offer you a fuller explanation. There are some small computers out there (i.e. PI sized) where hardware acceleration is provided as a binary blob as part of a kernel. These seem to be pushed out fairly rapidly. The acceleration works on the console, but it's never been tested with a remote session so doesn't always work with xrdp, or only works when the graphical console is not enabled. As a result, xrdp doesn't work out-of-the box, or (even worse) works some of the time but isn't reliable. It can be made to work without hardware acceleration, but this requires user intervention. See #2060 for an example of where this has happened. My own thinking is the more that xrdp works out-of-the-box, the more we can get it used by people. This benefits everyone. |
Hi @matt335672 -- sure sounds reasonable -- I had not seen any additional changes here: |
xorgxrdp
v0.10.2 does not work for hardware accerlation, but v0.10.1 does!xorgxrdp
v0.10.2 does not work for hardware acceleration, but v0.10.1 does!
oh my bad forgot to look at PR's thanks for that! |
I'm surprised and happy to see glamor used on these non intel / amd systems. I did some work on making the shaders in rdpEgl.c more portable. For example it works with VMWare virtual GPU and should work with more embedded devices. Getting a list of what devices are using glamor will help with testing. The branch is glsl_float1 |
glxinfo | grep Accelerated
in an XRDP session)Configure options for xrdp:
Configure options for xorgxrdp:
I compiled and tested for Ubuntu 20.04, 22.04, 24.04, tested for desktop KDE and Cinnamon.
And I use the same options as above for diffrent trials.
The result is the same: xorgxrdp v0.10.1 works, xorgxrdp v0.10.2 doesnt.
The text was updated successfully, but these errors were encountered: