Jump to content

Slow boot after update


windwalker78

Recommended Posts

               Hi,

 

              Initially my Armbian_5.75_Orangepilite_Ubuntu_bionic_next_4.19.20 was booting fast. After the apt-get upgrade it boots very slowly:

 

[    7.747226] lima 1c40000.gpu: pp1 - mali400 version major 1 minor 1
[    7.747259] lima 1c40000.gpu: l2 cache 64K, 4-way, 64byte cache line, 64bit external bus
[    7.752757] [drm] Initialized lima 1.0.0 20170325 for 1c40000.gpu on minor 1

 

I wait for 10 minutes from the above row to the login below:

 

Ubuntu 18.04.2 LTS homesystem ttyS0

homesystem login:

 

Any idea what could be the issue? This is already with loglevel 7 on boot debug.

 

Regards

 

Link to comment
Share on other sites

Actually dmesg, returns a couple more rows:

 

[    8.820618] zram: Added device: zram0
[    8.821346] zram: Added device: zram1
[    8.822184] zram: Added device: zram2
[    8.822872] zram: Added device: zram3
[    8.823426] zram: Added device: zram4
[    8.823959] zram: Added device: zram5
[    8.892129] zram1: detected capacity change from 0 to 64516096
[    9.915956] random: crng init done
[    9.915965] random: 7 urandom warning(s) missed due to ratelimiting
[    9.944798] Adding 63000k swap on /dev/zram1.  Priority:5 extents:1 across:63000k SSFS
[    9.954371] zram2: detected capacity change from 0 to 64516096
[    9.977844] Adding 63000k swap on /dev/zram2.  Priority:5 extents:1 across:63000k SSFS
[    9.980549] zram3: detected capacity change from 0 to 64516096
[   10.004868] Adding 63000k swap on /dev/zram3.  Priority:5 extents:1 across:63000k SSFS
[   10.006954] zram4: detected capacity change from 0 to 64516096
[   10.031167] Adding 63000k swap on /dev/zram4.  Priority:5 extents:1 across:63000k SSFS
[   10.131826] zram0: detected capacity change from 0 to 52428800
[   10.290412] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard
[   18.085851] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.048549] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   45.040395] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   46.809320] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

 

 

Link to comment
Share on other sites

2 minutes ago, Igor said:

None without


armbianmonitor -u

and what do you use it for?

Thank you very much for the tip!

 

I just found out that this was a dhclient timeout issue.

Timeout 300, which is too much, but was not reported.

Set it to 20 and now is much better.

 

I don't need need Network manager and prefer my own scripts for networking, as the PI will be hostapd or client depending on the situation.

 

Regards,

Todor

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines