[enebre]

:wave
Linux Lite just installed.

Tout fonctionne bien, mais le boot est vraiment très lent, je donne ci-dessous le résultat de systemd-analyze blame. Que puis-je faire pour améliorer la situation ?


It work fine, but at boot it took several minutes to show up. 
Please, have you suggestion ?

Code:

 ~  systemd-analyze blame 52.229s logrotate.service 49.892s networking.service 15.971s blueman-mechanism.service 11.244s systemd-udev-settle.service 10.279s dev-sda2.device 9.885s systemd-journal-flush.service 9.665s networkd-dispatcher.service 8.661s accounts-daemon.service 6.869s NetworkManager.service 6.645s udisks2.service 5.102s NetworkManager-wait-online.service 4.098s avahi-daemon.service 3.767s nmbd.service 3.597s systemd-resolved.service 3.492s polkit.service 3.078s grub-common.service 3.051s gpu-manager.service 2.723s thermald.service 2.539s wpa_supplicant.service 2.340s smbd.service 2.337s rsyslog.service 2.291s alsa-restore.service 2.209s lightdm.service 2.195s plymouth-quit-wait.service 2.163s e2scrub_reap.service 2.078s systemd-logind.service 2.003s systemd-udevd.service 1.884s apparmor.service 1.872s secureboot-db.service 1.831s resolvconf-pull-resolved.service 1.716s cups.service 1.584s systemd-modules-load.service 1.403s systemd-rfkill.service 1.403s lm-sensors.service 1.333s ModemManager.service 1.091s packagekit.service 1.063s systemd-random-seed.service 1.061s keyboard-setup.service 1.054s systemd-backlight@backlight:radeon_bl0.service   920ms ntp.service   802ms grub-initrd-fallback.service   750ms systemd-tmpfiles-setup-dev.service   734ms systemd-networkd.service   718ms [email protected]   707ms systemd-journald.service   700ms zfs-load-module.service   696ms hddtemp.service   580ms systemd-tmpfiles-setup.service   539ms swapfile.swap   532ms systemd-sysusers.service   520ms systemd-sysctl.service   517ms ifupdown-pre.service   511ms upower.service

[valtam]

I think there are enough of these kind of threads for me to create a Sticky topic with tips for people to read through and try. A lot of these threads are from people with old computers, low spec pc's or slow hard drives so I hope they find it useful. In your particular case, the increase occurs in networking. Consider using a static ip address as explained in the Help Manual under the Network section - "Connecting to the Internet - Wired".

[enebre]

Thank for your answer

Code:

mick  ~  SIGINT  systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 17.050s └─multi-user.target @1min 17.049s   └─smbd.service @1min 14.707s +2.340s     └─nmbd.service @1min 10.926s +3.767s       └─network-online.target @1min 10.901s         └─network.target @1min 10.899s           └─networking.service @21.002s +49.892s             └─apparmor.service @17.479s +1.884s               └─local-fs.target @17.471s                 └─zfs-mount.service @17.247s +223ms                   └─zfs-import.target @17.241s mick  ~  ^C mick  ~  SIGINT 

[enebre]

Désolé pour le bazard, je ne suis pas encore bien habitué par votre forum
Sorry for the mess, I'm still not used to your forum


OK Wifi is working  :dft012:

Mais le boot est toujours lent, un petit peu moins, il semble y avoir un souci graphique, pourriez-vous m'orienter s'il vous plait ?

But the boot still slow, a little less than before, there seems to be a graphic problem, could you please direct me?

Code:

mick  ~  systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @57.633s └─multi-user.target @57.633s   └─smbd.service @54.099s +3.532s     └─nmbd.service @50.432s +3.653s       └─network-online.target @50.394s         └─network.target @50.391s           └─NetworkManager.service @19.186s +4.975s             └─dbus.service @19.170s               └─basic.target @19.105s                 └─sockets.target @19.105s                   └─uuidd.socket @19.105s                     └─sysinit.target @18.882s                       └─apparmor.service @16.920s +1.961s                         └─local-fs.target @16.914s                           └─zfs-mount.service @16.642s +270ms                             └─zfs-import.target @16.638s  mick  ~  

J'ai suivi la procédure expliquée ici :
I followed the procedure explained here: please use google translate page, if...

https://askubuntu.com/questions/419867/q...untu-13-10

Les infos du pc, mais il faudrait suivre la procédure pour comprendre correctement ce que l'on fait.
Cependant les dossiers de LL sont différents.
The info from my pc, but you would have to follow the procedure to understand correctly what you are doing.
However the LL files are different.
Code: [Select]
sudo  mousepad /etc/modprobe.d/iwlwifi.conf

Que j'ai changé, comme ceci : 
Which I changed, like this:

Code:

# /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system.  When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. # remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=0

Code:

mick  ~  lspci | grep -i net 02:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0) 07:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) mick  ~ 

Code:

mick  ~  sudo rfkill list 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no mick  ~ 

Code:

sudo /etc/modprobe.d/modprobe -r iwlwifi.conf

Code:

mick  /  etc  1  lspci -nnk | grep -iA2 net 02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet [1969:1083] (rev c0) Subsystem: Acer Incorporated [ALI] AR8151 v2.0 Gigabit Ethernet [1025:0690] Kernel driver in use: atl1c Kernel modules: atl1c -- 07:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Lite-On Communications Inc AR9485 Wireless Network Adapter [11ad:6617] Kernel driver in use: ath9k Kernel modules: ath9k mick  /  etc 

[vint]

[member=50471]enebre[/member],
My machine is almost 11 years old and dual booting W7 hp and LL 5.8 and the boot time is 1minute 32 seconds and Jerry has explained the problem many times to those of us with older machines.  Lite brings everything up unlike what W7 does that is it boots up the welcome page and the user is unable to do anything until all of the system software gathers in the background.  My boot time may be effected by the dual boot process and I am on WiFi.  There are items that can be turned off on start up and for that I would refer you to the Linux Lite manual.  Good luck.

Best regards.

[valtam]

Have you set a static IP for your network connection?

Sent from my Mobile phone using Tapatalk

[valtam]

I'm also going to add a SystemD report to Lite System Report in the future.

[valtam]

https://mityer.khdlhfjijfrupr.tk/forums/start...inux-lite/

Mods - please refer people to here in the first instance when offering guidance. Cheers

[vint]

[member=2]Jerry[/member],
Thanks for the detailed explanation on older hardware running Linux Lite, I appreciate the hard work you have put into this awesome Operating System you have developed.  I'm so glad I found Lite as it has breathed new life into my old machine.

Best regards,

[valtam]

[member=2]Jerry[/member],
Thanks for the detailed explanation on older hardware running Linux Lite, I appreciate the hard work you have put into this awesome Operating System you have developed.  I'm so glad I found Lite as it has breathed new life into my old machine.

Best regards,

You're welcome