public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tomas Pilar (tpilar)" <tpilar@solarflare.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: iSCSI and iBFT
Date: Mon, 20 May 2019 15:56:52 +0000	[thread overview]
Message-ID: <3644c44636fb4fe5b719128ec1443b4c@ukex01.SolarFlarecom.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]

Hi,

I have a bit of an esoteric problem. When I configure the software iscsi intiator that is part of EDK2 platform network stack, the platform network stack with install iBFT table into the ACPI tables so that the configuration can be picked up by further boot loaders and the OS. So far so good.

Problem: When I PXE boot into iPXE using my adapter, exit back into boot manager, the iBFT has disappeared. Alternatively, if I use iPXE to then boot WDS, the software initiator in WinPE won't find the iBFT table and therefore won't hook the network drive.

Observations:
* When I boot into UEFI shell on disk and exit back into boot manager, the iBFT is preserved.

* When I PXE boot into UEFI shell and exit, the iBFT is preserved.

* When I boot into iPXE on disk and exit, the iBFT is preserved.

* When I use a different adapter (Intel) to pxe boot into iBFT and exit back to boot manager, the iBFT has moved from the penultimate position to the last position in the ACPI tables. Almost as if something uninstalled the iBFT and reinstalled it.

Any ideas?

Cheers
Tom
The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error, please notify the sender immediately and delete the message. Unless you are an addressee (or authorized to receive for an addressee), you may not use, copy or disclose to anyone this message or any information contained in this message. The unauthorized use, disclosure, copying or alteration of this message is strictly prohibited.

[-- Attachment #2: Type: text/html, Size: 4286 bytes --]

             reply	other threads:[~2019-05-20 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 15:56 Tomas Pilar (tpilar) [this message]
2019-05-21 14:54 ` iSCSI and iBFT Tomas Pilar (tpilar)
2019-05-21 19:47   ` [edk2-devel] " Laszlo Ersek
2019-05-22  9:55     ` Tomas Pilar (tpilar)
2019-05-22 10:19       ` Laszlo Ersek
2019-05-22 10:40         ` Tomas Pilar (tpilar)
2019-05-22 22:26           ` Michael Brown
2019-05-23  9:46             ` Tomas Pilar (tpilar)
2019-05-23 10:35               ` Michael Brown

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-list 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=3644c44636fb4fe5b719128ec1443b4c@ukex01.SolarFlarecom.com \
    --to=devel@edk2.groups.io \
    /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