Arch Linux

Mohamed37

Member

Registered: 2022-08-22

Posts: 2

Slow boot on lenovo laptop comparing to windows

Hello everyone i have a problem with my lenovo laptop 15iml05 .the lenovo logo appears after 30 seconds (the laptop during this 30 s turns up and turns down).this problem i encountred every linux distribution but in windows my laptop boot normally .this is a video short from youtube which explain my problem : https://www.youtube.com/shorts/tpqhXXBTgYg

mpan

Member

Registered: 2012-08-01

Posts: 1,208

Website

Re: Slow boot on lenovo laptop comparing to windows

Does that happen with Windows actually shut down or only hibernated?

Note that if you ask Windows to shut down, it will not shut down, but only hibernate in a way marketed as “Fast Startup” by Microsoft.⁽¹⁾ So to avoid comparing apples to oranges, first try with that feature disabled in Windows and ensure it too goes through the complete boot process. Alternatively compare with Linux hibernating, ensuring that all user’s processes are closed before suspending.
____
⁽¹⁾ May not happen if the hardware is not providing required features, but that is rare nowadays.

---

Sometimes I seem a bit harsh — don’t get offended too easily!

Mohamed37

Member

Registered: 2022-08-22

Posts: 2

Re: Slow boot on lenovo laptop comparing to windows

i haven't dual boot on my laptop i have only linux installed in my laptop. this problem occurs with all linux distributions that i installed . when i have windows only  installed in my laptop my system boot in 10 seconds but when i have only linux system installed in my laptop i have to wait about 30 to show lenovo logo (40s to boot system ) .

mpan

Member

Registered: 2012-08-01

Posts: 1,208

Website

Re: Slow boot on lenovo laptop comparing to windows

I did not mention dual boot.

Last edited by mpan (2022-08-22 14:30:09)

---

Sometimes I seem a bit harsh — don’t get offended too easily!

raindog1975

Member

From: Romania

Registered: 2017-04-04

Posts: 18

Re: Slow boot on lenovo laptop comparing to windows

Try ( as root or with sudo ) systemd-analyze blame and post the result.