Boot too slow on my laptop

Hello.

I think my boot is far too long on this machine, and I wondered if you could help me making it more quick. I have made two bootchart, one stopping at kdm and one stopping at firefox. I’ll explain the latter one.

I fixed /sbin/bootchartd to instead of stopping at kdm it stopped on firefox. I then added in kde’s autorun that it should start firefox at startup. I then fixed in YaST2 so it would autologin on my account. The result is that it will boot up, autologin and start firefox and bootchart will show what happens until then.

Bootchart till firefox:
http://img518.imageshack.us/img518/8521/bootchart.th.png](http://img518.imageshack.us/img518/8521/bootchart.png)

Bootchart till KDM:
http://img300.imageshack.us/img300/7016/bootcharttokdm.th.png](http://img300.imageshack.us/img300/7016/bootcharttokdm.png)

Smolts profile:
Show Box

I can’t pretend to understand, but I am VERY impressed…

It’s rather easy. To get the graph, you install Bootchart and on the boot loader write init=/sbin/bootchartd. Boot then up as normal, and then open up a terminal and write bootchart. It will then make a picture like the one you see I’ve linked to in your home folder.

:wink:

> :wink:

and, some folks can probably look at that chart and save two or three
seconds here or there…

but, if you wanna REALLY save some seconds dump KDE and Firefox and go
with something a lot lighter and simpler…maybe Xfce and
Konqueror…there are LOTS of other choices…


nom de plume

The thing is, as you can see in the second graph, isn’t the desktop environment. The time taken from BOOTLOADER to LOGIN is 50 seconds. That is too long in my opinion, and that is what I want to shorten.

I can time starting Vista from bootloader to login, just for comparison.

What do you think of this one: I changed the horrible slow internal 120GB sataII hdd for a 32GB SSD. Boottime from GRUB to KDE4 up and running with wifi connection in less than 40 secs.
I’ve tried turning off services etc., that just brings a couple of secs, this is a factor 2,5 speed-up.

well, the info on how speed it up is “out there” somewhere…i
remember a mag article in either Linux Format, Linux Magazine or Linux
Journal in the last three to five years that laid out the different
places you could save a second or two…

like, you can cut the grub screen from default (of 5 or 10 seconds)
down to (say) 3, and turn off some stuff…i do not remember
what…but we talking saving maybe 10 seconds…

10 seconds every time you boot…big deal…shouldn’t boot over once
six months anyway…


MultiplePersonality

Disclaimer, as I cannot know everything about your computer or your use of it…I do not take responsibility for any negative outcomes that may arise from following this advice. This tutorial is the road I took to a faster boot time, it involves installing the minimum and building up from there…you want to perform surgery on a full install, so I can’t even begin to guarantee similar results

What you can cut out of your boot sequence depends on what you use your computer for.
Looking at your bootchart against my typical laptop usage I’d cut…

Pre KDM Items:
sshd
rpcbind
avahi-daemon
bluetooth
postfix

ntfs partition

Post KDM Items:
ksplashx
dcopserver
kupdateapplet + policykit-kde
pulseaudio

The first 5 you can kill in YaST via the runlevels module.

Do you need to mount an NTFS partition at boot time? If not use YaST (or manually edit fstab) to prevent that. The same holds true for other partition types, if you only need a partition 1 out of 10 or even 5 boots…why mount it at start-up every time? Mount extra partitions as you need them.

You can turn off the KDM splash in ‘Personal Settings’. The default looks the same as the main boot splash but the flicker + bar reset makes it look like a glitch, might as well turn it off.

The dcopserver is the interprocess communications method used by KDE3. So if you can migrate to the KDE4 version of network manager [which I’m telling you now is still in testing - you’ve been warned] you should be able to get past dcopserver. Personally I have exactly one KDE3 app left on my laptop - K3B and the bare minimum kde3 libraries needed to make it work.

Do you use/need pulse audio? If the answer is ‘no’, scrap it.

Do you need the updater applet to tell you when updates are available? Or can you check yourself? If you don’t need the updater you can have it not auto-start. Alternatively you can uninstall it along with the “policykit-kde” package. AFAIK, kupdateappet is the only app in a default oS 11.1 KDE4 install that needs policykit-kde.

Lastly, you might want to turn of Nepomuk if you don’t use it. The option is under “Desktop Search” in “Personal Settings” under the “Advanced” tab.

Good luck, and always engage in safe computing practises…back-up your data and never perform surgery if you don’t have the time to clean up any potential mess!

GREAT post ReferenceSeete…

i can hardly wait to see if Torswin comes back and says he followed
your post and cut his BOOTLOADER to LOGIN time from 50 seconds to 20…

or, if he was more looking for a button he could push that said
“Initiate fast boot option”…

seems there many who spend so many seconds WAITING for their system to
come up that they don’t feel they have the TIME (and patience?) to do
the surgery you so well outlined…[they don’t even have the time to
SEARCH for pre-existing solutions…]


MultiplePersonality
*

If I followed Torswins advice, a couple of things would happen:

  • I would not be able to connect to PC’s en servers I manage (no ssh)
  • My NIS and NFS server wouldn’t work at all, or not as they should, missing rpcbind

There’s also lots of projects on fast booting. But as Multi… says, you’re going to spend years of your life to gain a couple of secs. No matter how you speed up the boot on your system, you’re never going to gain as much as by using SSD.

You might have a search of

EeeUser ASUS Eee PC Forum

Some of them are quite fond of this hobby…

> If I followed Torswins advice, a couple of things would happen:
>
> - I would not be able to connect to PC’s en servers I manage (no ssh)
> - My NIS and NFS server wouldn’t work at all, or not as they should,
> missing rpcbind

which is WHY he why he put this at the TOP:

“as I cannot know everything about your computer or your
use of it…I do not take responsibility for any negative outcomes
that may arise from following this advice.”

which should give most brave enough to try it to pause to THINK about
what needs to change to fit their system, needs, etc…


MultiplePersonality