Unable to boot successfully when using advanced options with Ubuntu Server 20.04.3 LTS

[saltedlolly]

When trying to use advanced mode to enable SSH, set hostname, password etc. with Ubuntu Server 64-bit the screen goes blank towards the end of the boot process when booting from the Pi 4 8Gb. No errors are displayed on the screen - the display seems to cut out.

[lurch]

Duplicate of #213 ?

[MiguelNdeCarvalho]

Hey, I have the same bug, however I'm using Ubuntu Server 21.04 64 Bits.

[trojan-xs]

I have the exact same issue.
Ubuntu server 20.04.3 LTS on 32 bits
Running on Raspberry Pi 3B+ 1GB

[suabahasa]

I have the exact same issue.
Is there any workaround? I didn't have a wired keyboard to do first-run wizard

[lurch]

Is there any workaround? I didn't have a wired keyboard to do first-run wizard

That's probably a question for the Ubuntu forums? 🤷

[saltedlolly]

Just a heads up in case people are unaware of this - I have since learnt that the Advanced Settings are only for customising Raspberry Pi OS and don't work with any other distros. The imager really doesn't make this clear, and it really should.

[lurch]

I have since learnt that the Advanced Settings are only for customising Raspberry Pi OS and don't work with any other distros.

Just like it says in the issue #213 that I linked to? 😉

[maxnet]

There is some experimental support for customizing Ubuntu server in git, if you are adventurous, and know how to compile it from source.
Not general release ready yet.

(Requires that you use the "use custom image file from disk" option for now. As it only does customization for images from the repository if they are marked there as supporting it, and that is not setup yet).

[saltedlolly]

There is some experimental support for customizing Ubuntu server in git, if you are adventurous, and know how to compile it from source. Not general release ready yet.

(Requires that you use the "use custom image file from disk" option for now. As it only does customization for images from the repository if they are marked there as supporting it, and that is not setup yet).

I'm pleased to hear that support for this is coming. It's a really useful feature to have. I'd love to be able to set the default user name as well - currently, you are stuck with 'pi'. IIIRC that's not possible to change at the moment.

[lurch]

I'd love to be able to set the default user name as well - currently, you are stuck with 'pi'. IIIRC that's not possible to change at the moment.

That's being discussed in #287

[guysoft]

Anyone knows if what fixes this is this: 8f9fbcf (First attempt at cloudinit support)?
Or this: 71c1ea2 ( Customization: also apply changes if there is only firstrun and no cmdline/config changes)?

I have custom ubuntu images and I am trying to figure out if I can build a CustomPiOS module for them that would get firstrun.sh working for them.

[maxnet]

Anyone knows if what fixes this is this: 8f9fbcf (First attempt at cloudinit support)?
Or this: 71c1ea2 ( Customization: also apply changes if there is only firstrun and no cmdline/config changes)?

Need both.

If you only cherry pick the first, it only applies custom settings if you also have an option selected that modifies config.txt, such as "disable overscan"

[guysoft]

Thanks, also worth mentioning this comment of yours since knowing that custom images work differently is also something important if you want to debug this :)
#324 (comment)

[colinwang1703]

What a coincidence, so am I. I also encountered this issue on Ubuntu Server 22.04 LTS 64-bit. Is there anyone too?
However, sometimes encountering this problem, sometimes burning it again and succeeding, strange!

[cillian64]

Closing as this should be resolved by cloudinit support which is now included in releases. Please re-open this if it still doesn't work with Ubuntu server.