Arch Linux

p2501

Member

Registered: 2008-07-26

Posts: 20

New kernel, no boot

Hello,

first things first, the standard supplied 2.6.32-ARCH x86_64 kernel boots fine, no udev problems and everything. So I took it's configuration for the new kernel (2.6.33-git4) made oldconfig and thinned out what I thought isn't needed. This resulted basically in a booting kernel, but when it came to running hooks I've got problems that resemble the ones in these threads, I get the message that udev already seems to be running afterwards root can't be found:

http://bbs.archlinux.org/viewtopic.php?id=81657
http://bbs.archlinux.org/viewtopic.php?pid=689678

with the difference that it doesn't boot further, it drops me to a ramfs shell because it can't find a root file system. I followed several hints in other threads like making sure the filesystems are compiled in-kernel and not as module but to no avail. What I found interesting that unlike in these threads it searches for a disk by UUID, not /dev/sdX. That the disks are still named via /dev/sdX in fstab shouldn't be the problem since it can't find  /, on which fstab lies. Or is it?

mkinitcpio.conf, didn't change anything:

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

# 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 filesystems"

# 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.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"

kernel .conf, on which I later changed the filesystems from module to in-kernel, which didn't work either and produced the same error:
http://pastebin.com/me928e7d

Are there any other conf files I need to supply so that everyone can get a clue what's going on?

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: New kernel, no boot

The 'udev alredy running' message is harmless and not related to your issue. See the second thread you have linked above.

If you are using an initramfs image to boot, you need your boot requirements compiled as modules, not built-in. Conversely, if you want to build them in, don't use initramfs.

p2501

Member

Registered: 2008-07-26

Posts: 20

Re: New kernel, no boot

Since I build the kernel via makepkg I take it that I'm using an initramfs image, right? So I'll have to have all drivers I need compiled as modules? Is that what you mean by boot requirements?

p2501

Member

Registered: 2008-07-26

Posts: 20

Re: New kernel, no boot

I tried compiling drivers and filesystems as modules and in-kernel, didn't work. Changed fstab to UUID scheme, didn't work. Started fresh and took the almost unmodified arch .config, didn't work either. In the it's still the same, first that udev error (which doesn't come up with the standard kernel) followed by two errors, can't find disk-by-uuid-blah, can't create --> ramfs shell.

Latest .config: http://pastebin.com/m34f48589

Edit: redid the whole thing again and made sure that I have all modules together, which would be these, taken from the running arch kernel:

Module                  Size  Used by
ipv6                  283303  44
ext2                   62873  2
snd_seq_dummy           1439  0
snd_hda_codec_atihdmi     2683  1
snd_seq_oss            29023  0
snd_seq_midi_event      5316  1 snd_seq_oss
snd_seq                50558  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          5181  3 snd_seq_dummy,snd_seq_oss,snd_seq
fan                     3378  0
snd_pcm_oss            39011  0
snd_mixer_oss          17299  1 snd_pcm_oss
snd_hda_intel          21586  0
snd_hda_codec          63659  2 snd_hda_codec_atihdmi,snd_hda_intel
snd_hwdep               6340  1 snd_hda_codec
snd_pcm                70318  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
ehci_hcd               34890  0
battery                 9388  0
snd_timer              18799  2 snd_seq,snd_pcm
i2c_i801                8422  0
usbcore               140421  2 ehci_hcd
snd                    57408  10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
ac                      3027  0
i2c_core               18137  1 i2c_i801
button                  4714  0
thermal                11834  0
soundcore               6095  1 snd
r8169                  36182  0
snd_page_alloc          7033  2 snd_hda_intel,snd_pcm
mii                     3738  1 r8169
asus_atk0110            9334  0
pcspkr                  1795  0
wmi                     4771  0
psmouse                56346  0
sg                     25275  0
serio_raw               4440  0
processor              29574  0
evdev                   8825  0
rtc_cmos                8904  0
rtc_core               14631  1 rtc_cmos
rtc_lib                 1810  1 rtc_core
ext4                  334927  6
mbcache                 5466  2 ext2,ext4
jbd2                   80162  1 ext4
crc16                   1273  1 ext4
ata_generic             3111  0
sr_mod                 15043  0
cdrom                  36354  1 sr_mod
sd_mod                 26313  10
pata_jmicron            2424  0
pata_acpi               3288  0
ahci                   34321  9
libata                151860  4 ata_generic,pata_jmicron,pata_acpi,ahci
scsi_mod               92676  4 sg,sr_mod,sd_mod,libata

Still no go, it can't find a hdd after that udev error.

Is there any piece of information left I could provide so that someone can help me?

Edit: Whatever the problem was, I took the exact .conf the exact latest git kernel on Ubuntu server and it works there magically, with GCC and ICC. Wonder if it was a problem with makepkg...

Last edited by p2501 (2010-01-19 09:43:46)