You are not logged in.

#1 2013-05-21 03:42:04

AdamCDunlap
Member
Registered: 2013-04-03
Posts: 11

[SOLVED] linux-3.9.3-1-i686 will not boot

Hello,

When I upgrade to linux-3.9.3-1, my system fails to boot. It goes through grub fine, displays "decompressing kernel" and then "booting kernel" and will not continue past that message for several minutes. Upon downgrading to linux-3.8.2-1, everything works fine.

I'm using the i686 version of everything. The only thing I'm seeing that could be wrong is

[2013-05-20 19:23] [PACMAN] Running 'pacman -U linux-3.9.2-1-i686.pkg.tar.xz'
[2013-05-20 19:23] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-05-20 19:23] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Starting build: 3.9.2-1-ARCH
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [timestamp]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Starting build: 3.9.2-1-ARCH
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [timestamp]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-05-20 19:23] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-05-20 19:23] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-05-20 19:24] [ALPM-SCRIPTLET] ==> Image generation successful

in pacman.log, which I've read is benign

My mkinitcpio.conf is

# 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 last, so it may be used to
# override the actual binaries included by a given hook
# 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.
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 block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block 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 block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="timestamp base udev autodetect modconf block resume filesystems keyboard fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"

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

Does anyone know what's going on? Thanks!

Last edited by AdamCDunlap (2013-05-21 23:51:18)

Offline

#2 2013-05-21 05:20:03

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [SOLVED] linux-3.9.3-1-i686 will not boot

I'm really not following where you think that there is an error in that output.  Besides taht you say that 3.9.3 is giving you issues, but hat downgrading to 3.8.2 makes things okay.  I think you meant 3.9.2-1-ARCH, yeah?

If this is the case, still the output you posted is your downgrade to 3.9.2-1-ARCH, which I can only assume has absolutely nothing to do with your upgrade the 3.9.3-1-ARCH.

I think you might need to do a bit more digging as to waht was going on.  Could it be that you didn't acually mount your partition when you upgraded to 3.9.3-1?  That will typically still "boot" but cause all kinds of problems once it does.  Though you never really know what it might end up doing to each individual system.  What happens is that it upgrades the modules (/usr/lib/modules/) but the kernel gets written to /boot/vmlinuz-linux like it is  supposed to, so if the /boot isn't mounted, it then gets mounted over, so you are trying to boot an old kernel/initramfs combo with a directory of new modules.

Of course this is just a total shot in the dark because the information you provided is not really relevant to your issue.  So the best that can be done is a simple guess.

Offline

#3 2013-05-21 23:52:04

AdamCDunlap
Member
Registered: 2013-04-03
Posts: 11

Re: [SOLVED] linux-3.9.3-1-i686 will not boot

I thought it was weird there was no cause -- it turned out to have fixed itself upon reupdating. It must have been a corrupted file or something.

Offline

#4 2013-05-24 16:36:22

SolarBoyMatt
Member
From: Columbus, Ohio
Registered: 2012-01-07
Posts: 258
Website

Re: [SOLVED] linux-3.9.3-1-i686 will not boot

Also, those mkinitcpio warnings should be harmless.

https://bbs.archlinux.org/viewtopic.php?id=162969

Last edited by SolarBoyMatt (2013-05-24 16:39:07)

Offline

Board footer

Powered by FluxBB