- Annoyance
Ive been bothering the Htop people for a bit now and i still think this is an issue with htop, to a certain degree as btop works fine and older htop version works to 50%, the sensors work fine too, although it could be a package that was updated but im only 1 person with 2 intel machines.
On the 2 systems ive tested it on, htop displayed the issue differently.
My actual unraid server displays NA temperature readings, while my PC will display bogus temperature infos for all cores.
Thats being said, within certain containers, htop is actually able to read the temperature correctly with the same version as unraid ships.
The odd part is, it started being broken with kernel 6.12.40 (beta.1) also at the same time, the thor kernel 6.16 showed this behavior.
Then came i think beta.2 with kernel 6.12.42, which actually fixed the issue and it worked as intended.(for thors 6.16.1, it was working again as well, last time i checked that kernel out)
So that led me to think it was just an issue with the kernel itself.
Then came Kernel 6.12.47(could have reappeared earlier but i wouldnt know) which absolutely broke it again and is still broken until now (6.12.53). But given that i can get proper readings from within containers, makes me believe it must be something else.
6.12.40 - Htop 3.4.1 i3-14100
6.12.40 - Htop 3.3.0 i3-14100
6.12.47 - Htop 3.4.1 i5-14600k
*bogus readouts as they all just read the same sensor of coretemp
6.12.53 - Htop 3.4.1 i3-14100
6.12.53 - Htop 3.4.1 i3-14100 inside Container
*the only way to get a proper and correct read out
6.12.53 - Btop 1.4.5 i3-14100
In all versions sensors hands out information correctly.
Would be handy we could get more eyes on and figure out what the hell is happening.
I attach the compiled version of btop btop-1.4.5-x86_64-1_Unraid.txz