USB Boot UEFI client into FOG menu (harder way)
-
I am trying this and for the most part it is seeing my USB drive and starting, however once it hits the Open Source Network Boot Firmware it closes and goes into windows. Am I missing something here. It never asks me for the server IP.
Here is the script I used in the ROM-o-matic site:
#!ipxe
dhcp
set next-server 10.20.60.14
set filename ipxe.efi
chain tftp://${next-server}/${filename}I have tested and the file is easily grabbable form all VLANs, so I am not sure what might be happening, unless the network card I am using just isn’t working. Is there anyway to tell. I am not seeing a IP being assigned.
-
@Psycholiquid I’d think you need to chain to the default.ipxe file of fog, not the ipxe.efi. The ipxe.efi should be already started by the usb stick, or at least how I’m seeing it.
Maybe I’m misunderstanding.
-
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.
Load the file itself directly
#!ipxe dhcp chain tftp://${next-server}/default.ipxeJust boot directly to what you need:
#!ipxe isset ${net0/mac} && dhcp net0 || goto dhcpnet1 echo Received DHCP answer on interface net0 && goto netboot :dhcpnet1 isset ${net1/mac} && dhcp net1 || goto dhcperror echo Received DHCP answer on interface net1 && goto netboot :dhcperror prompt --key s --timeout 10000 DHCP Failed, hit 's' for the iPXE shell; reboot in 10 seconds && shell || reboot :netboot cpuid --ext 29 && set arch x86_64 || set arch i386 params param mac0 ${net0/mac} param arch ${arch} param platform ${platform} param product ${product} param ipxever ${version} isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme :bootme chain http://fogserverip/fog/service/ipxe/boot.php##paramsThen again, i may be grossly misunderstanding the purpose of all of this.
-
@Tom Elliott Let me give that a try. I tried just loading the ipxe.efi directly form the server I get the same result. I hate these Dell XPS 12s
-
@Psycholiquid Let us know about anything you needed to do differently.
-
@Psycholiquid I believe the point of these usb files is for the cases where you do have problems. If you’re having problems with the files from PXE, booting “BACK” to them from the usb side would yield, I would imagine, the exact same results.
-
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.
-
@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.
This method requires a wired network connection still. Look into getting a USB to Ethernet adapter.
-
@Wayne-Workman Right I have a USB network card that seems to be showing up when I boot to the ipxe.efi just trying to get into FOG now
-
@Psycholiquid What is it’s make and model ?
-
@Psycholiquid You still need a network for fog to operate. I don’t include wireless drivers in the kernel, nor do I include the wireless utilities.
-
@Tom-Elliott See below. LOL we are all over this today.
-
From what I can tell I may have to do this same procedure for the MS Surfaces
Haven’t really tried it yet but it is looking like another UEFI nightmare. I havent seen any of my Surfaces boot to network yet.
-
@Psycholiquid What is the make and model of the USB adapter you’re using?
-
@Wayne-Workman StarTech USB31000SPTB
-
@Psycholiquid Ok… I don’t think that these instructions by the OP are going to help in your situation. We need to get your USB to Ethernet adapter going the regular way. Can you please start a new thread for the issue and post a screen shot of what you’re seeing when you try to network boot?
-
@Wayne-Workman Will do
-
@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.