Spiffberrpi | the setup steps

/ SprUng, KEEPERS, CODE-NOW-NOW-NOW, CHEAT SHEETS, Debugging, NOTES, Featured Today, raspberryPi / 6 minutes of reading

Ubuntu – wireless steps

https://help.ubuntu.com/stable/ubuntu-help/net-wireless-troubleshooting-hardware-check.html.en
https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide#:~:text=Troubleshooting%20Steps,-Troubleshooting%20wireless%20networks&text=Check%20that%20your%20wireless%20adapter,the%20Internet%3A%20see%20Wireless%20Connections.

spiffberrypi – usb

get img installer

burn to usb stick

login – at boootup screen (ubuntu server 20.04)

 

get info: 


ip address
ifconfig
sudo nano /etc/resolv.conf
nameserver 127.0.0.53
options edns0 trust-ad

FILES: 


sudo nano /etc/netplan/00-install-config.yaml
sudo nano /etc/netplan/50-cloud-init.yaml

 

 

If you are using an ethernet cable and are not connected to the network at this point you may need to run:

sudo dhclient eth0

 

gets you 192.168.*.**/**

REBOOT

 

then get network access up – so you can sudo apt update

 

1. You need 3 pieces of info in order to setup your WiFi:

  • Raspberry Pi wireless card name on your system;
  • WiFi router name you are trying to login (SSID), and
  • WiFi login password

You should already know your WiFi login name and password, the only info we need is WiFi name.

To clearly illustrate how to setup, let’s assume that your WiFi login name is “MyWiFi” and your password is “MyPass”.

2. Find WiFi card name:

$ ls /sys/class/net
eth0  lo  wlan0

also
ip address

on my machine, it’s “wlan0”. To simplify our demo, assume that yours is “wlan0” as well.

3. Edit network configuration file to add WiFi info:

first make a copy of original file 
sudo cp /etc/netplan/50-cloud-init.yaml /etc/netplan/50-cloud-init.yaml.orig
then edit - 
sudo nano /etc/netplan/50-cloud-init.yaml

you will see the following in the original file:

img

After adding your WiFi info such that it should look something like the following:

img

4. Make sure that the 3 pieces of info above is replaced with yours.

  • wlan0
  • MyWiFi
  • MyPass

And also please make sure that you are a very careful person to input the above info with exact format as original file started, and all indents should be typed with spaces (4 spaces each level), NOT tabs, which is very important!

checck config

 

sudo netplan --debug apply
sudo systemctl enable wpa_supplicant
sudo systemctl start wpa_supplicant
sudo netplan generate
sudo netplan apply

 

5. Save the file and reboot

you should have your WiFi setup when the machine is up and running again.

 

IP 192.168.*.**/** wlan0

image-20220714145528956

image-20220714145545144

After Setup

 

$ sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
and put the following line in it and save the file:
network: {config: disabled}

 

THen run sudo apt update

and make suer it is connnecting to outside world

 

Enable SSH

  1. Open the terminal with Ctrl+Alt+T and install the openssh-server package:

    sudo apt update
sudo apt install openssh-server

    When prompted, enter your password and press Enter to continue with the installation.

    ubuntu install ssh

  2. Once the installation is complete, the SSH service will start automatically. You can verify that SSH is running by typing:

    sudo systemctl status ssh

    The output should tell you that the service is running and enabled to start on system boot:

    ● ssh.service - OpenBSD Secure Shell server
    Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
    Active: active (running) since Mon 2020-06-01 12:34:00 CEST; 9h ago
...

    Press q to get back to the command line prompt.

  3. Ubuntu ships with a firewall configuration tool called UFW. If the firewall is enabled on your system, make sure to open the SSH port:

    sudo ufw allow ssh

That’s it! You can now connect to your Ubuntu system via SSH from any remote machine. Linux and macOS systems have SSH clients installed by default. To connect from a Windows machine, use an SSH client such as PuTTY .

 

Install Desktop

sudo apt-get update && sudo apt-get upgrade

 

1. install manager

sudo apt-get install lightdm

 

1a Switch between LightDM and GDM in Ubuntu
Open a terminal and use the following command:


sudo dpkg-reconfigure gdm3

gets you to choice screen

installer tool


sudo apt install tasksel

 

install desktop

 

a) You can also run the following command and select the software to install from a predefined collection of software:


tasksel

 

When prompted, choose Ubuntu desktop to install the chosen desktop environment.

 

b) OR JUST UNBUNTU


sudo tasksel install ubuntu-desktop

 

Use the space key to choose the desktop environment to be installed; hit the tab key to move the focus from the list of software to the OK button at the bottom, and hit enter.

 

c) NO TASKEL

 

Alternatively, you can also run the following sudo apt-get command to install ubuntu-desktop without using tasksel:

sudo apt-get install ubuntu-desktop

 

You can use the aforementioned apt-get command for installing any of the popular desktop environments.

 

5) reboot

 

set as default

If, however, your system doesn’t prompt a GUI and still returns you to the command-line interface for any reason, please run the following command to set the default interface on your system once and for all.

sudo systemctl set-default graphical.target

This command will ensure that your Ubuntu system defaults to the newly installed graphical target for the GUI..

 

Remote Access to GUI port: 3389

It’s an everyday use case to access your Ubuntu machine remotely. If you want to do that, you’ll need to install a remote desktop application like Xrdp. You can use the following command to do that:

sudo apt-get install xrdp

 

