My latest project utilizes OpenSuse Leap on the Rapsberry Pi. Unfortunately it’s required quite a few tweaks and fixes to get the base image to a usable level. Now this isn’t necessarily as much of an obstacle as it is an opportunity, time to create a custom setup script for the ultimate Pi foundation!
As a second hurdle, I’m attempting to post all my fixes to github via CMD line. 🙂
One issue I’ve found written about on forums (without resolution) and experienced with much frustration is getting remote desktop via VNC to work on Fedora 24 server and newer. It seems like something has changed in the matrix and running the standard setup for vnc server on Fedora that worked on Fedora 19/20/21/22/23.. just doesn’t seem to work. Now as curious as I am, I’m not going to go install a VM of any of those versions of Fedora and track down the minutia of differences. What I will describe though is how to get it to work.
If you’ve been trying this and can’t seem to get it to work, the problem may lie on the TigerVNC viewer for Windows. For me the Windows VNC client keeps connecting properly but the screen is always blank. I noticed the vncserver instances that I started on my Fedora server were all 24 bit and the Windows TigerVNC viewer kept “connecting” to 32 bit sessions. What did work for me was switching to RealVNC viewer, the connection worked perfectly on my local server.
The step by step instructions are as follows:
This is a quick and easy bit of command line to check the integrity of your files. Many downloads can come with a md5 checksum file or you can create your own for your own files.
After running the compare command you will see if the files have been altered, be it by you or outside nefarious forces.
Create md5 file:
md5sum yourScript.sh otherConfig.sh > checksum.md5
Compare md5 file against files :
md5sum -c checksum.md5