boot time

a0_dummy · 03-06-2019, 02:19 PM

Hi all,
I am new to MX Linux and not realy a subject matter expert.
Anyway I realy like MX and I installed it on one of my old laptops.
After booting it performance is quite good, but boot takes forever (at least 2 min).

I used systemd-analyse to find out why, but was not able to tune the boot process. Switching some services off did not really help and even though I disabled them with systemctl they get started again.

Here is the output of systemd-analyse and the hw profile of my laptop.

Hopefully somebody has some tips to speed up boot.

Many thanks
kalle

kalle@lappi:~$ systemd-analyze time
Startup finished in 5.209s (kernel) + 16.705s (userspace) = 21.915s
kalle@lappi:~$ systemd-analyze blame
14.681s lightdm.service
9.633s plymouth-quit.service
9.633s plymouth-quit-wait.service
3.663s webmin.service
2.886s upower.service
2.151s tlp.service
973ms networking.service

kalle@lappi:~$ sudo lshw
lappi
description: Notebook
product: EasyNote TK85 (Calpella_CRB)
vendor: Packard Bell

-cpu
description: CPU
product: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz
vendor: Intel Corp.

*-memory
description: System Memory
physical id: 1a
slot: System board or motherboard
size: 4GiB

*-disk (that is a SSD)
description: ATA Disk
product: ADATA SP900
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 7b
serial: 7E0220027071
size: 119GiB (128GB)

BW-userx · 03-06-2019, 02:42 PM

VOID linux boots like really fast,

product: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz
1st gen i3 @ 2.4

find out what these do, and figure out if you can do without them.

Code:

14.681s lightdm.service // replace with startx
9.633s plymouth-quit.service
9.633s plymouth-quit-wait.service
3.663s webmin.service
2.886s upower.service
2.151s tlp.service
973ms networking.service

a0_dummy · 03-07-2019, 03:38 AM

Quote:

Originally Posted by BW-userx

VOID linux boots like really fast,

product: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz
1st gen i3 @ 2.4

find out what these do, and figure out if you can do without them.

Code:

14.681s lightdm.service // replace with startx
9.633s plymouth-quit.service
9.633s plymouth-quit-wait.service
3.663s webmin.service
2.886s upower.service
2.151s tlp.service
973ms networking.service

Hi BW-User,
thanks for answering, but ......
I like to stay with MX Linux (and do not want to go to VOID linux)
I also switched off both plymouth** services and they became active again
(even though I "systemctl disable"'d them.

how would I replace ligthdm by startx ?
If doing so, I guess I would have to login at the console before the xwindows environment
gets started, right ?

a0_dummy · 03-07-2019, 09:32 AM

Quote:

Originally Posted by BW-userx

VOID linux boots like really fast,

maybe, but I would like to keep MX

Quote:

Originally Posted by BW-userx

find out what these do, and figure out if you can do without them.

Code:

14.681s lightdm.service // replace with startx
9.633s plymouth-quit.service
9.633s plymouth-quit-wait.service
3.663s webmin.service
2.886s upower.service
2.151s tlp.service
973ms networking.service

when I switch to startx, I guess login will be on console and not in gui
plymouth servers get reactivated when disabled with 'systemctl disable'

BW-userx · 03-07-2019, 03:39 PM

it was just a suggestion, and I do not run sysd or have ran it long enough to know exacly what you need to do, thouigh I found everything I needed to now about syctl by googling it, remember you are running it on a 1st gen i3 cpu no less. not even an i5 or i7. are they not the slowest cpu in the list of ix cpu's?

ondoho · 03-08-2019, 01:52 PM

Quote:

Originally Posted by a0_dummy

kalle@lappi:~$ systemd-analyze time
Startup finished in 5.209s (kernel) + 16.705s (userspace) = 21.915s
kalle@lappi:~$ systemd-analyze blame
14.681s lightdm.service
9.633s plymouth-quit.service
9.633s plymouth-quit-wait.service
3.663s webmin.service
2.886s upower.service
2.151s tlp.service
973ms networking.service

that's still nowhere near 2 minutes....
can you see what is taking so long?
ah, plymouth might be getting in the way... can you (temporarily) remove "quiet splash" from your linux command line?

you could try to further investigate what lightdm is doing there for 14s:

Code:

journalctl -b -u lightdm

also, systemd-analyze has one or two more options that might tell you more.

Code:

man systemd-analyze

namida12 · 03-09-2019, 09:08 AM

MX Forum might assist you:
https://forum.mxlinux.org/viewtopic....489732#p489732

JR

hazel · 03-09-2019, 09:40 AM

Quote:

Originally Posted by a0_dummy

how would I replace ligthdm by startx ?
If doing so, I guess I would have to login at the console before the xwindows environment
gets started, right ?

That's right. If you look in /etc/systemd/system, you will find a link called something like display_manager.service. That has to be deactivated with systemctl so that it won't be treated as required at boot.

rokytnji · 03-09-2019, 02:54 PM

You running MX hazel? I will head out to my shop computer with MX on it to double check if

Quote:

That's right. If you look in /etc/systemd/system,

Is present or not.

Code:

harry@shop1:~
$ cat /etc/lsb-release
PRETTY_NAME="MX-16 Metamorphosis"
DISTRIB_ID=MX
DISTRIB_RELEASE=16
DISTRIB_CODENAME=Metamorphosis
DISTRIB_DESCRIPTION="MX-16 Metamorphosis"

edit:

Code:

harry@shop1:~
$ cd /etc/systemd
harry@shop1:/etc/systemd
$ ls
bootchart.conf  logind.conf  ntp-units.d    system       timesyncd.conf  user.conf
journald.conf   network      resolved.conf  system.conf  user
harry@shop1:/etc/systemd
$ cat system
cat: system: Is a directory
harry@shop1:/etc/systemd
$ cd system
harry@shop1:/etc/systemd/system
$ ls
bluetooth.target.wants                      hibernate.target.wants     sleep.target.wants
dbus-org.bluez.service                      hybrid-sleep.target.wants  sockets.target.wants
dbus-org.freedesktop.Avahi.service          local-fs.target.wants      sshd.service
dbus-org.freedesktop.nm-dispatcher.service  multi-user.target.wants    suspend.target.wants
default.target.wants                        paths.target.wants         sysinit.target.wants
display-manager.service                     poweroff.target.wants      syslog.service
getty.target.wants                          printer.target.wants       systemd-rfkill@.service
halt.target.wants                           reboot.target.wants
harry@shop1:/etc/systemd/system

Code:

harry@shop1:/etc/systemd/system
$ cat display-manager.service 
[Unit]
Description=Light Display Manager
Documentation=man:lightdm(1)
After=systemd-user-sessions.service

[Service]
# temporary safety check until all DMs are converted to correct
# display-manager.service symlink handling
ExecStartPre=/bin/sh -c '[ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ]'
ExecStart=/usr/sbin/lightdm
Restart=always
BusName=org.freedesktop.DisplayManager

The reason for my post since systemctl was mentioned.
https://mxlinux.org/wiki/system/systemd/

ondoho · 03-10-2019, 06:59 AM

a package's default configuration is usually installed to /lib/systemd/, not /etc.
i suggest:

Code:

find /lib/systemd -name '*lightdm*'

if you modify that file, you should work on a copy in /etc/systemd. it will override what's in /lib/systemd.

anticapitalista · 03-13-2019, 07:31 PM

MX uses sysvinit by default, not systemd