-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Artwork
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login



Sponsoring


-
- Content .- Fans (1) .- Knowledge Base  . 

pyCatalystMonitor

   1.1  

Plasmoid Script

Score 61%
pyCatalystMonitor
zoom


Minimum required   KDE 4.x
Downloads:  314
Submitted:  Dec 10 2013
Updated:  May 17 2014

Description:

This is an updated version of Ryan Ho's AtiMonitor script. It's compatible with current KDE releases, and updated with a fanspeed monitor.




Changelog:

1.0 - modern KDE compatible.
1.1 - fanspeed monitor added (thanks BubuFearn!)




LicenseGPL
Send to a friend
Subscribe
Other  Artwork  from Kepsz
Report inappropriate content



goto page: prev   1  2 

-
.

 GitHub repo?

 
 by BubuFearn on: May 17 2014
 
Score 50%

I couldn't find a repo..

Would be cool if it has/had one :)


Reply to this

-
.

 Great work!

 
 by BubuFearn on: May 18 2014
 
Score 50%

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 :)


Reply to this

-
.

 Works GREAT thank you!

 
 by BubuFearn on: May 18 2014
 
Score 50%

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 :)


Reply to this

-

 Re: Works GREAT thank you!

 
 by Kepsz on: May 18 2014
 
Score 50%

I'm glay you are happy :)

Currently I'm thinking about the display of vram usage, but i can't find any means to do this. Catalyst can't supply this information by itself and withouth catalyst, it may be impossible to do.


If you have an idea about this... :)


Reply to this

-

 Re: Re: Works GREAT thank you!

 
 by BubuFearn on: May 18 2014
 
Score 50%

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!


Reply to this

-

 Re: Re: Works GREAT thank you!

 
 by BubuFearn on: May 18 2014
 
Score 50%

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.


Reply to this

-
.

 Re: Re: Re: Works GREAT thank you!

 
 by BubuFearn on: May 18 2014
 
Score 50%

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


Reply to this

-

 Re: Re: Re: Re: Works GREAT thank you!

 
 by Kepsz on: May 18 2014
 
Score 50%

Well, lspci reads some "directly mapped to cpu" vram, that's why it is display 256MB. So it's correct, just not usefull to us.
But total vram can be questioned from other sources like xorg.

There may be a way for getting dynamic usage with c code, but it's not tested yet.


Reply to this

-

 Re: Re: Re: Re: Re: Works GREAT thank you!

 
 by BubuFearn on: May 18 2014
 
Score 50%

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 :)


Reply to this

goto page: prev   1  2 

Add commentBack






-

-
How do you like Plasma 5?
 The best KDE Desktop ever.
 Definitely a nice improvement.
 Not decided yet. Haven't tried it yet.
 I do not like some of the changes.
 KDE is taking the wrong way.
 I am still sticking with KDE 3.5.
 I have no opinion, but wanted to vote anyway.

resultmore




 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Artwork
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
News RSS   
Discussion RSS   
Events RSS   

Participate
Groups
Forum
Add Artwork
Public API
About KDE-Look.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2001-2014 KDE-Look.org Team  
All rights reserved. KDE-Look.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.