All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omni Flux <omniflux+lists@omniflux.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Problems booting Linux via PXE
Date: Thu, 26 Aug 2010 15:27:25 -0600	[thread overview]
Message-ID: <4C76DC3D.1040704@omniflux.com> (raw)
In-Reply-To: <AANLkTi=K=KrX=vaXjrbGwHzh-Ozcp2TpRY0xSK4rnpSG@mail.gmail.com>

On 2010-08-26 09:06, Bruce Edge wrote:
> I have also seen this issue but chalked it up to user error. (version
> 1.98-1ubuntu7) I watched wireshark traces show 3 pkts and stop. This was
> from a Xen domU so I suspected a Xen problem at the time and gave up and
> went to Xen's pv-grub instead that has a built-in tftp client.
>
> Where can I retrieve a Grub2 branch that resolves this issue? An Ubuntu
> package would be nice, but I'll take anything that builds.
>
> Thanks
>
> -Bruce

I assumed user error on my part as well, until I saw someone else 
complain here...

You can checkout the newreloc branch from bazaar with the following command:

bzr branch http://bzr.savannah.gnu.org/r/grub/branches/newreloc/

I did the following to build and test it last night:

./autogen.sh
./configure
make
./grub-mkimage --directory=grub-core -O i386-pc --output=core.img 
--prefix="(pxe)/boot/grub" pxe pxecmd
cat grub-core/pxeboot.img grub-core/core.img > grub-core/grub2pxe
cp grub-core/*.mod /var/lib/tftpboot/boot/grub/
cp grub-core/*.lst /var/lib/tftpboot/boot/grub/
cp grub-core/grub2pxe /var/lib/tftpboot/boot/grub/

Your target directories will surely vary :)

-- 
Omni Flux


  reply	other threads:[~2010-08-26 21:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 19:02 Problems booting Linux via PXE Turner, Ian
2010-08-26  1:12 ` Omni Flux
2010-08-26  1:14 ` Omni Flux
2010-08-26  8:02   ` Omni Flux
2010-08-26  7:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-26  8:48   ` Omni Flux
2010-08-26 15:06     ` Bruce Edge
2010-08-26 21:27       ` Omni Flux [this message]
2010-08-26 22:55   ` Turner, Ian
2010-09-02 23:01     ` Vladimir 'φ-coder/phcoder' Serbinenko

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=4C76DC3D.1040704@omniflux.com \
    --to=omniflux+lists@omniflux.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.