Exposing/Reading More Hardware Sensors

[DigitalCorpus]

I'm still trying to get into the weeds on my new home server build. In particular, I'm jealous that Windows has HWInfo(64) that exposes *dozens* of values out to the user whereas linux I only get about 30 and more I have to reverse engineer their appropriate values. The latter I don't have much of an issue with, but there is a level of ignorance that generates obfuscation I'm looking for help to get around.

CPU: Intel i5-8500T
Motherboard: ASRock Z390 Phantom Gaming ITX/AC
Storage: Samsung 960 EVO + Samsung 5 TB 2.5" HDD + MX500

LM-Sensors parses what the hwmon outputs to /sys for coretemp and the NCT6791D. While poking around with FWTS, I noted the MAX34407 hanging out on the I2C buss aside from ~130 in /sys/bus/scpi/devices with explicit names.

How do I go about poking at them to identify and read them? Have I missed an off-shoot utility that is expressly verbose as HWInfo on Windows?

[wrc1944]

I've always liked http://gkrellm.srcbox.net/

Highly configurable with whatever you wish to show. I keep it open in a little small 3/4" verticlal display along the right side of the desktop.
Mine has all 16 Ryzen cpu threads, temps, fans, eth0, disk usage, and processes, but there are many more items available.

I run it without lm-sensors- works great, usually configured properly right out of the box.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.40-r5, gcc-14
kernel-6.12.8 USE=experimental python3_12.7-final-0

[Ant P.]

Most I2C sensor labels are guesswork and, as you've noticed, the quality of that varies wildly by who's doing it. There's not much anyone can do about that besides put more effort into it and compare notes.

Do you get any dmesg lines about ACPI resource conflicts? That may be hiding one of the chips from hwmon, it used to be a common problem.

[DigitalCorpus]

No conflicts, but I think I'm missing one or two options in my kernel config. It's difficult to guess because the live images via CD/USB don't always get all of the hardware. FWTS didn't have any issues and compared to the computer it is replacing, it's output is a massive vomit that takes a while to step through.

Thanks for another recommendation of gkrellm, though I need to see if it'll do cli output. I'm primarily running this as a headless box, though.

If I use a closed source example like HWInfo64, are there any suggestions at cross referencing or pulling info out of that to apply to the Linux setup?