USB Boot UEFI client into FOG menu (harder way)
-
@george1421 Best way to keep up with updates in that regard, would be, (for your setup at least), instead of booting to ipxe.efi, or some other filename, goto: tftp://FOGIP/default.ipxe.
THe problem with this approach (though) is it assumes the fogip in the file will always have tftp running. That’s why I recommend using a combination of your scripts and the ipxescript from the src as a part of the embedded script.
It leads you away from the need to have tftp running, and all the DB style checks can still be made.
-
Step Number 6 does not appear under the San boot protocols but under the Http Extension. Is this correct?
SAN boot protocols:
SANBOOT_PROTO_ISCSI, iSCSI protocolSANBOOT_PROTO_AOE, AoE protocol
SANBOOT_PROTO_IB_SRP, Infiniband SCSI RDMA protocol
SANBOOT_PROTO_FCP, Fibre Channel protocol
SANBOOT_PROTO_HTTP, HTTP SAN protocol
HTTP extensions:
HTTP_AUTH_BASIC, Basic authenticationHTTP_AUTH_DIGEST, Digest authentication
HTTP_ENC_PEERDIST, PeerDist content encoding
HTTP_HACK_GCE, Google Compute Engine hacks
-
@cnkpadobi Just be aware that this document was created over a year ago so some of the menu/values on the rom-o-matic site may have moved. But from memory I would say that the
HTTP Extensionsis the right location now. -
Thank you, was wondering why I am getting this message.
Thanks
-
@cnkpadobi This may not be an issue with the iPXE kernel settings specifically. I would test this pxe boot stick on a computer that does work with pxe booting today. The idea here is that there is a potential that the iPXE kernel may not have the required driver for this usb network adapter.
-
@george1421 Hmm that make sense is there a way to get a list of compatible USB adapter
-
@george1421
Here is the pic from the FOS USB -
@cnkpadobi I just rebuilt that image file and will test it tonight to see if something changed.
-
@george1421 Thank you
-
@cnkpadobi Here is the new error
-
@george1421 here is the error
