on first boot rpi2 cannot configure (core16)

[Greg Lutostanski]

On first boot when console-conf tries to come up, I get the following traceback. Before it stays around long enough it goes away. And asks me to "hit enter to configure". So I am stuck in a loop of hitting enter twice forever with this traceback after the second screen.

Screenshot of traceback issue here: http://imgur.com/a/5274U

Video of occurrence (please ignore clutter), here: https://drive.google.com/open?id=0B2wVCMf_bYxhbXEtV0JGVHd2eTg

This happens on first boot, my first experience with core 16.

Thanks!

[Greg Lutostanski (lutostag)]

Looks like it was a wireless dongle that was the issue, I switched out to a different and that let me proceed.

Still we should fail cleaner in this case. Perhaps let it show up in network device list as broken if we can't enumerate all the info we need?

[Michael Hudson-Doyle (mwhudson)]

Thanks for the screenshot :-)

This should be fixed in the edge core snap, can you try that instead?

[Greg Lutostanski (lutostag)]

Steps:
1) Proceed with normal rpi2 install with working dongle (and verified bad dongle still saw problem).
2) Enabled user-password login.
3) Was on core rev 396, changed to edge (645).
4) Plug in bad dongle
5) reboot
6) login locally
7) sudo console-conf

Confirmed there is no crash (could not confirm network settings worked -- it kept saying network connection timed out after I input/it had the correct info from last time), so rebooted from ssh and lost network connectivity (oh, well. will reflash, but this bug is confirmed to be fixed in edge).

It also did not list the device at all as the choices (nor did it show up in /sys/class/net nor anywhere else).

Can the released images get updated, or is there any way I can at an edge rpi2 image rather than the released one?

[Michael Hudson-Doyle (mwhudson)]

On 8 December 2016 at 08:04, Greg Lutostanski <email address hidden>
wrote:

> Steps:
> 1) Proceed with normal rpi2 install with working dongle (and verified bad
> dongle still saw problem).
> 2) Enabled user-password login.
> 3) Was on core rev 396, changed to edge (645).
> 4) Plug in bad dongle
> 5) reboot
> 6) login locally
> 7) sudo console-conf
>
> Confirmed there is no crash (could not confirm network settings worked
> -- it kept saying network connection timed out after I input/it had the
> correct info from last time), so rebooted from ssh and lost network
> connectivity (oh, well. will reflash, but this bug is confirmed to be
> fixed in edge).
>
> It also did not list the device at all as the choices (nor did it show
> up in /sys/class/net nor anywhere else).
>

Well that's not ideal either, but kinda a different bug I guess (in the
kernel I suppose if it's not in /sys/class/net). Can you dig out
/var/log/console-conf/subiquity-debug.log from the sd card and put it
somewhere I can see it? Also syslog I guess.

> Can the released images get updated, or is there any way I can at an edge
> rpi2 image rather than the released one?
>

You can make your own image using the edge snaps via something like:

$ wget
http://people.canonical.com/~vorlon/official-models/pi2-model.assertion
$ snap install --edge --devmode ubuntu-image
$ ubuntu-image -c edge pi2-model.assertion

[Launchpad Janitor (janitor)]

[Expired for Snappy because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for subiquity because there has been no activity for 60 days.]