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: Sun, 8 Jun 2014 09:22:00 +0400 [thread overview]
Message-ID: <20140608092200.55f3c290@opensuse.site> (raw)
In-Reply-To: <CAPSTsksdDeQd9MCvZkorguiZifdy0CL3Bnisp=rxN87uO=Fp8g@mail.gmail.com>
В Sat, 7 Jun 2014 21:11:04 +0300
Beeblebrox <zaphod@berentweb.com> пишет:
> I just updated my git repo (git log shows Apr 20 16:12:41), then
> re-compiled and reinstalled Grub. I then cd'ed to my TFTP root and ran
> "grub-mknetdir --net-directory=./" This completed without problem and
> displayed message to "direct TFTP to core.0" with correct path.
>
> PXE Booting process now fails as:
> Client gets IP address,
> "Welcome to GRUB" message displayed, then
>
> "error: file not found.
> Entering rescue mode...
> grub rescue> "
>
> TFTP log shows:
> tftp: client does not accept options
> RRQ from 192.168.2.34 filename grub/i386-pc/core.0
> RRQ from 192.168.2.34 filename /boot/grub/i386-pc/normal.mod
>
> $tftproot/boot/grub/i386-pc/grub.cfg has
> source boot/grub/grub.cfg
>
> What did this break?
Hard to tell without knowing what previous version was. I'm afraid in
this case your only possibility is to bisect (man git-bisect) to find
commit that broke things.
next prev parent reply other threads:[~2014-06-08 5:22 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 [this message]
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
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=20140608092200.55f3c290@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 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.