All of lore.kernel.org
 help / color / mirror / Atom feed
From: BandiPat <magicpage91@earthlink.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub2 svn2059
Date: Fri, 03 Apr 2009 10:47:46 -0400	[thread overview]
Message-ID: <49D62192.4010804@earthlink.net> (raw)
In-Reply-To: <acc911d90904030539r725e6185u5fd0fe30779cba85@mail.gmail.com>

step21 wrote:
> yes, it probably should. i know that when creating an efi image for an
> efi based system with grub-mkimage you specify the modules, so it gets
> specified there, on a bios system I'm not sure. I don't think a
> symlink is the right solution.Did you run autogen.sh after updating?
> What might also work is to re-check out grub to a seperate directory,
> and try if that works.
-----------

Shouldn't the autogen.sh be run during the build?  How do you mean 
re-check out grub to a separate directory?  Just drop it in another 
unrelated directory and use the commands to run it testing the setup. 
Sorry don't remember exactly the commands right now, but I've got that 
somewhere in notes.  :-)

I guess when it goes into rescue mode, I could "insmod minicmd.mod" to 
test as well?

Thanks for your patience & help.

Pat



  reply	other threads:[~2009-04-03 14:47 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
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 [this message]
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=49D62192.4010804@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.