10 minute Long Boot Time?

Support & Help Requests
, ,
#1

I installed Ubuntu MATE 18.04 and once I get to the desktop everything runs ok but it takes 10 minutes to see the desktop. Is this normal? Any way to troubleshoot or solve?

If someone could assist, I would appreciate it greatly! Here’s my computers info:

inxi -Fxz
System: Host: shortstop-Inspiron-1720 Kernel: 4.15.0-24-generic x86_64
bits: 64 gcc: 7.3.0
Desktop: MATE 1.20.1 (Gtk 3.22.30-1ubuntu1)
Distro: Ubuntu 18.04 LTS
Machine: Device: portable System: Dell product: Inspiron 1720 serial: N/A
Mobo: Dell model: 0UK439 serial: N/A
BIOS: Dell v: A09 date: 07/11/2008
Battery BAT0: charge: 74.4 Wh 100.0% condition: 74.4/73.3 Wh (102%)
model: Sony DELL 00 status: Full
CPU: Dual core Intel Core2 Duo T7250 (-MCP-)
arch: Conroe rev.13 cache: 2048 KB
flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 7980
clock speeds: max: 2001 MHz 1: 1905 MHz 2: 1635 MHz
Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
bus-ID: 00:02.0
Display Server: x11 (X.Org 1.19.6 )
drivers: modesetting (unloaded: fbdev,vesa)
Resolution: [email protected]
OpenGL: renderer: Mesa DRI Intel 965GM
version: 2.1 Mesa 18.0.0-rc5 Direct Render: Yes
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.15.0-24-generic
Network: Card-1: Broadcom Limited BCM4401-B0 100Base-TX
driver: b44 v: 2.0 bus-ID: 03:00.0
IF: eth0 state: down mac:
Card-2: Broadcom Limited BCM4321 802.11a/b/g/n
driver: wl bus-ID: 0c:00.0
IF: wlp12s0 state: up mac:
Drives: HDD Total Size: 128.0GB (13.4% used)
ID-1: /dev/sda model: SAMSUNG_SSD_SM84 size: 128.0GB
Partition: ID-1: / size: 117G used: 16G (15%) fs: ext4 dev: /dev/sda1
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 48.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 173 Uptime: 39 min Memory: 1349.5/3935.9MB
Init: systemd runlevel: 5 Gcc sys: 7.3.0
Client: Shell (bash 4.4.191) inxi: 2.3.56

systemd-analyze blame
38.724s apt-daily.service
7.385s apt-daily-upgrade.service
4.235s dev-sda1.device
3.240s dev-loop3.device
3.222s dev-loop0.device
3.220s dev-loop1.device
3.215s dev-loop2.device
3.199s dev-loop4.device
3.164s dev-loop5.device
1.901s snapd.service
1.604s udisks2.service
1.110s lightdm.service
1.093s plymouth-quit-wait.service
911ms hddtemp.service
806ms networkd-dispatcher.service
714ms systemd-rfkill.service
651ms loadcpufreq.service
547ms snapd.seeded.service
497ms apparmor.service
492ms keyboard-setup.service
448ms NetworkManager.service
388ms systemd-udev-trigger.service
380ms apport.service
378ms systemd-journald.service
365ms accounts-daemon.service
351ms avahi-daemon.service
349ms ModemManager.service
346ms swapfile.swap
343ms grub-common.service
337ms networking.service
318ms systemd-logind.service
315ms thermald.service
303ms systemd-journal-flush.service
292ms NetworkManager-wait-online.service
279ms gpu-manager.service
274ms upower.service
233ms pppd-dns.service
226ms wpa_supplicant.service
187ms rsyslog.service
173ms systemd-resolved.service
158ms speech-dispatcher.service
133ms snap-core-4486.mount
132ms snap-ubuntu\x2dmate\x2dwelcome-169.mount
128ms systemd-timesyncd.service
126ms polkit.service
123ms [email protected]
120ms plymouth-read-write.service
116ms console-setup.service
108ms lm-sensors.service
104ms snap-software\x2dboutique-31.mount
102ms snap-core-4917.mount
92ms snap-pulsemixer-8.mount
92ms plymouth-start.service
81ms snap-pulsemixer-23.mount
77ms systemd-udevd.service
69ms systemd-modules-load.service
69ms cpufrequtils.service
64ms packagekit.service
60ms sys-kernel-debug.mount
59ms dev-hugepages.mount
57ms dev-mqueue.mount
54ms kmod-static-nodes.service
49ms sys-fs-fuse-connections.mount
49ms systemd-remount-fs.service
48ms sys-kernel-config.mount
48ms systemd-sysctl.service
46ms kerneloops.service
45ms systemd-random-seed.service
42ms openvpn.service
35ms ufw.service
33ms systemd-tmpfiles-setup-dev.service
32ms systemd-tmpfiles-setup.service
31ms systemd-user-sessions.service
30ms setvtrgb.service
25ms systemd-backlight@backlight:acpi_video0.service
24ms systemd-tmpfiles-clean.service
17ms systemd-update-utmp.service
15ms ureadahead-stop.service
14ms systemd-update-utmp-runlevel.service
14ms bluetooth.service
13ms systemd-backlight@backlight:intel_backlight.service
8ms rtkit-daemon.service
7ms snapd.socket

