From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Grub broke out of the blue
Date: Tue, 17 Feb 2009 19:21:53 +0200 [thread overview]
Message-ID: <gnernf$2d9$1@ger.gmane.org> (raw)
In-Reply-To: <20090217080854.7fdb1f40@krikkit>
Neil Bothwick wrote:
> 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?
No, the change was a simple change of 1 byte ("1" -> "2").
> 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.
That won't work for me because I keep two different kernels (one for
vmware and one for native) and I sometimes rebuild one of them after
reconfiguring. With that approach I would end up with the "Native" Grub
entry trying to boot the vmware kernel.
One thing that could be at fault is that I had grub installed into hd0,2
(sda3) which is an ext4 partition. /boot is sda4 and is ext3. But I'm
sure grub should work no matter where you install it. I can even
install it on sda1 which is NTFS and it works. Hell, I can even install
it on the swap partition.
I guess the reason it broke will remain a mystery :P
next prev parent reply other threads:[~2009-02-17 17:22 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 ` [gentoo-user] " Neil Bothwick
2009-02-17 17:21 ` Nikos Chantziaras [this message]
2009-02-19 8:21 ` [gentoo-user] " 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='gnernf$2d9$1@ger.gmane.org' \
--to=realnc@arcor.de \
--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