Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: DR GM SEDDON <gavin.m.seddon@...>
Subject: Re: initrd
Date: Tue, 01 Nov 2005 14:45:11 +0000
Yes, I had missing the initial 'kernel-' from its definition in 
grub.conf.  It is down to me writing it on a pad with other stuff, I was 
ignoring the kernel word.  Extremely xorry.

Now it boots but asksme to
'specifya device to boot' it boots when I enter 'dev/hda3'.  It is 
specified in 'grub.conf' and 'fstab'.  Any ideas?

Also, I get 'dhcpd:required function  'interface _is_up' but networking 
isn't working.  And, I get 'netmount not started'.  Are these issues 
related.  Can you help?
Regards,
Gavin.

Drake Donahue wrote:

>   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@g.o mailing list


Replies:
Re: initrd
-- Drake Donahue
References:
Re: initrd
-- Dmitri Pogosyan
Re: initrd
-- William Tetrault
Re: initrd
-- Nuitari
Re: initrd
-- DR GM SEDDON
Re: initrd
-- Drake Donahue
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: initrd
Next by thread:
Re: initrd
Previous by date:
Re: emerge kde problems
Next by date:
Re: Re: libungif and giflib conflict.


Updated Jun 17, 2009

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.