After installing the remote desktop application, you would need to add it to the ssl-cert group. You can do that by running the following command:

sudo adduser xrdp ssl-cert

Now, you should be good to remotely connect to your freshly installed Ubuntu desktop with a GUI using port 3389.

 

 

 

More GUIs

 

Installing more than one GUI is straightforward to install more than one GUI on the Ubuntu server.

You can choose to switch between different GUIs by pressing the F1 key; doing that will toggle between GUI sessions. Apart from the GNOME, there are several other well-maintained GUIs that you can choose from, such as Xfce core server desktop, Xubuntu core server desktop, Lubuntu core server desktop, Cinnamon core server desktop, Budgie core server desktop, Mate core server desktop, KDE core server desktop, Kubuntu core server desktop, and so on.

Changing the GUI on Ubuntu doesn’t change the installation process by a lot if you’re using tasksel. For example, if you want to install Xubuntu GUI, you can do that using the following command:

sudo tasksel install xubuntu-desktop

Notice that this command is the same as the command you ran to install the GNOME desktop, except that you’re now installing Xubuntu-desktop instead of ubuntu-desktop.

Some of the similar commands to install different GUIs are listed below:

sudo tasksel install lubuntu coresudo tasksel install ubuntu mate

Note that multiple GUIs are completely optional.

 

Bluetooth

20.04 solution ([source FR]):

Install the pi-bluetooth package:

sudo apt-get install pi-bluetooth

Edit the /boot/firmware/usercfg.txt file to add the following line at the end:

include btcfg.txt

Reboot:

sudo reboot

Check that the device is detected:

hciconfig -a

hci0:   Type: Primary  Bus: UART
    ...

 

How to display your Raspberry Pi’s desktop on a Mac

I typically connect to my Raspberry Pis via SSH from my main machine, a Mac. This is fine for pretty much all of the tasks I perform on the Pis, but it only provides access to the commmand line. That’s not a problem for me, but I nonetheless wondered whether I might be able to access the Pi’s desktop UI remotely too.

 

Pi screen sharingMy Pi Zero’s desktop within my Mac desktop

It turns out that you can, using VNC (Virtual Network Computing). VNC is a standard, widely supported way of securely presenting a GUI remotely over a network connection. You need a suitable server running on the machine that will be sharing its desktop, and a client app to present that desktop on the computer you’re accessing the remote machine from. The client relays your mouse and keyboard input back to the remote computer.

The Raspberry Pi Foundation recommends a specific VNC server, tightvncserver, written by TightVNC Software. You can install in the usual way:

sudo apt-get install tightvncserver

When the software has downloaded and installed, it’s ready to run:

tightvncserver

You will be asked to set up an remote access control password and to enter it a second time, as verification. You’ll also be asked if you’d like to enter a password for view-only access. This is optional; I just entered ‘n’ for no.

The server is now running and, if you set it up using SSH, you can log out of the Pi if you wish.

TightVNC doesn’t supply a client for Mac OS X, though it does offer a client for Windows and a cross-platform client that runs under Java. I’m not a fan of cross-platform tools — you tend to lose the benefits of your preferred OS — so I wondered if there was a native Mac OS X VNC client. There is and it comes free with your Mac, though you might never have seen it before.

Apple has long provided Apple Remote Desktop (ARD), a tool for remotely accessing Mac desktops. Over the years, it has gained support for a variety of remote access technologies, including VNC.

ARD doesn’t live in the Applications folder — it’s actually buried deep in the System folder — but it can be launched via finder: just hit Command-K to invoke the standard Mac ‘Connect to Server’ dialog. Here, enter

vnc://pi.local:5901

and click on ‘Connect’. The ‘vnc’ at the start sets the protocol you’ll use to connect to your remote Pi, which is identified here by its Bonjour (mDNS) name: its hostname (typically set using raspi-config followed by .local). The number after the colon is the port through which the communication takes place. tightvncserver defaults to VNC port 1. 5900 is the base VNC port, hence 5901.

Pi Screen SharingPoint to your Pi using the standard ‘Connect to Server’ dialog

You’ll now be asked for the remote desktop’s access password. This is the password you set through tightvncserver, not your regular Pi password (they can be the same, of course, though it’s perhaps best to use different ones, for tighter security). You can choose to save the password in the keychain for faster access next time.

Pi Screen SharingConnect Screen Sharing to your Pi desktop server

All going well, you’ll now see your Pi’s X desktop appear in a window provided by an ARD app called Screen Sharing. Depending on your Pi (the faster the better) and the quality of your network connection (ditto), the desktop is quite useable. You might not want to do all of your Pi work this way, but it’s acceptable for occasional use.

When you’re done, you can open shut down your Pi (using the Terminal or the Pi menu) or select ‘Close’ from Screen Sharing’s Connection menu.

By default tightvncserver establishes an 800 x 400 desktop, but you can change that using the -geometry switch. You can set the colour depth using the -depth switch too. For example:

tightvncserver -geometry 1920x1080 -depth 24

Of course, the bigger the desktop and the higher the colour depth, the more data that needs to be sent to Pi to Mac, and the slower and less responsive the remote system will feel. Experiment to find the size you prefer. I usually stick with the default. I also set my Pis to boot to the command line and not to auto log in, so they don’t run separate X sessions in the background.

Show more
Show less

No WIFI>

reinstall ifupdown package




sudo apt-get autoremove --purge ifupdown
sudo apt-get install ifupdown
Scroll to Top