#2

Interesting as I have an old Sony laptop that’s virtually identical that I gave up on about a year or so ago as the later kernels don’t play too nicely with the GM965 chipset. I dragged it back out this weekend to explain to one of my sons that “No, you DON’T need to spend MY money on software to do your video projects!” and proceeded to install Ubuntu Studio – conveniently forgetting why I’d retired it in the first place.

Now that I think about it, it did seem to take an unusually long time to boot up. I wonder if it’s a similar problem to the ones with the 4.8(IIRC) and later kernels and some of the Intel chipsets?

I’ll try to make time in the next couple of days to check it out and we can compare notes, maybe figuring this out.

#3

Interesting that the apt-daily service takes that long. I assume the laptop uses wifi so it takes time to establish network. Can you try with a wired connection? My apt-daily takes 4s (wired)

#4

I use an old Dell laptop as a daily and thought I’d post my inxi and systemd-analyze blame

  • mine took approximately 56 seconds to boot from BIOS to desktop.

    $ inxi -Fxz
    System: Host: D830 Kernel: 4.15.0-24-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: MATE 1.20.1 (Gtk 3.22.30)
    Distro: Ubuntu 18.04 LTS
    Machine: Device: portable System: Dell product: Latitude D830 serial: N/A
    Mobo: Dell model: 0HN341 serial: N/A BIOS: Dell v: A13 date: 07/21/2008
    Battery BAT0: charge: 73.3 Wh 148.3% condition: 49.4/73.3 Wh (67%) model: SMP DELL YD6236 status: Full
    CPU: Dual core Intel Core2 Duo T7300 (-MCP-) arch: Conroe rev.10 cache: 4096 KB
    flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 7979
    clock speeds: max: 2001 MHz 1: 1541 MHz 2: 1384 MHz
    Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary) bus-ID: 00:02.0
    Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa)
    Resolution: [email protected]
    OpenGL: renderer: Mesa DRI Intel 965GM version: 2.1 Mesa 18.0.0-rc5 Direct Render: Yes
    Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
    Sound: Advanced Linux Sound Architecture v: k4.15.0-24-generic
    Network: Card-1: Broadcom Limited NetXtreme BCM5755M Gigabit Ethernet PCI Express
    driver: tg3 v: 3.137 bus-ID: 09:00.0
    IF: eth0 state: down mac:
    Card-2: Broadcom Limited BCM4311 802.11a/b/g driver: b43-pci-bridge bus-ID: 0c:00.0
    IF: wlan0 state: up mac:
    Drives: HDD Total Size: 500.1GB (57.4% used)
    ID-1: /dev/sda model: WDC_WD5000BPVT size: 500.1GB
    Partition: ID-1: / size: 20G used: 9.0G (49%) fs: ext4 dev: /dev/sda9
    ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
    RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
    Sensors: System Temperatures: cpu: 46.0C mobo: N/A
    Fan Speeds (in rpm): cpu: N/A
    Info: Processes: 170 Uptime: 2:51 Memory: 1014.5/7967.8MB Init: systemd runlevel: 5 Gcc sys: 7.3.0
    Client: Shell (bash 4.4.191) inxi: 2.3.56

    systemd-analyze blame
    15.199s dev-sda9.device
    13.087s systemd-journal-flush.service
    9.808s systemd-tmpfiles-setup-dev.service
    9.621s systemd-sysctl.service
    7.126s udisks2.service
    6.857s NetworkManager-wait-online.service
    6.317s snapd.service
    5.389s ModemManager.service
    5.060s NetworkManager.service
    4.694s accounts-daemon.service
    4.116s dev-loop2.device
    4.106s dev-loop1.device
    4.096s dev-loop0.device
    4.094s dev-loop3.device
    4.088s dev-loop5.device
    4.077s dev-loop6.device
    3.939s dev-loop4.device
    3.500s loadcpufreq.service
    3.189s networking.service
    3.130s thermald.service
    2.892s polkit.service
    2.890s networkd-dispatcher.service
    2.415s grub-common.service
    2.257s x2goserver.service
    1.853s powerwaked.service
    1.496s sshguard.service
    1.313s avahi-daemon.service
    1.203s systemd-random-seed.service
    1.069s lightdm.service
    1.062s plymouth-quit-wait.service
    1.059s gpu-manager.service
    1.011s keyboard-setup.service
    967ms wpa_supplicant.service
    957ms systemd-rfkill.service
    851ms systemd-fsck@dev-disk-by\x2duuid-ce4649f8\x2dcc57\x2d4f35\x2d9d1b\x2d52cc1efab9bb.service
    829ms systemd-modules-load.service
    777ms apport.service
    713ms rsyslog.service
    607ms colord.service
    561ms cpufrequtils.service
    513ms sys-kernel-debug.mount
    453ms apparmor.service
    438ms systemd-remount-fs.service
    407ms dev-hugepages.mount
    402ms dev-mqueue.mount
    382ms systemd-journald.service
    320ms systemd-udevd.service
    308ms kmod-static-nodes.service
    299ms plymouth-read-write.service
    282ms snap-core-4650.mount
    233ms setvtrgb.service
    231ms plymouth-start.service
    224ms systemd-tmpfiles-setup.service
    213ms snap-core-4917.mount
    208ms [email protected]
    187ms snap-core-4830.mount
    179ms systemd-udev-trigger.service
    179ms home-data4.mount
    177ms upower.service
    158ms systemd-timesyncd.service
    146ms dev-disk-by\x2duuid-c57e19bd\x2d5f78\x2d4098\x2d8cce\x2d3b3c48707ea7.swap
    145ms systemd-resolved.service
    133ms ssh.service
    119ms systemd-logind.service
    98ms speech-dispatcher.service
    89ms lm-sensors.service
    79ms snap-pulsemixer-8.mount
    74ms snap-ubuntu\x2dmate\x2dwelcome-169.mount
    65ms snapd.seeded.service
    52ms pppd-dns.service
    35ms ufw.service
    34ms snap-pulsemixer-23.mount
    33ms snap-software\x2dboutique-31.mount
    27ms kerneloops.service
    22ms hddtemp.service
    20ms systemd-update-utmp.service
    19ms alsa-restore.service
    11ms console-setup.service
    10ms openvpn.service
    9ms systemd-update-utmp-runlevel.service
    9ms rtkit-daemon.service
    8ms systemd-user-sessions.service
    6ms systemd-backlight@backlight:intel_backlight.service
    5ms sys-kernel-config.mount
    5ms sys-fs-fuse-connections.mount
    1ms snapd.socket

