Image 01
profile-image

BubuFearn

Bubu Fearn
plasma Simple System Monitor

Plasma 4 Extensions by dhabyx 35 comments

OK,

Finaly managed to spot the 1 pixel sized comment button on Github!

Sorry about that, have replied to your comments there now. - May 27 2014
plasma Simple System Monitor

Plasma 4 Extensions by dhabyx 35 comments

Hi!

I only started using Git a few days ago and somehow lost the comments you made after viewing them once. I have no idea how to get them back. Or how to reply to them if I did, so please accept my appologies for replying here rather than directly on Github. I am working hard to imprpve.

In answer to your question on the akt0110-acpi-0 sensors.
Yes there is only a 0 there is no 1,2 or 3.

The problm is that whilst ASUS is a very popular board for AMD processors there maybe other users with different boards.

If that becomes a headache for you to support, I completely understand and would have no problem maintaining my own custom version.

Of course if you can include my use case into the main code without too many problems that would be fantastic!

I don't know if you have a Bitcoin/Litecoin/Dogecoin/Paypal address, but if you do I'd like to make a small donation as way of thanks for all your hard work so far. - May 27 2014
plasma Simple System Monitor

Plasma 4 Extensions by dhabyx 35 comments

I posted a picture of my desktop here:

http://i58.tinypic.com/2vj7477.jpg

If you look closely you can see where I modified coreTemp slightly.

What I'd really like to do is put some of the other sensors I found below "CPU Temp", because as you can see it looks a bit lonely on the left there.

Anyway check out my fork and let me know if it would be too much hassel to customise it.
- May 23 2014
plasma Simple System Monitor

Plasma 4 Extensions by dhabyx 35 comments

Hi dhabyx!

Please excuse the wall of text, but I've been really busy with your code and wanted to give you some feedback on how I'm doing.

I managed to modify your code to get it to work for my use case, but ended up introducing a weird bug I think is caused by either/both coreTempModel and monitorActions not liking something I've done...

Some background on my use case.

Processor is an AMD Phenom II x6
Motherboard is an ASUS M5A78L-M

The processor has one sensor (k10temp-pci-00c3 temp1) for all 6 cores but it is not a "true" temperature...
As an example right now my motherboard temperature is 30c and yet k10temp reads only 24.5c (note that its a float)

This is because k10temp is a "relative" to "max" temperature used by AMD to tell the processor when to apply extra cooling and not as a reliable guide as to what the "actual" core temperature is.

There are two solutions to this problem:

You could write a formula to convert the relative temperature into an actual core temperature, but the problem with this is that as the temperature changes (and gets lower) the formula you use becomes more inaccurate because its an arbitrary scale and not an actual temperature reading.

The second solution seems to me to be the most sensible for my use case and that is to simply use the motherboards sensors chip which gives us an accurate enough CPU temperature with the added bonus of a few other sensors such as CPU and chasis speeds as well as some voltage stats.

Using plasmaengine explorer I've been able to connect to these sensors and pull data from them.

$ sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.34 V (min = +0.80 V, max = +1.60 V)
+3.3V Voltage: +3.27 V (min = +2.97 V, max = +3.63 V)
+5V Voltage: +5.01 V (min = +4.50 V, max = +5.50 V)
+12V Voltage: +12.11 V (min = +10.20 V, max = +13.80 V)
CPU Fan Speed: 1638 RPM (min = 600 RPM, max = 7200 RPM)
Chassis Fan Speed: 1896 RPM (min = 600 RPM, max = 7200 RPM)
CPU Temperature: +41.0°C (high = +60.0°C, crit = +95.0°C)
MB Temperature: +30.0°C (high = +45.0°C, crit = +75.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1: +24.5°C (high = +70.0°C)
(crit = +83.5°C, hyst = +78.5°C)

As you can see k10temp has weird readings, the high crit and hyst are basicaly thresholds that temp1 uses to control fanspeed, and temp1 itself is of no real value to us as an actual reading of true temperature.

The motherboard's sensors (atk0110-acpi-0) seesm much more useful to us and that's what I successfully changed in the code, replacing the original k10temp lines with the new sensors on atk0110-acpi-0.

I also had to change text: 'Core '+model.index+':' to text: 'CPU Temp:' in CoreTempList because I don't have a per core sensor. Somehow this has caused CpuWidget to freak out here:

plasma-simpleMonitor/contents/code/monitorWidgets/CpuWidget.qml:20: Unable to assign QObject* to QDeclarativeComponent*

I think this has caused some issues, I've had a problem with the logo changing back to Tux after logout even when the changes are applied and saved, after logout for some reason it won't apply changes. (Possibly I didn't package the plugin correctly before installing it)

Although the CPU Temp is now correct, when I tried to add an extra sensor (a Motherboard Temp using a modifed coreTempModel I had issues anchoring it nicely below CPU Temp, I suspect this is because I have invisible coreTemps being generated by coreTempModel and generating white space.

I've created a fork on github so you can have a look at the mess I made of your code :P
I have a good idea of what I want to achieve but my JavaScript knowledge is letting me down, so please forget any obvious code mistakes.

Here:

https://github.com/Bubu-Fearn/plasma-simpleMonitor - May 23 2014
plasma Simple System Monitor

Plasma 4 Extensions by dhabyx 35 comments

From what I can see, the code doesn't pipe the command to lmsensors it pulls it from a plasma data engine source, so I imagine he will need to do the conversion on the fly or possibly modify the datasource, which I imagine would be more dificult.
It is probably lmsensors doing a conversion on the fly that gives you degrees F.
If you install plasmate and run plasmaengineexplorer you'll be able to see what he has to work with :)
Having said that I know with Python we can pipe commands to a terminal by calling 'popen' and then use regular expressions to find any data we want.
I'm not sure if this is possible with JavaScript? - May 23 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

Yeah I see what you mean about lspci.

I found this quote from a guy on an overclocking forum which explains the problem better than I can.

Source: http://www.techpowerup.com/forums/threads/hmm-ati-hd5xxx-memory-usage-monitor-not-possible.127140/
-----------------------
cadaveca
"Data in mem is "in flight" and as such, is not "actively" stored in mem. It requires the use of debugging tools(GPUPerfMonitor et al./virtualiztion of the app, sometimes), or custom code to find out how much is actually being used( for example, GTA4 bench will tell you % of memory was used).

Also, you must be sure to not be querying the local store, which is just 32k.

There basically is not one large 1GB data share on 1GB AMD cards. It's literally broken up into 4x256MB groupings(as the memory controller is not 256-bit, but 4x64 bit, but as they all run in tandem, it's considered 256-bit overall), making proper monitoring even more difficult. 4x data stores means it's very possible that monitoring calls may stall an app, leading to crashes. "
---------------

So according to cadaveca it seems that just by monitoring we *might* cause some applications to stall and crash.

I'm waaay out of my depth on this one :) - May 18 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

As for getting a dynamic update of vram in use, I'm still working on it :) - May 18 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

OK I have a solution.

But it may not be totaly reliable as it involves greping the Xorg.0.log file, which might be unreliable for some people...:

grep -i 'Video ram' Xorg.0.log

Returns:

[ 20.182] (--) fglrx(0): Video RAM: 1048576 kByte, Type: GDDR5

So as long as they log it. We can use it.
Give it a try on your system and let me know if you think its a reliable enough method for us to use. - May 18 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

So far I've found nothing in aticonfig can do that will help us display vram, so this one will be a little tricky!

However!
We can query the info we need with:

lspci -v | grep VGA -A12

However on my system it reports:

Memory at d0000000 (64-bit, prefetchable) [size=256M]

So either I got ripped off by ASUS and they sold be a 256M card badged as a 1GB card, or lspci is misreading the info. (Probably I have 4x blocks of 256)

I will keep digging, I'm sure there is a way to do this. The 14.10 driver from their website using catalyst control centre displays it, along with the type, clock and bandwidth, so there *is* a way and they use it.
We just need to work how!
- May 18 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

As I'm overclocking my card I really needed to make sure the fan was operating at an appropriate speed.

Now I have a really nice visual indication of exacty what the gfx card is doing all the time.

I can't thank you enough :) - May 17 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

Just finished rebuilding my system.

Just about to install your new version now, and will let you know how it goes.

Well done for turning out some new code so fast :) - May 17 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

I couldn't find a repo..

Would be cool if it has/had one :) - May 17 2014
Modern KDM Archlinux

KDM4 Themes by xiorone 3 comments

This theme alone has tempted me to install Arch.

Unless of course I could persuade you to do a Kubuntu version? :P - May 16 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

I'm a bit of a Python noob/learner but if I can find an IDE that works I'll try and help as much as possible!
I've been using plasmate and it's preview is pretty buggy with python, so I will try kdevelop and see how that goes.

