On 8 December 2016 at 08:04, Greg Lutostanski <[email protected]> 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646625 Title: on first boot rpi2 cannot configure (core16) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1646625/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
