X1 AIO Desktop - i7 vPro network issue with Intel I219-LM [was: Make new bzImage...]
-
@mandrade Based on what I see of the image as found in the reply link It appears the place where it’s trying to download the file is unreachable. Maybe this is due to firewall? The IP address looks correct, but what’s the IP address of the system? Maybe a DHCP command is needed?
-
Thanks for the response Tom. Other workstations work fine, I am able to image them without issue. I did mention earlier that this setup is slightly different from the others in that this laptop doesn’t have an onboard NIC. It uses a OneLink+ mini dock. The thing is I can see it gets an IP from the DHCP server before it starts to the boot process. Somewhere along the line it loses it’s config somehow and then Fog server is no longer reachable.
-
@mandrade The boot process is a bit strange.
Most likely where you’re seeing the issue is one of a couple potential pitfalls. The biggest one, I believe, is that the tftp files you’re using appear to be from a newer (developmental) version of fog. As I understand this is a debug generated set of files, I suppose this isn’t the underlying issue, rather a symptom of something else.
The boot process, in simple terms, is not as simple as the initial DHCP. The first DHCP is for PXE to grab information from. Then it hands the system off to the bootfile, in your case undionly.{k,kk}pxe. When it is in undonly side, it needs to reestablish the DHCP protocol. Do you see the system getting an IP from there? Normally it would reboot, but if it’s just skipping and trying to boot, maybe the bootfile is doing something differently as well? Issues that could be happening, I suppose, are STP (Spanning Tree Protocol), firewall blocking this series of data, system is on a vlan that can’t reach the fog server to download the http data, or possibly (unlikely) all of the above.
-
I am indeed using a trunked version of FOG. There is no firewall, VLAN separation between the host and FOG. It does get an IP otherwise I would not be able to get to the menu to select an option am I right?
When I select inventory from the menu list it starts to attempt to load the bzImage but fails with connection timed out. All just very strange! I then run the same thing only this time on another host that has an onboard NIC and BOOM it works fine. So my take is that it’s something to do with the mini DOCK. Perhaps drivers? I dunno pure speculation from my part.
-
@mandrade Totally understand, just trying to clarify too. Yes, if it’s getting to the menu it should be fine. What if you change the boot file (undionly) to ipxe.pxe?
-
This thread has gotten pretty long. Have you tried all the things Sebastian posted? Can we summarize where things are?
-
this is what happens if I boot from ipxe.pxe:
It just sits there and eventually reboots
-
Yep tried all the things Sebastian has posted. I was requested to send new tcpdump which I sent to the previously supplied e-mail address.
At this stage I am able to image all my workstations with exception of my Lenovo Thinkpad x1 Carbon machines which connect to the network via a OneLink+ mini docking station as they do not have an onboard NIC.
-
@mandrade You’ve tried intel.pxe?
-
DHCP fails and I’m requested to pres ‘S’ to exit to iPXE shell. Probably worth the mention the machine is seeing the interface as a Realteck RTL8153 USB Ethernet Controller (xHCI) v2.00
USB, would FOG handle USB NIC’s differently perhaps?
-
@mandrade the picture appears to show Intel though. If you use realtek.pxe then?
-
Well derp I see the rtl now…
-
same result as when I run Intel.pxe
-
@mandrade said in Make new bzImage...:
would FOG handle USB NIC’s differently perhaps?
Yes,
in the host’s kernel arguments, you would puthas_usb_nic=1 -
Right but in this case I would have to capture the Host manualy first right? Because, I cannot inventory the computer.
-
@mandrade You could try to register it manually with just a name and MAC.
Also - not sure how possible this might be but you may try @george1421 's USB tutorial.
He wrote a tutorial that was put in the wiki, it outlines how to create a bootable flash drive with FOS on it, that will allow you to image. I’m not sure how you’d incorporate it into the Lenovo Thinkpad x1 Carbon, perhaps a MicroSD card, perhaps a USB Hub…
Basically, this process removes iPXE and PXE from the equation totally. You still use the FOG server, but you’re booting from removable media.
Read through it here:
https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media -
So no dice either way. Tried manually registering the machine and also booting from the bootable USB following the wiki how to https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media. If I boot from the usb it just returns back to the boot menu. If I add the has_usb_nic=1 parameter it boots through to start imaging but hangs at loading the bzImage.
I tried another laptop different hardware of course, one that has an onboard NIC. This worked no problems booted straight and created images seamlessly. So more and more I think the problem here is how FOG handles the Onelink+ mini doc.
-
So I found out that the OneLink+ mini dock required a Firmware update. I now get straight through to the boot menu but when I try an inventory it’goes to the bzImage and hangs at 0%.
I have take another dump and forwarded it to Sabastian hopefully now we will see what’s causing the problem.
-
@mandrade In the mean time, if you have custom menu entries it might be worth trying to load for example an ISO and see if that gets any further.
I’ve had a few devices that wouldn’t get far with the downloading of files in PXE, not sure if (and how) I resolved that, though.
Just for clarity sake as well, which binary are you currently using?
Seeing as the NIC is Realtek, it might be worth testing with Realtek.kpxe if you aren’t already.
edit: Also, seeing as it’s a USB NIC, it might be worth checking out the USB settings in BIOS, particularily those related to XHCI handoff and see if that helps any.
-
@mandrade well then it seems simple to me what needs done next. Order a few different adapters for the device. There are some known good models on the foruforums and wiki. I’d order three or four different models and brands. When you find one that works, order as many as you need.
