Ok, looks like in Windows this fancy operating system will automatically re-configure itself when I restart and enable, disable, and load it's own drivers for pretty much any BIOS setting I do. I've been spoiled by that, and was expecting Ubuntu server 16 to do the same thing. It does not. I spent the last week trying to learn and do tests, getting really confused. There is an AHCI driver that loads or a P-STATE driver (or module) that loads when I install an Ubuntu 16 operating system. If I CHANGE my bios setting or GRUB, than the modules or drivers (or whatever needs to be done) is still set to however it was originally loaded when I installed the operating system. The TURBO cpu frequencies are also changed if I switch bios settings, since if I reduce the # of active cores, the maximum CPU frequency should change. I can't seem to trigger Linux to recognize I changed my bios settings and re-load the appropriate modules it needs to use. I can't manage all this manually, and now have resorted to having to re-load my operating system from scratch every time I change a bios setting just to run another test. Does anyone have advice on how I can do this easier ? Is there a procedure somewhere to trigger linux to rebuild it's own kernel, detect the CPU bios settings from the begninning again without me having to reload the operating system from scratch for each bios setting change?