Mint 18.2 upgrade went super well

[MurphCID]

I am down to the little linux laptop right now. My old system died, my new Ryzen is in BSOD hades, my mac laptop is boring, and this one is fun. Anyway, the upgrade from 18.1 to 18.2 went super smoothly, the installation of lightDM was easy. Mint just keeps impressing me.

[riki]

I am down to the little linux laptop right now. My old system died, my new Ryzen is in BSOD hades, my mac laptop is boring, and this one is fun. Anyway, the upgrade from 18.1 to 18.2 went super smoothly, the installation of lightDM was easy. Mint just keeps impressing me.

Aren't you experiencing much longer login time? Short of 2 minutes since upgrading to 18.2. Previous versions 30 seconds... Thanks for any tips.

[MurphCID]

I haven't noticed anything so far, but I will start paying more attention to it. I did not do anything special, just ran the installer to upgrade to 18.2, and then removed MDM for the new display manager.

I am down to the little linux laptop right now. My old system died, my new Ryzen is in BSOD hades, my mac laptop is boring, and this one is fun. Anyway, the upgrade from 18.1 to 18.2 went super smoothly, the installation of lightDM was easy. Mint just keeps impressing me.

Aren't you experiencing much longer login time? Short of 2 minutes since upgrading to 18.2. Previous versions 30 seconds... Thanks for any tips.

[riki]

How long is your boot time from cold start to desktop? Thanks.

[WharfRat]

Anyway, the upgrade from 18.1 to 18.2 went super smoothly, the installation of lightDM was easy. Mint just keeps impressing me.

Did four computers here yesterday with no problems

[riki]

Anyway, the upgrade from 18.1 to 18.2 went super smoothly, the installation of lightDM was easy. Mint just keeps impressing me.

Did four computers here yesterday with no problems

And how long do they take all four computers to boot from a cold start to desktop? Thanks.

[WharfRat]

I didn't notice any difference from 18.1 - so I would say the boot times were the same as far as I can tell.

[riki]

I didn't notice any difference from 18.1 - so I would say the boot times were the same as far as I can tell.

Please, what were the boot times?

[WharfRat]

I only have access to the XPS system so here is

Code: Select all

[bill@XPS] ~ $ systemd-analyze time
Startup finished in 21.353s (firmware) + 11.895s (loader) + 4.441s (kernel) + 20.953s (userspace) = 58.643s
[bill@XPS] ~ $ 

[riki]

I only have access to the XPS system so here is

Code: Select all

[bill@XPS] ~ $ systemd-analyze time
Startup finished in 21.353s (firmware) + 11.895s (loader) + 4.441s (kernel) + 20.953s (userspace) = 58.643s
[bill@XPS] ~ $ 

Thanks. Under a minute is not too bad, my PC takes almost 2 minutes whereas with Rosa and Maya it took only 30-40 seconds.

[WharfRat]

I only have access to the XPS system so here is

Code: Select all

[bill@XPS] ~ $ systemd-analyze time
Startup finished in 21.353s (firmware) + 11.895s (loader) + 4.441s (kernel) + 20.953s (userspace) = 58.643s
[bill@XPS] ~ $ 

Thanks. Under a minute is not too bad, my PC takes almost 2 minutes whereas with Rosa and Maya it took only 30-40 seconds.

This is from another system

Code: Select all

bill@C540 ~ $ systemd-analyze time
Startup finished in 5.908s (firmware) + 10.789s (loader) + 4.187s (kernel) + 22.096s (userspace) = 42.981s
bill@C540 ~ $ 

Like a I said earlier, I didn't notice any difference in boot time if there is any change.

[greerd]

What does

Code: Select all

systemd-analyze blame

say?

[WharfRat]

Code: Select all

[bill@XPS] ~/script $ systemd-analyze --no-pager blame|head
         12.954s NetworkManager-wait-online.service
          6.551s apt-daily.service
          4.615s ModemManager.service
          2.877s lvm2-monitor.service
          2.712s ssh.service
          2.407s dev-sda2.device
          1.904s NetworkManager.service
          1.735s colord.service
          1.695s loadcpufreq.service
          1.458s accounts-daemon.service
