Raspberry Pi as x2go “thin” client • Hacker News Board

Re: Raspberry Pi as x2go “thin” client

#51

Post by zamadatix » Sun, Jan 24, 2021, 12:32 AM UTC

gruez wrote: post #40

zamadatix wrote: post #35

Earlier quoted context omitted.

RemoteFX will enable both GPU acceleration in apps as well as GPU acceleration in the RDP session encode but... RDP is still only limited to 30 FPS for whatever reason and so you may continue to be disappointed in it. Also 1,300 Mbps sounds like a wireless network so your main problem on the network side is being half duplex and airtime delays (even from just beacons) not throughput. I'd pick a 100 Mbps hardwire to R…

Doesn't remote fx require special hardware/os on the host side?

Not really, OS wise it can't be Home edition but because Homedoesn't officially support hosting RDP at all. Hardware wise it requires basically "a gpu", even a low end decade old integrated Intel GPU will work.

Re: Raspberry Pi as x2go “thin” client

#52

Post by nemosaltat » Sun, Jan 24, 2021, 12:33 AM UTC

plg wrote: post #48

6gvONxR4sf7o wrote: post #44

The capabilities of using a tiny client for a beefy/flexible server seem to be getting better and more mature as robust clients get cheap and bandwidth get solid. I love it. I’ve been very very slowly using AWS as my “computer” more and more. S3 is a wonderfully cheap infinite hard drive and I never have to worry about migrating scripts. And EC2 is as flexible as computing gets. And since I need to recreate everythin…

I would love to read a blog post about your setup and your routine using this arrangement.

+1

Re: Raspberry Pi as x2go “thin” client

#53

Post by gruez » Sun, Jan 24, 2021, 1:25 AM UTC

zamadatix wrote: post #51

gruez wrote: post #40

Earlier quoted context omitted.

Doesn't remote fx require special hardware/os on the host side?

Not really, OS wise it can't be Home edition but because Homedoesn't officially support hosting RDP at all. Hardware wise it requires basically "a gpu", even a low end decade old integrated Intel GPU will work.

Yeah my use case isn't really some sort of RDI farm, but just a way to access one of my existing machines which I also happen to use physically. For that use case RDP (without remotefx) works fine, but it doesn't look like setting up remotefx would be easy.

Re: Raspberry Pi as x2go “thin” client

#54

Post by Fnoord » Sun, Jan 24, 2021, 12:30 PM UTC

amryl wrote: post #45

whalesalad wrote: post #19

How’s the experience of working on it? I’ve been struggling to get a decent remote setup even in my home lab due to network latency. Could be because I’m trying to drive 4K. Even Win10 RDP over a 1300mbps network struggles. I wonder if I need to bite the bullet and install a real graphics card in the R720. Would love to hear more experiences of others who remote this way where you are “offloading” your compute power…

You could try solutions oriented toward gaming like Parsec or Nvidia Gamestream with Moonlight. They use hardware acceleration for video encoding and may have better latency than RDP. https://parsec.app/ https://moonlight-stream.org/

Don't these and Stadia use RDP under the hood?

Re: Raspberry Pi as x2go “thin” client

#55

Post by amryl » Sun, Jan 24, 2021, 5:11 PM UTC

Fnoord wrote: post #54

amryl wrote: post #45

Earlier quoted context omitted.

You could try solutions oriented toward gaming like Parsec or Nvidia Gamestream with Moonlight. They use hardware acceleration for video encoding and may have better latency than RDP. https://parsec.app/ https://moonlight-stream.org/

Don't these and Stadia use RDP under the hood?

Afaik for both Parsec and Moonlight the video is a capture of the screen encoded in h264 or h265 and streamed to the remote client. They may be based on RDP for input but I don't think that's the case.

Moonlight is open-source, you can see in the code yourself as I don't understand most of it. There is also a project that attempt to replace the associated Nvidia Gamestream server but it is quite basic and no longer maintained : https://github.com/loki-47-6F-64/sunshine

