Announcement

**comonda2** · Jul 29, 2018, 09:55 AM

ahmet@ahmet:~$ sudo systemd-analyze
[sudo] password for ahmet:
Startup finished in 7.223s (kernel) + 9.388s (userspace) = 16.612s
graphical.target reached after 9.380s in userspace
ahmet@ahmet:~$ sudo systemd-analyze blame
6.140s NetworkManager-wait-online.service
1.473s networkd-dispatcher.service
1.268s udisks2.service
1.260s ModemManager.service
1.215s dev-sdb1.device
1.084s systemd-journal-flush.service
903ms grub-common.service
902ms accounts-daemon.service
854ms apport.service
831ms thermald.service
830ms avahi-daemon.service
824ms pppd-dns.service
822ms gpu-manager.service
821ms rsyslog.service
805ms systemd-logind.service
709ms NetworkManager.service
621ms snapd.service
323ms mpd.service
321ms systemd-udevd.service
272ms apparmor.service
234ms upower.service
157ms systemd-resolved.service
146ms systemd-timesyncd.service
146ms systemd-tmpfiles-setup.service
124ms systemd-tmpfiles-setup-dev.service
116ms keyboard-setup.service
99ms systemd-udev-trigger.service
79ms motd-news.service
66ms setvtrgb.service
65ms plymouth-quit.service
57ms systemd-modules-load.service
55ms polkit.service
51ms systemd-journald.service
49ms systemd-sysctl.service
46ms user@1000.service
40ms packagekit.service
39ms wpa_supplicant.service
34ms dev-disk-by\x2duuid-9d798bd5\x2da17f\x2d4629\x2da28c\x2db0af811a7fd4.s wap
33ms binfmt-support.service
25ms bluetooth.service
24ms dev-mqueue.mount
lines 1-41

**claydoh** · Jul 29, 2018, 12:43 PM

You note 25 seconds total, systemd shows 16 seconds, so 10 seconds is the bios doing its thing before grub and the kernel is ever loaded. A "fast boot" option in the bios may help, but that may cause problems on Linux, so I have heard. Your network connection is taking 6-7 seconds, which is one area to investigate.

My old-sh i5-3470 workstation takes forever to load the bios and firmware.

Code:

gus@gus-HP-Compaq-Elite-8300-SFF:~$ systemd-analyze 
Startup finished in [COLOR="#FF0000"]29.482s (firmware)[/COLOR] + 12.966s (loader) + 3.721s (kernel) + 20.385s (userspace) = 1min 6.555s

Code:

gus@gus-HP-Compaq-Elite-8300-SFF:~$ systemd-analyze blame
         [COLOR="#FF0000"] 8.040s NetworkManager-wait-online.service[/COLOR]
          7.075s configure-printer@usb-003-003.service
          5.058s nmbd.service
          2.655s apt-daily-upgrade.service
          1.043s dev-sda2.device
          1.015s udisks2.service

Note mine takes forever to get wired networking up as well, as well as the shared printer and nmbd (Samba), plus I have some autostart on this system. It is also on a slow, super cheeep SSD

My new laptop =, i5-8250U, nvme SSD:

Code:

claydoh@widget-Lenovo:~$ systemd-analyze
Startup finished in 2.574s (firmware) + 11.365s (loader) + 8.038s (kernel) + 1.147s (userspace) = 23.125s

Code:

claydoh@widget-Lenovo:~$ systemd-analyze blame
           637ms snapd.seeded.service
           619ms snapd.service
           613ms apt-daily-upgrade.service
           528ms apt-daily.service
           441ms dev-nvme0n1p2.device
           219ms accounts-daemon.service
           169ms NetworkManager.service
           167ms lvm2-monitor.service
           113ms dev-loop0.device
           112ms grub-common.service
           101ms networking.service

Note that this one takes no time at all, but still takes a spell at the bios- I think I have fast boot disabled, but can't remember, but the wifi network takes no time??

But I googled it:
https://askubuntu.com/questions/1018...ine-service-do
https://ubuntuforums.org/showthread.php?t=2342450

The NetworkManager-wait-online.service can be disabled or the timeout reduced, which should help you greatly. And me as well

**jlittle** · Jul 29, 2018, 02:30 PM

On my 18.04 the boot does not wait for the network to come up. That finishes a little after I've logged in and the desktop appears.

Do you see the grub menu appear? I think the default is a 10 second timeout.

I suggest turning off the "quiet splash"; you might see something. To do that edit /etc/default/grub to delete those words and run sudo update-grub.

Regards, John Little

**comonda2** · Jul 29, 2018, 02:37 PM

thank u for infos but i cant live without internet

**comonda2** · Jul 29, 2018, 02:44 PM

Originally posted by jlittle View Post

On my 18.04 the boot does not wait for the network to come up. That finishes a little after I've logged in and the desktop appears.

Do you see the grub menu appear? I think the default is a 10 second timeout.

I suggest turning off the "quiet splash"; you might see something. To do that edit /etc/default/grub to delete those words and run sudo update-grub.

Regards, John Little

so must delete that line : GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" right? sorry for my english i dont understand fully and i dont want do wrong.

here, my grup file:

Code:

# If you change this file, run 'update-grub' afterwards to update# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT="0"
GRUB_TIMEOUT_STYLE="hidden"
GRUB_TIMEOUT="10"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="640x480"

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

no, grub menu does not appear.

**jlittle** · Jul 29, 2018, 02:56 PM

Deleting it wouldn't hurt, but IMO it's better to remove just the words, so that the variable is set to blank. That way, if you want them back it's easier to remember where they go. Making a copy of the line before the change and commenting the copy out by inserting a # at the front helps me remember too.

