MakerGram Logo

    MakerGram

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    • Users
    • Groups

    How to use Raspberry pi4 without display and keyboard with a VNC viewer.

    Raspberry Pi
    raspberrypi vnc putty
    3
    5
    303
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Abhay
      Abhay last edited by

      Raspberry Pi

      Screenshot from 2020-04-22 06-58-09.png

      The Raspberry Pi is a series of small single-board computers developed in the United Kingdom by the Raspberry Pi Foundation to promote the teaching of basic computer science in schools and in developing countries. The original model became far more popular than anticipated, selling outside its target market for uses such as robotics. Usually, it does not include peripherals (such as keyboards and mouse ) or cases but they can be attached via the USB ports

      Download the os image: https://www.raspberrypi.org/downloads/raspbian

      rpi image download.png

      Then flashing the memory card for booting os (minimum 8 GB recommended, can use balenaEtcher)
      After flashing open boot directory from the memory card

      • Create an empty file and rename it ssh (remove extensions if any)
      • Create another empty file and rename it wpa_supplicant.conf
      • Open wpa_supplicant.conf and copy the below code
        country=US
        ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
        update_config=1
        network={
        ssid="NETWORK-NAME"
        psk="NETWORK-PASSWORD"
        }

      Replace “NETWORK-NAME” with your network name and
      “NETWORK-PASSWORD” with the password of your network

      Find the IP of raspberry-pi (Rpi)
      You can install the Fing app in your smartphone and connect it to the same network as Rpi.
      Then find the IP of Rpi.

      Install PuTTY SSH client

      putty.png

      • Type the IP of Rpi in the Host Name.
      • Then click open. Then a terminal opens asking your username and password. By default, the username will be pi and password raspberry.
      • Type sudo raspi-config.
      • In the window that appears activate VNC by moving the arrow key.

      Now to use VNC viewer
      Download it from:https://www.realvnc.com/en/connect/download/viewer

      • Install VNC viewer
      • Enter the IP of pi in the window that opens.
      • Enter the username and password.

      If the display is not available
      Type sudo raspi-config
      Go to advance settings.
      Adjust resolution by selecting the appropriate one.

      1 Reply Last reply Reply Quote 4
      • salmanfaris
        salmanfaris last edited by

        Thanks for the tip @Abhay. keep in mind, after flashing the OS to the SD card, it will not open the window machine because Windows is only able to manage only its own partitions (fat16, fat32, ntfs, exfat).

        so you need to software that can read Linux ext format for you, I used Ext2Read, and it does the job.

        Capture.PNG

        Abhay 1 Reply Last reply Reply Quote 2
        • Abhay
          Abhay @salmanfaris last edited by

          @salmanfaris Thanks for reminding about windows machine partitions and insight about using Ext2Read.

          For Linux users, can skip the process of installing PuTTy SSH Client since SSH client are installed in Linux by default.
          Open terminal and type: **

          • ssh pi@ipaddress //Replace ipaddress with IP address of your pi.
            then enter the username (by default: pi)
            password (by default: raspberry)

          Download and install deb package for VNC viewer.

          1 Reply Last reply Reply Quote 0
          • kowshik1729
            kowshik1729 last edited by

            @Abhay and @salmanfaris . This post is a life saviour to many of us. I use to face lot of issues for the headless setup of Raspberry pi. I finally fail with headless setup and use to borrow a screen from my friends and set it up. Seems like this post will help me out for sure.

            Thanks again for the post @Abhay. 😊 😊

            Abhay 1 Reply Last reply Reply Quote 1
            • Abhay
              Abhay @kowshik1729 last edited by

              @kowshik1729
              We couldn't find monitor during a hackathon and it cost the majority of our time to set up pi, this was the alternative that saved us back then.

              Hope it will be helpful for you to @kowshik1729

              1 Reply Last reply Reply Quote 2
              • First post
                Last post

              Recent Posts

              • Testing Raspberry Pi's Camera Module 3 (NEW for 2023)

                • read more
              • 1666287f-258d-437d-b2c5-91851d08617c-image.png
                The classic compact camera for Raspberry Pi with a 12MP sensor and autofocus

                Available from $25 with your choice of standard and wide lenses, with or without an infrared filter

                bf34763e-5ba3-4962-8e92-75583fd1e96c-image.png

                More details: https://www.raspberrypi.com/products/camera-module-3/

                Raspberry Pi Camera Module 3 - Autofocus cameras!

                Resource:
                Documentation: https://www.raspberrypi.com/documentation/accessories/camera.html
                Camera Software: https://www.raspberrypi.com/documentation/computers/camera_software.html

                • read more
              • Hey @rafitc99 ,

                Did your issue resolve? Curious to know 😊

                • read more
              • @rafitc99 said in NMCLI AP Mode config error | Connection activation failed: No suitable device found for this connection | Raspberry Pi 3 Model B Rev 1.2:

                host="MyRPiAPMode"
                sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host
                sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
                sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk
                sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword"
                sudo nmcli radio wifi on
                sudo nmcli con up $host

                Hi @rafitc99, Are you able to set up the AP when trying the commands individually?

                • read more
              • I was trying to configure AP mode in Raspberrypi by using Network Manager. I'm using the below script. but it is throwing some errors.

                Bash Script to set AP Mode

                host="MyRPiAPMode" sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword" sudo nmcli radio wifi on sudo nmcli con up $host

                Error ----

                Connection 'MyRPiAPMode' (60965f2a-f510-48ef-afaf-0864242d0c06) successfully added. Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name)).

                nmcli con (After script execution)

                NAME UUID TYPE DEVICE Wired connection 1 9589ff1a-9923-3de3-a8a4-90b319661878 ethernet eth0 MyRPiAPMode 60965f2a-f510-48ef-afaf-0864242d0c06 wifi --

                nmcli dev

                DEVICE TYPE STATE CONNECTION eth0 ethernet connected Wired connection 1 wlan0 wifi unavailable -- lo loopback unmanaged --

                I tried to make it availble via sudo nmcli radio wifi on
                But not working.

                this is the log

                -- Journal begins at Sat 2021-08-07 09:28:21 IST. -- Aug 10 15:06:19 NWPI-b5b072 NetworkManager[16140]: <info> [1660124179.9816] audit: op="connection-update" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" args="802-11-wireless-security.psk" pid=25120 uid=0 result="success" Aug 10 15:06:20 NWPI-b5b072 NetworkManager[16140]: <info> [1660124180.0902] audit: op="radio-control" arg="wireless-enabled" pid=25125 uid=0 result="success" Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4241] agent-manager: agent[641f99ab55d9691c,:1.692/nmcli-connect/0]: agent registered Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4281] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0573] agent-manager: agent[70ee130ba0f26cd7,:1.696/nmcli-connect/1000]: agent registered Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0614] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0370] agent-manager: agent[cc77ef461499c164,:1.700/nmcli-connect/0]: agent registered Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0414] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8406] agent-manager: agent[79b01af218789b42,:1.702/nmcli-connect/0]: agent registered Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8446] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))."

                • read more
              By MakerGram | A XiStart Initiative | Built with ♥ NodeBB
              Copyright © 2021 MakerGram, All rights reserved.
              Privacy Policy | Terms & Conditions | Disclaimer | Code of Conduct