You are not logged in.

#1 2020-04-23 07:54:34

mkoniec
Member
Registered: 2020-04-23
Posts: 2

Slow dual boot with Windows 10

Hi. I hope you are able to help me. I have installed Windows 10 (for games) and Arch on the same laptop (Core I7 7th gen, 8 RAM + Nvidia Optimus). The problem is while Windows 10 boots really quick, Arch takes ages to boot. Here is my configuration:

/dev/nvme0n1p1 - 529 M - Windows Recovery
/dev/nvme0n1p2 - 100 M - EFI
/dev/nvme0n1p3 - 16 M - Microsoft partition (whatever it is needed for...)
/dev/nvme0n1p4 - 476.3 G - main Windows partition

/dev/sda1 - 500 G - Games (NTFS)
/dev/sda2 - 100 G - Documents (NTFS)
/dev/sda3 - 10 G - Documents (FAT - encrypted with vera crypt; for documents that have personal information )
/dev/sda4 - 321,5 G - Ext4, Linux

When it comes to GPU, I have installed nvidia proprietary drivers and disabled the Intel one. I am using KDE + GDM.

The outcome of "systemd-analyze blame":

18.730s systemd-journal-flush.service                       
13.536s mariadb.service                                     
10.045s udisks2.service                                     
7.829s org.cups.cupsd.service                               
6.099s lvm2-monitor.service                                 
5.338s dev-sda4.device                                     
4.048s accounts-daemon.service                             
3.797s user@120.service                                     
3.540s bluetooth.service                                   
3.536s NetworkManager.service                               
3.330s systemd-tmpfiles-setup.service                       
2.684s systemd-logind.service                               
2.424s systemd-udevd.service                               
1.788s polkit.service                                       
1.241s ufw.service                                         
  943ms systemd-tmpfiles-clean.service                       
  834ms upower.service                                       
  764ms systemd-random-seed.service                         
  688ms systemd-modules-load.service                         
  663ms systemd-backlight@backlight:intel_backlight.service 
  660ms systemd-udev-trigger.service                         
  564ms gdm.service                                         
  506ms wpa_supplicant.service                               
  499ms systemd-tmpfiles-setup-dev.service                   
  466ms modprobe@drm.service                                 
  461ms colord.service                                       
  439ms systemd-rfkill.service                               
  401ms systemd-journald.service                             
  399ms systemd-binfmt.service   
663ms systemd-backlight@backlight:intel_backlight.service 
  660ms systemd-udev-trigger.service                         
  564ms gdm.service                                         
  506ms wpa_supplicant.service                               
  499ms systemd-tmpfiles-setup-dev.service                   
  466ms modprobe@drm.service                                 
  461ms colord.service                                       
  439ms systemd-rfkill.service                               
  401ms systemd-journald.service                             
  399ms systemd-binfmt.service                               
  333ms systemd-update-utmp.service                         
  262ms systemd-fsck@dev-disk-by\x2duuid-8C77\x2dC96B.service
  203ms systemd-sysctl.service                               
  167ms user@1000.service                                   
  119ms kmod-static-nodes.service                           
   95ms boot-efi.mount                                       
   61ms systemd-user-sessions.service                       
   59ms dev-hugepages.mount                                 
   57ms dev-mqueue.mount                                     
   55ms sys-kernel-debug.mount                               
   53ms sys-kernel-tracing.mount                             
   39ms systemd-remount-fs.service                           
   38ms user-runtime-dir@120.service                         
   25ms tmp.mount                                           
   23ms user-runtime-dir@1000.service                       
   16ms rtkit-daemon.service                                 
    4ms proc-sys-fs-binfmt_misc.mount                       
    3ms sys-fs-fuse-connections.mount                       
    2ms sys-kernel-config.mount 

I have noticed that two steps cause quite a delay: loading initramfs and KDE startup. Any help would be much appreciated. Thank you.

Offline

#2 2020-04-23 10:37:56

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: Slow dual boot with Windows 10

Have you disabled "Fast Startup" [sic] for Windows? That would allow for a fairer comparison and it's possible that Windows' hybrid suspend state may be delaying your Arch boot.

mkoniec wrote:

The outcome of "systemd-analyze blame"

How about the plain `systemd-analyze` output? That should show kernel & firmware times for UEFI systems. Not that there's much you can do about those but it would at least give a fuller picture.

mkoniec wrote:

I have noticed that two steps cause quite a delay: loading initramfs and KDE startup

For the initramfs stage you could try stripping it down, see falconindy's guide here: http://blog.falconindy.com/articles/opt … tcpio.html (nice choice of logo, Mr. Reisner).

For KDE perhaps try SDDM as a display manager instead of GDM, or even no display manager at all for the none-more-minimal approach.

Offline

#3 2020-04-23 17:02:02

mkoniec
Member
Registered: 2020-04-23
Posts: 2

Re: Slow dual boot with Windows 10

Thank you for your suggestions. I have the fast boot option turned off.

I have now managed to reduce the boot time quite efficiently. The systemd-analyze is now:

Startup finished in 3.821s (firmware) + 3.730s (loader) + 3.267s (kernel) + 13.276s (userspace) = 24.096s
graphical.target reached after 10.346s in userspace

The graphical.target value before was 30s. I have switched to SDDM, followed the instructions for initramfs (I also disabled fsck - not quite sure if that was a good idea).

Additionally, I used the following link to adjust systemd journal flush.

https://unix.stackexchange.com/question … h-later-ma

I think I will change the SSD partition split and include some space for Arch and just leave /home on the sda.

Offline

Board footer

Powered by FluxBB