public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] x86 boot failure
Date: Fri, 7 May 2010 07:28:00 +0100	[thread overview]
Message-ID: <201005070728.24211.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4BE2E86A.10304@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 890 bytes --]

On Thursday 06 May 2010 17:03:54 Dale wrote:
> Neil Bothwick wrote:
> > On Thu, 06 May 2010 10:03:59 -0500, Dale wrote:
> >>>> Did you mean press e ?
> >>>
> >>> No.
> >>
> >> I don't see anything in the man page about hitting the c key.  What
> >> does that do?  I've used e, b and such but never heard of c.
> >
> > It drops you to the grub command line, it's documented on the GRUB menu
> > screen itself, just after it tells you about e.
> 
> Oh OK.  I didn't reboot and read that part.  lol  I learned something
> today.  Just hope I will remember it when I need it.    ;-)

'c' is good as long as the error is only with the GRUB entry.  I usually find 
that on new installs the causes of failure to boot may be deeper and I will 
need to chroot back into the installation to fix things; e.g. reconfigure the 
kernel, add drivers and what not.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-05-07  6:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  8:37 [gentoo-user] x86 boot failure Roger Mason
2010-05-06 11:52 ` Mick
2010-05-06 12:38   ` Roger Mason
2010-05-06 12:51     ` Mick
2010-05-06 13:03     ` Neil Bothwick
2010-05-06 13:34       ` Dale
2010-05-06 14:06         ` Neil Bothwick
2010-05-06 15:03           ` Dale
2010-05-06 15:25             ` Neil Bothwick
2010-05-06 16:03               ` Dale
2010-05-07  6:28                 ` Mick [this message]
2010-05-07  8:22                   ` Neil Bothwick
2010-05-06 14:19     ` Roger Mason
2010-05-09 21:46       ` Walter Dnes
2010-05-10 15:18         ` [gentoo-user] x86 boot failure [solved] Roger Mason
2010-05-07  8:51   ` [gentoo-user] x86 boot failure Peter Humphrey
2010-05-06 14:25 ` Stroller
2010-05-06 15:37   ` Roger Mason
2010-05-06 16:03     ` Helmut Jarausch
2010-05-06 16:48     ` Neil Bothwick
2010-05-07  7:07   ` Andrea Conti
2010-05-07 10:03     ` Roger Mason
2010-05-07 11:30       ` Helmut Jarausch
2010-05-07 13:33         ` Roger Mason
2010-05-08 14:16           ` [gentoo-user] Boot gentoo with GTP Disk label claude angéloz
2010-05-08 19:30             ` Mick
2010-05-10 16:01             ` Paul Hartman
2010-05-12 20:00               ` Mick
2010-05-12 20:47                 ` Paul Hartman
2010-05-12 21:47                   ` Mick
2010-05-12 21:59                     ` Paul Hartman
2010-05-12 22:22             ` [gentoo-user] " walt
2010-05-13 21:08               ` Stroller
2010-05-13 22:12                 ` Mick
2010-05-13 23:21                   ` walt
2010-05-14 11:34                     ` Tanstaafl
2010-05-14 12:23                       ` Neil Bothwick
2010-05-14 14:45                         ` Tanstaafl
2010-05-15 14:58                           ` walt

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=201005070728.24211.michaelkintzios@gmail.com \
    --to=michaelkintzios@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