So the current problem is:
GRUB wants to EXCLUSIVE open SNP, though if other application/driver already
opens SNP with EXCLUSIVE attribute, the GRUB would fail. According to UEFI spec
V2.5 page 182,
If Attributes is BY_DRIVER , BY_DRIVER|EXCLUSIVE, or EXCLUSIVE, and
there are any items
ISC DHCPD, specifically, v4.1.1 running on RHEL6.6x64
The code block needed is adding to the top of the config file:
"allow bootp;"
Then in the subnet (I call them scopes since I have a wide variety of different
dhcps setup in our lab and there's more windows units than linux),
A bootp specif
14.10.2015 21:09, Rivard, Matthew T пишет:
Just going by these definitions of bootp and dhcp here:
https://technet.microsoft.com/en-us/library/cc781243%28v=ws.10%29.aspx
The net_bootp only works with a bootp enabled scope on the dhcp server after chaining
from iPXE to grub2. Without a "bootp"
14.10.2015 21:09, Rivard, Matthew T пишет:
Just going by these definitions of bootp and dhcp here:
https://technet.microsoft.com/en-us/library/cc781243%28v=ws.10%29.aspx
The net_bootp only works with a bootp enabled scope on the dhcp server after chaining
from iPXE to grub2. Without a "bootp"
Sorry, I thought I had replied back to this.
I found a work around by calling net_bootp on the adapters (I wrote a manual
block of 64 potential devices given that that's not an unrealistic number of
adapter ports to be found in a server in our lab), and setting a bootp range on
our DHCP serv
Just going by these definitions of bootp and dhcp here:
https://technet.microsoft.com/en-us/library/cc781243%28v=ws.10%29.aspx
The net_bootp only works with a bootp enabled scope on the dhcp server after
chaining from iPXE to grub2. Without a "bootp" scope setup on the dhcp,
calling net_bootp
14.10.2015 19:56, Rivard, Matthew T пишет:
Sorry, I thought I had replied back to this.
I found a work around by calling net_bootp on the adapters (I wrote a manual
block of 64 potential devices given that that's not an unrealistic number of
adapter ports to be found in a server in our lab), a
14.10.2015 15:16, Vladimir 'phcoder' Serbinenko пишет:
Le 14 oct. 2015 6:50 AM, "Andrei Borzenkov" a écrit :
10.10.2015 03:28, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
On 09.10.2015 23:14, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 13.09.2015 08:32, Andrei Borzenkov wrote:
08.09
14.10.2015 11:00, Ye, Ting пишет:
Could you please describe the details how does GRUB use UEFI network protocols?
When efinet driver is loaded it enumerates handles with SNP; these
handles represent network cards for grub. If driver is part of initial
core.img (default for network boot image
> On Oct 14, 2015, at 4:08 AM, Daniel Kiper wrote:
>
>> On Wed, Oct 14, 2015 at 05:19:32AM +, Ye, Ting wrote:
>> Hi all,
>>
>> If I understand the issue correctly, I don't quite agree that UEFI
>> spec is imprecise about SNP constraints described as following.
>> The "constraint" described
Le 14 oct. 2015 6:50 AM, "Andrei Borzenkov" a écrit :
>
> 10.10.2015 03:28, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
>
>> On 09.10.2015 23:14, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>
>>> On 13.09.2015 08:32, Andrei Borzenkov wrote:
08.09.2015 20:11, Vladimir 'φ-coder/phcoder
On Wed, Oct 14, 2015 at 05:19:32AM +, Ye, Ting wrote:
> Hi all,
>
> If I understand the issue correctly, I don't quite agree that UEFI
> spec is imprecise about SNP constraints described as following.
> The "constraint" described here is that the grub should use attribute
> "EXCLUSIVE" to open
Could you please describe the details how does GRUB use UEFI network protocols?
I see the thread says that EXCLUSIVE open SNP causes PXE boot fail.
If you read below description about 'EXCLUSIVE' in UEFI specification, you will
find when GRUB exclusive opens SNP protocol, the UEFI will remove a
Hi all,
If I understand the issue correctly, I don't quite agree that UEFI spec is
imprecise about SNP constraints described as following.
The "constraint" described here is that the grub should use attribute
"EXCLUSIVE" to open SNP protocol to gain exclusive access. This usage is
clearly descr
May I know the details what problems it causes in some cases?
Thanks,
Ye Ting
-Original Message-
From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
Sent: Wednesday, October 14, 2015 1:58 PM
To: Ye, Ting; Laszlo Ersek; daniel.ki...@oracle.com; grub-devel@gnu.org
Cc: konrad.w...@oracle.c
14.10.2015 04:01, Yinghai Lu пишет:
On Tue, Oct 13, 2015 at 3:11 PM, Daniel Kiper wrote:
On Thu, Oct 01, 2015 at 08:53:44PM +0300, Andrei Borzenkov wrote:
Hatayama-san, would you consider implementing MNP-based driver for GRUB?
Having at least proof of concept available for testing would be go
14.10.2015 09:15, Ye, Ting пишет:
May I know the details what problems it causes in some cases?
One is being discussed in this thread:
http://lists.gnu.org/archive/html/grub-devel/2015-10/msg00013.html
http://lists.gnu.org/archive/html/grub-devel/2015-10/msg00068.html
Another was reported re
17 matches
Mail list logo
