SpeedUP boot procces

Hello. I am totally newbie at archlinux and my english is broken My arch is (IMO) to slow - boot startIt's starts more than 35s - my slack started <15s I know that i need to delete udev and I need to load modules.But How?Have got I edit MODULES in mkinitcpio.conf or in rc.conf ?and have got I delete udev from HOOKS in mkinitcpio.confAnd what modules have got I load?It's to hard for me, now.I now you are thinking "you start computer only one of day, and this some of seconds not happy you"But it is very important for me.Please Help me.

Re: SpeedUP boot procces

Some things I do..

1) See the wiki on mkinitcpio and read up on hooks and modules to find out what is safe to remove. My HOOKS are like this..

HOOKS="base udev autodetect pata filesystems fbsplash"

I don't need to boot the kernel from sata, scsi, or usb devices so I removed them. Once you change your /etc/mkinitcpio.conf file you have to do mkinitcpio -g [your kernel] for the new changes to be in the kernel image.

in rc.conf..2) the modules line I don't have much because I use MOD_AUTOLOAD. I imagine that you may be able to speed things up by manually setting the modules you need in this line and shutting off MOD_AUTOLOAD. I don't know if it's worth the constant hassle though.

3) Use static address assignment for your NIC's (if you can), you can save some time instead of waiting for the DHCP server to give an addy. It shaved like 2-3 seconds for me.

4) the daemons line drop whatever you dont need. I never use network filesystems (other then Samba/SMB) so I drop netfs. You can background daemons also by prefixing them with the @ symbol. Don't background something that is a dependancy for another daemon as they might not load in order. Also overlooked is the hal daemon autoloads the dbus daemon so no need to explicitly put it in there if your using hal. here's my line

Re: SpeedUP boot procces

my chart

Wow.. 29 seconds does seem long considering how little daemons you have loading.Like I said.. my old system was Athlon XP 3200 on an Asrock k7s41gx and after all the optimizations I posted above I had it down to the 18-20 second range.

Re: SpeedUP boot procces

Re: SpeedUP boot procces

I tried something to delete udev but udev is still started My rc.conf:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="pl_PL"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Warsaw"
KEYMAP="pl"
CONSOLEFONT=lat2-16.psfu.gz
CONSOLEMAP=
USECOLOR="yes"
#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="no"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=(mii via-rhine)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="xmat"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
eth0="eth0 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255"
lo="lo 127.0.0.1"
INTERFACES=(lo eth0)
gateway="default gw 192.168.1.1"
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
ROUTES=(gateway)
#
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)
#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(@kdm network @alsa @syslog-ng @hal)
# End of file

My mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="pata_via ata_generic ext3 cdrom agpgart via-agp rtc evdev pcspkr
psmouse serio_raw tsdev radeonfb
fb_ddc snd-via82xx soundcore slhc usbcore ehci-hcd uhci-hcd sd_mod sr_mod"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base autodetect"

this is my bootchart:what files you need to see else?What should I do else?I know that I can to speedUp my boottime more.Please help me

Re: SpeedUP boot procces

Re: SpeedUP boot procces

Udev takes a long time, that simple. It's started from /etc/rc.conf, by the way.I use udev module autoloading and a simple HOOKS="base udev autodetect pata filesystems" in mkinitcpio.conf, together with persistent block device naming.So far I could live with the boot time, I have less than 5 modules I don't need in lsmod and the configuration files stay small and readable.

Re: SpeedUP boot procces

but what will give me compile a kernel when the loading uevents takes near 10s ? I have not got udev in mkinitcpio.conf in HOOKS and I have MOD_Autoload-"no" in rc.conf but Uevents still starts and takes 10s !:/

Re: SpeedUP boot procces

The best method is probably to use either ABS to compile one of the kernels in extras (/var/abs/extras/kernels - my personal preference is the beyond patchset). Or put together your own PKGBUILD and makepkg, along with your customised .config.