Re: [gentoo-user] Gentoo failed to start

Re: [gentoo-user] Gentoo failed to start

[Stephen Liu]

Hi Richard,

Further to my late posting, after mounting
# mount /dev/hda2 /mnt/gentoo
# mount /dev/hda1 /mnt/gentoo/boot

Ran
# ls -l /mnt/gentoo/boot
boot -> .
grub
lost+found
# ls -l /mnt/gentoo/boot/boot
boot -> .
grub
lost+found
# ls -l /mnt/gentoo/boot/boot/boot
boot -> .
grub
lost+found
# ls -l /mnt/gentoo/boot/boot/boot/boot
boot -> .
grub
lost+found

It looks to me quite funny.  It seems continue endlessly.  boot was
symlink to "."

There was no kernel nor bzimage there.

B.R.
SL


--- Stephen Liu <satimis@yahoo.com> wrote:

> Hi Richard,
> 
> < snip >
> 
> > So try specifying the paths without the /boot/ part.  So your boot
> > entry would look like:
> > 
> > title Gentoo linux 2.6.17.-r7
> >    kernel (hd0,0)/kernel-2.6.17-gentoo-r7 root=/dev/hda2
> 
> Tried;
> kernel (hd0,0)/kernel-2.6.17-gentoo-r7 root=/dev/hda2
> and
> kernel /kernel-2.6.17-gentoo-r7 root=/dev/hda2
> 
> Still the same "file not found"
> 
> 
> kernel version was previously found by running;
> # ls -l /usr/src/linux
> ............ /usr/sru/linux -> linux-2.6.17-gentoo-r7
> 
> Others noted with tks.
> 
> 
> > PS: please stop top-posting.
> 
> Sorry I don't follow.  Please advise.  This is webmail direct from
> Yahoo site.  I checked the mail option and could not find any
> top-posting option there.
> 
> B.R.
> SL
> -- 
> gentoo-user@gentoo.org mailing list
> 
> 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Gentoo failed to start

[Richard Fish]

On 9/1/06, Stephen Liu <satimis@yahoo.com> wrote:
> Ran
> # ls -l /mnt/gentoo/boot
> boot -> .
> grub
> lost+found

Well, this is why you cannot boot.  You do not have a kernel image in /boot.

Are you actually _following_ the guide that you posted a link to
originally, because you seem to have missed[1]:

"""
When the kernel has finished compiling, copy the kernel image to
/boot. Use whatever name you feel is appropriate for your kernel
choice and remember it as you will need it later on when you configure
your bootloader. Remember to replace kernel-2.6.17-gentoo-r5 with the
name and version of your kernel.

Code Listing 13: Installing the kernel

# cp arch/x86_64/boot/bzImage /boot/kernel-2.6.17-gentoo-r5
"""

> It looks to me quite funny.  It seems continue endlessly.  boot was
> symlink to "."

No, this is normal.  It is to allow people to use hd(X,Y)/boot/kernel,
even if hd(X,Y) is the "/boto" filesystem.

> There was no kernel nor bzimage there.

Yes, you need to compile and install a kernel.

> > PS: please stop top-posting.
>
> Sorry I don't follow.  Please advise.  This is webmail direct from
> Yahoo site.  I checked the mail option and could not find any
> top-posting option there.
>

Top-posting[2] means that you are inserting your message above
mine...and fully quoting my message.  It means that if somebody wants
to read this thread in the archives, they will have to read it
starting at the bottom for it to make sense.  It also means you are
sending out a lot more text to the other subscribers on this list than
you need to be, because you are sending my message in it's
entirety...and the other subscribers have already received that.

On this list, bottom-posting or interleaved replies is the normal
format.  So for yahoo,  first delete out any parts of the quoted
message that you are not responding to.  Then insert your responses
below.

[1] http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=7
[2] http://en.wikipedia.org/wiki/Top-posting

HTH,
-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Gentoo failed to start

[Stephen Liu]

Hi Richard,

> On 9/1/06, Stephen Liu <satimis@yahoo.com> wrote:
> > Ran
> > # ls -l /mnt/gentoo/boot
> > boot -> .
> > grub
> > lost+found
> 
> Well, this is why you cannot boot.  You do not have a kernel image in
> /boot.
> 
> Are you actually _following_ the guide that you posted a link to
> originally, because you seem to have missed[1]:
> 
> """
> When the kernel has finished compiling, copy the kernel image to
> /boot. Use whatever name you feel is appropriate for your kernel
> choice and remember it as you will need it later on when you
> configure
> your bootloader. Remember to replace kernel-2.6.17-gentoo-r5 with the
> name and version of your kernel.
> 
> Code Listing 13: Installing the kernel
> 
> # cp arch/x86_64/boot/bzImage /boot/kernel-2.6.17-gentoo-r5
> """
> 
> > It looks to me quite funny.  It seems continue endlessly.  boot was
> > symlink to "."

I completed all steps listed there at least in 2 rounds.  I found;
# ls -l /usr/src/linux
lrwxrwxrwx    1 root   root    12 Oct 13 11:04 /usr/src/linux ->
linux-2.6.17-gentoo-r7

there.  But now it disppears.  I don't know why?.  Even I can't find
the directory "src" after chroot.  Another directory I failed to find
was "modules".  I ran;

# find / -name src -type d
and
# find / -name modules -type d
Both no printout

