![]() If I try to connect the VNC viewer now, it’ll connect just fine, but I’ll see nothing but black. Interestingly, the RealVNC server’s background process (or daemon in *nix terms) is running even though the desktop isn’t. You need to get the desktop running before there will be anything to look at. If you’re reading this section, then I assume your pi boots to the command line, so there’s no desktop to see right now. You’ll get an acknowledgement that the server was enabled, which you can dismiss, and then select “Finish” to exit raspi-config. Go to “Advanced Options”, and then select the “VNC” option.Īt the prompt, select “Yes” to enable the VNC server. If you want to log in remotely via SSH, make sure you run raspi-config and enable it before removing the monitor and keyboard, sudo raspi-config Note: With the November 2016 release of Raspbian, SSH is disabled by default. Either way, log in, get to a command line, and run raspi-config. Mine is not, so I’ll be connecting via SSH using PuTTY. If the Pi is still hooked up to a monitor and keyboard, you can do this directly from the Pi itself. If your Pi is set to boot straight to the desktop, then you can skip this section and move on to Method 2. Method 1 (if you’re booting to the command-line) The choice is yours, but I’m going to leave my Pi booting to the desktop for the moment, but I’ll walk you through two different ways to enable the RealVNC server. With the Pi 2 and 3, this becomes less of an issue, and the desktop environment really isn’t that much of a drag. This frees up resources for the other programs that I’m running. For servers, I usually like to leave the desktop disabled, and set the computer to boot to the command line (CLI). You can’t remote in to the desktop if it’s not running. If, for some reason, you don’t like RealVNC, or don’t want to use the latest version of Raspbian, you can still go back and read my instructions for installing X11VNC in the previous version of this post. Since the introduction of the Pixel desktop, Raspbian images have had a RealVNC server built right in. Sometimes, though, you just want to see a desktop, and that’s not easy when the computer you’re trying to see has no monitor, keyboard, or mouse.Īdding remote desktop abilities to the Raspberry Pi is now trivially easy. So far in this series, we’ve set up the Raspberry Pi for remote login via SSH. Reading the instructions is one thing, but watching it done demystifies the whole process. ![]() ![]() If you have a Pluralsight subscription, please consider watching it. Self-Promotion: I have recorded this series as a screencast for Pluralsight: ![]() Please refer to the series Introduction for a list of all the different posts in the series. If you’ve started from something other than a non-NOOBS Raspbian image, then you’ll probably need to adjust for that. If you are just trying to add one thing to an existing system that was not built following this series, then I cannot promise that these instructions will work for you, although they probably will. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |