[arch] How fast could boot Arch?

Colin Pitrat colin.pitrat at bull.net
Mon Jul 23 09:24:54 EDT 2007


Usually, I do a lsmod after a boot with autodetection. Then, I select 
only modules that are used (none 0 value) and are not needed by other 
modules (no module name on the last column).

For example :
[colin at frcls0509 ~]$ lsmod | head -n 5
Module                  Size  Used by
i915                   21376  2
drm                    70420  3 i915
nls_cp850               5120  1
parport_pc             35172  0

parport_pc is not used
drm is used but is needed by i915 so loading i915 will load drm
i915 and nls_cp850 are needed

But you should be careful. Some modules may be missing (usb-storage for 
example, if you didn't plug your UMS device but may use one), and some 
may be unused but usefull (parport_pc could be used). Other modules may 
be loaded but you don't want to use it (pcmcia on a laptop if you don't 
plan to use it).

So this is not just that easy. It's just a good start.

Colin Pitrat (Bull Services Telco)
Bull,  Architect of an Open World (TM)
Tél : +33 (0)  1 30 80 72 93
www.bull.com


> -------- Message original --------
> De: LEVIS Cyril <atlas95 at gmail.com>
> Pour: colin.pitrat at bull.net, General Discusson about Arch Linux <arch at archlinux.org>
> > Date: 23/07/2007 3:02:42 PM +0200
> Objet: [arch] How fast could boot Arch?
>
> How to find needed module ? I have add some specific module but how
> kknow what are the hidden moduels i must add?
> (sorry for my english)
> thanks
> Le lundi 23 juillet 2007 à 14:28 +0200, Colin Pitrat a écrit :
>> I tried to make my system boot as fast as possible too, and the two 
>> really important improvements where :
>>
>> 1) MOD_AUTOLOAD = no and put all needed modules in MODULES in /etc/rc.conf
>>
>> 2) tune mkinitcpio.conf to specify only needed modules and remove all 
>> unneeded HOOKS (including udev and autodetect)
>>
>> If you don't need autodetect but want to keep udev, I think it should 
>> also speedup boot. If you want to keep udev and autodetect, I don't 
>> think you can do better.
>>
>> Colin Pitrat (Bull Services Telco)
>> Bull,  Architect of an Open World (TM)
>> Tél : +33 (0)  1 30 80 72 93
>> www.bull.com
>>
>>
>>> -------- Message original --------
>>> De: Dimitrios Apostolou <jimis at gmx.net>
>>> Pour: General Discusson about Arch Linux <arch at archlinux.org>
>>>> Date: 23/07/2007 1:37:55 PM +0200
>>> Objet: [arch] How fast could boot Arch?
>>>
>>> My primary complaint for the long boot time is udev... It takes 20 seconds on 
>>> my 800MHz system, even if I disable MOD_AUTOLOAD. But I guess this is not 
>>> arch specific, I have seen similar times on other distros as well and even 
>>> minutes of wait time on older systems. 
>>>
>>> I suppose it has to do with the "including the kitchen-sink" default kernel, 
>>> which causes udev_settle to wait for too many triggered events. So one 
>>> solution would be to compile a custom kernel, with only the necessary modules 
>>> enabled. 
>>>
>>> Any other ideas on improving udev? 
>>>
>>>
>>> Dimitris
>>>
>>> _______________________________________________
>>> arch mailing list
>>> arch at archlinux.org
>>> http://archlinux.org/mailman/listinfo/arch
>>>
>> _______________________________________________
>> arch mailing list
>> arch at archlinux.org
>> http://archlinux.org/mailman/listinfo/arch
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: colin.pitrat.vcf
Type: text/x-vcard
Size: 247 bytes
Desc: not available
Url : http://archlinux.org/pipermail/arch/attachments/20070723/67556e05/attachment.vcf 


More information about the arch mailing list