*** This bug is a duplicate of bug 1425376 ***
https://bugs.launchpad.net/bugs/1425376
** This bug has been marked a duplicate of bug 1425376
Ubuntu Core provides no console login prompt if network is unavailable
--
You received this bug notification because you are a member of Ubuntu
Bug
@Martin,
Everything i shared was done in the BeagleBone Black latest image.
Cheers,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431836
Title:
Boot process takes too long when Ethernet is not con
@Oli: timesyncd is part of systemd, and it doesn't need any integration
with ifupdown. It listens for coming and going network connections by
itself and adjusts its wakeups according to network availability and
precision of the clock. I specifically enabled this because the snappy
team asked me to
i dont think timesyncd is seeded yet (or integrated in any way with if-
up/-down atm). i know there was work going on in the snappy team to fix
this though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Martin and Oliver,
Here're some things requested:
root@localhost:/home/ubuntu# grep -r . /etc/network/interfaces.d/
/etc/network/interfaces.d/usb0:auto usb0
/etc/network/interfaces.d/usb0:iface usb0 inet static
/etc/network/interfaces.d/usb0:address 192.168.7.2
/etc/network/interfaces.d/usb0:netw
Ah, thanks Oli for the explanation, that explains the identical start
time. Why isn't timesyncd working? I mean, I do see why it's not working
if you pull the ethernet plug, but it should work fine if you are
online?
** Changed in: snappy-ubuntu
Importance: Undecided => Low
--
You received th
we dont have timesyncd support yet.
fixrtc kicks in and sets the clock to the last mount time so you dont end up
with the clock set to the epoch (which is worse than only being off by the
image install time at least) ...
if the mount time (as seen by dumpe2fs) didnt change between the two boots
Ah, this is snappy, this explains all the errors about read-only
directories.
In the "with ethernet" case, boot started at 19:00:44, and eth0 DHCP is
done at 19:00:57, so 13 s. Then it spends half a minute or so in cloud-
init and click hooks, so that's not systemd's fault. So I consider the
"with
Ah, I forgot about interfaces.d/ .. can you please give me the output of
"grep -r . /etc/network/interfaces.d/" too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431836
Title:
Boot process takes t
Martin,
Thanks for looking at this. The content of /etc/network/interfaces is:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
Find attached the two files requested.
Kind regards,
** Attachment added:
A minute is really long; can you please do "journalctl -b > journal.txt"
and attach journal.txt here? Please do that for both cases (connected
and not).
What do you have in your /etc/network/interfaces?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug no
11 matches
Mail list logo
