mkinitcpio cannot find modules

Gremnon · 2012-01-19 17:52:44

I had previously put this up to some kind of minor issue on my box, but now I'm not so certain.
Since the 3.1 series of the 'linux' package, mkinitcpio has not been able to automatically build new boot images, as it always does when there's an update to the 'linux' package, and oftentimes it doesn't do it manually either.
Previously, running 'depmod -a' would reveal this was because it was looking in a folder that did not exist, for a previous kernel version. Making a symlink to the folder provided by the new version of the 'linux' package's modules resolved this.
However now, this workaround is no longer functioning. 'depmod -a' reveals absolutely nothing, and thus 'mkinitcpio -p linux' continues to fail to build the new boot images with the following output:

==> Building image from preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.2.1-1-ARCH
==> ERROR: module not found: `i915'
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [autodetect]
  -> Parsing hook: [pata]
  -> Parsing hook: [scsi]
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
  -> Parsing hook: [keymap]
==> Creating xz initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Image generation successful
==> Building image from preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.2.1-1-ARCH
==> ERROR: module not found: `i915'
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [pata]
==> ERROR: module not found: `pata_atp867x'
==> ERROR: module not found: `pata_opti'
==> ERROR: module not found: `pata_it821x'
==> ERROR: module not found: `pata_cmd64x'
==> ERROR: module not found: `pata_sis'
==> ERROR: module not found: `pata_ns87415'
==> ERROR: module not found: `pata_amd'
==> ERROR: module not found: `pata_sc1200'
==> ERROR: module not found: `pata_ninja32'
==> ERROR: module not found: `pata_it8213'
==> ERROR: module not found: `pata_rz1000'
==> ERROR: module not found: `pata_hpt3x3'
==> ERROR: module not found: `pata_efar'
==> ERROR: module not found: `pata_jmicron'
==> ERROR: module not found: `pata_cs5520'
==> ERROR: module not found: `pata_netcell'
==> ERROR: module not found: `pata_mpiix'
==> ERROR: module not found: `pata_cypress'
==> ERROR: module not found: `pata_cs5536'
==> ERROR: module not found: `pata_sl82c105'
==> ERROR: module not found: `pata_optidma'
==> ERROR: module not found: `pata_triflex'
==> ERROR: module not found: `pata_atiixp'
==> ERROR: module not found: `pata_oldpiix'
==> ERROR: module not found: `pata_pdc202xx_old'
==> ERROR: module not found: `pata_marvell'
==> ERROR: module not found: `pata_radisys'
==> ERROR: module not found: `pata_legacy'
==> ERROR: module not found: `pata_cs5530'
==> ERROR: module not found: `pata_hpt3x2n'
==> ERROR: module not found: `pata_pdc2027x'
==> ERROR: module not found: `pata_sch'
==> ERROR: module not found: `pata_sil680'
==> ERROR: module not found: `pata_artop'
==> ERROR: module not found: `pata_via'
==> ERROR: module not found: `pata_rdc'
==> ERROR: module not found: `pata_hpt37x'
==> ERROR: module not found: `pata_ali'
==> ERROR: module not found: `pata_serverworks'
==> ERROR: module not found: `pata_piccolo'
==> ERROR: module not found: `pata_ns87410'
==> ERROR: module not found: `pata_cmd640'
==> ERROR: module not found: `pata_pcmcia'
==> ERROR: module not found: `pata_hpt366'
==> ERROR: module not found: `pata_acpi'
==> ERROR: module not found: `pata_arasan_cf'
==> ERROR: module not found: `ata_generic'
==> ERROR: module not found: `ata_piix'
  -> Parsing hook: [scsi]
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
  -> Parsing hook: [keymap]
==> Creating xz initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Image generation successful

Past experience has taught me that neither of these two images will be bootable, because previous versions displaying the same output were also unbootable.

Contents of the /lib/modules directory, as reported by 'ls -l'

drwxr-xr-x 2 root root 4096 Jan 19 17:52 3.1.9-2-ARCH
drwxr-xr-x 3 root root 4096 Jan 13 05:54 3.2.1-1-ARCH
drwxr-xr-x 2 root root 4096 Jan 19 17:35 extramodules-3.2-ARCH

I cannot see the cause nor solution to this problem. Any help?

karol · 2012-01-19 18:16:05

Post your /etc/mkinitcpio.conf.
Are you using [testing]?

wonder · 2012-01-19 18:21:44

pata was dropped some time ago. ditch pata hook from mkinitcpio.

Gremnon · 2012-01-19 18:23:12

@wonder: pata removed. Problem remains unchanged.

@karol
I am not using [testing].

Requested file contents:

# 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="i915"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency 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 any way.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
#    FILES="/etc/modprobe.d/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
# '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 scsi sata filesystems"
#
##   This is identical to the above, except the old ide subsystem is
##   used for IDE devices instead of the new pata subsystem.
#    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 pata scsi sata usb filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev pata mdadm 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 filesystems usbinput keymap"

# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
COMPRESSION="xz"
#COMPRESSION="lzop"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

wonder · 2012-01-19 18:27:35

do you have /lib/modules/3.2.1-1-ARCH/kernel/drivers/gpu/drm/i915/i915.ko.gz ?

Gremnon · 2012-01-19 18:28:46

Yes, that file is present in that directory.

falconindy · 2012-01-19 19:02:28

What does 'uname -r' show? My suspicion is that its not 3.2.1-1-ARCH.

Last edited by falconindy (2012-01-19 19:03:02)

Gremnon · 2012-01-19 19:03:46

