[SOLVED]Kernel 3.0 boot problems.

bsilvereagle · 2011-07-27 14:15:12

I recently built the 3.0 kernel (downloaded from kernel.org) and am trying to make it bootable.
After creating an image and editing grub, I get an error talking about how modules.dep was not found, that /dev/sda7 does not exist and can't be mounted to new_root, that I'm on my own and Good Luck, and then I get dropped to ram fs.
I listed the contents of the kernel26.img and kernel30.img and there is quite a difference even though they were both built using the same mkinitcpio.conf. kernel26.img was built with -p kernel26. I haven't found a preset for kernel30.
kernel26.img boots fine.
I think the .imgs need to be similar but I don't know how to make them similar. Or I could be completley wrong and on the wrong track. Any ideas?

kernel26.img listed:

/proc
/sys
/dev
/bin
/sbin
/lib
/usr
/usr/bin
/usr/lib
/usr/sbin
/run
/dev/null
/dev/zero
/dev/console
/dev/mem
/bin/busybox
/lib/libc.so.6
/lib/libc-2.13.so
/lib/ld-linux-x86-64.so.2
/lib/ld-2.13.so
/sbin/modprobe
/sbin/blkid
/lib/libblkid.so.1
/lib/libblkid.so.1.1.0
/lib/libuuid.so.1
/lib/libuuid.so.1.3.0
/init_functions
/init
/config
/etc
/etc/modprobe.d
/etc/modprobe.d/usb-load-ehci-first.conf
/sbin/udevd
/lib/librt.so.1
/lib/librt-2.13.so
/lib/libpthread.so.0
/lib/libpthread-2.13.so
/sbin/udevadm
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/50-firmware.rules
/lib/udev/rules.d/50-udev-default.rules
/lib/udev/rules.d/60-persistent-storage.rules
/lib/udev/rules.d/80-drivers.rules
/lib/udev/firmware
/lib/udev/ata_id
/lib/udev/path_id
/lib/udev/scsi_id
/lib/udev/usb_id
/lib/udev/load-modules.sh
/etc/udev
/etc/udev/udev.conf
/hooks
/hooks/udev
/sbin/v86d
/etc/modprobe.d/uvesafb.conf
/lib/modules
/lib/modules/2.6.38-ARCH
/lib/modules/2.6.38-ARCH/kernel
/lib/modules/2.6.38-ARCH/kernel/drivers
/lib/modules/2.6.38-ARCH/kernel/drivers/connector
/lib/modules/2.6.38-ARCH/kernel/drivers/connector/cn.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/video
/lib/modules/2.6.38-ARCH/kernel/drivers/video/uvesafb.ko.gz
/hooks/v86d
/lib/modules/2.6.38-ARCH/kernel/drivers/scsi
/lib/modules/2.6.38-ARCH/kernel/drivers/scsi/scsi_mod.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/scsi/sd_mod.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/cdrom
/lib/modules/2.6.38-ARCH/kernel/drivers/cdrom/cdrom.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/scsi/sr_mod.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/ata
/lib/modules/2.6.38-ARCH/kernel/drivers/ata/libata.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/ata/libahci.ko.gz
/lib/modules/2.6.38-ARCH/kernel/drivers/ata/ahci.ko.gz
/lib/modules/2.6.38-ARCH/kernel/fs
/lib/modules/2.6.38-ARCH/kernel/fs/mbcache.ko.gz
/lib/modules/2.6.38-ARCH/kernel/fs/jbd2
/lib/modules/2.6.38-ARCH/kernel/fs/jbd2/jbd2.ko.gz
/lib/modules/2.6.38-ARCH/kernel/lib
/lib/modules/2.6.38-ARCH/kernel/lib/crc16.ko.gz
/lib/modules/2.6.38-ARCH/kernel/fs/ext4
/lib/modules/2.6.38-ARCH/kernel/fs/ext4/ext4.ko.gz
/lib/modules/2.6.38-ARCH/modules.dep
/lib/modules/2.6.38-ARCH/modules.alias
/lib/modules/2.6.38-ARCH/modules.symbols

kernel30.img :

