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

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

[lukebarone]

@Tom-Elliott I updated to RC-11 with git. Ran the install, was using Kernel 4.7.3. Same issues as before. Switched back to 4.1.0 (another tech in the school district ran into the problem), and the systems are imaging. I’m still using the USB keyboard, as the built-in laptop keyboard is not working for registering.

If it helps any, the BIOS version is A06 out of the box. I’ve tried with A08 (the newest), and no change.

[george1421]

@Wirefall [Moderator note:] I’ve forked this users post since the issue is similar to the OP of this thread, but deals with a different version of FOG. You can find your post here: https://forums.fogproject.org/topic/9201/fog-will-not-boot-failed-to-get-an-ip-via-dhcp