FOG USB Boot media with Intel NUC7i5BNH
-
@Sebastian-Roth UEFI. If I disable UEFI mode and try booting to legacy it doesn’t even try to boot from the USB stick. Just gives error, no operating system found.
-
@theland10 Ok, so I guess you downloaded “EFI PXE bootstrap 64-bit (.efi)” from https://rom-o-matic.eu/, right? Have you tried “EFI x86_64 snponly (.efi)” yet?
Are you absolutely sure this issue is specific to the NUC model? I am just trying to prevent us from running down the wrong lane right from the start. Can you please try one of your other models (known working) right at the same spot where this NUC fails (exact same network cable/port/switch)?
-
@Sebastian-Roth Yes that is correct, followed the instructions from ‘the harder way’ here. I just tried the snponly.efi and with it booting to UEFI it shows the iPXE menu for a split second and immediately goes back to the boot selection screen. With UEFI off it’s just as before, no boot device found.
I did find the known working device list and systems with known issues list. The NUC7i5BNH model is not on either list. We have some older NUC models I can try but likewise they aren’t on either list. As for other systems this is the same cable/port/switch I have been using for all systems I have captured/imaged.
-
@Sebastian-Roth I have confirmed our fog setup works with no fuss on NUC5i3 model.
-
@theland10 I have a NUC 5i5myhe on my test bench I can test with.
But some things I can suggest to you .
- Make sure the firmware is up to date with these NUCs especially if you are using UEFI mode. Its pretty easy to update them if you copy the firmware to a use flash drive.
- The network adapter is a I219-V, while you are still in iPXE boot loader, I can say that FOS Linux does support that network adapter since forever.
- In the fwiw bucket, for uefi mode you don’t need to use the rom-o-matic site you can just grab ipxe.efi from the fog server, rename and move to a usb formatted flash drive in the proper directory and it will boot.
Does your NUC7i5 have a built in wifi adapter too (where it might shift eth0 from the hardware ethernet adapter to the wifi adapter)?
If all else fails to get you going, we can boot directly into FOS Linux from a usb flash drive. It will work this way, but you will have less caveats and better booting experience if we can get iPXE working correctly.
-
@george1421 Thanks George, and yes, I have tried both with updated firmware and with a new one, no changes, straight out of the box. Same issue.
It does have a built in wireless card. I just tried disabling in bios and booting from the stick, no luck. I do not think I have tried with the default ipxe.efi from the server.
I have some things to attend to this morning and will update later today.
Thank you.
-
@george1421 With default ipxe.efi from server, same issue. Only slight difference is instead of showing ‘no config methods succeeded’ and immediately kicking back to the boot menu it attempts to configure twice then gives option to hit ‘s’ for iPXE shell. Using ‘dhcp’ command gives same output, no configs succeeded.
-
@theland10 From what you have tried and told us so far it’s very likely iPXE simply doesn’t like/support the network interface card. Do you know the exact network chip you have in those models? Please try booting a Live Linux from CD/DVD, run
lspci -nn | grep -i -e ethernet -e networkand post output/picture here.Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
Sebastian-Roth said in FOG USB Boot media with Intel NUC7i5BNH:
Please try booting a Live Linux from CD/DVD, run lspci -nn | grep -i -e ethernet -e network and post output/picture here.
Or from a running windows computer post the hardware id for that network adapter both the vendor and model bits.
-
@george1421 Intel l219-V
PCI\VEN_8086&DEV_15D8&SUBSYS_20688086&REV_21
PCI\VEN_8086&DEV_15D8&SUBSYS_20688086
PCI\VEN_8086&DEV_15D8&CC_020000
PCI\VEN_8086&DEV_15D8&CC_0200 -
@theland10 Intersting, the iPXE lists this NIC as supported: https://ipxe.org/appnote/hardware_drivers
Can you try using
intel.efi? -
@theland10 As well please do a simple link check. Boot to the point where it tries to get an IP twice and drops you to a shell. Now check the LED. Link on? Pull the cable, wait 3 seconds, plug it back in and wait to see if the LED comes back on?!
Now run
ifstatin the iPXE shell and post output here. -
@Sebastian-Roth Gives MAC address on first line:
xx:xx:xx:xx:xx:xx using i319v-4 on 0000:00:1f.6 (closed)
[Link:up, TX:8 TXE:2 RX:0 RXE:0]
[TXE: 2 x “Operation not supported (http://ipxe.org/3c654083)”] -
@theland10 said in FOG USB Boot media with Intel NUC7i5BNH:
TX:8 TXE:2 RX:0 RXE:0That’s the interesting part of the output. It tried to send eight packets (transmitted packets) and got two errors (TXE). While error sounds bad it really does not have to be in all cases. I am not a iPXE hacker and only know the code a bit but as far as I remember there are many situations where TXE count doesn’t actually mean a problem. But the issue I see is that there is no RX (received packets) whatsoever. I have no idea why that might happen.
Did you do the link check I asked you to in the last post? As well tried
intel.efiyet? -
@Sebastian-Roth Yes and yes. That ifstat output was directly after ensuring I had link lights from replugging the Lan cable. Which was directly after entering the ipxe menu from a failed boot using the intel.efi
-
@theland10 Then I suppose we are down to the bones and need to enable debugging in iPXE. When requesting a binary from rom-o-matic there is a field Debug build. Put
intelinto that field and you should get some more output - fancy in colors. -
@Sebastian-Roth Here is the output from the debugger:
Also, our resident linux guru (I’m very much a beginner but I pick up quickly) and myself have been trying to set up the FOS Linux boot stick in the meantime. We are able to get to the selection menu to choose quick register/full register/capture etc. It sees both our DHCP servers and pulls an IP ok but ends with an error unable to access FogserverIP/fog/index.php or FogserverIP/index.php.
-
@theland10 Hmmmmm, in the picture I see
Received DHCP answer on interface net0… Looks very different to what you told us before. Maybe debugging causes different timings within the driver and make it work?!The error in the picture makes me think that maybe the default gateway option is not properly propagated to the client and it cannot reach IP 172.17.1.171 because of that?! Why is the IP different on the first TFTP pull (
ipxe.efi) than on the second one (default.ipxe). Possibly it’s for a good reason but things just don’t add up for me here. -
@Sebastian-Roth I was confused about that myself. The 172.17.65.19 is our fog server. 172.17.1.171 is the server for our virtual devices we have set up for PXE booting, and the reason why we are using the USB boot media as opposed to using straight PXE booting for fog. That IP was not entered anywhere in the setup on rom-o-matic for the efi file. I’m going to try a slight change to the script on that.
-
@theland10 I did add some hints for booting straight into FOS via usb in the forum chat. Look at the chat bubble in the upper right corner of the browser window.
