Welcome!
Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Slower boot times [solved]

Help for Current Versions of MX
User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 4585
Joined: Sun May 27, 2007 5:37 am

Re: Slower boot times

#11

Post by asqwerth » Tue Jan 08, 2019 10:50 pm

Mauser wrote:
Tue Jan 08, 2019 9:29 pm
dreamer wrote:
Tue Jan 08, 2019 6:40 pm
The increased time seems to be during the MX splash progression screen
I see two potential problems:

1. You are using Plymouth. Get rid of it in MX Boot Options and see what happens.
2. Plymouth makes it hard for you to see what happens during the prolonged boot. See problem 1.

Without having scientific evidence to back it up I put Plymouth in the same bag of broken Linux tech as Systemd and Pulseaudio. Sometimes your own experience is enough to make you stay away from or reduce your exposure to certain technologies.

I think MX team made it really easy to enable/disable Plymouth (haven't tried it myself) so you don't have to install/uninstall anything to try this.
I don't know if I am using Plymouth. There is nothing in MX Boot Options that says "Plymouth". Besides it booted 3 times before with the splash screen.
Plymouth is the graphical splash screen.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
Mauser
Forum Guide
Forum Guide
Posts: 1068
Joined: Mon Jun 27, 2016 7:32 pm

Re: Slower boot times

#12

Post by Mauser » Tue Jan 08, 2019 11:02 pm

asqwerth wrote:
Tue Jan 08, 2019 10:50 pm



Plymouth is the graphical splash screen.
Thank you. Now we are getting somewhere. It seems there is an error that keeps repeating it's self as "usb -1-1 device decipher error" that is slowing down the boot process. I don't know why there is this error when all my USB ports are working fine. Any ideas?
I am command line illiterate. :confused:

User avatar
figueroa
Forum Regular
Forum Regular
Posts: 396
Joined: Fri Dec 21, 2018 12:20 am

Re: Slower boot times

#13

Post by figueroa » Tue Jan 08, 2019 11:18 pm

My installed x86_64 MX Linux, upgraded from 17 to 18 through routine updates, has no plymouth packages installed. Plymouth did not get installed as part of the update process. I think that's the better deal. I'd prefer that splash was not a grub default now because I don't think users should be shielded from boot logging messages. I know some users have complained that the boot messages give an unpolished feel to distros, but I believe they don't understand the benefit of the learning experience from watching those messages. This is, of course, just an opinion.
Andy Figueroa
Using Unix from 1984; GNU/Linux from 1993

User avatar
figueroa
Forum Regular
Forum Regular
Posts: 396
Joined: Fri Dec 21, 2018 12:20 am

Re: Slower boot times

#14

Post by figueroa » Tue Jan 08, 2019 11:30 pm

Regarding boot times, my VirtualBox virtual machine of MX-17 fully upgraded to MX-18 with kernel 4.19 (but no plymouth) boots in 11 seconds from grub to a usable desktop (logged in automatically) on really fast hardware, i-7 3400 with 16 gigs, giving the vm 4 gigs and two CPUs. I never clocked it before it was upgraded at the end of December, but it seems faster now than when first installed.
Andy Figueroa
Using Unix from 1984; GNU/Linux from 1993

User avatar
Mauser
Forum Guide
Forum Guide
Posts: 1068
Joined: Mon Jun 27, 2016 7:32 pm

Re: Slower boot times

#15

Post by Mauser » Tue Jan 08, 2019 11:36 pm

figueroa wrote:
Tue Jan 08, 2019 11:30 pm
Regarding boot times, my VirtualBox virtual machine of MX-17 fully upgraded to MX-18 with kernel 4.19 (but no plymouth) boots in 11 seconds from grub to a usable desktop (logged in automatically) on really fast hardware, i-7 3400 with 16 gigs, giving the vm 4 gigs and two CPUs. I never clocked it before it was upgraded at the end of December, but it seems faster now than when first installed.
MX-18 use to boot that fast for me even with the splash screen. This puseling USB error seems to slow it down to Windows 98se times. As you can see the spelling checker works as well as my spelling. :wink:
I am command line illiterate. :confused:

User avatar
dreamer
Forum Regular
Forum Regular
Posts: 437
Joined: Sun Oct 15, 2017 11:34 am

Re: Slower boot times

#16

Post by dreamer » Tue Jan 08, 2019 11:53 pm

skidoo wrote:
Tue Jan 08, 2019 9:08 pm
mauser, toward speeding up the "boot time", check which services (daemons) are being autostarted & disable any that you're sure you don't need.

dreamer, I too am not a fan of plymouth. Under sysV init, regardless whether plymouth runs, a bootlog file should be available for review, pathed under /var/log
It might be enlightening to grep the logfile (or open in a text editor and search ) for instances of "warn" or "fail"
Good suggestion. I knew there was a log, but I didn't know where. Mauser, you should examine that file and if you post it here someone might actually understand what is going on.
Also disconnect USB devices.

User avatar
Mauser
Forum Guide
Forum Guide
Posts: 1068
Joined: Mon Jun 27, 2016 7:32 pm

Re: Slower boot times

#17

Post by Mauser » Tue Jan 08, 2019 11:56 pm

dreamer wrote:
Tue Jan 08, 2019 11:53 pm
skidoo wrote:
Tue Jan 08, 2019 9:08 pm
mauser, toward speeding up the "boot time", check which services (daemons) are being autostarted & disable any that you're sure you don't need.

dreamer, I too am not a fan of plymouth. Under sysV init, regardless whether plymouth runs, a bootlog file should be available for review, pathed under /var/log
It might be enlightening to grep the logfile (or open in a text editor and search ) for instances of "warn" or "fail"
Good suggestion. I knew there was a log, but I didn't know where. Mauser, you should examine that file and if you post it here someone might actually understand what is going on.
Also disconnect USB devices.
I disabled what I didn't need. Same slow boot. What log? Where? Also, if I disconnect all the USB devices I can't operate the computer.
I am command line illiterate. :confused:

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 4585
Joined: Sun May 27, 2007 5:37 am

Re: Slower boot times

#18

Post by asqwerth » Wed Jan 09, 2019 12:07 am

Is it "decipher" or "descriptor" error?

I found this by googling "usb1-1 device error on bootup"

https://bbs.archlinux.org/viewtopic.php?id=149384
https://paulphilippov.com/articles/how- ... ress-error

Second link has this bit:
If Linux suddenly happen to fail to recognize a USB drive, check

Code: Select all

dmesg


for errors. Once you see a bunch of errors like

usb 1-5: device descriptor read/64, error -32
usb 1-5: new high speed USB device using ehci_hcd and address 21
usb 1-5: device not accepting address 21, error -32

most probably it’s a result of hardware failure rather than a driver or kernel bug. USB has an over-current protection, which gets triggered when power consumption from the port is too high.

Unplug all USB devices from PC, turn power off, and wait a minute or two. Plug everything back and boot into Linux.

I spent the whole morning, until found out why. I hope that this message will save someone a few hours, and nerves.

PS: Actual errors may vary. You may see different port and/or error code. Ex.:.....
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
Mauser
Forum Guide
Forum Guide
Posts: 1068
Joined: Mon Jun 27, 2016 7:32 pm

Re: Slower boot times

#19

Post by Mauser » Wed Jan 09, 2019 12:17 am

asqwerth wrote:
Wed Jan 09, 2019 12:07 am
Is it "decipher" or "descriptor" error?

I found this by googling "usb1-1 device error on bootup"

https://bbs.archlinux.org/viewtopic.php?id=149384
https://paulphilippov.com/articles/how- ... ress-error

Second link has this bit:
If Linux suddenly happen to fail to recognize a USB drive, check

Code: Select all

dmesg


for errors. Once you see a bunch of errors like

usb 1-5: device descriptor read/64, error -32
usb 1-5: new high speed USB device using ehci_hcd and address 21
usb 1-5: device not accepting address 21, error -32

most probably it’s a result of hardware failure rather than a driver or kernel bug. USB has an over-current protection, which gets triggered when power consumption from the port is too high.

Unplug all USB devices from PC, turn power off, and wait a minute or two. Plug everything back and boot into Linux.

I spent the whole morning, until found out why. I hope that this message will save someone a few hours, and nerves.

PS: Actual errors may vary. You may see different port and/or error code. Ex.:.....
Thanks. The strangest thing happened. I didn't change anything. I just re-booted to double check on what USB error it was precisely and it booted fine, nice and fast. I am going to enable the splash screen and reboot to see if it still boots fast as it should. I will report back after this reboot.
I am command line illiterate. :confused:

User avatar
dreamer
Forum Regular
Forum Regular
Posts: 437
Joined: Sun Oct 15, 2017 11:34 am

Re: Slower boot times

#20

Post by dreamer » Wed Jan 09, 2019 12:25 am

Mauser wrote:
Tue Jan 08, 2019 11:56 pm
I disabled what I didn't need. Same slow boot. What log? Where? Also, if I disconnect all the USB devices I can't operate the computer.
The file seems to be /var/log/boot

It contains lots of info, but at the end there is info from the latest boot up. Look at the timestamps and post what you think is relevant.

This is info from last boot up of this computer (lots of info for people who understand it - look for error messages and warnings)

Code: Select all

Tue Jan  8 22:27:07 2019: [....] Activating swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:08 2019: [....] Cleaning up temporary files... /tmp^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:08 2019: [....] Starting early crypto disks...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:08 2019: [....] Starting remaining crypto disks...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:08 2019: [....] Activating lvm and md swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:08 2019: [....] Checking file systems...fsck from util-linux 2.29.2
Tue Jan  8 22:27:08 2019: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:09 2019: [^[[36minfo^[[39;49m] Loading kernel module lp.
Tue Jan  8 22:27:09 2019: [^[[36minfo^[[39;49m] Loading kernel module ppdev.
Tue Jan  8 22:27:09 2019: [^[[36minfo^[[39;49m] Loading kernel module parport_pc.
Tue Jan  8 22:27:09 2019: [^[[36minfo^[[39;49m] Loading kernel module loop.
Tue Jan  8 22:27:09 2019: [....] Mounting local filesystems...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:09 2019: [....] Activating swapfile swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:09 2019: [....] Cleaning up temporary files...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:09 2019: [....] Skip starting firewall: ufw (not enabled)...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:09 2019: [....] Setting kernel variables...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:09 2019: [....] Setting up resolvconf...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:10 2019: [....] Configuring network interfaces...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:10 2019: [....] Starting RPC port mapper daemon: rpcbind^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:11 2019: [....] Starting NFS common utilities: statd idmapd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:11 2019: [....] Cleaning up temporary files...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:11 2019: [....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:11 2019: [....] Setting up ALSA...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:11 2019: [....] Setting sensors limits...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:11 2019: INIT: Entering runlevel: 5
Tue Jan  8 22:27:11 2019: [^[[36minfo^[[39;49m] Using makefile-style concurrent boot in runlevel 5.
Tue Jan  8 22:27:11 2019: [....] Starting acpi_fakekey daemon...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:12 2019: [....] Starting cgroup management daemon: cgmanager[....] Setting up console font and keymap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:12 2019: [....] Starting cgroup management proxy daemon: cgproxy^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:13 2019: [....] Not starting NFS kernel daemon: no exports. ...^[[?25l^[[?1c^[7^[[1G[^[[33mwarn^[[39;49m^[8^[[?25h^[[?0c ^[[33m(warning).^[[39;49m
Tue Jan  8 22:27:13 2019: [....] VirtualBox Additions disabled, not in a Virtual Machine ...^[[?25l^[[?1c^[7^[[1G[^[[33mwarn^[[39;49m^[8^[[?25h^[[?0c ^[[33m(warning).^[[39;49m
Tue Jan  8 22:27:13 2019: [....] Starting enhanced syslogd: rsyslogd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:13 2019: [....] Starting ACPI services: acpid^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:13 2019: [....] Starting anac(h)ronistic cron: anacron^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:14 2019: [....] Starting periodic command scheduler: cron^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:14 2019: [....] Starting CUPS Bonjour daemon: cups-browsed^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:14 2019: Applying power save settings...done.
Tue Jan  8 22:27:14 2019: Setting battery charge thresholds...done.
Tue Jan  8 22:27:14 2019: Radio device states restored.
Tue Jan  8 22:27:15 2019: [....] Starting Common Unix Printing System: cupsd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:15 2019: [....] Starting NTP server: ntpd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:15 2019: [....] Starting system message bus: dbus^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:16 2019: [....] Loading cpufreq kernel modules...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone (acpi-cpufreq).
Tue Jan  8 22:27:16 2019: [....] Starting Light Display Manager: lightdm^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:16 2019: [....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:16 2019: [....] CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU1...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Tue Jan  8 22:27:16 2019: [....] saned disabled; edit /etc/default/saned^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:17 2019: [....] Starting network connection manager: NetworkManager^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Tue Jan  8 22:27:19 2019: vboxdrv.sh: Starting VirtualBox services.
Tue Jan  8 22:27:20 2019: [....] Starting virtual private network daemon:^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.

Post Reply

Return to “MX Help”