Arch Linux

aRcHaTe

Member

Registered: 2006-10-24

Posts: 646

little help

im trying to compile my own kernel and it gives an error that a cant figure it out..:P

:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
ERROR: module 'sd[-_]mod' not found
ERROR: module 'sr[-_]mod' not found
:: Parsing hook [scsi]
:: Parsing hook [sata]
ERROR: module 'sd[-_]mod' not found
ERROR: module 'sr[-_]mod' not found
:: Parsing hook [usbinput]
:: Parsing hook [filesystems]
:: Parsing hook [fbsplash]

MMC is set to module...

---

Its a sick world we live in....

kano

Member

From: Michigan

Registered: 2007-05-04

Posts: 185

Website

Re: little help

Could you post your /etc/mkinitcpio.conf?

---

\\ archlinux on a XPS M1530 //

aRcHaTe

Member

Registered: 2006-10-24

Posts: 646

Re: little help

Could you post your /etc/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="ata_generic ahci ata_piix"

# 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 udev autodetect pata scsi sata usbinput filesystems fbsplash"

---

Its a sick world we live in....

ataraxia

Member

From: Pittsburgh

Registered: 2007-05-06

Posts: 1,553

Re: little help

It's looking for disk and CD modules. If you built those (sd_mod and sr_mod) into your kernel instead of using modules, take "pata" and "sata" out of your HOOKS.