I'll say right off that my 2.8..upgraded from 2.6....from 2.4...was running fine. I thought, what the heck, i'll wipe the SSD and try the brand new shiny 3.0. Big mistake...the install worked but the startup on this version is 30 seconds. My 2.4/2.6/2.8 version was 5 to 6 seconds.
getting to the desktop and functionality seems the same but man is it slow to get there...can someone shed some light on why its so slow? Are there any tweaks that can get this thing up and moving like before?
thanks
This is not a common complaint so far. To help your specific problem you should consider uploading a system report so those interested may be able to supply some help.
Open a terminal and do:
Code:
systemd-analyze blame
Paste the results using the [ code ] tags. Thank you.
(06-05-2016, 02:41 PM)Jerry link Wrote: [ -> ]Open a terminal and do:
Code:
systemd-analyze blame
Paste the results using the [ code ] tags. Thank you.
Code:
systemd-analyze blame
7.418s apt-daily.service
5.449s NetworkManager-wait-online.service
496ms lvm2-monitor.service
479ms dev-sda1.device
446ms nmbd.service
336ms samba-ad-dc.service
295ms networking.service
259ms upower.service
247ms smbd.service
239ms ModemManager.service
238ms accounts-daemon.service
220ms systemd-logind.service
191ms ufw.service
186ms gpu-manager.service
184ms NetworkManager.service
180ms apparmor.service
161ms console-setup.service
154ms irqbalance.service
145ms grub-common.service
139ms virtualbox-guest-utils.service
132ms ondemand.service
127ms alsa-restore.service
120ms lightdm.service
If needed, I can reinstall LL 3 from scratch and compare. OR I could install 2.8..either way I'd be willing if needed
this is from post to desktop
I reinstalled 2.8 and the speed is back...without any tweaks or even updating after install....it's 9 seconds to desktop...systemd-analyze didn't work with 2.8 so i just timed it with a clock...i'm going to reinstall 3.0 and see again
whats odd is when 3.0 is booting, the hdd activity light is hardly showing any activity....then when it gets near the end of 30 seconds, it comes to life...with 2.8 it seems like its on or blinking most of the time
2.8 uses a completely different init (boot sequence) system to 3.0
2.8 uses upstart and 3.0 uses systemd. IMO, both have their pros and cons, you can easily find anywhere on the net, people who have long boot ups under upstart, and quick boots under systemd. Mine boots so fast under 3.0 that I barely get to see the splash screen.
fresh install of 3.0...2 different startups
Code:
$ systemd-analyze blame
7.473s NetworkManager-wait-online.service
829ms apt-daily.service
465ms dev-sda1.device
401ms accounts-daemon.service
380ms ModemManager.service
359ms lvm2-monitor.service
348ms nmbd.service
314ms networking.service
301ms samba-ad-dc.service
271ms systemd-logind.service
256ms NetworkManager.service
249ms lightdm.service
248ms avahi-daemon.service
242ms smbd.service
222ms upower.service
212ms ufw.service
195ms irqbalance.service
189ms ondemand.service
187ms grub-common.service
185ms gpu-manager.service
171ms virtualbox-guest-utils.service
171ms apparmor.service
154ms console-setup.service
Code:
systemd-analyze blame
7.304s NetworkManager-wait-online.service
668ms lvm2-monitor.service
455ms dev-sda1.device
292ms nmbd.service
265ms ModemManager.service
249ms samba-ad-dc.service
246ms accounts-daemon.service
239ms smbd.service
238ms networking.service
217ms ufw.service
202ms systemd-logind.service
185ms upower.service
173ms NetworkManager.service
167ms lightdm.service
166ms irqbalance.service
150ms grub-common.service
150ms virtualbox-guest-utils.service
147ms gpu-manager.service
130ms ondemand.service
102ms apparmor.service
90ms alsa-restore.service
90ms systemd-udev-trigger.service
85ms console-setup.service
maybe its the hardware. I'm not sure. It's startling that my bootup is this far apart from the old version. I guess its going to be 2.8 for a while.
Hi, I've slowly moved up from 2.6 on 2 notebooks and 2.8 on this Presario 2100 with 1gb Ram. 2.8 had what I consider a normal boot time - LL3 on the Presario takes aprox 15 minutes. It only has USB 1, which I used Kplop to boot up from - I can't get my USB2 PCAMIA slots to boot even with plop for that. I've got LL3 on a 32gb stick & 8gb stick to trial it on the notebooks and it's fine on those.
Here's my system report: (I've also carried out a full system report - showing the innards of this machine, but that's 52 pages long!
Any ideas?
Thx for your time. Iestyn
dads@dads-Presario-2100-KE-Mx-xx:~$ systemd-analyze blame
10min 5.644s dev-sda1.device
9min 47.677s systemd-udev-trigger.service
3min 45.122s ntp.service
1min 14.577s apt-daily.service
25.069s nmbd.service
21.814s samba-ad-dc.service
14.320s NetworkManager-wait-online.service
10.457s smbd.service
9.050s NetworkManager.service
7.753s lightdm.service
7.591s apparmor.service
7.109s ufw.service
6.310s ModemManager.service
6.270s accounts-daemon.service
5.436s systemd-udevd.service
5.267s thermald.service
3.845s lvm2-monitor.service
3.587s systemd-tmpfiles-setup-dev.service
2.691s upower.service
2.526s gpu-manager.service
2.405s grub-common.service
2.176s systemd-journald.service
2.104s virtualbox-guest-utils.service
lines 1-23
(07-27-2016, 07:31 PM)Iestynrl link Wrote: [ -> ]Hi, I've slowly moved up from 2.6 on 2 notebooks and 2.8 on this Presario 2100 with 1gb Ram. 2.8 had what I consider a normal boot time - LL3 on the Presario takes aprox 15 minutes. It only has USB 1, which I used Kplop to boot up from - I can't get my USB2 PCAMIA slots to boot even with plop for that. I've got LL3 on a 32gb stick & 8gb stick to trial it on the notebooks and it's fine on those.
Here's my system report: (I've also carried out a full system report - showing the innards of this machine, but that's 52 pages long!
Any ideas?
Thx for your time. Iestyn
dads@dads-Presario-2100-KE-Mx-xx:~$ systemd-analyze blame
10min 5.644s dev-sda1.device
9min 47.677s systemd-udev-trigger.service
3min 45.122s ntp.service
1min 14.577s apt-daily.service
25.069s nmbd.service
21.814s samba-ad-dc.service
14.320s NetworkManager-wait-online.service
10.457s smbd.service
9.050s NetworkManager.service
7.753s lightdm.service
7.591s apparmor.service
7.109s ufw.service
6.310s ModemManager.service
6.270s accounts-daemon.service
5.436s systemd-udevd.service
5.267s thermald.service
3.845s lvm2-monitor.service
3.587s systemd-tmpfiles-setup-dev.service
2.691s upower.service
2.526s gpu-manager.service
2.405s grub-common.service
2.176s systemd-journald.service
2.104s virtualbox-guest-utils.service
lines 1-23
Message may have been overlooked because you've posted your issue in someone else's thread. Best practice is to start your own thread. Cheers.
Sent from my Nexus 6 using Tapatalk