From: Andreas Born <futur.andy@googlemail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub2 svn2059
Date: Sun, 05 Apr 2009 15:56:05 +0200 [thread overview]
Message-ID: <49D8B875.4090604@googlemail.com> (raw)
In-Reply-To: <49D7B682.3050008@earthlink.net>
BandiPat schrieb:
> Thanks Andreas, I just figured that out as well when testing on
> another machine just now. If you still have the file I sent you for
> svn2059, would you mind testing it on your machine as well. I'm
> tempted to send you the svn2059 or 2065 to compile on your current
> machine, to see if it behaves differently than the one I built. Be
> prepared though, as I'm sure you'll need to re-install svn2031 back
> after 2059 fails to boot. Keep your LiveCD available to reboot! :-)
I tested the svn2059-60.1 build on my current Zenwalk installation. It
would boot here, but I have it installed to superblock of my ext3
partition, so that might be the difference. Therefore I installed grub2
to the MBR, but like that it would work too.
But I noticed two other problems:
* If I drop to console with 'c' from the menu and then reload the
menu with 'configfile (hd0,3)/boot/grub/grub.cfg', 'prefix' is
unset and I can't boot. If I drop then back to console I can set
'prefix' properly to '(hd0,3)/boot/grub' and boot from console,
but configfile won't work.
* With the 'linux' loader as opposed to the 'linux16' loader, I
would always get a verbose splash, although I force a silent one
with 'splash=silent'. My assumption was that the kernel parameters
are ignored at all, but passing a wrong root resulted in a error.
So either only 'splash=silent' is ignored or its something
completely different. I think the problem is related to the one
described in "New linux loader doesn't like vga=1".
Andreas
next prev parent reply other threads:[~2009-04-05 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49D7744B.4040708@googlemail.com>
2009-04-04 15:01 ` Grub2 svn2059 Andreas Born
2009-04-04 19:35 ` BandiPat
2009-04-05 13:56 ` Andreas Born [this message]
2009-04-06 3:27 ` BandiPat
2009-04-15 20:27 ` BandiPat
2009-04-02 21:00 BandiPat
2009-04-02 22:19 ` Pavel Roskin
2009-04-03 4:15 ` BandiPat
2009-04-03 4:50 ` BandiPat
2009-04-03 5:17 ` step21
2009-04-03 12:19 ` BandiPat
2009-04-03 12:39 ` step21
2009-04-03 14:47 ` BandiPat
2009-04-03 18:44 ` Yoshinori K. Okuji
2009-04-03 19:02 ` BandiPat
2009-04-03 19:12 ` Yoshinori K. Okuji
2009-04-04 2:09 ` BandiPat
2009-04-04 10:53 ` phcoder
2009-04-04 12:50 ` BandiPat
2009-04-06 21:37 ` BandiPat
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=49D8B875.4090604@googlemail.com \
--to=futur.andy@googlemail.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.