/proc
/sys
/dev
/bin
/sbin
/lib
/usr
/usr/bin
/usr/lib
/usr/sbin
/run
/dev/null
/dev/zero
/dev/console
/dev/mem
/bin/busybox
/lib/libc.so.6
/lib/libc-2.13.so
/lib/ld-linux-x86-64.so.2
/lib/ld-2.13.so
/sbin/modprobe
/sbin/blkid
/lib/libblkid.so.1
/lib/libblkid.so.1.1.0
/lib/libuuid.so.1
/lib/libuuid.so.1.3.0
/init_functions
/init
/config
/etc
/etc/modprobe.d
/etc/modprobe.d/usb-load-ehci-first.conf
/sbin/udevd
/lib/librt.so.1
/lib/librt-2.13.so
/lib/libpthread.so.0
/lib/libpthread-2.13.so
/sbin/udevadm
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/50-firmware.rules
/lib/udev/rules.d/50-udev-default.rules
/lib/udev/rules.d/60-persistent-storage.rules
/lib/udev/rules.d/80-drivers.rules
/lib/udev/firmware
/lib/udev/ata_id
/lib/udev/path_id
/lib/udev/scsi_id
/lib/udev/usb_id
/lib/udev/load-modules.sh
/etc/udev
/etc/udev/udev.conf
/hooks
/hooks/udev

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

# 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
# '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 v86d 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. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"

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

Last edited by bsilvereagle (2011-07-27 23:29:25)

Army · 2011-07-27 14:25:00

You could try the kernel package from [testing]. There it's simply called linux, so pacman -S linux will do it.

bsilvereagle · 2011-07-27 14:28:01

I enabled testing but pacman can't find "linux". Which is alright for now, I can't redownload anything major for a couple of days.

Last edited by bsilvereagle (2011-07-27 14:28:20)

karol · 2011-07-27 14:35:54

bsilvereagle wrote:

I enabled testing but pacman can't find "linux". Which is alright for now, I can't redownload anything major for a couple of days.

You need to run 'pacman -Syy' after you enable a new repo.
Works here:

