From: BandiPat <magicpage91@earthlink.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub2 svn2059
Date: Fri, 03 Apr 2009 00:15:50 -0400 [thread overview]
Message-ID: <49D58D76.1020100@earthlink.net> (raw)
In-Reply-To: <1238710774.10732.16.camel@mj>
Pavel Roskin wrote:
> On Thu, 2009-04-02 at 17:00 -0400, BandiPat wrote:
>> Hi guys,
>> Help a Grub2 novice out please. I try to keep up with most of the
>> changes you guys make, but I've either missed something or there is a
>> problem with the latest svn release, listed in the subject.
>
> Why are you writing that? Did any previous revision work for you?
-------
Sure, presently using svn2031 and have had no problems like this with
any other previous build.
>
>> Upon building the package for Zenwalk, installing, then running
>> grub-install, I rebooted the machine to test. I got the "Welcome to
>> Grub2" then an error!
>> error: the symbol 'grub_command_list not found
>> Entering Rescue mode...
>
> I cannot reproduce that problem with revision 2059. Please give details
> how exactly you built and installed GRUB.
> -----------
I can include my build script, if that will help you determine the
problem. I can assure you though the only changes I made in the script
from 2031 to 2059 was the version number though. Installation was
standard "upgradepkg", then I ran grub-install (device). Could it be
that something didn't copy over? I'm using ext3 filesystem, where I was
using xfs, but again 2031 works fine.
>> What happened?
>
> GRUB cannot find some module, probably "minicmd". Please post the
> output of "ls" and "set". Perhaps "prefix" points to an undetected
> device.
> --------
I didn't write that down when testing 2059 and cannot remember the
output of either, sorry.
>> Did I fail to build it correctly?
>
> I don't know. You message doesn't indicate any build failures.
> ========
I ask this in case there was something else I needed to include in the
./configure I may have left out. One thing I'll mention, but I don't
believe it plays a part, is that we just started using the latest gcc 4.3.3?
> It looks like the failure happens before grub.cfg is loaded, so the
> contents of grub.cfg is irrelevant at that stage.
>
--------
Ok, so either something failed to compile or I built it incorrectly.
Included find the build text, which may be of help. I did not see any
errors. The mail list wouldn't take the large text file, so I'll post
it on my download site for you to grab with the build script.
http://zenwalk.pinguix.com/user-accounts/BandiPat/files,etc/build-grub2.sh
http://zenwalk.pinguix.com/user-accounts/BandiPat/files,etc/grub2-svn2059-build.txt
thanks again,
Pat
next prev parent reply other threads:[~2009-04-03 4:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 21:00 Grub2 svn2059 BandiPat
2009-04-02 22:19 ` Pavel Roskin
2009-04-03 4:15 ` BandiPat [this message]
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
[not found] <49D7744B.4040708@googlemail.com>
2009-04-04 15:01 ` Andreas Born
2009-04-04 19:35 ` BandiPat
2009-04-05 13:56 ` Andreas Born
2009-04-06 3:27 ` BandiPat
2009-04-15 20:27 ` 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=49D58D76.1020100@earthlink.net \
--to=magicpage91@earthlink.net \
--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.