Boot times

Chat about anything related to Linux Mint
Forum rules
Do not post support questions here. Before you post read the forum rules. Topics in this forum are automatically closed 6 months after creation.
Locked
AllanPen
Level 2
Level 2
Posts: 96
Joined: Fri Nov 01, 2013 8:33 pm
Location: Nanoose Bay, B.C., Canada

Boot times

Post by AllanPen »

I recently took the plunge and shrunk my laptop ssd drive to accommodate Mint. Actually I am a long time Mint user, but was a bit nervous dealing with the new UEFI format. Anyways it all went well. Also my ageing PC crashed and I built a new one with a B360 HD3 MB and an i5-8400 CPU with 16GB RAM.
I have a question. The laptop boots in 12 seconds. The PC is about 30 seconds and still multiple times faster than Windows 10. This is not a complaint, but I'm curious as to why my laptop boots Mint a couple of times faster than my PC. The laptop is a Dell Inspiron 15-5578.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
JerryF
Level 16
Level 16
Posts: 6571
Joined: Mon Jun 08, 2015 1:23 pm
Location: Rhode Island, USA

Re: Boot times

Post by JerryF »

The laptop has an SSD. Does the PC have an SSD or hard disk?

If the PC has a hard disk, then the laptop will boot quicker because is has an SSD, which is usually faster than a hard disk.
User avatar
trytip
Level 14
Level 14
Posts: 5367
Joined: Tue Jul 05, 2016 1:20 pm

Re: Boot times

Post by trytip »

this will tell you errors in boot (some can be fixed some issues like nvidia driver loading is up to nvidia devs.

Code: Select all

dmesg | grep -i "error\|warn\|fail"
this will tell you how everything is loaded (not available in 17.3)

Code: Select all

systemd-analyze blame
the more hardware you have installed the longer the boot will be. i have 5 spinning drives and settled for slow boot a while back but around 30-45 seconds is fine for me. sometimes when things are updating 1 minute is also fine
Image
AllanPen
Level 2
Level 2
Posts: 96
Joined: Fri Nov 01, 2013 8:33 pm
Location: Nanoose Bay, B.C., Canada

Re: Boot times

Post by AllanPen »

Yikes this doesn't look too good; I must have done something wrong.
allan@AllansPC ~ $ dmesg | grep -i "error\|warn\|fail"
[ 0.014410] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x33CDA (20170531/psloop-242)
[ 0.014417] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x33CE3 (20170531/psloop-242)
[ 0.014449] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x343CE (20170531/psloop-242)
[ 0.014454] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x343D7 (20170531/psloop-242)
[ 0.014484] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x34AC2 (20170531/psloop-242)
[ 0.014489] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x34ACB (20170531/psloop-242)
[ 0.014518] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x351B7 (20170531/psloop-242)
[ 0.014523] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x351C0 (20170531/psloop-242)
[ 0.014551] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x358AC (20170531/psloop-242)
[ 0.014556] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x358B5 (20170531/psloop-242)
[ 0.014564] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x35C5F (20170531/psloop-242)
[ 0.014569] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x35C68 (20170531/psloop-242)
[ 0.106809] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170531/dswload2-191)
[ 0.106817] ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170531/psparse-550)
[ 0.108030] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170531/dswload2-191)
[ 0.108035] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170531/psparse-550)
[ 0.109041] ACPI Error: [_SB_.PCI0.RP13.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170531/dswload2-191)
[ 0.109046] ACPI Error: Method parse/execution failed \_SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20170531/psparse-550)
[ 0.111893] ACPI Error: [\_SB_.PCI0.RP05.PXSX.WIST] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 0.111893] ACPI Error: Method parse/execution failed \CNDP, AE_NOT_FOUND (20170531/psparse-550)
[ 0.111893] ACPI Error: Method parse/execution failed \, AE_NOT_FOUND (20170531/psparse-550)
[ 3.230782] ACPI Error: Method parse/execution failed \_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170531/psparse-550)
[ 3.230790] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170531/uteval-103)
[ 3.231914] ACPI Error: Method parse/execution failed \_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170531/psparse-550)
[ 3.231921] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170531/uteval-103)
[ 4.051447] dpc 0000:00:1d.3:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 4.232540] RAS: Correctable Errors collector initialized.
[ 12.629021] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro
[ 1979.950791] ata5: COMRESET failed (errno=-16)
[ 2298.413757] ata5: COMRESET failed (errno=-16)
User avatar
trytip
Level 14
Level 14
Posts: 5367
Joined: Tue Jul 05, 2016 1:20 pm

Re: Boot times

Post by trytip »

@AllanPen
reboot a few times and check again dmesg | grep -i "error\|warn\|fail" some errors may be gone . ACPI errors are common but not so many. updating kernel can remove some but also new errors appear.
Image
AllanPen
Level 2
Level 2
Posts: 96
Joined: Fri Nov 01, 2013 8:33 pm
Location: Nanoose Bay, B.C., Canada

Re: Boot times

Post by AllanPen »

Did three reboots with the same results. Upgraded kernel to v4.14.15; same results:
~ $ dmesg | grep -i "error\|warn\|fail"
[ 0.015759] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x33CDA (20170728/psloop-247)
[ 0.015767] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x33CE3 (20170728/psloop-247)
[ 0.015822] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x343CE (20170728/psloop-247)
[ 0.015828] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x343D7 (20170728/psloop-247)
[ 0.015881] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x34AC2 (20170728/psloop-247)
[ 0.015886] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x34ACB (20170728/psloop-247)
[ 0.015939] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x351B7 (20170728/psloop-247)
[ 0.015944] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x351C0 (20170728/psloop-247)
[ 0.016054] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x358AC (20170728/psloop-247)
[ 0.016060] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x358B5 (20170728/psloop-247)
[ 0.016072] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x35C5F (20170728/psloop-247)
[ 0.016078] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x35C68 (20170728/psloop-247)
[ 0.115075] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
[ 0.115088] ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170728/psparse-550)
[ 0.116545] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
[ 0.116553] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170728/psparse-550)
[ 0.117806] ACPI Error: [_SB_.PCI0.RP13.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
[ 0.117814] ACPI Error: Method parse/execution failed \_SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20170728/psparse-550)
[ 0.121227] ACPI Error: [\_SB_.PCI0.RP05.PXSX.WIST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
[ 0.121227] ACPI Error: Method parse/execution failed \CNDP, AE_NOT_FOUND (20170728/psparse-550)
[ 0.121227] ACPI Error: Method parse/execution failed \, AE_NOT_FOUND (20170728/psparse-550)
[ 3.303199] ACPI Error: Method parse/execution failed \_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170728/psparse-550)
[ 3.303209] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170728/uteval-103)
[ 3.304551] ACPI Error: Method parse/execution failed \_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170728/psparse-550)
[ 3.304559] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170728/uteval-103)
[ 4.210615] dpc 0000:00:1d.3:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 4.395251] RAS: Correctable Errors collector initialized.
Locked

Return to “Chat about Linux Mint”