[karol@black ~]$ pacman -Syy
:: Synchronizing package databases...
 testing                          30,8K  192,5K/s 00:00:00 [################################] 100%

<some more repos>

[karol@black ~]$ pacman -S linux
resolving dependencies...
looking for inter-conflicts...
:: linux and kernel26 are in conflict. Remove kernel26? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: linux and kernel26 are in conflict

bsilvereagle · 2011-07-27 14:38:08

I did:

[~@vaio ~]$ pacman -Syy
error: you cannot perform this operation unless you are root.
[b~@vaio ~]$ sudo !!
sudo pacman -Syy
Password: 
:: Synchronizing package databases...
 testing                       29.6K   76.3K/s 00:00:00 [##############################] 100%
 core                          37.9K   93.1K/s 00:00:00 [##############################] 100%
 extra                        468.6K  135.9K/s 00:00:03 [##############################] 100%
 community                    439.4K  127.0K/s 00:00:03 [##############################] 100%
 multilib                      25.0K    6.6K/s 00:00:04 [##############################] 100%
[~@vaio ~]$ sudo pacman -S linux
error: target not found: linux

karol · 2011-07-27 14:40:24

linux went to testing on 2011-07-24 so all the mirrors should have already synced.
You can grab a fresh mirrorlist from http://www.archlinux.org/mirrorlist/

bsilvereagle · 2011-07-27 14:51:02

I'd rather not remove kernel26 to have the linux package installed, but thanks for the advice.

Army · 2011-07-27 16:05:54

You could install the longterm supported kernel to be sure there's one kernel left which will definitely boot. pacman -S kernel26-lts

bsilvereagle · 2011-07-27 16:20:52

Oh, I have lts installed, I'd just like to have both kernel26 and 3.0.

karol · 2011-07-27 16:25:42

bsilvereagle wrote:

Oh, I have lts installed, I'd just like to have both kernel26 and 3.0.

linux 3.0 is just the next version of the kernel26, and we don't have versioned kernel yet https://bugs.archlinux.org/task/16702
It's just the same as you uninstall foo-1.2.3 and install e.g. foo-1.2.4 or bar-1.0.0 if package foo gets replaced by package bar.

bsilvereagle · 2011-07-27 16:27:04

karol wrote:

bsilvereagle wrote:
Oh, I have lts installed, I'd just like to have both kernel26 and 3.0.
linux 3.0 is just the next version of the kernel26, and we don't have versioned kernel yet https://bugs.archlinux.org/task/16702
It's just the same as you uninstall foo-1.2.3 and install e.g. foo-1.2.4 or bar-1.0.0 if package foo gets replaced by package bar.

I know, I'd just like to be able to boot .38-ARCH and 3.0. I have problems w/ thermal and I'm trying to find the coolest kernel.

Ramses de Norre · 2011-07-27 17:10:15

bsilvereagle wrote:

karol wrote:
bsilvereagle wrote:
Oh, I have lts installed, I'd just like to have both kernel26 and 3.0.
linux 3.0 is just the next version of the kernel26, and we don't have versioned kernel yet https://bugs.archlinux.org/task/16702
It's just the same as you uninstall foo-1.2.3 and install e.g. foo-1.2.4 or bar-1.0.0 if package foo gets replaced by package bar.
I know, I'd just like to be able to boot .38-ARCH and 3.0. I have problems w/ thermal and I'm trying to find the coolest kernel.

You could rebuild the original .38 arch kernel but name it differently, look at e.g. the kernel26-lts package or the lots of custom AUR kernels for references.

bsilvereagle · 2011-07-27 18:09:06

I built the kernel with a different .config and now have received

FATAL: Could not load /lib/modules/3.0.0-ARCH/modules.dep: No such file or directory.

There *isn't* a 3.0.0-ARCH but there is a 3.0.0. How do I stop -ARCH from getting appended? Is it a mkinitcpio switch? or do I need to rebuild the kernel?

EDIT

Looks like I need to rebuild since the .config has a LOCALVERSION "-ARCH" unless there is a way to build modules with the LOCALVERSION.

Last edited by bsilvereagle (2011-07-27 18:11:24)

karol · 2011-07-27 18:11:00

https://bbs.archlinux.org/viewtopic.php?pid=965213
In make menuconfig, there is a option within the general settings to change/replace the -ARCH line. Same thing as tomgun said, but then in the menu itself. Also still possible to change it in the .config file.
CONFIG_LOCALVERSION="-ARCH"

bsilvereagle · 2011-07-27 23:29:03

I updated to .39 and watched pacman do it's job and saw "-k 2.XXX-ARCH" so I built kernel30.img with a "-k 3.0.0-ARCH" and it worked. Even have nvidia drivers installed.

Arch Linux

#1 2011-07-27 14:15:12

[SOLVED]Kernel 3.0 boot problems.

#2 2011-07-27 14:25:00

Re: [SOLVED]Kernel 3.0 boot problems.

#3 2011-07-27 14:28:01

Re: [SOLVED]Kernel 3.0 boot problems.

#4 2011-07-27 14:35:54

Re: [SOLVED]Kernel 3.0 boot problems.

#5 2011-07-27 14:38:08

Re: [SOLVED]Kernel 3.0 boot problems.

#6 2011-07-27 14:40:24

Re: [SOLVED]Kernel 3.0 boot problems.

#7 2011-07-27 14:51:02

Re: [SOLVED]Kernel 3.0 boot problems.

#8 2011-07-27 16:05:54

Re: [SOLVED]Kernel 3.0 boot problems.

#9 2011-07-27 16:20:52

Re: [SOLVED]Kernel 3.0 boot problems.

#10 2011-07-27 16:25:42

Re: [SOLVED]Kernel 3.0 boot problems.

#11 2011-07-27 16:27:04

Re: [SOLVED]Kernel 3.0 boot problems.

#12 2011-07-27 17:10:15

Re: [SOLVED]Kernel 3.0 boot problems.

#13 2011-07-27 18:09:06

Re: [SOLVED]Kernel 3.0 boot problems.

#14 2011-07-27 18:11:00

Re: [SOLVED]Kernel 3.0 boot problems.

#15 2011-07-27 23:29:03

Re: [SOLVED]Kernel 3.0 boot problems.

Board footer