I finally got this working, after several wasted hours. Skip using the image built-in to the Raspberry Pi Imager tool, and download the “preinstalled” image directly. I wrote up a brief about my experience.
Thanks for the tutorial! The example code for “network-config” seems to be incorrect. The lines below “wlan0” should be indented one more level. This is how the real “network-config” looks like and it would make more sense because those lines are the configuration for “wlan0”.
It seems YAML parser will not deal with the space in ': ’ required by cloud-init for the ssh_pwauth: yes thereby causing the server to default to non-password authentication.
I was able to boot up to the login prompt. I’ve read other posts about the login and password as “ubuntu”. That has not worked always getting the incorrect password. I’ve checked the wan0 script half a dozen times to make sure I’ve entered the wifi name/password correctly with the quotes. Still not able to login. Also, trying to get the IP using arp command yields nothing as well. Am I missing something???
Thanks,
Don
Thanks for the note on the 5GHz on your article. I was tearing my hair out with it not working for RP3 B+. And the issue was the 5GHz Wifi network. That apparently is not an issue on RP4 though
While the netboot process is fairly different from the standard process, the PoE process is highly similar, so I would like to see it being reflected in the tutorial.
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 ?