and could not find it.  Beside the command "env-update", emerge, etc.
were not found on "bash".

I think I have to run another round again wiping out the complete HD.


Another thing, what did you mean "...Use whatever name you feel is
appropriate for your kernel choice and remember it as you will need it
later on when you configure your bootloader. Remember to replace
kernel-2.6.17-gentoo-r5 with the name and version of your kernel." 

I used "kernel-2.6.17-gentoo-r7" previously.

Tks.

B.R.
SL
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Gentoo failed to start

[Richard Fish]

On 9/1/06, Stephen Liu <satimis@yahoo.com> wrote:
> I think I have to run another round again wiping out the complete HD.

Yeah, I think so...

> Another thing, what did you mean "...Use whatever name you feel is
> appropriate for your kernel choice and remember it as you will need it
> later on when you configure your bootloader. Remember to replace
> kernel-2.6.17-gentoo-r5 with the name and version of your kernel."

When you compile the kernel, it is going to build a file called
bzImage, that you have to copy to /boot.  But it is very rare to copy
it to /boot/bzImage...most linux users will rename the file to
something else.  Some people (and helper scripts like genkernel)
prefer to use the full version of the kernel, so if you build a kernel
from gentoo-sources-2.6.17-r5, you might:

cp arch/x86_64/boot/bzImage /boot/linux-2.6.17-gentoo-r5
... or ...
cp arch/x86_64/boot/bzImage /boot/vmlinuz-2.6.17-gentoo-r5
... or ...
cp arch/x86_64/boot/bzImage /boot/mykernel-17r5

It is usually a good idea to keep a backup kernel in /boot that you
can use in case a kernel upgrade goes wrong.  So I usually keep 2
kernels, /boot/vmlinuz-2.6 and /boot/vmlinuz-safe.  Once I know that
vmlinuz-2.6 boots and works reliably, I will copy it to -safe.

The second part about remembering the name for your boot loader refers
to your menu.lst/grub.conf entries.  You must specify the actual name
that you copied your kernel image to, or (as you already saw), you
will get a "file not found" when you try to boot.

So if you copy bzImage to /boot/vmlinuz-2.6, you must use an entry like:

title Whatever
    kernel hd(0,0)/vmlinuz-2.6 ...

The title doesn't really matter, but the "kernel" line needs to
reference your actual kernel file.

Clear?

-Richard
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Gentoo failed to start

[Harm Geerts]

On Saturday 02 September 2006 03:52, Richard Fish wrote:
> On 9/1/06, Stephen Liu <satimis@yahoo.com> wrote:
> > I think I have to run another round again wiping out the complete HD.
>
> Yeah, I think so...
>
> > Another thing, what did you mean "...Use whatever name you feel is
> > appropriate for your kernel choice and remember it as you will need it
> > later on when you configure your bootloader. Remember to replace
> > kernel-2.6.17-gentoo-r5 with the name and version of your kernel."
>
> When you compile the kernel, it is going to build a file called
> bzImage, that you have to copy to /boot.  But it is very rare to copy
> it to /boot/bzImage...most linux users will rename the file to
> something else.  Some people (and helper scripts like genkernel)
> prefer to use the full version of the kernel, so if you build a kernel
> from gentoo-sources-2.6.17-r5, you might:
>
> cp arch/x86_64/boot/bzImage /boot/linux-2.6.17-gentoo-r5
> ... or ...
> cp arch/x86_64/boot/bzImage /boot/vmlinuz-2.6.17-gentoo-r5
> ... or ...
> cp arch/x86_64/boot/bzImage /boot/mykernel-17r5
>
> It is usually a good idea to keep a backup kernel in /boot that you
> can use in case a kernel upgrade goes wrong.  So I usually keep 2
> kernels, /boot/vmlinuz-2.6 and /boot/vmlinuz-safe.  Once I know that
> vmlinuz-2.6 boots and works reliably, I will copy it to -safe.

This can also be done with installkernel from sys-apps/debianutils

>From it's manpage:
installkernel installs a new kernel image onto the system from the Linux 
source tree. It is called by the Linux kernel makefiles when "make install" 
is invoked there.

The new kernel is installed into {directory}/vmlinuz-{version}, a link is made 
from {directory}/vmlinuz to the new  kernel, and the previously  installed 
kernel is available as {directory}/vmlinuz.old.

> The second part about remembering the name for your boot loader refers
> to your menu.lst/grub.conf entries.  You must specify the actual name
> that you copied your kernel image to, or (as you already saw), you
> will get a "file not found" when you try to boot.
>
> So if you copy bzImage to /boot/vmlinuz-2.6, you must use an entry like:
>
> title Whatever
>     kernel hd(0,0)/vmlinuz-2.6 ...
>
> The title doesn't really matter, but the "kernel" line needs to
> reference your actual kernel file.

For grub.conf you can use the symlinks installkernel creates (vmlinuz and 
vmlinuz.old). Now you'll never have to change your grub config again, just 
make sure /boot is mounted ;)

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Gentoo failed to start

[Nick Rout]

On Sat, 2 Sep 2006 00:01:59 +0800 (CST)
Stephen Liu <satimis@yahoo.com> wrote:

> It looks to me quite funny.  It seems continue endlessly.  boot was
> symlink to "."

that is perfectly normal. 
-- 
gentoo-user@gentoo.org mailing list