USB Boot UEFI client into FOG menu (harder way)
-
@Tom-Elliott said:
I guess what I’m trying to say, if you’re using the usb, you’re already IN ipxe in some way, why would you want to redirect to another ipxe file. Why not make the config the same AS the default.ipxe file, or just load the file itself.
The intent (right or wrong) was to not alter the FOG workflow. My intentions were to get the client booted well enough to then load the official ipxe.efi kernel with all of its goodness. There are many more network checks being done with its boot script than is being done with the USB boot. Was this the right idea, I guess time says… maybe?
-
@Psycholiquid said:
What I am trying to do is boot from USB pxe because the laptop has no NIC or UEFI is not cooperating like it should.and Wireless wont boot from network. So basically trying to make a live USB drive so I can boot to FOG on machine where there is no nic or the docking station wont show up.
While this is the intended purpose of the usb boot, dealing with wireless nics is a bit of a pain since the number of models is staggering. I don’t think I included the wireless management code in my how to script. The preference would be to use a usb ethernet nic.
The issue I see is some how you need to tell the client what SSID to connect to and any security keys required to connect. Unless you create a fully open wireless network just for imaging.
-
@george1421 I don’t think you’re doing anything wrong, but at this point you’re already in ipxe. so why not just use the file with the modified embedded script? you’re already in there. ipxe.efi or ipxe.pxe already have ALL the same drivers ours do. Only difference is the embedded script at that point.
-
@Tom-Elliott OK great. I just wanted to give the usb booted device just enough to get into the official FOG ipxe.efi kernel. That way if you guys developed new or additional tests this external boot would not have to stay in lock step with your updates.
BUT, with that said, if there is an easier/better/preferred way to do this, just let me know and I’ll update this document.
-
@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
