FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):"

[lukebarone]

@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!

[lukebarone]

@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.

[Tom Elliott]

@lukebarone I think this proves the point more readily because I have not had any changes between the RC

[Tom Elliott]

And by no changes I’m directly referring to inits and how DHCP is offered

[Tom Elliott]

I wonder if you add ip=dhcp to the global kernel arts

[lukebarone]

@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.

[lukebarone]

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/fog instead of /var/www/fog like 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.

[Wayne Workman]

@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.

[lukebarone]

@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?

[Wayne Workman]

@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_Update

if 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.

[Tom Elliott]

@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.

[lukebarone]

@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.

[adukes40]

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.

[lukebarone]

@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?

[adukes40]

@lukebarone Sorry you are correct. I remember now

I took the 3350’s and grabbed their MAC address from the BIOS and input them in fog manually. Then I assigned them to groups and mass updated them. I did it for 3 carts worth of laptops. Didn’t really take me that long by my self.

Then yes once the 3350’s got the pci=noacpi argument, they ran right through.

[Wayne Workman]

@adukes40 That’s really rough. We need to figure out how to support the keyobard on these Dells in the Linux kernel.

[adukes40]

@Wayne-Workman Only way I could figure out how to do them “easily”. With little time to play with to get them deployed before summer.

[Wayne Workman]

@Tom-Elliott Found this: https://wiki.archlinux.org/index.php/Latitude_E5520

and this:
http://en.community.dell.com/support-forums/laptop/f/3518/t/19593360

[Wayne Workman]

@lukebarone Try to go back to firmware version A8 and see what happens.

[Tom Elliott]

I updated kernels last night with surface keyboard support built in more properly than 4.7.1 had. Would you mind updating fog / reinstalling so you will have the latest kernels? If it doesn’t work we aren’t any better or worse off.