Turning off the quiet splash won't make the boot any faster, but you might see something causing a delay.

Regards, John Little

**claydoh** · Jul 29, 2018, 03:04 PM

Originally posted by comonda2 View Post

thank u for infos but i cant live without internet

It does not disable internet at all. It disables the service that is simply waiting for it to come up before continuing to boot.

I saved the 8 seconds boot time lost to it by disabling it.

https://askubuntu.com/questions/1018...ine-service-do

Sent from my LG-H931 using Tapatalk

**comonda2** · Jul 29, 2018, 03:08 PM

Originally posted by jlittle View Post

Deleting it wouldn't hurt, but IMO it's better to remove just the words, so that the variable is set to blank. That way, if you want them back it's easier to remember where they go. Making a copy of the line before the change and commenting the copy out by inserting a # at the front helps me remember too.

Turning off the quiet splash won't make the boot any faster, but you might see something causing a delay.

Regards, John Little

on that link says if i have plymouth-theme-ubuntu-text package i musnt do it and i have the package which i dont know any thing about it :

https://askubuntu.com/questions/33416/how-do-i-disable-the-boot-splash-screen-and-only-show-kernel-and-boot-text-inst

so is there any alternative solution?

**comonda2** · Jul 29, 2018, 03:09 PM

Originally posted by claydoh View Post

It does not disable internet at all. It disables the service that is simply waiting for it to come up before continuing to boot.

I saved the 8 seconds boot time lost to it by disabling it.

https://askubuntu.com/questions/1018...ine-service-do

Sent from my LG-H931 using Tapatalk

ok i will try

**comonda2** · Jul 29, 2018, 03:19 PM

the new startup time :

Code:

ahmet@ahmet:~$ sudo systemd-analyze[sudo] password for ahmet: 
Startup finished in 7.209s (kernel) + 3.603s (userspace) = 10.813s
graphical.target reached after 3.596s in userspace
ahmet@ahmet:~$

but the main problem black screen before kde logo.so can not I get rid of black screen?

**GreyGeek** · Jul 29, 2018, 03:57 PM

What does your /etc/fstab have in it. Here's mine:

Code:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=00fa8116-00d7-4611-9603-434769265d10 /               btrfs   defaults,noatime,autodefrag,subvol=@ 0       1
# /home was on /dev/sda1 during installation
UUID=00fa8116-00d7-4611-9603-434769265d10 /home           btrfs   defaults,noatime,autodefrag,subvol=@home 0       2
#/swapfile                                 none            swap    sw              0       0

My boot up times:

:~$ systemd-analyze
Startup finished in 3.183s (kernel) + 8.374s (userspace) = 11.558s
graphical.target reached after 1.895s in userspace

:~$ systemd-analyze blame
7.110s configure-printer@usb-003-002.service
809ms keyboard-setup.service
791ms dev-sda1.device
361ms mpd.service
291ms systemd-logind.service
279ms NetworkManager.service
210ms systemd-timesyncd.service
182ms systemd-resolved.service
164ms snapd.service
154ms upower.service
149ms networkd-dispatcher.service
128ms udisks2.service
126ms gpu-manager.service
101ms systemd-rfkill.service
95ms motd-news.service
86ms systemd-journal-flush.service
83ms accounts-daemon.service

**claydoh** · Jul 29, 2018, 04:09 PM

Originally posted by comonda2 View Post

the new startup time :

Code:

ahmet@ahmet:~$ sudo systemd-analyze[sudo] password for ahmet: 
Startup finished in 7.209s (kernel) + 3.603s (userspace) = 10.813s
graphical.target reached after 3.596s in userspace
ahmet@ahmet:~$

but the main problem black screen before kde logo.so can not I get rid of black screen?

Probably not, as I think, depending on the system - video card/driver used, that the boot sometimes is sort of too fast, as in it does not have enough time to load the graphic between the time it switches from the framebuffer to the actual video driver and before it gets to the login. Again, I think. It may also have to do with screen resolution during the process

Yours is fast - 7 seconds from grub to login screen.

BUUUTTTT.... I am investigating a fix for those who want to see a logo......

**claydoh** · Jul 29, 2018, 04:16 PM

Ok
Simple
First make sure we have the kubuntu logo theme installed and in use
make sure that plymouth-theme-kubuntu-logo is installed, it should be (I think)

Then make sure it is the default instead of the text (plain) logo

run this in a terminal:

Code:

sudo update-alternatives --config default.plymouth

Select #2 here:

Code:

There are 2 choices for the alternative default.plymouth (providing /usr/share/plymouth/themes/default.plymouth).

  Selection    Path                                                           Priority   Status
------------------------------------------------------------
  0            /usr/share/plymouth/themes/breeze/breeze.plymouth               160       auto mode
  1            /usr/share/plymouth/themes/breeze/breeze.plymouth               160       manual mode
* 2            /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth   150       manual mode

Press <enter> to keep the current choice[*], or type selection number:

Enter this command in a terminal:

Code:

sudo update-initramfs -u

Create a text file with the following text:

Code:

FRAMEBUFFER=y

Save it as /etc/initramfs-tools/conf.d/splash

Enter this command in a terminal:

Code:

sudo update-initramfs -u

Reboot.....

Happydance

**claydoh** · Jul 29, 2018, 04:45 PM

Ok, maybe not. It is working on my 1080p laptop, but not on my 4k TV

Announcement

Kubuntu opens in 25 seconds Too slow why?

[System] Kubuntu opens in 25 seconds Too slow why?

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment