UEFI-PXE-Boot (Asus t100 Tablet)
-
@K.Hays Do you get to a different point or does it still sit at the “Start pxe over ipv4”?
There are several .efi files to choose from (ipxe.efi, snp.efi, snponly.efi, realtek.efi, intel.efi)
-
@Scott-Adams Just sits at that screen
-
@Scott-Adams I just have to switch bootfiles on the dhcp correct? I dont have to do it anywhere else?
-
@K.Hays Nope. Just on the DHCP server. Just so we’re not overlooking the obvious, you are setting the boot file (option 67) on the IP scope that your plugged into right?
-
@Scott-Adams yessir
-
@K.Hays Ok. Let’s try this. Remove the “has_usb_nic=1” from FOG_KERNEL_ARGS.
Next, manually create a host from the Web UI with the MAC address of the USB nic you are using (the one that you found should work).
On that host, change your Host Kernel to bzImage32 (as I believe the T100 is a 32bit device). Then, enter “has_usb_nic=1” (minus the quotes) for Host Kernel Arguments.
-
@K.Hays Can we have a photo of what you’re seeing?
-
@Scott-Adams same thing happened.
-
-
@K.Hays Anything happening before that?
-
-
@K.Hays Can you try to change the firmware mode? If it’s in BIOS, put it in UEFI, if it’s in UEFI, try BIOS. Also can you check for firmware updates?
What do the other adapters do?
-
@Wayne-Workman the two adapters do that, and the other one isn’t recognized as a boot option. It’s only capable of uefi also.
-
@K.Hays Firmware update.
-
@Wayne-Workman I can attempt to update the firmware, but I feel like that probably isn’t the issue. We have an HP laptop that we put into UEFI mode to help us troubleshoot and it is doing the same thing as the tablets, and it’s not using a USB adapter.
-
and you’ve been able to use fog with non-uefi systems prior to these tests with uefi, right?
-
@K.Hays Well, the problem you’re describing isn’t a fog problem. It’s a firmware or adapter or network issue. You’re not even getting to the point of communicating with the fog server at all.
-
@K.Hays said in UEFI-PXE-Boot (Asus t100 Tablet):
all other computers work just fine to image.
-
@Wayne-Workman I am currently updating the firmware. If it is a network issue as you’re thinking, could it be caused by the fact that we’re running a Sever 2008 DHCP?
-
@Wayne-Workman Firmware update was ineffective.
