Arch Linux

SpookyET

Member

Registered: 2008-01-27

Posts: 410

mkinitcpio generates broken images

It's not a hooks issues because fallback is broken as well. It tells me "SUCCESS" of coarse. My system is up to date.

# 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 pata 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 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 dsdt usb keymap uresume filesystems"

bender02

Member

From: Germany

Registered: 2007-02-04

Posts: 1,328

Re: mkinitcpio generates broken images

How broken?

SpookyET

Member

Registered: 2008-01-27

Posts: 410

Re: mkinitcpio generates broken images

How broken?

It doesn't boot.

Sigi

Member

From: Thurgau, Switzerland

Registered: 2005-09-22

Posts: 1,121

Re: mkinitcpio generates broken images

Any error messages or more information about how far the boot process gets?

---

Dammit, haven't been here in a while. Still rocking Arch.

SpookyET

Member

Registered: 2008-01-27

Posts: 410

Re: mkinitcpio generates broken images

Any error messages or more information about how far the boot process gets?

Black screen after grub.

bender02

Member

From: Germany

Registered: 2007-02-04

Posts: 1,328

Re: mkinitcpio generates broken images

That looks like the kernel itself doesn't load. It doesn't even get to initcpio.

SpookyET

Member

Registered: 2008-01-27

Posts: 410

Re: mkinitcpio generates broken images

If I use the fallback image, it gets to "Setting up PCI devices." Then it freezes.

bender02

Member

From: Germany

Registered: 2007-02-04

Posts: 1,328

Re: mkinitcpio generates broken images

Wow, that's interesting. You sure that you have the same 'kernel' line in grub/menu.lst?

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,604

Re: mkinitcpio generates broken images

SpookyET, if you're going to report that something is broken, please try to include as much detail as possible in the report. Thanks.

SpookyET

Member

Registered: 2008-01-27

Posts: 410

Re: mkinitcpio generates broken images

SpookyET, if you're going to report that something is broken, please try to include as much detail as possible in the report. Thanks.

It's been fixed. It was a corrupt custom DSDT. I've had it there for a long time; I just didn't update the image in a while, and had a surprise.

For future reference, if you are lucky enough to have a backup, create a 2 directories. One "working," and the other "broken"

Change to the respected directory, and use the following line in a fakeroot environment.

    gzip -dc /boot/kernel26.img | cpio -id --no-absolute-filenames

Then use diff -r broken working to compare them.

You may close this thread.

Last edited by SpookyET (2008-04-19 11:58:16)