From: Beeblebrox <zaphod@berentweb.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: PXE-Grub has no menu - File not found
Date: Mon, 23 Jun 2014 22:39:43 +0300 [thread overview]
Message-ID: <20140623223943.15d2a963@rsbsd.rsb> (raw)
In-Reply-To: <CAPSTsksFgcqFepLAzw0HRd2GYHcZK9Jcf8w80Woh64d26dQpVQ@mail.gmail.com>
I just now updated to latest in trunk, then deleted the gub/i386-pc
folder and reinstalled with "grub-mknetdir --net-directory=/path/to"
At first the PXE-boot process breaks with
"Error message: File not found", because the i386-pc folder has perm
700 root:wheel. Only after chmod 755 does that error go away. But, the
grub boot process is now showing a new message when it fails:
error: Access violation \ Entering rescue mode... \ grub rescue>
I ran wireshark during grub-pxe to see where the process was failing.
Does the below finding mean anything?
90 7.084908000 192.168.2.1 (tftp root) 192.168.2.34 (pxe client) TFTP
63 Error Code, Code: Access violation, Message: Access violation
Source File: //boot/grub/i386-pc/normal.mod
Opcode: Error Code (5)
Error code: Access violation (2)
ls -la i386-pc/normal.mod > -r--r--r-- 1 root wheel
I wanted to make sure that file permission was not the reason so I
did "chmod -R 777 i386-pc". This gave the same violation error.
Also, why does grub-mknetdir create a 700 folder? Is the folder user
supposed to be _dhcp or some other daemon?
Regards.
next prev parent reply other threads:[~2014-06-23 19:40 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 [this message]
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=20140623223943.15d2a963@rsbsd.rsb \
--to=zaphod@berentweb.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 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).