FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):"
-
@lukebarone Could you please boot up a live linux CD/DVD and run the following commands to get the exact model of your ethernet chip:
lspci -nn | grep EthernetOr boot windows, go to driver manager and find out the PCI IDs there. Otherwise it’s just a lot of useless research and guesswork to find out what NIC is build into your devices.
-
@Sebastian-Roth said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
Or boot windows, go to driver manager and find out the PCI IDs there. Otherwise it’s just a lot of useless research and guesswork to find out what NIC is build into your devices.
Vendor 14E4, Device ID 1681.
@Tom-Elliott said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
I’m now thinking the primary issue with DHCP is because of firmware. I’m guessing the tg3 fw is not available on first boot until after the error message displays. So the system doesn’t have a mapping capability to look for the nic. On a warm boot however, it’s already been uploaded to the nic. So the system can now map it as expected, which might explain why quick reg worked.
Can you remove the host from fog and let it boot into wibdows and shutdown to see if a cold boot->quick reg still works or gives the same error?The host was never registered, and the hard drives switched out with SSDs. I’ve even tried with removing the battery and AC adapter for 5 minutes, and trying it again. Quick Reg works, Full Reg does not.
-
@lukebarone so both times you could started for quick and for full?
-
And the quick reg working is actually creating the entries?
-
@Tom-Elliott No, I could only get it to work by Quick Registering first. If I choose Full, then I get the issue shown above in the question.
After choosing Quick, I log in to the Web UI, rename the system, assign an image and tell it to join AD. Then, I can deploy the image on the next boot. -
Just for the records. This is a Broadcom NetXtreme BCM5761 Gigabit Ethernet PCIe chip. Other people had issues with those as well.
Are you able to boot into a linux live CD and have ethernet setup properly???
-
@Sebastian-Roth said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
Are you able to boot into a linux live CD and have ethernet setup properly???
Yes, I can use the NetInst ISO for Debian Jessie (8.1), and ping my machines and download web pages. Hope that helps!
-
@Sebastian-Roth So I also just tried the new version from Git (1.3.0 RC-10), and the Dell 3350’s will register OK, but I get the same error message during the image deployment. It boots to the network, downloads the bzImage and init.xz, then the same data as posted earlier. These laptops are using a Realtek driver, but I could NetBoot them and register.
-
@lukebarone I think this proves the point more readily because I have not had any changes between the RC
-
And by no changes I’m directly referring to inits and how DHCP is offered
-
I wonder if you add
ip=dhcpto the global kernel arts -
@Tom-Elliott said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
I wonder if you add ip=dhcp to the global kernel arts
No change. Same error message. I added that line to one host, as I don’t know where to apply it to every host.
-
This issue has been fixed!
Upgrading from RC-8 to RC-9 to RC-10, somewhere in there, it started putting files in
/var/www/html/foginstead of/var/www/foglike the rest of the installation. After switching the TFPTBOOT directory to/var/www/html/fog/service/ipxe, and downloading the 4.1.0 kernel, these Dell e3350’s would boot to the Deploy job. Next up, figuring out why the keyboard won’t work and I need to plug a USB one in.Thanks for the help though, it was quite helpful.
-
@lukebarone said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
Next up, figuring out why the keyboard won’t work and I need to plug a USB one in.
That’s likely kernel related.
-
@Wayne-Workman said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
That’s likely kernel related.
While only semi related - how can I find a kernel that works with all my hardware? Is experimentation my only way?
-
@lukebarone You don’t have to find one, you can always build one as a last resort, or if you’re just into that sort of thing.
This wiki article might help you out:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_Updateif a full linux kernel, like something that is in Ubuntu 16 live, works with the keyboard, then it’s just a matter of figuring out which kernel build parameter that enables it, and asking the devs to include that in the next fog kernel.
-
@lukebarone has the keyboard on the laptop worked in the past with registering a host? What kind of keyboard is it? Does it detach or just isn’t recognizes? If you’re doing a tasking and unable to use the keyboard, this is normal.
-
@Tom-Elliott said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
@lukebarone has the keyboard on the laptop worked in the past with registering a host? What kind of keyboard is it? Does it detach or just isn’t recognizes? If you’re doing a tasking and unable to use the keyboard, this is normal.
Hi Tom,
It’s the built-in keyboard on the laptop of the Dell e3350. Plug in a USB keyboard, and it works fine. I’m thinking that Dell is just doing weird things to get everyone on to Windows 10 and their custom installs of it. The keyboard works in the menu, and logging in to FOG’s PXE boot menu. Once I select a task (i.e. Full Host Registration), it stops working. Plug in the keyboard, and I can type in the hostname and other options.
-
For our 3350’s you have to set
Host Kernel Arguments pci=noacpi
for each host. (maybe needs to be for 5520s as well??) We do not have any here, so I don’t know.
But I created a group, registered them all to the group, and mass updated all the host arguments.
-
@adukes40 said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
For our 3350’s you have to set
Host Kernel Arguments pci=noacpi
for each host. (maybe needs to be for 5520s as well??) We do not have any here, so I don’t know.
But I created a group, registered them all to the group, and mass updated all the host arguments.I think I may create a new post for this, but… How do I get them registered if I can’t type with the keyboards initially? Dell doesn’t send the MAC addresses in their packing slips. Once they’re registered, I can certainly do that (and I see no reason NOT to), but it is still not going to work initially, right?
