You are not logged in.

#1 2009-01-28 06:56:06

PandaMine
Member
Registered: 2008-10-06
Posts: 25

[SOLVED] Kernel 26 - Bad Variable Name Kernel Panic

What basically happened is I synced a lot of packages from pacman from a fresh installation, everything working correctly. Then I installed KDE 4.2 (which installed a lot of other things like avahi etc etc) and now I am having this kernel panic, the lines are exactly as shown

:: Loading Initramfs
export: 36: : bad variable name
Kernel Panic - not syncing: Attempted to kill init!

The fallback (arch linux failsafe) image however works without problems (the only 2 differences when the images are created is that the normal kernel image has the auto detect hook). I have tried re-installing the kernel many times

Here is my /etc/mkinitcpio.conf file

# 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="pata_acpi ata_generic scsi_mod 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 pata scsi sata usb filesystems"
#
#    This setup assembles an pata raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev pata 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 usb pcmcia net usbinput keymap encrypt filesystems"

Here is my modprobe.conf

#
# /etc/modprobe.conf (for v2.6 kernels)
#
options snd-pcsp index=2

Any help would be appreciated

Last edited by PandaMine (2009-01-28 21:21:16)

Offline

#2 2009-01-28 07:07:26

fwojciec
Member
Registered: 2007-05-20
Posts: 1,411

Re: [SOLVED] Kernel 26 - Bad Variable Name Kernel Panic

The only thing that stands out to me that you include modprobe.conf in your boot image (any reason for this?).

Offline

#3 2009-01-28 07:17:19

PandaMine
Member
Registered: 2008-10-06
Posts: 25

Re: [SOLVED] Kernel 26 - Bad Variable Name Kernel Panic

It was the other way before, and I changed it thinking that it would fix the problem (which it didn't).

Ill change it back if thats how its supposed to be (but it isn't causing the problem)

Just to say I did some searching about the problem, and it seems to be a missing variable in a config file. The key is that the problem is happening somewhere in the "autodetect" hook, because the failsafe kernel image works without problems

Last edited by PandaMine (2009-01-28 07:37:19)

Offline

Board footer

Powered by FluxBB