You are not logged in.
Hi, I've read some topic lately about this
http://bbs.archlinux.org/viewtopic.php?id=49202
http://bbs.archlinux.org/viewtopic.php?id=31926
I've not (already) tested every suggestion but I've got a question...
"what is your boot time and what have you done to speedup it?"
('cause I've read of <15 seconds.)
I'll start with:
28 seconds (grub-to-openbox)
I modified this line in my rc.sysinit
/sbin/modprobe $mod &
as suggested in the second linked topic..
and in /etc/rc.conf I have this DAEMONS line
DAEMONS=(syslog-ng hal @network @netfs @crond @alsa)
said that I leave the discussion to you
Offline
My boot time is currently 27 seconds, but I hope to get it faster.
Offline
2 minutes here to get a full working env.
Offline
I didn't read those threads but i think you can get the most substantial increase in your boot time from compiling all of your needed drivers into the kernel. Then you have no need for an initrd. Toofishes made a cutom kernel for the asus eee which does that (among other things like removing stuff you don' t need). It takes 15 seconds to boot into openbox from grub. Thanks again toofishes!!
Offline
cool...
I always thought that initrd was necessary, do you know a guide that explains what to do?
(I looked in the wiki "kernel compilation" section, but I didn't find anything)
anyway when I compiled my own kernel the boot time difference with the arch one was inconsistent..
Last edited by _Marco_ (2008-05-28 17:01:34)
Offline
Some info on an initrd-less boot would be appreciated; it was going to be my next step too. Is it just a case of looking at the initcpio hooks and compiling those drivers into the kernel, or is there more to it?
For the record, I get about 20s from bootchart here - more like 40s once POST and loading the WM and desktop are taken into account. I haven't installed bootchart on the 600MHz Celeron, but it takes something like 1m 30s to the desktop with more or less the same tweaks I have here.
0 Ok, 0:1
Offline
ah just for reference.. I've tryed the MOD_AUTOLOAD="no" and extremely long modules array in /etc/rc.conf (hwdetect --modules)
paradoxically my boot time is even bigger than the MOD_AUTOLOAD="yes" ... strange...
Last edited by _Marco_ (2008-05-28 21:59:28)
Offline
My boot time is currently 27 seconds, but I hope to get it faster.
15 seconds on my desktop, 27 seconds on my laptop.
Offline
i dont use an initrd, and have compiled all my modules which are used everyday into the kernel, apart from oss4 modules and nvidia for obvious reasons and i have a boot time of 20s.
To boot successfully without an initrd i think you simply need filesystem drivers and ide/hdd drivers compiled in. Someone please correct me if im wrong as i havnt tested what the bare minimum is, ive only tested with the modules i need.
(this is running on a XP 2200+ , not sure how much difference this makes compared to a newer faster system)
Last edited by Kane (2008-05-29 10:22:37)
Offline
thanks kane for the clarification.. I will experiment a little then
(p.s. if someone have an howto anyway it would be nice )
@ misfit
I'm running arch on a laptop too so this maybe the point... thanks!
Offline
hey sorry i forgot about this thread but i have some great .pdf's on rebuilding your kernel. I'll post the link when i find it or if anyone else knows what i'm talkin about... go ahead.
Offline
great!
thanks for the good news czar
Offline
SO are you saying that you ( actually me) can rebuild the kernel so that it speeds up the boot process
Offline
removing useless modules and removing the initrd (theoretically) yes, only rebuilding the kernel doesn't give (almost ?) any improvement in speed...
Offline
I decreased my boot time by roughly 6 seconds recompiling the kernel and stripping out a load of things I didn't need.
Offline
how do I figure out what I need and what I don't need ( I know sounds like a silly question) I am used to that MS operating system I used to use nLite/vLite and other to strip out things I didn't need to make smaller faster os. but with Linux ( which I like allot ) I am not sure which is what
Offline
There's a good program called hwinfo that I used as a guide to compile my own kernel on Ubuntu. The essential idea is that if you can't see yourself using it (like bluetooth, or 30 different video drivers, ad infinitum), dont compile in support for it.
Unfortunately, I forgot to compile in support for PTY (yeah, I know, don't laugh at me) so no process on runlevel 5 could use any type of shell.
That sucked.
That was about 2 months ago, before I heard of Arch - but now that I looked over a couple threads regarding rc.conf and rc.sysinit, my boot time is around 10 - 20 seconds less than what it was with Ubuntu... But still far too long!!! ~35 seconds!!
I've read a post somewhere on these forums about a guy with a P3 with 500mhz booting in 15!! I've got a P4 with 2.6 GHz!! How do you people do it??
I've tried mkinitcpio as well, everything except compiling my own kernel and bypassing initrd.
Is it really worth it? Some people say the speed results are negligible..
Last edited by vsk (2008-05-30 23:04:27)
Offline
Is it really worth it? Some people say the speed results are negligible..
IMHO the time you need to boot your system is not very important but it is nice to have a system that boots fast.
what is fast?
for me (and my hardware and my system-configuration) 18-20 seconds are fast but loading my bios takes more time than loading arch. i have a e6750 overclocked @3.44 ghz and a p35-ds3 mainboard with 2x1 ghz ddr2 800 ram@4-4-4-15.
guys with a p3 can boot their systen faster depending on the config.
Offline
@koch: I have the same "bios turtle" problem on my desktop .. very irritating
Offline
I reduced my BIOS load time as much as I could by specifying the hard drive as the first boot device, rather than checking the floppy and CD drives first.
Offline
Offline
Using a static IP shoud also shave a couple seconds off; dhcpcd takes a few extra seconds to grab an IP.
Offline
Thanks czar
@misfit
since dhcp is done (at least for the interfaces listed in /etc/rc.conf, eth0 only for me) by the network daemon (correct me if I'm saying an heresy) I've put the network daemon in background (@network) ... so even dhcp is done "in background" and you don't lose seconds ...
...
imho
Offline
I reduced my BIOS load time as much as I could by specifying the hard drive as the first boot device, rather than checking the floppy and CD drives first.
normally i have only one boot device configured so this is not the problem. when i have to boot from cd i change it in bios.
unnecessary things like game ports, etc. are disabled.
i have no floppy so this is disabled completely.
i don't know exactly how long it takes until grub menu shows up but i think it takes more time than booting arch.
will do a google search about this the next days. this weekend i have to work a lot so i don't wanna think about this.
saturday and sunday it will be about 26 hours so i drink a beer or two now and go to bed.
edit:
DAEMONS=(syslog-ng @netfs @hal @fam @network @alsa @crond)
Last edited by koch (2008-05-31 23:37:27)
Offline