Linux Mint Forums

Linux is an ideal OS to run on old, if not ancient hardware and, because of that it is brilliant on newer gear too. As can be seen from this little debacle, where a simple edit in the grub made all the difference. Perhaps, for a laugh, we should try Windows 10 on a ten year old computer. Anyhow, I do believe the Devs should test on the extremes of equipment which is generally in use out there in the World before release.

I remember, not that long ago, Plymouth was pulled from the boot sequence for a while because, as on the Devs computers they had a GUI up in <10 seconds until I pointed out a minute of a black screen was very disturbing on an old computer. We should always learn from the past.

raywoods wrote: ⤴Sat Aug 04, 2018 7:22 pm Linux is an ideal OS to run on old, if not ancient hardware and, because of that it is brilliant on newer gear too. As can be seen from this little debacle, where a simple edit in the grub made all the difference. Perhaps, for a laugh, we should try Windows 10 on a ten year old computer. Anyhow, I do believe the Devs should test on the extremes of equipment which is generally in use out there in the World before release.

Depends on the hardware. 10 years ago may not actually be all that bad. I would take a 10-year old Core 2 E8400, Core 2 Q9550 or i7-920 over any of the netbooks currently being sold pre-installed with Windows 10.

As for newer gear, relatively new, sure. Absolute bleeding edge might pose some compatibility issues.

Using LM19- Xfce. Followed the "[SOLVED}" solution, checked everything, GA-78LMT-USB3 board, 1TB HD, 6Mb RAM, onboard Radeon video - sadly, no improvement on the 8-10min. boot time. Any further advice please? did I do something wrong? need something different for this HW? other comments, suggestions?

Hello,

I have tried the solutions described above but it was not working for me.
So, I have done a new fresh install and it seems to be related that I have choose to encrypt for /home.
When I not select this option on the installation, the boot time was improved drastically

i have a notebook acer i5 7200

i think is very slow

systemd-analyze
Startup finished in 3.988s (firmware) + 6.310s (loader) + 36.616s (kernel) + 1min 5.539s (userspace) = 1min 52.454s
graphical.target reached after 1min 5.532s in userspace


System: Host: e15 Kernel: 4.15.0-29-generic x86_64 bits: 64 Desktop: MATE 1.20.1 Distro: Linux Mint 19 Tara
Machine: Device: laptop System: Acer product: Aspire E5-575 v: V1.12 serial: N/A
Mobo: Acer model: Ironman_SK v: V1.12 serial: N/A UEFI: Insyde v: V1.12 date: 08/02/2016
Battery BAT1: charge: 32.0 Wh 83.8% condition: 38.2/40.9 Wh (93%)
CPU: Dual core Intel Core i5-7200U (-MT-MCP-) cache: 3072 KB
clock speeds: max: 3100 MHz 1: 789 MHz 2: 780 MHz 3: 780 MHz 4: 788 MHz
Graphics: Card: Intel HD Graphics 620
Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1366x768@59.97hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2) version: 4.5 Mesa 18.0.5
Audio: Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel Sound: ALSA v: k4.15.0-29-generic
Network: Card-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter driver: ath10k_pci
IF: wlp2s0 state: up mac: <filter>
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
IF: enp3s0f1 state: down mac: <filter>
Drives: HDD Total Size: 1240.3GB (49.6% used)
ID-1: /dev/sda model: KINGSTON_SA400S3 size: 240.1GB
ID-2: /dev/sdb model: ST1000LM048 size: 1000.2GB
ID-3: /dev/mmcblk0 model: N/A size: 15.9GB
Partition: ID-1: / size: 125G used: 61G (52%) fs: ext4 dev: /dev/sdb2
ID-2: swap-1 size: 12.58GB used: 0.00GB (0%) fs: swap dev: /dev/dm-0
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 37.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 226 Uptime: 32 min Memory: 1352.4/11877.1MB Client: Shell (bash) inxi: 2.3.56


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 @1min 5.532s
└─multi-user.target @1min 5.532s
└─getty.target @1min 5.532s
└─getty@tty1.service @1min 5.532s
└─system-getty.slice @1min 5.531s
└─setvtrgb.service @1min 5.498s +32ms
└─systemd-user-sessions.service @33.258s +255ms
└─network.target @33.255s
└─NetworkManager.service @25.732s +7.517s
└─dbus.service @22.676s
└─basic.target @22.641s
└─sockets.target @22.641s
└─snapd.socket @22.623s +18ms
└─sysinit.target @22.408s
└─apparmor.service @19.009s +3.287s
└─local-fs.target @19.008s
└─run-vmblock\x2dfuse.mount @45.743s
└─local-fs-pre.target @13.038s
└─keyboard-setup.service @2.510s +10.527s
└─systemd-journald.socket @2.495s
└─system.slice @2.495s
└─-.slice @2.491s


on dmesg message:

