From: Bean <bean123@126.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB 2 does not show new kernel :(
Date: Wed, 27 Jun 2007 11:07:00 +0800 [thread overview]
Message-ID: <20070627030700.GA2806@ws3.vdp.com> (raw)
In-Reply-To: <20070627015838.GA2686@ws3.vdp.com>
On Wed, Jun 27, 2007 at 09:58:38AM +0800, Bean wrote:
> On Wed, Jun 27, 2007 at 01:18:41AM +0530, shirish wrote:
> > Hi all,
> > I thought long & hard before making this post. I tried all
> > the avenues , the #GRUB channel on IRC, the forums at ubuntuforums (
> > 136 views at this point in time but no answers :( ) . hence made long
> > posts about the issue at
> > http://ubuntuforums.org/showthread.php?t=484856
> >
> > If anybody knows what I need to do or look for , please lemme know.
> >
> > Cheers !
>
> Currently, the script engine of grub2 doesn't support comment line ! Just
> remove any line that starts with #, and you should be fine.
My mistake. Although the script engine doesn't handle comment, lines start
with # are dropped when read from config file, so it wouldn't cause problem.
I suspect the device name is wrong. If you are booting with the hard disk,
the device name should be (hd0,1). The wrong device name causes the font
command to fail, and it in turn causes other problem. Change (hd1,1) to
(hd0,1), see if it fixes the problem.
--
Bean
next prev parent reply other threads:[~2007-06-27 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 19:48 GRUB 2 does not show new kernel :( shirish
2007-06-27 1:58 ` Bean
2007-06-27 3:07 ` Bean [this message]
2007-06-27 2:18 ` Bean
-- strict thread matches above, loose matches on Subject: below --
2007-06-27 6:25 shirish
2007-06-27 6:39 ` Bean
2007-06-27 14:05 shirish
2007-06-27 16:17 ` Bean
2007-06-27 20:06 shirish
2007-06-27 20:44 shirish
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=20070627030700.GA2806@ws3.vdp.com \
--to=bean123@126.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.