@Nick Now that you're mentioning 'hpet', I'm pretty sure that's a bios or efi option. Why would my chipset disable it? Because I purchased a gaming motherboard and it screws with games if you overclock anything. Since I don't have an unlocked CPU, nor do I care to break my brand new hardware by messing with voltage and timings, I'm going to enable it. Thanks

@Dave From what I'm reading, the message you are getting is just a warning that the CPU is untested and not supported yet. Your OS should still work if you just ignore this warning. I would still go with a distro with more community support, but I can see how you might like this project as it's simple and clean. Smaller communities just have a smaller test sample to work with. Laby Lake should be fully supported by now though.

I am not sure what issue is being discussed here, but see TSC has been thrown into the mix. I know the choice of clocksourde defaults to tsc, but is can be changed in the boot line to other things such as "hpet" and "acpi_pm"

cat /sys/devices/system/clocksource/clocksource0/available_clocksource

Shows available options. For me it is just tsc, hpet and acpi_pm and I have also heard of "pit".

You can also change it temporarily with:

echo "acpi_pm" > /sys/devices/system/clocksource/clocksource0/current_clocksource

I have also bumped into a further bootcode "hpet=force" but I don't know what it does.

The TSC is the CPU's time stamp counter, which is an internal counter for the CPU. It's possible that patches for Spectre, Meltdown, and other vulnerabilities we've seen on intel CPU's have made their way into newer hardware. I'm on 8th gen, I'm sure you're on a patched version of 7th. It would only be a problem with certain software that uses a CPU counter to track things. Could also be a problem for logging or admin tasks. My main home PC is Fedora 30, my 12tb server and the new software dev box I just built today are centOS. I'm 4th gen xeon with the server, and 7th gen with fedora. Kaby lake also. Fedora works just fine because the kernel is up to date. Only solution I can think of is to compile a newer kernel version, but that's only if you're having issues. It seems to work fine so far, but some of the software I'm going to be using may need this counter. Not sure yet what to do. The i3-8100 is surprisingly good with 4 cores at 3.6ghz, and I like it so far. Just let me know if you find a solution. I've tried to search RHEL docs but I have to have some kind of subscription or own one of their enterprise products. Sorry for the long reply. Hopefully we can point each other towards a solution.

Thanks for responding Phillip. Are you seeing any bad behavior other than the warning message? I've just gotten my copy of RHEL 8 and I don't know if it is affecting my Kaby Lake board because I'm using it somewhere else. I've not seen a single problem back in January other than the message. So if you see something odd, let me know and I'll try to test your scenario on my board.

Sorry that nobody ever responded back to you. I'm having similar issue with 8th gen intel CPU and Centos 7. Both of these OS are based on redhat enterprise. I'm sure there must be a fix somewhere out there. Did you find a solution yet?