You are not logged in.
the solution to the problem is to install the "haveged" package (I also wanted to write)
https://debianforum.de/forum/viewtopic. … 5#p1173564
This works for me with the old CPU O:)
Thank you!
Offline
This works for me too ! thx guys :kiss:
Last edited by Holic_Fr (2018-05-08 21:27:42)
Offline
Hi guys, I was also frustrated with this problem. This seems to have solved it. But I'll be testing more.
sudo apt install haveged
PC specs : Sony Vaio YB series 11" netbook - AMD E-350, Radeon 6310, 4gb Ram, 1 TB SATA (no SSD).
I ran the Bunsen Lab Helium off a live USB stick and it worked flawlessly, the system booted instantly and I was impressed with the performance. My dual monitor setup also worked great.
I decided to install it, but the installer was a headache (manual partitioning), took me 3 tries to wrap my head around the installer and finally got it done. I configured my wifi during the install, Someone had mentioned above that that might be the culprit. But I haven't tested the install without the wifi.
The prob starts from the GRUB bootloader screen:
- Bootloader to login screen is very long ~2-3 mins, I thought the computer has frozen. It just displayed a black screen. Pressed keys on keyboard, and maybe that might've moved it ahead.
- Login to actual desktop : Here also, the computer became unresponsive. Finally everything loaded after 3-5 mins. Very sluggish.
- Firefox launch ,: Just the launch took 1min to load. Youtube and other sites take forever to load. And most sites say "Problem with network" or something similar.
Now these probs were not there during the live USB, it was just fast.
I noticed that the culprit might be the the OS not utilizing full CPU.
On live USB boot, the CPU was at :
Idle - 3%
Firefox launch - 95%
Youtube site launch -80-95%
but after installation on HDD:
Idle CPU avg - 5-10%
Firefox launch - 60%
Any site launch (youtube/ faceboo) - still 40-65%
max usage is 85%
So I think the installed version is not utilizing my CPU efficiently and since its a very weak CPU utilizing, half the power would result in the system being unresponsive.
I am attaching the output
systemd-analyze blame
and maybe the network might also be an issue (but the same network worked flawlessly with the Live USB boot)
@debian~$ systemd-analyze blame
30.216s NetworkManager-wait-online.service
4.997s dev-sda9.device
4.436s ModemManager.service
4.422s NetworkManager.service
3.673s alsa-restore.service
3.257s loadcpufreq.service
1.981s systemd-rfkill.service
1.806s networking.service
1.683s polkit.service
1.426s cpufrequtils.service
1.208s lvm2-monitor.service
1.159s rsyslog.service
817ms systemd-udevd.service
789ms keyboard-setup.service
720ms upower.service
637ms lm-sensors.service
532ms systemd-backlight@backlight:acpi_video0.service
398ms dev-mqueue.mount
396ms sys-kernel-debug.mount
386ms wpa_supplicant.service
338ms systemd-tmpfiles-setup-dev.service
332ms systemd-remount-fs.service
292ms dev-hugepages.mount
280ms systemd-udev-trigger.service
253ms systemd-logind.service
241ms systemd-journald.service
210ms lightdm.service
198ms systemd-tmpfiles-setup.service
189ms ntp.service
153ms systemd-journal-flush.service
140ms user@109.service
135ms console-setup.service
135ms systemd-modules-load.service
124ms kmod-static-nodes.service
Offline
theblur, i'm not sure i understand: is your problem solved now?
Offline