Re: Raspberry Pi as x2go “thin” client

#56

Post by zamadatix » Sun, Jan 24, 2021, 5:17 PM UTC

gruez wrote: post #53

zamadatix wrote: post #51

Earlier quoted context omitted.

Not really, OS wise it can't be Home edition but because Homedoesn't officially support hosting RDP at all. Hardware wise it requires basically "a gpu", even a low end decade old integrated Intel GPU will work.

Yeah my use case isn't really some sort of RDI farm, but just a way to access one of my existing machines which I also happen to use physically. For that use case RDP (without remotefx) works fine, but it doesn't look like setting up remotefx would be easy.

I think you might be reading about RemoteFX vGPU or something else in the RemoteFX family? If so that's a different thing than RemoteFX for RDP. The latter is literally just enabling a couple Group Policies in gpedit - otherwise it's exactly the same as running normal RDP.

Re: Raspberry Pi as x2go “thin” client

#57

Post by wkearney99 » Sun, Jan 24, 2021, 5:27 PM UTC

raphinou wrote: post #33

posix_me_less wrote: post #28

Earlier quoted context omitted.

Do you know if there is a functioning xrdp server+client combination for Linux? I would like to try to compare to x2go. I tried some on opensuse last year but it didn't work.

I'm successfully using the packages in ubuntu focal (20.04, the latest LTS). It was nearly straight-forward: install and run xrdp on the server, install package freerdp2-x11 on the client. The only unintuitive thing was the keyboard mapping to use, specified with an awkward value passed to the /kbd flag.

well, there's also the audio issues. pulseaudio config for remote use isn't always reliable. but otherwise, yeah xrdp works great for access from machine that already have the client installed.

Re: Raspberry Pi as x2go “thin” client

#58

Post by gruez » Sun, Jan 24, 2021, 6:48 PM UTC

zamadatix wrote: post #56

gruez wrote: post #53

Earlier quoted context omitted.

Yeah my use case isn't really some sort of RDI farm, but just a way to access one of my existing machines which I also happen to use physically. For that use case RDP (without remotefx) works fine, but it doesn't look like setting up remotefx would be easy.

I think you might be reading about RemoteFX vGPU or something else in the RemoteFX family? If so that's a different thing than RemoteFX for RDP. The latter is literally just enabling a couple Group Policies in gpedit - otherwise it's exactly the same as running normal RDP.

Which group policies are you talking about? Are they the policies for enabling AVC encoding? eg.

https://admx.help/?Category=Windows_10_2016&Policy=Microsoft...

Re: Raspberry Pi as x2go “thin” client

#59

Post by zamadatix » Sun, Jan 24, 2021, 11:30 PM UTC

gruez wrote: post #58

zamadatix wrote: post #56

Earlier quoted context omitted.

I think you might be reading about RemoteFX vGPU or something else in the RemoteFX family? If so that's a different thing than RemoteFX for RDP. The latter is literally just enabling a couple Group Policies in gpedit - otherwise it's exactly the same as running normal RDP.

Which group policies are you talking about? Are they the policies for enabling AVC encoding? eg. https://admx.help/?Category=Windows_10_2016&Policy=Microsoft... https://admx.help/?Category=Windows_10_2016&Policy=Microsoft... https://admx.help/?Category=Windows_10_2016&Policy=Microsoft...

Every nerd knob for RDP host configuration can be found under this tree in the group policy editor https://i.imgur.com/PtN0fNt.png

The 2 you need to enable to just enable RemoteFX are "Use hardware graphics adapters for all Remote Desktop Service sessions" to Enabled and "RemoteFX for Windows Server 2008 R2/Configure RemoteFX" to "Enabled". These 2 should net you GPU acceleration in the remote session.

For GPU accelerated encoding you can also set "Configure H.264/AVC hardware encoding for Remote Desktop Connections" to "Enabled".

Those 3 policies are all I usually tick but the rest of the policies in that tree are nerd knob tunables with many relating to bandwidth/resource utilization/image quality tradeoffs if that so interests you.