- #Amd system monitor doesnt show temps how to
- #Amd system monitor doesnt show temps drivers
- #Amd system monitor doesnt show temps Patch
- #Amd system monitor doesnt show temps code
- #Amd system monitor doesnt show temps download
Thank you very much for you guide!! I will try it. > about it, so that I don't repeat this mistake in the future. > And if this is not the place for such explanations, please, someone write me > This may not be the most proper way to do it, but it works for me. > This fix is simple enough, but I have to repeat all this with some Plasma > 5) After that, just restart System Monitor and all sensors should appear in > path is used by me, I am not sure that it is the same on all distributions) > must be copied with a replacement to /usr/lib/qt/plugins/ksystemstats/ (this > 4) File ksystemstats_plugin_lmsensors.so will appear in the folder. > 3) In the root folder of the project run: plugins/lmsensors/lmsensors.cpp (comment or remove some lines).
#Amd system monitor doesnt show temps Patch
> 2) Automatically or manually apply the patch from comment #33 to the file
#Amd system monitor doesnt show temps download
> download its contents to your computer. > 1) You need to open the required branch of ksystemstats (in your case This may not be the most proper way to do it, but it works for me.Īnd if this is not the place for such explanations, please, someone write me about it, so that I don't repeat this mistake in the future. This fix is simple enough, but I have to repeat all this with some Plasma updates, which is a bit depressing.
bin, it must be copied with a replacement to /usr/lib/qt/plugins/ksystemstats/ (this path is used by me, I am not sure that it is the same on all distributions) (you can backup old file).ĥ) After that, just restart System Monitor and all sensors should appear in the "Hardware sensors" category. plugins/lmsensors/lmsensors.cpp (comment or remove some lines).ģ) In the root folder of the project run:Ĥ) File ksystemstats_plugin_lmsensors.so will appear in the folder. > (I don't have AMD sensors on my laptop, intel and nvidia) KDE Neon 5.23.5ġ) You need to open the required branch of ksystemstats (in your case Plasma/5.23: ), download its contents to your computer.Ģ) Automatically or manually apply the patch from comment #33 to the file.
#Amd system monitor doesnt show temps how to
> Hi! how do you solve it? sorry for this, but I don't know how to remove the > Thank you, this workaround will help me wait for the official fix in greater I am ashamed that I could not find it myself.
#Amd system monitor doesnt show temps code
> there is a simple blacklist in ksystemstats code > (In reply to Maciej Stanczew from comment #33) Don't look to macOS or Windows as if the grass was greener there, just because it's more polished. And sometimes that choice changes when beginners become experts. * There's a reason why people choose a particular OS and desktop environment. Doing it at the application layer is conceptually wrong (but of course still a nice-to-have option, especially when the layers below leave something to be desired). That's the layer were cleanup should happen.
* There's the kernel, lm_sensors, and systemd-sensorsd suddenly popping up wouldn't surprise me. Any attempt to properly clean up a raw list of sensors is futile. * This is not macOS running exclusively on a limited, well-known set of Apple hardware. Any processing that helps to better dig through and display that information is a nice-to-have option, but should only be that - an option.
KSysGuard and KDE System Monitor are system utilities, and as such should first and foremost display system information as it is.
#Amd system monitor doesnt show temps drivers
That way users could use sensors from CPU/GPU plugins for basic temperature/frequency/usage monitoring, while more demanding users could get all the data that the drivers provide. Is there any harm in having those sensors duplicated? Personally I think that CPU/GPU plugins could expose a vendor-neutral, standardized set of sensors, while Hardware Sensors could still expose raw, driver-specific sensor data. > The cause of the problem is, that in the new sensors plugin coretemp, k10temp and amdgpu are intentionally excluded to not expose duplicated sensors because these are already handles by the CPU and GPU plugins. (Also, k10temp only provides package temperatures, so it's a bit unintuitive when the CPU plugin splits it per-core, with all cores reporting the same temperature.)Īmdgpu: This I think is the most clear, we're missing edge/junction/memory temperatures, fan speed, power, and voltage, and they are not available in any other way. K10temp: Ryzen CPUs have a peculiar way of reporting Tctl (search "Ryzen sawtooth"), and because of that I'd like to also monitor Tccd1 (which behaves much more reasonably). My usecases for all of the filtered drivers:Ĭoretemp: Similarly to what Artem mentioned, I'm interested in package temperature, not per-core temperatures.
0 kommentar(er)
