Arch Linux

christianpurefoy

Member

Registered: 2005-10-16

Posts: 136

hwdetect

I've just done the recent upgrade to the new kernel and then switched to hwdetect by

- adding MOD_AUTOLOAD="yes" in /etc/rc.conf
- AUTODETECT=1 in /etc/mkinitrd.conf
- then running mkinitrd auto
- putting !hwd in my daemons in /etc/rc.conf and deleting hotplug

everything reboots fine, but i've seen a lot of stuff written on adding and blacklisting modules, etc, etc... but is there anything else i should or could do concerning hwdetect??

thanks!

postlogic

Member

Registered: 2005-02-24

Posts: 410

Website

Re: hwdetect

You can background a few of the daemons for your machine to boot faster, by putting @ infront of the names. Just make sure other daemons doesn't depend on the ones you background.

T-Dawg

Forum Fellow

From: Charlotte, NC

Registered: 2005-01-29

Posts: 2,736

Re: hwdetect

everything reboots fine, but i've seen a lot of stuff written on adding and blacklisting modules, etc, etc... but is there anything else i should or could do??

yes. Edit your /etc/mkinitrd file and rerun mkinitrd auto. See the wiki for initrd for more info.

christianpurefoy

Member

Registered: 2005-10-16

Posts: 136

Re: hwdetect

i've already changed my /etc/mkinitrd.conf file to the one given in the example in the wiki.

But are you talking about adding / removing modules? how do i know which modules i need and which ones i don't? (to put in Add modules / remove modules)... and if i put in modules here- do i uninstall hwd? (or just keep it like !hwd in my modules in /etc/rc.conf?)

thanks

T-Dawg

Forum Fellow

From: Charlotte, NC

Registered: 2005-01-29

Posts: 2,736

Re: hwdetect

I wasn't talking about adding or removing modules, just adjusting mkinitrd appropriately.
Here's mine with a ide system and ext3 root filesystem:

# Initial Ramdisk setup
# Attention:
# You need only the stuff to be able to mount your root device!
# USB/FW are only needed if you boot from such devices!

# REMOVE_IDE:           removes the complete IDE subsystem
# REMOVE_SCSI:          removes the complete SCSI subsystem
# REMOVE_SATA:          removes the complete SATA subsystem
# REMOVE_CDROM:         removes cdrom support
# REMOVE_USB:           removes the complete USB subsystem
# REMOVE_FW:            removes the complete Firewire subsystem
# REMOVE_RAID:          removes the complete Software RAID subsystem
# REMOVE_DM:            removes the complete device-mapper/LVM subsystem
# REMOVE_FS:            removes the complete Filesystems
#                       (you have to include the filesystem in kernel then!)
# AUTODETECT:           enables Arch Linux autodetection 
# HOSTCONTROLLER_*:     specify the modules you need to setup the subsystem "mod
uleX moduleY",
#                       empty means all modules are included
# FILESYSTEMS:          specify your filesystem modules here, eg. "ext3 reiserfs
"
#                       empty means all modules are included
# USB_TIMEOUT:          value means  seconds to wait for bringing up usb disks
# CRYPT_DEVICE:         the path to your encrypted root device, if you use one
# RAID_DEVICES:         a space-delimited list of the devices belonging in
#                       your /dev/md0 (root) RAID array
#                           (eg, "/dev/hda3 /dev/hdc3")
#
# ADD_MODULE:           adds modules e.g. "moduleX moduleY"
# REMOVE_MODULE:        removes modules e.g. "moduleX moduleY"
#
# To rebuild initrd for Arch standard kernel just rerun 'mkinitrd auto'



# Disable whole subsystems by setting to "1"
REMOVE_IDE=
REMOVE_SCSI=1
REMOVE_SATA=1
REMOVE_CDROM=1
REMOVE_USB=1
REMOVE_FW=1
REMOVE_RAID=1
REMOVE_DM=1
REMOVE_FS=

# Enable auto-detection of HOSTCONTROLlER and FILESYSTEMS (set to "1")
#   (NOTE: This is still experimental, so it is disabled by default)
AUTODETECT=0

# Define which modules are needed by adding "moduleX moduleY"
# If left empty, all modules are included if they are not disabled above
HOSTCONTROLLER_IDE="via82cxxx"
HOSTCONTROLLER_SCSI=
HOSTCONTROLLER_SATA=
HOSTCONTROLLER_USB=
FILESYSTEMS="ext3"

# Number of seconds to wait for USB devices to settle
USB_TIMEOUT=5

# If you have an encrypted root filesystem, set it here (eg, /dev/hda4)
CRYPT_DEVICE=

# If you use software RAID for your root device then list all the devices
# that belong to your root array here.  If your root RAID device is
# something other than md0, then change the RAID_ROOT_ARRAY setting.
#    eg, RAID_ROOT_DEVICES="/dev/hda3 /dev/hdc3"
RAID_ROOT_ARRAY="md0"
RAID_ROOT_DEVICES=

# Define additional modules here
ADD_MODULE=
REMOVE_MODULE=

Yes you will need to use something like hwd or hwdetect to load the appropriate modules.

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: hwdetect

If your system is working, then all the modules you need are being loaded. There may be a few extras loaded as well, but if you don't know which one you need and which you don't, I'd recommend leaving it all alone.

If you're very concerned about this,

hwdetect --show-modules

will show you all the modules required for your system, and

lsmod

will list all the modules loaded, so you can put unwanted ones from lsmod in rc.conf's MOD_BLACKLIST.

Putting !hwd in your DAEMONS array is the same as removing hwd from the array, by the way.

christianpurefoy

Member

Registered: 2005-10-16

Posts: 136

Re: hwdetect

okay my mkinitrd file seems fine and, just in case, i went through the modules- which appears to have made no difference at all- which is fine! ...though it takes longer than it used to before modules are loaded on startup...

thanks!