Alright, sorry, I'll try to start over.
There are supposed to be two main ways to get information: directly from the CPU, and via a monitoring chip on the motherboard. Directly from the CPU is borked for now on Linux, as Chuckula said. The monitoring chip is an NCT-something-something (I forgot) using the NCT6775 driver, and it's pretty well-supported. Lm-sensors knows how to handle it, and the only issue that should come up is that it can't read high voltages so a lot of values are rescaled in hardware to fit its inputs and have to be manually scaled back. For instance, you have to double in1 to get the real Vcore.
This NCT chip has inputs for several thermistors as well as what look like a couple of inputs that let it get the temperature as reported by the CPU. None of the latter are hooked up.
The motherboard theoretically has as good fan controls as most modern motherboards (I always configure that in its firmware interface), but it can't control them on information it doesn't have. It's operating on the data provided by this same monitoring chip. Not only is this terrible data in general, but it turns what were previously very nice fan control features into misfeatures that may make the CPU throttle in situations where it has no business needing to throttle.
Here's the thermal monitoring both the mobo and I have to work with:
Motherboard: +117.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor
CPU: +32.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
Auxillary: +37.5°C sensor = thermistor
VRM: +108.0°C sensor = thermistor
AUXTIN2: +107.0°C sensor = thermistor
CPU (PECI): -128.0°C sensor = thermistor
The two that look reasonably scaled are the only two that ever change. 32C is a very low idle, and it gets maybe as high as 52C under prime95. If put under prime95 from 32C, it may take 30 seconds getting to 43C. I know how I want my fans to behave, and I can't make it happen on data that shoddy.