Daemons and modules loaded at boot problem

samuele.mattiuzzo · 2010-01-30 13:31:55

Hi all, i have a problem with my booting time and modules / daemons loaded at boot
This is my bootchart:

[IMG=http://img195.imageshack.us/img195/4701/bootchartpw.th.png][/IMG]

This is 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"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# 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="it_IT.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Rome"
KEYMAP="it"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(lib80211_crypt_tkip wl !snd-pcsp !pcspkr)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="neplero"

# 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
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)

# 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
#
gateway="default gw 192.168.0.1"
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.d
#
# This now requires the netcfg package
#
#NETWORKS=(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=(syslog-ng netfs crond hal !dbus !bluetooth @alsa)

How can i modify my modules loaded and daemons to lower some boot time.
And why is that bluetooth is still loaded even if it's !bluetooth? And is it possible to background ntfs-3g?

Thanks all for advices!

sHyLoCk · 2010-01-30 14:03:18

what do you mean by background ntfs-3g?

You can use @netfs @crond

samuele.mattiuzzo · 2010-01-30 16:36:32

ok thanks, that fixed something on the ntfs-3g loading, but what about bluetooth? why does it starts anyway, even if it's blacklisted?

sHyLoCk · 2010-01-30 16:40:23

sudo chmod -x /etc/rc.d/bluetooth

samuele.mattiuzzo · 2010-01-30 16:47:18

still being present into bootchart

patroclo7 · 2010-01-30 19:14:20

Please clarify what you mean. If the bluetooth service is started, then there is a bug or something very very odd. IF on the contrary you mean that the bluetooth-related modules are loaded by udev, this is perfectly normal: udev autoloads modules according to your hardware, not to your services. You need to blacklist the loaded bluetooth-related kernel modules (check them with 'lsmod') and to blacklist them in the MODULES array.

Last edited by patroclo7 (2010-01-30 19:14:51)

samuele.mattiuzzo · 2010-01-30 19:43:00

it's because is used from btusb, so i guess it's my wireless mouse...

i think that's it

patroclo7 · 2010-01-30 20:04:08

Yes, the bluetooth kernel module is certianly required by your wireless mouse: without the module, no mouse for you.

Always keep distinct the level of services and the level of modules in the init system, there is no automatism between them. If you do not want udev to autodetect and autoload needed modules, just put "MOD_AUTOLOAD=no" in rc.conf.

Last edited by patroclo7 (2010-01-30 20:04:27)

samuele.mattiuzzo · 2010-01-30 21:55:52

yeah i used hwdetect to find out the array of modules i need at boot, and then put them in rc.conf, and set modules autoload to no (and still udevs takes 1040ms doing something...)

Arch Linux

#1 2010-01-30 13:31:55

Daemons and modules loaded at boot problem

#2 2010-01-30 14:03:18

Re: Daemons and modules loaded at boot problem

#3 2010-01-30 16:36:32

Re: Daemons and modules loaded at boot problem

#4 2010-01-30 16:40:23

Re: Daemons and modules loaded at boot problem

#5 2010-01-30 16:47:18

Re: Daemons and modules loaded at boot problem

#6 2010-01-30 19:14:20

Re: Daemons and modules loaded at boot problem

#7 2010-01-30 19:43:00

Re: Daemons and modules loaded at boot problem

#8 2010-01-30 20:04:08

Re: Daemons and modules loaded at boot problem

#9 2010-01-30 21:55:52

Re: Daemons and modules loaded at boot problem

Board footer