You are not logged in.
sorry for the delay. The hard disk is dead. Today i'm gonna buy another similar, install again Helium and put the output of this commands.Thanks.
Looks like you found the culprit then. Dying hard drives and SSD’s can manifest themselves with issues like what you encountered. Hope you can back up data before the drive goes entirely.
Real Men Use Linux
Offline
Installed Helium in the new hard drive. same problems.
sudo systemd-analyze blame
11.997s apparmor.service
6.514s NetworkManager-wait-online.service
5.631s dev-sda1.device
4.217s ModemManager.service
2.614s loadcpufreq.service
2.517s NetworkManager.service
2.107s systemd-logind.service
1.932s rsyslog.service
1.926s alsa-restore.service
1.875s lm-sensors.service
1.873s lvm2-monitor.service
1.521s polkit.service
1.489s networking.service
1.464s keyboard-setup.service
1.321s systemd-tmpfiles-setup-dev.service
784ms upower.service
673ms dev-mqueue.mount
670ms dev-hugepages.mount
642ms dev-disk-by\x2duuid-812219d9\x2da45d\x2d4ee4\x2da62d\x2d6dcf1c40a6c
624ms systemd-sysctl.service
595ms systemd-udevd.service
587ms lightdm.service
550ms systemd-remount-fs.service
471ms systemd-tmpfiles-setup.service
462ms systemd-random-seed.service
456ms cpufrequtils.service
420ms sys-kernel-debug.mount
417ms systemd-journal-flush.service
356ms console-setup.service
344ms systemd-journald.service
338ms systemd-update-utmp.service
328ms ntp.service
321ms systemd-udev-trigger.service
264ms systemd-modules-load.service
264ms kmod-static-nodes.service
225ms user@109.service
80ms user@1000.service
57ms hddtemp.service
43ms systemd-user-sessions.service
16ms systemd-update-utmp-runlevel.service
10ms sys-fs-fuse-connections.mount
sudo systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @27.065s
└─multi-user.target @27.063s
└─ntp.service @26.734s +328ms
└─network-online.target @26.732s
└─NetworkManager-wait-online.service @20.217s +6.514s
└─NetworkManager.service @17.698s +2.517s
└─dbus.service @16.081s
└─basic.target @15.950s
└─sockets.target @15.943s
└─dbus.socket @15.943s
└─sysinit.target @15.943s
└─apparmor.service @3.945s +11.997s
└─local-fs.target @3.944s
└─run-user-109.mount @24.075s
└─local-fs-pre.target @3.943s
└─lvm2-monitor.service @2.070s +1.873s
└─lvm2-lvmetad.service @3.201s
└─lvm2-lvmetad.socket @2.066s
└─-.mount @1.681s
└─system.slice @1.766s
└─-.slice @1.681s
Offline
See what this does...
sudo systemctl disable NetworkManager-wait-online.service
And if you aren't using a modem...
sudo systemctl disable ModemManager.service
I always disable both of these on my installs.
Maybe also investigate apparmor, and see if disabling it helps?: Debian AppArmor HowToUse
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
All disabled (NetworkManager-wait-online, ModemManager and AppArmor), not better results
Offline
All Solved with: (after reading this page NvidiaGraphicsDrivers)
apt-get install -t stretch-backports linux-headers-$(uname -r|sed 's/[^-]*-[^-]*-//')
and
apt-get install -t stretch-backports nvidia-driver
Many many thanks for your effort and time.
Last edited by meravega (2018-09-17 22:58:57)
Offline