The best way to avoid this problem is to understand how your BIOS is setup to boot.
Often newer machines will default to U(EFI) which is different than the traditional MBR/Legacy mode.
The problem is that this may not be apparent, often a BIOS Boot Menu will show a Legacy Boot Option and EFIOption without defining it.
A good example of this is if your USB is called "Kingston" you may see in your Boot Menu "Kingston" and also "Ubuntu"........
It looks like this has something to do with APIC but I am not sure. I have similar CPUs with a different MB and BIOS that work fine on the same type of kernel. A lot of time the issue is because of the C-step setting in the BIOS.
The same thing happened on the 2.6 kernel with Centos 6 but this is a homebrew 4.4 kernel soI am not sure why it is happening when even Centos 7 (3.2) kernel works OK.
Solution - It comes down to the BIOS set........
tftp: client does not accept options
I spent the good portion of a late evening on this double checking settings that I know always worked right for tftp!
This error can also happen if you are trying to boot PXE in UEFImode. Enter your BIOS and change it to "Legacy PXE" or non-UEFI PXE mode and you'll be good to go!........
Done on Centos 7.3 very important as clearly based on older guides it was a lot easier and more simpler! Hint do not use grub2-install!
If you have trouble booting after this check this CentOS mdadm RAID booting/fixing guide.
One huge caveat if you are an oldschool user or sysadmin who has avoided UEFIbooting
The nor........
Download from here http://www.avagotech.com/products/server-storage/host-bus-adapters/sas-9200-8e#downloads
sudo Installer_P20_for_Linux/sas2flash_linux_i686_x86-64_rel/sas2flash -listall
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved
&nbs........