Boot needs up to 7 minutes on Ubuntu 16.04
#1
Hi together!

I need help with my Pine64 2GB RAM Board.

The problem is a very long boot time, if ethernet is unplugged. The systems hangs on "[XXXXXXXX] Call trace:".
Nothing else behind this note.
The system boots completely after 4-7 minutes, but only if ethernet is unplugged.
If ethernet is plugged in, the system starts within 1 minute.

It doesn't matter which version of Pine64 I'm using, because I already tried 512 MB, 1 GB and 2 GB of RAM.

Some information about my setup:
- Ubuntu 16.04 with updated kernel and U-Boot via update scripts.
- installed WiFi-/Bluetooth module.
- Static IP address via WiFi in /etc/network/interfaces and router.
- No connection via ethernet, just via WiFi.
- Samsung Evo microsd card.
- Official Pine64 power supply from Pine64 shop.
- Deleted standard MAC address.

Please help me with my little problem.

Best regards
Julian
My forum topics:
• Create a WiFi hotspot on Debian 8
• Turn your Pine64 into a music server with mpd
• Adjust brightness of LCD on Armbian Desktop with 1 click
• My cases for Pine64 (acryl, lego & wood)

• Pine 64 - DACH - Facebook page for german-speaking Pine64-fans.
  Reply
#2
(03-10-2017, 02:52 AM)JulianM Wrote: The problem is a very long boot time, if ethernet is unplugged. The systems hangs on "[XXXXXXXX] Call trace:".
Nothing else behind this note.
The system boots completely after 4-7 minutes, but only if ethernet is unplugged.
If ethernet is plugged in, the system starts within 1 minute.

Hi Julian,

This is happening because when your ethernet is unplugged, linux is still looking for your ethernet, and so keeps checking for five minutes, and then times out and allows bootup to continue.

You need to edit the /etc/networking/interfaces, and add the line

allow-hotplug eth0

to it. This tells the network manager the ethernet can be plugged in at any time... and isn't required at bootup.

Edit: refer to post #4 where I correct myself Wink
  Reply
#3
Hi pfeerick,

thanks for your reply, but it doesn't fixed the problem.
I changed the "timeout" in /etc/dhcp/dhclient.conf from 300 to 10 seconds.
This solutions doesn't fixed the problem, but this is a "good enough" solution for me.

Best regards
Julian
My forum topics:
• Create a WiFi hotspot on Debian 8
• Turn your Pine64 into a music server with mpd
• Adjust brightness of LCD on Armbian Desktop with 1 click
• My cases for Pine64 (acryl, lego & wood)

• Pine 64 - DACH - Facebook page for german-speaking Pine64-fans.
  Reply
#4
(03-13-2017, 04:44 PM)JulianM Wrote: Hi pfeerick,

thanks for your reply, but it doesn't fixed the problem.
I changed the "timeout" in /etc/dhcp/dhclient.conf from 300 to 10 seconds.
This solutions doesn't fixed the problem, but this is a "good enough" solution for me.

Best regards
Julian

My apologies... I mean to say "replace", not add :-O

in your /etc/network/interfaces file, if it currently contains the auto eth0 line, replace it with allow-hotplug eth0 

If /etc/network/interfaces contains a line saying source-directory /etc/network/interfaces.d  you instead need to instead be looking at and editing /etc/network/interfaces.d/eth0

That should fix cure your no-ethernet boot woes. Wink
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Ethernet --> Causing boot loop podtofs 3 5,225 05-16-2017, 03:41 AM
Last Post: m17

Forum Jump:


Users browsing this thread: 1 Guest(s)