I'm a bit stuck with how to pipe the

aticonfig --pplib-cmd 'get fanspeed 0'

command via Popen on line 172 and add it to the list in order to populate a chart.

This is probably just a combination of my poor syntax escaping the quote marks 'get fanspeed 0' and/or plasmate just failing to reload the code in the preview window correctly each time I make a change.

If I can work out how the original code loops through each iteration of aticonfig and then parses the results it should then be fairly simple to add a --pplib-cmd iteration that we can use in an additional chart, either above or below the GPU Temp area.

Additionaly aticonfig --pplib-cmd can be used to set values i.e core clock speed at low,mid,high and the fan speed itself programaticaly.

I belive

http://sourceforge.net/projects/amdovdrvctrl/

uses this method to dynamicaly adjust the fan speed and clocks depending on how you config it.

It would be *nice/wish* to add some of these features in future versions, so there is at least one plasmoid out there which can both display and adjust/overclock settings in catalyst on the fly. - May 16 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

Yep it does :)

aticonfig --pplib-cmd 'get fanspeed 0'

Fan speed query:
Query Index: 0, Speed in percent
Result: Fan Speed: 41%

I've tried poking around with the code. I think I need to modify the getresult and updateTime functions. The fanspeed is reported as a percentage so I imagine the chart code there will be similar to the GPU Load one and I can re-use it for the fan? - May 16 2014
pyCatalystMonitor

Plasma 4 Extensions by Kepsz 29 comments

Hi,

A few questions please.

Is there any sign of the original author yet?
If he comes back do you plan to merge?
I'd like to add a reading for the fan also, is this possible/difficult?

Thanks for helping to make my desktop rock! - May 15 2014
plasma Simple System Monitor

Plasma 4 Extensions by dhabyx 35 comments

I think I found my problem. :)

http://yeupou.wordpress.com/2012/02/18/getting-accurate-temperature-reading-for-the-cpu/


- May 12 2014
plasma Simple System Monitor

Plasma 4 Extensions by dhabyx 35 comments

Thank you so much for coming back to me so quickly!

I installed Plasmate as you suggested (excellent tool) and I think I've found the entries you were talking about.

Have taken a screenshot.

http://i57.tinypic.com/sqo6yw.png

I think line 147 is pulling the temprature data from:

lmsensors/k10temp-pci-00c3/temp1

And I think the sensor it should be is called:

lmsensors/atk0110-acpi-0/CPU_Temperature

I'm not really confident enough to edit the code myself yet, as I'm not familiar with the syntax and escape chars.

On a side note..
I did notice some really tasty sensors in there such as lmsensors/atk0110-acpi-0/CPU_Fan_Speed which would be really handy!

How difficult would it be to add some custom sensors to the list such as fan speeds etc? I assume I'd need to create the sensor in main.qml and then reference it somewhere in a UI file? - May 12 2014
plasma Simple System Monitor

Plasma 4 Extensions by dhabyx 35 comments

Really love the look of this plasmoid on my desktop just 1 thing doesn't work, CPU temp shows 0 degrees.

I think its grabbing the temp from a wrong sensor that isn't used on my board (PCI 0 I think).

I think the code is doing something like:

sensors | grep temp

And gets back:

temp1: +0.0°C (high = +70.0°C)

which is obviously a sensor that is not used.


If I do:

sensors | grep 'CPU Temperature'

I get:

CPU Temperature: +32.0°C (high = +60.0°C, crit = +95.0°C)

Is there something I need to modify in main.qml to get this working on my boxen?
- May 11 2014
bneko

Plasma 4 Extensions
by ibuscher

7 .7
May 22 2014
Modern KDE 4 Splash Screen

KDE 4 Splashscreens
by xiorone

8 .3
May 16 2014
7 .2
May 16 2014
pyCatalystMonitor

Plasma 4 Extensions
by Kepsz

7 .0
May 15 2014
plasma Simple System Monitor

Plasma 4 Extensions
by dhabyx

7 .3
May 11 2014
Modern KDE 4 Splash Screen

KDE 4 Splashscreens
by xiorone

8 .3
9   May 16 2014
7 .2
9   May 16 2014
pyCatalystMonitor

Plasma 4 Extensions
by Kepsz

7 .0
9   May 15 2014
plasma Simple System Monitor

Plasma 4 Extensions
by dhabyx

7 .3
9   May 11 2014