You are not logged in.

#1 2008-05-03 08:52:09

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,554

[SOLVED] 2.6.25.1 and mkinitcpio

hi archers,

just tried latest 2.6.25.1 (2008.05.01), it builds fine but mkinitcpio does not like it:

>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
ERROR: module 'ata[-_]generic' not found
ERROR: module 'ahci' not found
ERROR: module 'ata[-_]piix' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [sata]
:: Parsing hook [resume]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
ERROR: module 'ata[-_]generic' not found
ERROR: module 'ahci' not found
ERROR: module 'ata[-_]piix' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [sata]
:: Parsing hook [resume]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS

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 sata resume filesystems"

TIA for any advice.

[edit] using [TESTING] on i686 + vanilla kernel build [/edit]

Last edited by bangkok_manouel (2008-05-06 15:44:32)


All design goals must be phrased in such a way that it is hard to use them as slogans to justify stupidity.

Offline

#2 2008-05-04 01:53:51

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [SOLVED] 2.6.25.1 and mkinitcpio

looks like ata_piix is not checked in kernel .config, so module is missing and mkinitcpio is complaining
if you don't need ata_piix then remove it from mkinitcpio.conf, or if module is required for your hardware, make sure that it is compiled (checked in kernel config and as module not build-in)

Offline

#3 2008-05-04 03:54:55

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,554

Re: [SOLVED] 2.6.25.1 and mkinitcpio

Thanks for the reply broch.

What made me post here is that :
- I used the same config to build 2.6.25 and had no problem at all.
- My config is based on Arch's one with slight modifications (not modules related)

BTW, did anyone install 2.6.25.1 successfully (using makepkg+pacman) ?


All design goals must be phrased in such a way that it is hard to use them as slogans to justify stupidity.

Offline

#4 2008-05-04 15:24:30

patroclo7
Member
From: Bassano del Grappa, ITALY
Registered: 2006-01-11
Posts: 915

Re: [SOLVED] 2.6.25.1 and mkinitcpio

I have built and installed it sucessfully, but in the old way, and using at the end manually mkinitcpio to generate the initramfs. However MODULES is empty in my mkinitcpio.conf, because autodetect works really fine for me, and actually my kernel configuration is highly personalized, so I am not sure to be of any help for you.

Did you run 'make modules_install' after 'make', didn't you? Otherwise it is obvious that mkinitcpio does not find any module at all.


Mortuus in anima, curam gero cutis

Offline

#5 2008-05-05 06:02:32

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,554

Re: [SOLVED] 2.6.25.1 and mkinitcpio

Thanks for the reply patroclo7.

patroclo7 wrote:

I have built and installed it sucessfully, but in the old way, and using at the end manually mkinitcpio to generate the initramfs. However MODULES is empty in my mkinitcpio.conf, because autodetect works really fine for me, and actually my kernel configuration is highly personalized, so I am not sure to be of any help for you.

Got the autodetect hook as well and as I'm living dangerously, I tried to boot my machine even with the b0rked mkinitcpio process. Got a kernel panic directly related to those missing modules. Hmmm I wonder if autodetect "skips" everything being already in the module array (thinking as I type, didn't check how that works yet).

Did you run 'make modules_install' after 'make', didn't you? Otherwise it is obvious that mkinitcpio does not find any module at all.

I just used a slightly modified PKGBUILD of the Arch's repo 2.6.25, I removed Arch's patch and added 2.6.25.1 patching. FWIW, it has been working for me since ages but not anymore. I'll fight that beast tonight again, did not touch it since first post.


All design goals must be phrased in such a way that it is hard to use them as slogans to justify stupidity.

Offline

#6 2008-05-05 13:07:52

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [SOLVED] 2.6.25.1 and mkinitcpio

I have several .25 kernels since first -rc (old way built). while I do not use ata_piix, I have not seen anybody complaining recently about this module at lkml, so is it possible that there is something wrong with your modified script?
I would really check before booting to the new kernel, whether this module is built.

Offline

#7 2008-05-05 13:38:56

patroclo7
Member
From: Bassano del Grappa, ITALY
Registered: 2006-01-11
Posts: 915

Re: [SOLVED] 2.6.25.1 and mkinitcpio

A possible error in the PKGBUILD is if for some reason mkinitcpio expect the moduls to be where they are not. It seems very unlikely to me theta autodetect fails in a so simple case, thus my impression is that none of the modules is actually taken into account. Which folders are in /lib/modules? Something with 2.6.25.1 instead of 2.6.25?


Mortuus in anima, curam gero cutis

Offline

#8 2008-05-06 15:40:03

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,554

Re: [SOLVED] 2.6.25.1 and mkinitcpio

patroclo7 wrote:

A possible error in the PKGBUILD is if for some reason mkinitcpio expect the moduls to be where they are not. It seems very unlikely to me theta autodetect fails in a so simple case, thus my impression is that none of the modules is actually taken into account. Which folders are in /lib/modules? Something with 2.6.25.1 instead of 2.6.25?

You were totally right! I had to remove the extraversion from makefile and everything went fine.

Thanks a lot to both of you guys.


All design goals must be phrased in such a way that it is hard to use them as slogans to justify stupidity.

Offline

Board footer

Powered by FluxBB