#5

This might help with those long boot times. Flip done timed out - May 26, 2018 -

I should’a made a note of this when it first happened on 16.04. Same fix - add video=SVIDEO-1:d in grub. See -

And also see -

From the first Askubuntu post: This is a bug. To avoid delay you can use a workaround. From your terminal run:

sudo pluma /etc/default/grub

Then add the kernel boot parameter: video=SVIDEO-1:d, so it will look like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"

Then

sudo update-grub
sudo reboot

No more flip done timed out messages, drastically shorter boot times.

2 Likes
UM 18.04 taking long time (like 5 minutes) to complete boot
Very Slow Boot after updating from 16.04 to 18.04
#6

Maybe you are affected by this: https://www.linuxuprising.com/2018/07/ubuntu-1804-linux-kernel-update-causes.html

#7

@joesplace:
I worked on my Sony with the same hardware and had the same problems under the Ubuntu Studio I was already playing with, UM and Antergos XFCE . The above fix solved the whole thing in all three cases. Should be at least worth a shot.

@mdooley:
Thanks for the fix. I now have something to plug into my old Kenwood receiver and drown out my neighbors when they annoy me with what they consider to be music.

Time for some Led Zeppelin IV, I think…

1 Like
#8

Thanks for this info. Nine months on, this information has just been a huge help!

#9

Hey @joesplace can you please give us some update?
This fix presented by @mdooley has apparently solved look-alike issues for two users plus myself, so if you don't give us a sign I'm gonna mark it as the solution.