From: Francisco Ares <frares@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] grub2 or kernel config - unable to properly boot
Date: Mon, 26 Aug 2013 12:41:47 -0300 [thread overview]
Message-ID: <CAHH9eM4gY1zeTdUQy=HBgpjay13c-w1yhQmeDzeemjWt1hWWtQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2369 bytes --]
Hi,
After a few solved problems, I am still unable to completely boot using
grub:2, and now I just can't find anything else to fiddle with.
So I would really appreciate if someone could take a look at my
configuration:
- system is amd64;
- hard disk partitioning:
- two first primary partitions, unused (for now);
- third (/dev/sda3) is /boot partition, kernel built and in place;
- extended partition as fourth partition;
- logical partition (/dev/sda5) is "/" linux partition, ext4 formated;
- emerged the following, before building kernel;
- genkernel ;
- media-gfx/splashutils-1.5.4.4-r1;
- media-gfx/splash-themes-gentoo-20101212-r1 ;
- sys-apps/v86d-0.1.10;
- genkernel command line:
genkernel all \
--color --menuconfig --splash=natural_gentoo \
--splash-res=1024x768,1280x1024,1366x768,1440x900 \
--mountboot --install --unionfs --real-root=/dev/sda5 \
--ramdisk-modules --postclear
- kernel built with:
- CONFIG_FB_UVESA=y
- CONFIG_INITRAMFS_SOURCE="/usr/share/v86d/initramfs"
- CONFIG_EXT4_FS=y
- CONFIG_EXT4_FS_POSIX_ACL=y
- CONFIG_EXT4_FS_SECURITY=y
- grub2 defaults (/etc/defaults/grub2) only difference from original:
GRUB_CMDLINE_LINUX="init=/linuxrc real_root=/dev/sda5
video=uvesafb,mtrr:3,ywrap splash=silent,fadein,theme:natural_gentoo
nodevfs udev devfs=nomount CONSOLE=/dev/tty1 quiet"
- sample extract from grub:0 config file, used in a working (a bit older)
system:
title=Gentoo Linux (3.8.13-gentoo)
root (hd0,1)
kernel /boot/kernel-genkernel-x86_64-3.8.13-gentoo ro root=/dev/ram0 \
init=/linuxrc real_root=/dev/sda4 vga=791
splash=silent,theme:natural_gentoo \
console=tty1 verbose nodevfs udev devfs=nomount CONSOLE=/dev/tty1
quiet
initrd /boot/initramfs-genkernel-x86_64-3.8.13-gentoo
Now the boot stops showing the messages (after the Tux logos appeared):
Can't open cfg file //etc/splash/natural_gentoo/640x480.cfg
No verbose picture specified in the theme
No silent picture specified in the theme
No verbose picture specified in the theme
Can't open cfg file //etc/splash/natural_gentoo/640x480.cfg
No verbose picture specified in the theme
No silent picture specified in the theme
!! Block device /dev/sda5 is not a valid root device
The last line explains the ones preceding it.
Any hints on where to look at?
Thanks
Francisco
[-- Attachment #2: Type: text/html, Size: 3020 bytes --]
next reply other threads:[~2013-08-26 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 15:41 Francisco Ares [this message]
2013-08-26 16:17 ` [gentoo-user] grub2 or kernel config - unable to properly boot Michael Hampicke
2013-08-26 18:11 ` Francisco Ares
2013-08-27 6:37 ` Michael Hampicke
2013-08-27 10:18 ` Francisco Ares
2013-08-27 10:28 ` Wang Xuerui
2013-08-27 11:31 ` Francisco Ares
2013-08-27 12:21 ` Neil Bothwick
2013-08-27 20:41 ` Francisco Ares
2013-08-27 10:28 ` Francisco Ares
2013-08-27 11:33 ` Francisco Ares
2013-08-27 12:14 ` Francisco Ares
2013-08-27 20:40 ` Francisco Ares
2013-08-28 6:47 ` Michael Hampicke
2013-08-28 11:36 ` Francisco Ares
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHH9eM4gY1zeTdUQy=HBgpjay13c-w1yhQmeDzeemjWt1hWWtQ@mail.gmail.com' \
--to=frares@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox