From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Grub broke out of the blue
Date: Tue, 17 Feb 2009 08:08:54 +0000 [thread overview]
Message-ID: <20090217080854.7fdb1f40@krikkit> (raw)
In-Reply-To: <gnddo3$doq$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Tue, 17 Feb 2009 06:17:07 +0200, Nikos Chantziaras wrote:
> I've no idea how it broke, but after an emerge --sync, a kernel
> (gentoo-sources) update was there. After I compiled the kernel, I did
> the usual "make modules_install && make install". I edited grub.conf
> only to the point of changing the booted kernel to the
> new one (just a matter of changing -r1 to -r2 at the end of the kernel
> filename). I reboot, Grub stops working. It just displays "GRUB" and
> hangs there.
Could you have inadvertently made more of a change to grub.conf than
that? Grub is notoriously fragile when it comes to its config file?
Why did you edit it in the first place? As you used make install,you will
have symlinks from vmlinuz and vmlinuz.old to the new and previous
kernels. Use these in GRUB and there's no need to edit anything.
--
Neil Bothwick
File Not Found - Loading something that looks similar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-02-17 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 4:17 [gentoo-user] Grub broke out of the blue Nikos Chantziaras
2009-02-17 4:44 ` Stroller
2009-02-17 4:51 ` [gentoo-user] " Nikos Chantziaras
2009-02-17 5:01 ` Stroller
2009-02-17 17:30 ` [gentoo-user] " Dirk Heinrichs
2009-02-17 4:49 ` [gentoo-user] " Nikos Chantziaras
2009-02-17 8:08 ` Neil Bothwick [this message]
2009-02-17 17:21 ` Nikos Chantziaras
2009-02-19 8:21 ` Mick
2009-02-17 8:18 ` [gentoo-user] " Roy Wright
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=20090217080854.7fdb1f40@krikkit \
--to=neil@digimed.co.uk \
--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