7,612
edits
Changes
Jump to navigation
Jump to search
http://c-nergyAlso, create a launcher on the desktop with the same info.be/blog/?p=13972
no edit summary
This page details the build of our [[DIGITS DevBox]]. There's also a page giving information on [[Using the DevBox]]. nVIDIA, famous for their incredibly poor supply-chain and inventory management, have been saying [https://developer.nvidia.com/devbo "Please note that we are sold out of our inventory of the DIGITS DevBox, and no new systems are being built"] since shortly after the [https://en.wikipedia.org/wiki/GeForce_10_series Titax X] was the latest and greatest thing (i.e., somewhere around 2016). But it's pretty straight forward to update [https://www.azken.com/download/DIGITS_DEVBOX_DESIGN_GUIDE.pdf their spec].
==Introduction==
And change into the sample directory and run the tests:
cd /usr/local/cuda-10.10/samples/bin/x86_64/linux/release ./deviceQuery ./bandwidthTest
Everything should be good at this point!
https://helpdeskgeek.com/how-to/tunnel-vnc-over-ssh/
====Connection Issues==== Coming back to this, I had issues connecting. I set up the tunnel using the saved profile in puTTY.exe and checked to see which local port was listening (it was 5901) and not firewalled using the listening ports tab under network on resmon.exe(it said allowed, not restricted under firewall status). VNC seemed to be running fine on Bastard. , and I set up the tunnel using puTTY.exe and then tried connecting to localhost::1 (that is 5901 on the localhost, through the tunnel to 5902 on Bastard) using VNC Connect by RealVNC.The connection was refused. I checked it was listening and there was no firewall: netstat -tlpn tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN 2025/Xtightvnc ufw status Status: inactive The localhost port seems to be open and listening just fine: Test-NetConnection 127.0.0.1 -p 5901 So, presumably, there must be something wrong with the tunnel itself. '''Ignoring the SSH tunnel worked fine: Connect to 192.168.2.202::5902 using the TightVNC (or RealVNC, etc.) client.'''
===RDP===
vi /etc/X11/Xwrapper.config
allowed_users = anybody
This was promising as it was previously set to consol.
https://www.linuxquestions.org/questions/linux-software-2/xrdp-under-debian-9-connection-problem-4175623357/#post5817508
apt-get install xorgxrdp-hwe-18.04
Couldn't find the package... This lead was promising as it applies to 18.04.02 HWE, which is what I'm running
https://www.nakivo.com/blog/how-to-use-remote-desktop-connection-ubuntu-linux-walkthrough/
dpkg -l |grep xserver-xorg-core
ii xserver-xorg-core 2:1.19.6-1ubuntu4.3 amd64 Xorg X server - core server
Which seems ok, despite having a problem with XRDP and Ubuntu 18.04 HWE documented very clearly here: http://c-nergy.be/blog/?p=13972
There is clearly an issue with Ubuntu 18.04 and XRDP. The solution seems to be to downgrade xserver-xorg-core and some related packages, which can be done with an install script (https://c-nergy.be/blog/?p=13933) or manually. But I don't want to do that, so I removed xrdp and went back to VNC!
apt remove xrdp
===Other Software===
I installed the community edition of PyCharm:
snap install pycharm-community --classic
#Restart the local terminal so that it has updated paths (after a snap install, etc.)
/snap/pycharm-community/214/bin/pycharm.sh
On launch, you get some config options. I chose to install and enable:
*IdeaVim (a VI editor emulator)
*R
*AWS Toolkit
Make a launcher: In /usr/share/applications:
vi pycharm.desktop
[Desktop Entry]
Version=2020.2.3
Type=Application
Name=PyCharm
Icon=/snap/pycharm-community/214/bin/pycharm.png
Exec="/snap/pycharm-community/214/bin/pycharm.sh" %f
Comment=The Drive to Develop
Categories=Development;IDE;
Terminal=false
StartupWMClass=jetbrains-pycharm