[bill@XPS] ~/script $ 

Code: Select all

bill@C540 ~ $ systemd-analyze --no-pager blame|head
          8.384s NetworkManager-wait-online.service
          6.882s apt-daily.service
          4.392s upower.service
          3.934s lvm2-monitor.service
          3.675s dev-sda5.device
          3.498s ModemManager.service
          2.726s systemd-fsck@dev-disk-by\x2duuid-9e0397dd\x2d8346\x2d4abf\x2dbd2e\x2dc1c5b2e274bd.service
          2.603s accounts-daemon.service
          2.290s loadcpufreq.service
          2.289s systemd-logind.service
bill@C540 ~ $ 

[riki]

What does

Code: Select all

systemd-analyze blame

say?

riki@riki-System-Product-Name ~ $ systemd-analyze blame
11.843s dev-sda1.device
10.638s ModemManager.service
10.544s networking.service
8.007s loadcpufreq.service
7.780s accounts-daemon.service
7.309s grub-common.service
6.873s irqbalance.service
6.434s virtualbox-guest-utils.service
5.887s ondemand.service
5.831s systemd-logind.service
5.347s hddtemp.service
5.203s alsa-restore.service
5.194s systemd-user-sessions.service
5.178s avahi-daemon.service
5.100s ufw.service
4.868s pppd-dns.service
4.866s iio-sensor-proxy.service
4.865s rsyslog.service
4.839s thermald.service
4.708s lm-sensors.service
4.689s console-kit-log-system-start.service
3.962s systemd-udevd.service
3.893s NetworkManager.service
lines 1-23

[greerd]

That looks decent, what does systemd-analyze critical-chain and systemd-analyze time show?

[MintBean]

Thread jacking is pretty rude.

[greerd]

Thread jacking is pretty rude.

Oops, I didn't realize this wasn't the OP, sorry.

[WharfRat]

Code: Select all

[bill@XPS] ~/script $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @20.931s
└─multi-user.target @20.931s
  └─hddtemp.service @20.583s +347ms
    └─network-online.target @20.565s
      └─NetworkManager-wait-online.service @7.610s +12.954s
        └─NetworkManager.service @5.686s +1.904s
          └─dbus.service @5.165s
            └─basic.target @5.161s
              └─paths.target @5.161s
                └─cups.path @5.161s
                  └─sysinit.target @5.138s
                    └─systemd-update-utmp.service @5.020s +107ms
                      └─systemd-tmpfiles-setup.service @5.007s +12ms
                        └─local-fs.target @4.968s
                          └─run-cgmanager-fs.mount @6.025s
                            └─local-fs-pre.target @3.837s
                              └─lvm2-monitor.service @959ms +2.877s
                                └─lvm2-lvmetad.service @1.386s
                                  └─systemd-journald.socket @939ms
                                    └─-.slice @910ms
[bill@XPS] ~/script $ 

Code: Select all

[bill@XPS] ~/script $ systemd-analyze time
Startup finished in 21.353s (firmware) + 11.895s (loader) + 4.441s (kernel) + 20.953s (userspace) = 58.643s
[bill@XPS] ~/script $ 

[riki]

Thread jacking is pretty rude.

The OP hasn't complained. We are all trying to help each other.

[MintBean]

I am down to the little linux laptop right now. My old system died, my new Ryzen is in BSOD hades, my mac laptop is boring, and this one is fun. Anyway, the upgrade from 18.1 to 18.2 went super smoothly, the installation of lightDM was easy. Mint just keeps impressing me.

I'm liking 18.2 a lot. Upgrade was painless here too. I for one prefer LightDM over MDM and I'm loving that I no longer get screen tearing on my Intel/Nvidia setup. My Mac was the best laptop I've ever seen - not the best OS obviously, but the best hardware overall.