From: "Drake Donahue" <donahue95@comcast.net>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] initrd
Date: Mon, 31 Oct 2005 11:39:56 -0500 [thread overview]
Message-ID: <003e01c5de39$ba721cf0$0200a8c0@donahues.us> (raw)
In-Reply-To: 43661F7B.70806@manchester.ac.uk
Grub really does work. The problem you are having is that grub can't
find your kernel.
May I suggest:
Boot the gentoo install cd:
At the prompt - livecd gentoo # - execute the following commands:
mount /dev/hda1 /mnt/gentoo/boot
cd /mnt/gentoo/boot
ls -l
ls kernel* initramfs*
The output of "mount /dev/hda1 /mnt/gentoo" will tell you about the
filesystem on the boot partition and should contain no surprises.
The output of "ls -l" is the boot file and directory structure that
grub will
see if "root (hd0,0)" is in grub.conf.
The output of "ls kernel* initramfs*" is the kernel name and the
initramfs
name that need to appear in grub.conf.
If a 'No such file or directory' error appears, the kernel and/or the
initramfs
is not located in /mnt/gentoo/boot and thus is not in (hd0,0)/ as far as
grub is
concerned. In this case look for a boot -->'something' symbolic link that
points
to 'something' as the kernel location. Most likely a boot directory will
appear
in the "ls -l" output and you should look there for kernel and initramfs. If
mislocated, I think you should move them to /mnt/gentoo/boot and rerun
" ls kernel* initramfs* ".
I believe that the " ls kernel* initramfs* " output you see will be
"kernel-2.6.13-gentoo-r3 initramfs-genkernel-amd64-2.6.13-gentoo-r3".
In that case, I believe grub.conf should read:
default 0
timeout 5
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.13
root (hd0,0)
kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 init=/linuxrc ramdisk=8192
real_root=/dev/hda3 udev
initrd /initramfs-genkernel-amd64-2.6.13-gentoo-r3
If " ls kernel* initramfs* " produced other results, then "the other
kernel name" must be
substituted exactly for 'kernel-2.6.13-gentoo-r3' above and "the other
initramfs name" for
'initramfs-genkernel-amd64-2.6.13-gentoo-r3' above respectively. Don't lose
the initial
slashes in the process.
If you try this and it does not help, posting the results of the
commands and the grub.conf
may get more help from the smarter than I multitude.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-31 16:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 18:07 [gentoo-amd64] initrd Dmitri Pogosyan
2005-10-30 19:24 ` William Tetrault
2005-10-30 20:32 ` Nuitari
2005-10-31 9:52 ` DR GM SEDDON
2005-10-31 13:43 ` DR GM SEDDON
2005-10-31 16:39 ` Drake Donahue [this message]
2005-11-01 14:45 ` DR GM SEDDON
2005-11-01 17:31 ` Drake Donahue
2005-11-01 18:06 ` Drake Donahue
2005-11-02 12:38 ` DR GM SEDDON
2005-11-02 13:14 ` Harm Geerts
2005-10-31 9:47 ` DR GM SEDDON
-- strict thread matches above, loose matches on Subject: below --
2005-10-31 0:56 Dmitri Pogosyan
2005-10-30 15:59 Dmitri Pogosyan
2005-10-30 15:59 Dmitri Pogosyan
2005-10-30 17:35 ` Karol Krizka
2005-10-31 9:33 ` DR GM SEDDON
2005-10-29 23:54 Dmitri Pogosyan
2005-10-29 23:49 Dmitri Pogosyan
2005-10-28 16:19 Dmitri Pogosyan
2005-10-29 6:12 ` Lee Thompson
2005-10-29 13:21 ` DR GM SEDDON
2005-10-29 13:29 ` Craig Webster
2005-10-29 14:16 ` DR GM SEDDON
2005-10-29 15:41 ` Karol Krizka
2005-10-30 9:48 ` DR GM SEDDON
2005-10-30 15:45 ` Karol Krizka
2005-10-30 17:38 ` William Tetrault
2005-10-29 16:40 ` Drake Donahue
2005-10-29 18:12 ` Drake Donahue
2005-10-29 17:15 ` William Tetrault
2005-10-31 1:23 ` bruce harding
2005-10-28 14:13 DR GM SEDDON
2005-10-28 14:54 ` Mark Knecht
2005-10-29 15:36 ` Hemmann, Volker Armin
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='003e01c5de39$ba721cf0$0200a8c0@donahues.us' \
--to=donahue95@comcast.net \
--cc=gentoo-amd64@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