Slow to Boot Tara LM19

[LarryT]

Hello All,

I am experiencing slow boot time of about 3-4 minutes whenever I boot Tara LM19. Below are the results of inxi -Fxz and systemd-analyze blame and any help would be appreciated!! I have the UEFI set to Nvidia only and the secure boot disabled. I installed the /home directory on a separate drive but the LM18.3 booted just fine so wondering what the problem is?

Thanks,
LarryT

Code: Select all

:~$ inxi -Fxz
System:    Host: larrry-ThinkPad-W520 Kernel: 4.15.0-24-generic x86_64
           bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1)
           Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: LENOVO product: 4284CV4 v: ThinkPad W520 serial: N/A
           Mobo: LENOVO model: 4284CV4 serial: N/A
           UEFI: LENOVO v: 8BET63WW (1.43 ) date: 10/20/2016
Battery    BAT0: charge: 37.0 Wh 98.4% condition: 37.6/86.6 Wh (43%)
           model: SANYO 42T4799 status: N/A
CPU:       Quad core Intel Core i7-2760QM (-MT-MCP-) 
           arch: Sandy Bridge rev.7 cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 19138
           clock speeds: max: 3500 MHz 1: 802 MHz 2: 825 MHz 3: 913 MHz
           4: 827 MHz 5: 827 MHz 6: 885 MHz 7: 1304 MHz 8: 845 MHz
Graphics:  Card-1: Intel 2nd Generation Core Integrated Graphics Controller
           bus-ID: 00:02.0
           Card-2: NVIDIA GF108GLM [Quadro 1000M] bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1920x1200@59.95hz, 1920x1080@60.00hz
           OpenGL: renderer: Quadro 1000M/PCIe/SSE2
           version: 4.6.0 NVIDIA 390.48 Direct Render: Yes
Audio:     Card-1 Intel 6 Series/C200 Series Family High Def. Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 GYROCOM C&C driver: USB Audio usb-ID: 001-006
           Sound: Advanced Linux Sound Architecture v: k4.15.0-24-generic
Network:   Card-1: Intel 82579LM Gigabit Network Connection
           driver: e1000e v: 3.2.6-k port: 6080 bus-ID: 00:19.0
           IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
           Card-2: Intel Centrino Ultimate-N 6300
           driver: iwlwifi bus-ID: 03:00.0
           IF: wlp3s0 state: down mac: <filter>
Drives:    HDD Total Size: 410.1GB (20.4% used)
           ID-1: /dev/sda model: INTEL_SSDSA2BW16 size: 160.0GB
           ID-2: /dev/sdb model: Samsung_SSD_850 size: 250.1GB
Partition: ID-1: / size: 146G used: 8.2G (6%) fs: ext4 dev: /dev/sda3
           ID-2: /home size: 229G used: 70G (33%) fs: ext4 dev: /dev/sdb1
           ID-3: swap-1 size: 0.03GB used: 0.00GB (0%)
           fs: swap dev: /dev/sda2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 55.0C mobo: N/A gpu: 0.0:52C
           Fan Speeds (in rpm): cpu: 2725
Info:      Processes: 239 Uptime: 10 min Memory: 1104.3/15923.5MB
           Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56

Code: Select all

:~$ systemd-analyze blame
           596ms systemd-journal-flush.service
           424ms systemd-timesyncd.service
           381ms systemd-resolved.service
           380ms systemd-logind.service
           346ms dev-sda3.device
           297ms lightdm.service
           295ms plymouth-quit-wait.service
           286ms NetworkManager.service
           250ms upower.service
           228ms udisks2.service
           182ms ubuntu-system-adjustments.service
           179ms networkd-dispatcher.service
           144ms gpu-manager.service
           131ms dns-clean.service
            97ms grub-common.service
            95ms systemd-fsck@dev-disk-by\x2duuid-BBD0\x2d2570.service
            88ms apparmor.service
            86ms lvm2-monitor.service
            79ms ModemManager.service
            78ms keyboard-setup.service
            74ms accounts-daemon.service
            74ms thermald.service
            68ms systemd-udev-trigger.service
            67ms bluetooth.service
            65ms systemd-journald.service
            62ms avahi-daemon.service
            61ms hddtemp.service
            59ms systemd-rfkill.service
            56ms systemd-tmpfiles-setup-dev.service
            50ms lm-sensors.service
            47ms systemd-sysctl.service
            45ms systemd-tmpfiles-setup.service
            45ms apport.service
            43ms user@1000.service
            41ms systemd-udevd.service
            40ms networking.service
            38ms pppd-dns.service
            37ms systemd-fsck@dev-disk-by\x2duuid-328af653\x2db5e2\x2d49ab\x2da5fb
            37ms rsyslog.service
            32ms systemd-modules-load.service
            32ms wpa_supplicant.service
            31ms colord.service
            31ms speech-dispatcher.service
            26ms polkit.service
            25ms alsa-restore.service
            17ms dev-disk-by\x2duuid-f72b7cfe\x2dd542\x2d479f\x2d8b4e\x2d0fe140e36
            16ms flatpak-system-helper.service
            16ms sys-kernel-debug.mount
            15ms kmod-static-nodes.service
            15ms ufw.service
            14ms ureadahead-stop.service
            13ms console-setup.service

[smurphos]

Hi, the 4.15.0-24 kernel is problematic for many hardware configurations. Any of the prior kernels listed in Update manager > View > Linux Kernels should be fine and hopefully the next kernel update after -24 will resolve the issue.

In the meantime, reboot, select an earlier kernel in grub (normally shift or escape to access the grub menu) and then remove 4.15.0-24 via update manager. It will probably come up as an update again - either ignore or blacklist it pending a new kernel update from upstream.

[LarryT]

Thanks for the advice, I'll do it now.
Regards,
LarryT

[fstjohn]

Probably best to turn off automatic update until a new kernel is offered. My question, if I right click on the kernel in update mgr and select "Ignore updates for this package", does that cause update manager to ignore ALL kernel updates or just the present one?

[smurphos]

I think it should just be the present one as each new kernel is a new set of packages rather than an update to the existing. But not 100% sure as I've never had cause to blacklist a kernel before now..

[all41]

Everything listed for your $ systemd-analyze blame results took place in less than 6 seconds.

[fstjohn]

Kernel 4.15.0-29 received and installed today. All seems to be OK on a restart to activate the new kernel. Normal boot time.

[Joe2Shoe]

It just ignores/blacklists that specific kernel: 24
I upgraded to 29 today and all is good.
I have a 10 year old Core2Duo 2.20GHz laptop with kernel 29, 4GB DDR-800MHz RAM, LM19 MATE 64-bit, and it boots in 1 minute.

[LarryT]

I updated to Kernel 4.15.0-29 yesterday and all is well here, too. I guess that 4.15.0-24 kernel had some issues with the Nvidia driver however if you twirled your finger on the trackpad, it booted right up!
Thanks,
LarryT