That returns '3.1.9-2-ARCH' as that is the kernel I was and still am running when the last upgrade to 'linux' was pulled in.

karol · 2012-01-19 19:46:01

wonder wrote:

pata was dropped some time ago. ditch pata hook from mkinitcpio.

I'm still using pata hook w/o a problem, I get no errors.

karol · 2012-01-20 08:41:02

I've found a similar thread https://bbs.archlinux.org/viewtopic.php?id=133831 but maybe it's just the superficially similar output that tricked me and the underlying issue is different.

Gremnon · 2012-01-20 12:22:59

While I use yaourt, which according to that thread suggests it is the culprit, I use it only after pacman and only for AUR integration. Normal day-to-day updates have always been handled by pacman on this box.
Also, the problem persists even if mkinitcpio is run separately, whether by sudo or run directly as root. I don't think it's the same cause.

Have temporarily made the system bootable by downgrading to the previous linux version and telling pacman not to upgrade it, but I don't like that kind of 'fix'. Would rather resolve the problem itself.

brain0 · 2012-01-20 12:35:13

wonder wrote:

pata was dropped some time ago. ditch pata hook from mkinitcpio.

Just wanted to say, that is shit. ide was dropped, pata might be vital and dropping it could result in a non-booting system.

Gremnon · 2012-01-20 12:39:22

OTOH, removing it doesn't seem to have made any difference. I suspect because it was never actually needed in favour of sata on this system, but I don't pretend I know what the differences are. It still works, and that's enough for me.
That said, I do seem to have slightly less HD usage than usual without it, but that might just be an incidental.

karol · 2012-01-20 12:40:04

brain0 wrote:

wonder wrote:
pata was dropped some time ago. ditch pata hook from mkinitcpio.
Just wanted to say, that is shit. ide was dropped, pata might be vital and dropping it could result in a non-booting system.

Yup: http://mailman.archlinux.org/pipermail/ … 01792.html
and a recent one: http://mailman.archlinux.org/pipermail/ … 22285.html

Tom Gundersen wrote:

Since then, several "legacy" things have been dropped from udev
(support for the ide subsystem comes to mind)

MorningWood · 2012-07-13 23:42:13

I am also having the same problem but since I cannot boot I can't get a debug log
Does anyone know of any other ways to reinstall the arch kernel? I have tried reinstalling with the arch iso and chrooting in. Any help would be greatly appreciated.

MorningWood · 2012-07-15 16:37:12

Anyone? I'm getting tired of using Windows to be honest.

Lone_Wolf · 2012-07-15 21:30:28

Morningwood : it would probably be best to start a new thread for your problem.

include info like /etc/mkinicpio.conf and the mkinitcpio command you used along with the output .

nomorewindows · 2012-07-15 22:56:46

MorningWood wrote:

I am also having the same problem but since I cannot boot I can't get a debug log
Does anyone know of any other ways to reinstall the arch kernel? I have tried reinstalling with the arch iso and chrooting in. Any help would be greatly appreciated.

So what did you do so far? You'll probably have to use this method to get it back running. You didn't specify what you did or what went wrong.

MorningWood wrote:

Anyone? I'm getting tired of using Windows to be honest.

You will banished to the ends of cyberspace to use Windows! Ha Ha Ha. No, just use the iso. We can do this.

MorningWood · 2012-07-16 02:40:17

nomorewindows wrote:

MorningWood wrote:
I am also having the same problem but since I cannot boot I can't get a debug log
Does anyone know of any other ways to reinstall the arch kernel? I have tried reinstalling with the arch iso and chrooting in. Any help would be greatly appreciated.
So what did you do so far? You'll probably have to use this method to get it back running. You didn't specify what you did or what went wrong.
MorningWood wrote:
Anyone? I'm getting tired of using Windows to be honest.
You will banished to the ends of cyberspace to use Windows! Ha Ha Ha. No, just use the iso. We can do this.

hahah I sure hope not! I miss my Arch setup:( To not further derail Gremnon's thread, I posted the details here:
https://bbs.archlinux.org/viewtopic.php?id=145123

Arch Linux

#1 2012-01-19 17:52:44

mkinitcpio cannot find modules

#2 2012-01-19 18:16:05

Re: mkinitcpio cannot find modules

#3 2012-01-19 18:21:44

Re: mkinitcpio cannot find modules

#4 2012-01-19 18:23:12

Re: mkinitcpio cannot find modules

#5 2012-01-19 18:27:35

Re: mkinitcpio cannot find modules

#6 2012-01-19 18:28:46

Re: mkinitcpio cannot find modules

#7 2012-01-19 19:02:28

Re: mkinitcpio cannot find modules

#8 2012-01-19 19:03:46

Re: mkinitcpio cannot find modules

#9 2012-01-19 19:46:01

Re: mkinitcpio cannot find modules

#10 2012-01-20 08:41:02

Re: mkinitcpio cannot find modules

#11 2012-01-20 12:22:59

Re: mkinitcpio cannot find modules

#12 2012-01-20 12:35:13

Re: mkinitcpio cannot find modules

#13 2012-01-20 12:39:22

Re: mkinitcpio cannot find modules

#14 2012-01-20 12:40:04

Re: mkinitcpio cannot find modules

#15 2012-07-13 23:42:13

Re: mkinitcpio cannot find modules

#16 2012-07-15 16:37:12

Re: mkinitcpio cannot find modules

#17 2012-07-15 21:30:28

Re: mkinitcpio cannot find modules

#18 2012-07-15 22:56:46

Re: mkinitcpio cannot find modules

#19 2012-07-16 02:40:17

Re: mkinitcpio cannot find modules

Board footer