Unable to register hosts

[Wayne Workman]

@Sebastian-Roth Where would it best fit? Troubleshoot downloading ? Troubleshoot Registration ? Troubleshoot upload ? Maybe just an article about helpful kernel arguments?

[Matthieu Jacquart]

@Sebastian-Roth ARgh, I began to search before opening thread but didn’t find this one…
Thanks Seb, I’ll try it tomorrow !

[Sebastian Roth]

@Wayne-Workman said:

Where would it best fit? Troubleshoot downloading ? Troubleshoot Registration ? Troubleshoot upload ? Maybe just an article about helpful kernel arguments?

I thought about simply adding this machine to our “known working hardware” list including the kernel parameter in the comments.

[Matthieu Jacquart]

@Sebastian-Roth I’ve just read the topic, it’s a semi good news because… We have to entered manually our 40 hosts into fog interface before putting kernel parameter to the host ??? what a mess.
But once it’s done, we will be tranquil

EDIT : bad news, it seems not working…
If I put pci=noacpi in Host Kernel Arguments, no change, same error message.
If I put pci=noacpi in Host Kernel, I’ve got this error :

I use undionly.kpxe

[Sebastian Roth]

@Wayne-Workman Nevermind, I just saw that you added the 3350 latitude including the kernel parameter back when we figured this out.

@Matthieu-Jacquart You could import the 40 hosts via CSV but seems like we need to figure this ugly hardware issue out before. Definitely needs to be in “Host Kernel Arguments” not “Host Kernel”! Are you absolutely sure you had it set in Host Kernel Arguments when testing with one of your machines - set in the correct one? Have you read through the whole story I posted the link to?
You can try other kernel parameters like acpi=off or pci=routeirq (described here).

[Tom Elliott]

@Matthieu-Jacquart Host Kernel (no arugments) is the kernel file. The message you see below is because it’s looking for a file named pci=noacpi

[Matthieu Jacquart]

@Sebastian-Roth Hi, So I have imported my 40 hosts with csv file after looking for mac adress on each bios, but indeed even with pci=noacpi in host kernel arguments there no difference.
I’ll try other arguments on monday ! Have a nice weekzend

[Wayne Workman]

@Sebastian-Roth said in Unable to register hosts:

Nevermind, I just saw that you added the 3350 latitude including the kernel parameter back when we figured this out.

LOL, I did?

[Sebastian Roth]

@Wayne-Workman said in Kernel update:

@Pascal-Gazaille I’ve updated our working hardware list with this model and the kernel argument.
https://wiki.fogproject.org/wiki/index.php?title=WorkingDevices#Devices

[Matthieu Jacquart]

@Sebastian-Roth So, tested the Four arguments in Host Kernel arguments, tested on 2 laptop :

• noapic
• pci=routeirq
• pci=noacpi
• acpi=off

And each time, same error, as if there was no argument… depressed !

EDIT : ok it works ! For testing I always selected in fog menu “client system information” (because my image is not ready to deploy so I didn’t test quick image or task deployment) and it gave me the same error. BUT if I test to deploy an image (never mind for non ready image…), everything seems fine ! We can close this topic, I confirm that Dell Latitude 3350 work with pci=noacpi host kernel argument

[Sebastian Roth]

@Matthieu-Jacquart Good to hear that you found why it wasn’t working with the host kernel parameter set!

@Tom-Elliott Should we add the host kernel parameters to the “client system information” as well?

[Tom Elliott]

@Sebastian-Roth for unregistered hosts you would setup the args under global settings kernelArgs

[Wayne Workman]

@Tom-Elliott You think it might be good to allow an edit-able drop down list for kernel arguments? Something like this? http://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_datalist

[Wayne Workman]

Following up on this topic with new news.

I was just told about issues with imaging a Latitude 3350. Currently we’re on FOG 1.3.0 RC-18 and using kernel 4.8.1.

I’ve added the kernel arguments pci=noacpi into this spot here:
Web Interface -> FOG Configuration -> FOG Settings -> General Settings -> FOG_KERNEL_ARGS in order for the issue to just go away for any system that may have the problem.

This worked, but the keyboard on the Dell Latitude 3350 would not work. We worked around this by attaching a USB keyboard.