UEFI-PXE-Boot (Asus t100 Tablet)
-
Were trying to image 250 t100 tablets we have. We got three different network adapters as these tablets have no on board ethernet port. From what Ive read two of the three should work with it. When we boot to the network we get “Start pxe over ipv4” and then it just sits there. Not sure what to do at this point. Have read a lot of forum posts on this but haven’t gotten much luck. Is it even possible at this point. We have server 2008 for the dhcp, i read somewhere that we might need 2012. Other than that we have fog trunk, and have also changed option 67 to point towards ipxe.efi with no luck.
-
Have you tried putting the value “has_usb_nic=1” (minus the quotes) under FOG Configuration -> FOG Settings -> General Settings -> FOG_KERNEL_ARGS?
Also, check your BIOS settings for Secure Boot. Secure Boot needs to be turned off/disabled in order to work.
You could try using a different boot file as well. I typically use snponly.efi for my UEFI devices.
-
Can you image other computers fine with your fog setup?
Can you please share the exact models of USB adapters you have?
-
This post is deleted! -
@K.Hays Secure boot is off, we are just about to test out the rest of what you stated Scott.
Wayne, all other computers work just fine to image. The main adapter we are using is
Asus 90-XB3900CA00040- USB 2.0 to Ethernet Adapter -
@Scott-Adams Didn’t work. Were also testing it with a Uefi laptop with a built in port and it’s also not working.
-
@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.
