For the newer Raspberry Pis ssh is turned off by default, perhaps we should add a note describing how to address that? I believe the solution is to add a file named ssh to the boot partition.
adding an “ssh” file to the boot partition is a hack to the openssh package the pi foundation added for their PiOS, I do not think this hack exists in any official ubuntu image.
I just installed on a raspberry pi 4. 2 short comment:
i, HDMI is switched off default, so only ssh access is working. It could be mentioned somewhere
ii, unattended upgrade is installed, so ‘sudo apt upgrade’ fail by default, because auto update is in progress.
HDMI is working fine here on all my test installs (and it would indeed be odd (and a blocking bug) if it would not)…
well, it does that once per day (you can adjust it) so i guess you had some bad timing … but after all it is just doing what you just wanted it to do anyway with that command, isnt it ?
windows https://downloads.raspberrypi.org/imager/imager_latest.exe
macos https://downloads.raspberrypi.org/imager/imager_latest.dmg
ubuntu x86 https://downloads.raspberrypi.org/imager/imager_latest_amd64.deb
To install on Raspberry Pi OS, type `sudo apt install rpi-imager` in a Terminal window.
Installed server and xubuntu-desktop without issue, however the wifi manager does not work. I am still connected to my wifi though. I am guessing because it is “hard wired” per the instructions for getting wifi to work pre desktop install.
How do I undo the hard wire and let the network manager manage my wifi?
Suggest this be added to the instructions.
Good tutorial, but I could never get Wifi to work by editing the config file before first boot. And even the ethernet was a pain. Probably add that one may have to run sudo dhclient eth0 in order to bring the ethernet up, that’s what I had to do in order to get a connection. Very frustrating setup process, haha. Perhaps add the commands to use NetworkManger cli to add a wifi network if you missed the first boot or its not working with the initial boot config file.
May I suggest an example of editing the network-config file to give the server a static IP address. Then you don’t need to do all the hunting in arp for the address
Hey Francis o/ - Good idea, would you mind suggesting exactly how you would amend the current tutorial? Then I can publish your suggestion? (We’re working on a better way for helpful folks like you to more easily contribute your ideas)
If you want to use your local lan’s DHCP server to get an IP address for your pi then there are two ways to get your Pi connected to the internet:
The first is to connect your Pi to your router with an ethernet cable. In this case, you can skip this step and go to the next one in the tutorial.
The second requires a local Wi-Fi network that both your computer and Pi can be connected to. We are going to edit files you just downloaded on your SD card to ensure your Pi can connect to the Wi-Fi network at boot.
If you want to have the pi boot the pi to known IP address then see the section “Set a Static IP” below Wifi where you will edit the same file that the Wifi section tells you to modify
Then Section Set A Static IP
To set a static IP you need to replace the dhcp4: true
line in the network-config file with lines that specify the intended IP address of the pi as well as its default gateway and DNS server. You can do this for either the eth0 or wlan0 interface (or both). It is important that you get the indenting right for this work correctly
For example if you were planning to give the pi the address 192.168.1.23 in the 192.168.1.0/24 subnet with a default gateway of 192.168.1.1 and a DNS server of 192.168.1.53 then the following text would work.