Manjaro KDE boot time on ssd vs windows 10 on same ssd.

Hello everybody,
I just bought an acer laptop with windows 10 in 128G SSD. It's boot time was pretty low like 7secs to login environment.
but i liked manjaro kde so much that i formatted my 128G ssd and installed kde there.
but my boot time here is like:- 9.8sec( 4.7firmware, 1.2loader, 1.9kernel, 1.9userspace) & graphical target reached after 1.7sec.

Thing is, can i make it boot even faster like in 6-7secs??
is it possible to decrease firmware time?? need urgent help plz.
I gotta challenge against my entire batch buddies who are bragging about their 7sec boot time in Windows 10.

The youth of today :wink:

I can darkly remember times when, after switching on the PC, I went into the kitchen to make myself a coffee and smoke a cigarette. When I came back the PC was almost ready to boot. :wink:
Today it's fortunately better, I don't smoke anymore. :wink:

~ >>> systemd-analyze                                                                                                          [130]
Startup finished in 2.334s (kernel) + 2.760s (userspace) = 5.095s 
graphical.target reached after 2.658s in userspace

show systemd-analyze blame

sgs@mx Linux 5.3.13-1-MANJARO x86_64 18.1.3 Juhraya
~ >>> systemd-analyze blame                                                                                                         
1.235s systemd-logind.service                
1.182s lightdm.service                       
 709ms systemd-modules-load.service          
 661ms media-sdd3.mount                      
 507ms ufw.service                           
 417ms upower.service                        
 400ms udisks2.service                       
 396ms dev-sda2.device                       
 263ms systemd-journald.service              
 210ms systemd-timesyncd.service             
 189ms systemd-random-seed.service           
 185ms systemd-udevd.service                 
 172ms ldconfig.service                      
 163ms media-sdc2.mount                      
 148ms org.cups.cupsd.service                
 133ms media-sdc1.mount                      
 131ms media-sdc3.mount                      
 101ms accounts-daemon.service               
  94ms media-sdd1.mount                      
  86ms media-sdd2.mount                      
  73ms systemd-udev-trigger.service          
  69ms polkit.service                        
  69ms user@1000.service                     
  58ms dev-zram0.swap                        
  53ms NetworkManager.service                
  51ms lm_sensors.service                    
  50ms systemd-rfkill.service                
  33ms systemd-tmpfiles-clean.service        
  22ms media-sdb1.mount                      
  22ms systemd-journal-flush.service         
  20ms systemd-sysusers.service              
  19ms wpa_supplicant.service                
  19ms systemd-tmpfiles-setup.service        
  18ms systemd-journal-catalog-update.service
  16ms colord.service                        
  15ms zram-setup@zram0.service              
  12ms user-runtime-dir@1000.service         
  10ms systemd-binfmt.service                
  10ms systemd-tmpfiles-setup-dev.service    
   9ms systemd-remount-fs.service            
   9ms alsa-restore.service                  
   9ms dev-hugepages.mount                   
   8ms dev-mqueue.mount                      
   8ms sys-kernel-debug.mount                
   8ms systemd-update-utmp.service           
   7ms kmod-static-nodes.service             
   7ms tmp.mount                             
   6ms systemd-sysctl.service                
   5ms systemd-update-done.service           
   5ms sys-kernel-config.mount               
   4ms systemd-user-sessions.service         
   4ms sys-fs-fuse-connections.mount         
   3ms rtkit-daemon.service                  
   2ms proc-sys-fs-binfmt_misc.mount  

3 Likes

reducing boot time for bragging rights to your windoze buddies is hardly an urgent matter.

if manjaro is installed as UEFI then disable legacy support in bios so it's "UEFI ONLY" and firmware times should be shorter. making grub's timeout to 0 can also speed things up but if you ever need to use grub menu for whatever reason you'll need to spam the esc key during boot to get to it.

tell them to disable "fast boot" and then compare times considering fast boot doesnt actually shutdown the computer, it's more of a hibernate. or see how fast your manjaro can resume from hibernate since it's pretty much what windoze fast boot really is. but again this is not an urgent matter.

in the time your "buddies" even get steam launched you could already be in a game launched from steam on linux. comparing linux vs. windows is a joke, just ask them how long their last update took :face_with_hand_over_mouth:

3 Likes

When your boot time will be 5sec you will be the weirdo who is using that linux, you are not gonna win against Win users anyway...

2 Likes

This is Linux!

Bragging rights are earned by the amount of uptime in Linux. Let your idiotic Windows buddies (why do you have friends in low places?) try to match you at that. :smiley:

3 Likes

Smart guy. :+1:

2 Likes

yeah I have three days! My work Lenovo P53with Win has 123 days! :star_struck:

Screenshot%20from%202019-11-28%2020-19-40

Wrong range or do nothing else?

Don't trust a photo you didn't fake yourself.

Zusammenfassung

image

1 Like

Yeah why not? This machine is meant to run SIL 24/7

One of us should change the translation aid.

Every OS these days can run for months without reboot, but Android :slight_smile:

One's a rolling-release. The other...a broken-release?

We're comparing water to sheet metal.

My advice is to use your PC instead of over-tweaking it. This is how my boot time looks like [after tweaking]:

$ systemd-analyze
Startup finished in 14.260s (firmware) + 3.237s (loader) + 3.193s (kernel) + 10.962s (userspace) = 31.652s 
graphical.target reached after 10.819s in userspace

Firmware and userspace "times" are extra long only because of consequences of extra comfort (network shares and services) and firmware limitations (charging laptop through usb hub adds extra time for checking even more usb boot devices).

1 Like

At first i got a bit confused with 'windoze' or 'windose' but then after several hours of rigorous thinking in my newly learned yoga position, i finally understood what you meant, it was the epiphany moment :grinning:

And the answer was windoze because they sold hibernation to people as their fastboot. So manjaro won by default. Windoze never was in competition.
Now the hard part here is explaining this to my windoze buddies :cold_sweat:

no, windoze because it's slow. but your understanding of it also works. :+1:

4 Likes

haha. this made me chuckle. its been the case for a very long time. Their startup times are horrible (even worse if you are in one of those positions where maybe wifi drivers wont initialize for 20+ minutes) so the obvious solution was 'lets just not shut down, and say we did!'.

Oh, windoze, you devilish malware, you. :kissing: :japanese_ogre:

[also by the way - one of the main reasons for the moniker 'windoze' is not to be derogatory so much as that continually plugging a certain term in here will mean it becomes common and scraped - we will end up with even more M$oft questions then we already do now. Besides, they dont need any extra free advertising. And so something is used as a stand-in thats easy to type and gets the point across]

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by