Skip to main content

[pi] Headless pi connection with VNC on Mac system

Sometimes we have to access our pi with limited resources like lacking of monitor or keyboard. The Headless mode is useful to connect to your pi with another computer or your laptop without additional screen!
Now let’s get started to give it a try!

Setting Raspberry pi board

Connection to pi
connect to raspberry pi board with 

ssh pi@rapberrypi.local

and input your password(Default password has been setted to raspberry)

Configue the VNC
Input

sudo raspi-config

Navigate to Advance Option
enter image description here

Select [P3 VNC] and click [OK]
enter image description here
After setting up of the VNC, reboot the pi

sudo reboot

On Mac

Downlaod VNC viewer from:
https://www.realvnc.com/en/download/viewer/

enter image description here

After installed the VNC viewer, Input the IP address of raspberry pi and click Continue.
enter image description here
Now we have successfully connect to our pi with VNC!
enter image description here

Improve the resolution

We have justed connected to the pi with VNC. However, the screen is quite small and the resolution wasn’t really good. How can we improve it?

Let SSH to our pi gain with

ssh pi@192.168.1.110

(192.168.1.110 is my pi’s address)
Now we need to modify the config.txt setting for better VNC viewer resolutions.

sudo nano /boot/config.txt

uncomment and change the HDMI settings

hdmi_group=5
hdmi_mode=85
hdmi_ignore_edid=0xa5000080

hdmi_mode=85 represents the resolution of HDMI mode will be setted into 1280x720.
enter image description here
after the parameter setting, click [Ctrl+X] and click [Y] and [Enter] to modify the config.txt file.

After all the setting processs, we can now reboot the machine.

sudo reboot

Connect again with VNC Viewer

If everything goes well. The resolution of HDMI mode will be setted to 1280x720 like the screen shot showing below :-D
enter image description here

Happy piING~

Labels:

Comments

Post a Comment

Popular posts from this blog

[MinGW] Fix [Linker error] undefined reference to '_imp__curl_easy_init'

Recently, I found some error during the compiling progress of my curl program with Code::Blocks. The error keep showing in Code::Blocks like this: [Linker error] undefined reference to `_imp__curl_easy_init' I try to repair the Linker settings and Search directories but found out that there’s nothing wrong with it. It turns out the MinGW version has been modified to Win64 version last time when I was trying to deal with some W64 programs few days ago. I found that the MinGW download directly from the official website cannot be used in Code::Block properly. Hence, I use tdm-gcc instead . Here’s the procedure to fix the curl reference error. Download the tdm32 bundle from: http://tdm-gcc.tdragon.net/ Install MinGW/TDM(32-bit) by just clicking Next in the next few steps After the installation process, the MinGW will be installed under C:\TDM-GCC-32 Open your Code::Blocks program and go to Settings>Compiler Change the setting as followed Now th...
Post a Comment
Read more

[curl]First curl program with Code::Block

Code::Block is tiny powerful cross-platform IDE for C/C++ program. However, the pre-installed complier is 32-bit. Both curl and openSSL is needed in this tutorial. Hence, it is really important to make sure if they are also installed accordingly. Compiler of your Code::Block can be check from: Setting>Toolchan executables It shows that the compiler is located at C:\MinGW and it is Win32 based. Both Curl and openSSL need to be download for this tutorial.It is highly recommended to install all the program with win32 version!! 1. Download and install the openSSL openSSL can be download from this location. https://slproweb.com/products/Win32OpenSSL.html In this demo, full version of v1.1 is installed. The openSSL folder will be located at C:\OpenSSL-Win32 2. Download and install curl You can find the guideline to setup curl properly from previous article. Just need to remind again that Win32 version is needed in this case. https://aconcaguac...
Post a Comment
Read more