grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: zaphod@berentweb.com
Subject: Re: PXE-Grub has no menu - File not found
Date: Wed, 25 Jun 2014 21:36:50 +0400	[thread overview]
Message-ID: <20140625213650.10731668@opensuse.site> (raw)
In-Reply-To: <20140624181900.10517d67@rsbsd.rsb>

В Tue, 24 Jun 2014 18:19:00 +0300
Beeblebrox <zaphod@berentweb.com> пишет:

> Is it possible my findings below show that PXE booting on grub2 (trunk)
> when compiled and running on FreeBSD is broken?
> 
> * When isc-dhcpd.conf has "grub/i386-pc/core.0" as filename, wireshark
>   shows abort due to "file not found: grub/i386-pc/normal.mod".
> * From linux laptop, "tfpt 192.168.2.1" then
> "tftp> get grub/i386-pc/normal.mod" => 
> file downloads without problem. Also, any other file in the (-s) path of tftp server gets downloaded.
> * When isc-dhcpd.conf has "pxeboot" as filename (the BTX equivalent of
>   core.0), BTX menu gets displayed, allowing next step for boot.
> 

Could you make available full tcpdump/tshark trace of both cases? With
capture size 1500 so it captures full packets?


  reply	other threads:[~2014-06-25 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07 18:11 PXE-Grub has no menu - File not found Beeblebrox
2014-06-08  5:22 ` Andrey Borzenkov
2014-06-09  5:20   ` Beeblebrox
2014-06-23 19:39     ` Beeblebrox
2014-06-24 15:19       ` Beeblebrox
2014-06-25 17:36         ` Andrey Borzenkov [this message]
2014-06-26 15:58         ` Andrey Borzenkov
2014-06-27  6:26           ` Beeblebrox
2014-06-27 16:08             ` Andrey Borzenkov
2014-07-02  6:24               ` Beeblebrox

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=20140625213650.10731668@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=zaphod@berentweb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).