[ 0.146441] platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
[ 0.146447] acpi MSFT0101:00: platform device creation failed: -16

in this point, seems 30 seconds wait

I timed the total time, from the beginning until the graphical screen appeared, it spent 1:55 seconds

candido...you need to start your own thread as the original poster of this one has marked it solved...this will then get the attn. of everyone here that can help you...DAMIEN

ps...when you do start your very own new thread post...please copy and paste the results of ... systemd-analyze blame ...DAMIEN

With respect, Damien, I would invite you to re-examine your recommendation to candido1212. Frankly, I find it absurd - his report is exactly pertinent to the topic. Some folks have found that "[SOLVED] Linux Mint 19 very slow boot times of ten minutes or so." is not "[SOLVED]". Any and all evidence relating must be relevant? Perhaps the great moderator-in-chief will invite the initiator of the thread to somewhat modify his title claim, since it is clear that a claim "[SOLVED]" turns out not yet to be universally substantiated, ipso facto more discussion on slow booting will be most welcome and all evidence needs to be considered until a universal " [SOLVED]" can be justifiably claimed. Seniority in posting is not always the best guide to impartial comment and decisions.

gort2000 wrote: ⤴Mon Jul 16, 2018 3:21 pm In short, normal boot times were restored to kernel 4.15 (but not 4.15.0-24) by adding "video=SVIDEO-1:d" to /etc/default/grub line GRUB_CMDLINE_LINUX_DEFAULT
It now reads;

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

Then update grub; sudo update-grub

gort2000 I subscribed just to say thank you. You rock man!

Problem solved on my HP Compaq 6510b which was incredibly slow at booting Linux MATE

How-old! wrote: ⤴Thu Aug 09, 2018 2:55 am With respect, Damien, I would invite you to re-examine your recommendation to candido1212. Frankly, I find it absurd - his report is exactly pertinent to the topic. Some folks have found that "[SOLVED] Linux Mint 19 very slow boot times of ten minutes or so." is not "[SOLVED]". Any and all evidence relating must be relevant? Perhaps the great moderator-in-chief will invite the initiator of the thread to somewhat modify his title claim, since it is clear that a claim "[SOLVED]" turns out not yet to be universally substantiated, ipso facto more discussion on slow booting will be most welcome and all evidence needs to be considered until a universal " [SOLVED]" can be justifiably claimed. Seniority in posting is not always the best guide to impartial comment and decisions.

To borrow your language, it's your proposal that is absurd. I get where you are coming from, but if the OP's specific problem is solved, then that's that. That's why we (and the forum rules) urge you to make your own thread for your own problem. The fact that it's not solved for you makes it more than clear that your problem is actually are different one from the one that OP has, so a different solution will have to be found for you.

how old said..."all evidence needs to be considered until a universal " [SOLVED]" can be justifiably claimed."...if there was such a thing as "universal" solved, then there would be no need for posting threads on a forum because it would be "one size fits all"...that is not how it works...people have so many different customisations, different softwares etc. which invites different conflicts etc. dual booting versus not dual boot, the possibilities are endless, therefore separate threads for each unique individual problem is warranted and indeed expected according to forum rules...DAMIEN

If you install Linux Mint 19 with no swap partition this is the fix that will bring your boot time back to normal:


https://askubuntu.com/a/1031667

1. Edit the file /etc/default/grub file so that the string noresume is included in the GRUB_CMDLINE_LINUX_DEFAULT line, for example:

   Code: Select all

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noresume"
   

2. Run this command to update GRUB:

   Code: Select all

   sudo update-grub
   

3. Reboot the computer

update
Apparently this won't work if you are using hibernation, then there is another fix:
https://askubuntu.com/a/1013935/605477

thanks,

now, and update to Linux Mint 19 v2

systemd-analyze

Startup finished in 4.038s (firmware) + 2.676s (loader) + 4.097s (kernel) + 16.892s (userspace) = 27.704s
graphical.target reached after 16.881s in userspace

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.

Code: Select all

graphical.target @16.881s
└─multi-user.target @16.881s
  └─virtualbox.service @16.765s +115ms
    └─network-online.target @16.763s
      └─NetworkManager-wait-online.service @10.499s +6.263s
        └─NetworkManager.service @10.218s +255ms
          └─dbus.service @10.175s
            └─basic.target @10.146s
              └─sockets.target @10.145s
                └─docker.socket @10.134s +9ms
                  └─sysinit.target @10.113s
                    └─swap.target @10.112s
                      └─home-swapfile.swap @9.727s +384ms
                        └─home.mount @9.386s +339ms
                          └─systemd-fsck@dev-disk-by\x2duuid-fc1a6362\x2db80c\x2d424b\x2daa9a\x2d27d34cacb462.service @1.136s +8.248s
                            └─dev-disk-by\x2duuid-fc1a6362\x2db80c\x2d424b\x2daa9a\x2d27d34cacb462.device @874ms

my /etc/default/grub