From: "Arends, R.R." <r.r.arends@hro.nl>
To: "Thomas Miletich" <thomas.miletich@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
etherboot-developers@lists.sourceforge.net,
Robert Millan <rmh@aybabtu.com>
Subject: Re: [Etherboot-developers] gPXE and GRUB2
Date: Thu, 19 Nov 2009 11:00:16 +0100 [thread overview]
Message-ID: <4B052543.7FDC.0010.0@hro.nl> (raw)
In-Reply-To: <422fdd8a0911190153qa7c58bcle4780880401b1720@mail.gmail.com>
Thomas,
Ah yes your right. I'm doing it the gpxelinux way. Gpxe -> pxelinux -> grub2 (vesamenu entry).
Rene
PS: sorry for the double post
>>> On 19-11-2009 at 10:53, in message
<422fdd8a0911190153qa7c58bcle4780880401b1720@mail.gmail.com>, Thomas Miletich
<thomas.miletich@gmail.com> wrote:
> Hi
> The .0 postfix is used by pxelinux to indicate a NBP. gPXE will not
> use the filename as an indication of the image type. gPXE will
> autodetect the image type. As long as multiboot support is compiled
> in, it will always conclude it's a multiboot kernel.
>
> Loading pxelinux from gPXE and letting pxelinux load grub2pxe.0 is way
> to use an unmodified GRUB 2 and gPXE image.
>
> Thanks for bringing up this idea
> Thomas
>
> On Thu, Nov 19, 2009 at 10:03 AM, Arends, R.R. <r.r.arends@hro.nl> wrote:
>> Hi Thomas,
>>
>> I had the same issue after following that wiki and loading the grub2pxe from
> gpxe.
>>
>> You can fix it by renaming the grub2pxe file to grub2pxe.0, then the
> pxestack of gpxe stays intact and it will try to load the needed mod's from
> your tftp server (next-server).
>> I didn't manage to get grub loadings its files over gpxe http yet tho... So
> if anyone else managed that, i would like to know how :D.
>>
>> Best regards,
>>
>> Rene Arends
>>
>>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
>
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Etherboot-developers mailing list
> Etherboot-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/etherboot-developers
prev parent reply other threads:[~2009-11-19 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 23:28 gPXE and GRUB2 Vladimir 'phcoder' Serbinenko
2009-11-14 15:44 ` Robert Millan
[not found] ` <422fdd8a0911140615n5e16d736l7462dfcf968e2f23@mail.gmail.com>
2009-11-14 15:57 ` [Etherboot-developers] " Vladimir 'phcoder' Serbinenko
2009-11-14 17:38 ` Robert Millan
[not found] ` <422fdd8a0911141003j3839662dm30489e08e87da90e@mail.gmail.com>
2009-11-14 18:46 ` Robert Millan
2009-11-19 9:10 ` Arends, R.R.
[not found] ` <4B0517EC.7FDC.0010.0@hro.nl>
[not found] ` <422fdd8a0911190153qa7c58bcle4780880401b1720@mail.gmail.com>
2009-11-19 10:00 ` Arends, R.R. [this message]
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=4B052543.7FDC.0010.0@hro.nl \
--to=r.r.arends@hro.nl \
--cc=etherboot-developers@lists.sourceforge.net \
--cc=grub-devel@gnu.org \
--cc=rmh@aybabtu.com \
--cc=thomas.miletich@gmail.com \
/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.