Kernel update
-
@Sebastian-Roth For a quick test, I’ve put this argument “pci=noacpi” and my fog started… do you still need the result of the “cat /proc/interrupts”?
-
@Pascal-Gazaille If the kernel parameter “pci=noacpi” allows the FOS client (the software that runs on the target to capture and deploy FOG) then you are done. You have the key to making this system deploy correctly. You will have to add this kernel parameter for each 3350 in your fleet. If you setup a Computer Group for these 3350s you can push that setting to all of the registered 3350s that is currently in FOG.
-
@Pascal-Gazaille Well, if this kernel parameter is working for you I think we are done with this. Making it solved. Please let us know if you still see issues.
-
@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#DevicesBut for completeness of the records, what boot file are you using?
-
@Wayne-Workman said in Kernel update:
what boot file are you using?
What do you mean? Wich one? I have theses settings :
FOG_PXE_BOOT_IMAGE init.xz
FOG_TFTP_PXE_KERNEL_32 bzImage32
FOG_PXE_BOOT_IMAGE_32 init_32.xz -
@Pascal-Gazaille Wayne is asking for the iPXE boot file, so
undionly.kpxe
,undionly.kkpxe
,ipxe.pxe
,ipxe.efi
,snponly.efi
… -
@Sebastian-Roth ok thanks, we have undionly.kpxe
-
@Pascal-Gazaille Is this with an external DHCP server? Just for the fun of it, would you want to try UEFI as well? Change from legacy BIOS to UEFI on your DELL Latitude and from undionly.kpxe to ipxe.efi on the DHCP server…
More and more UEFI is coming and it’s good for us to know how well we handle this already.