jemino

Jean-Michel Nourrit , France

Hi, I am jemino and I create Plasma 4 Widgets and QtCurve.

Statistics

3 Products

33 Comments

Plinged 0 Products

Got 0

Has 0 Affiliates

Fan of 0 Products

Got 8 Fan-Likes

Last time active : Jan 25 2014

Joined : May 15 2010

Plasma 4 Widgets

Radeon Power Management

Plasma 4 Widgets Jun 20 2012

Score 86.9%

Panel maximizer

Plasma 4 Widgets May 15 2010

Score 50.0%

QtCurve

CD-dark (QtCurve)

QtCurve Mar 02 2011

Score 66.7%

Radeon Power Management

Plasma 4 Widgets 71 comments

by jemino

Score 86.9%

Jun 20 2012

Glad it works. I just updated the plasmoid description. - May 25 2013

After a bit googling, I found out that Opensuse has another file that's executed on each boot, though it's executed much earlier in the boot sequence than rc.local. Still, you could try putting the commands in there :

/etc/init.d/boot.local
- May 25 2013

Hi,

Did you put those two commands in /etc/rc.local (so that they're executed each time the machine boots) ?
- May 25 2013

chown isn't an option here. What about chmod (a+x for every directory in the path, a+r for the file itself) ? For example (as root) :

chmod a+x /sys/kernel/debug
chmod a+x /sys/kernel/debug/dri
chmod a+x /sys/kernel/debug/dri/0
chmod a+r /sys/kernel/debug/dri/0/radeon_pm_info

- Feb 23 2013

If debugfs is already mounted (which seemes to be the case), you need to make sure that normal users have read permission :

sudo chmod -R o+r /sys/kernel/debug

- Jan 14 2013

I'll try to fix bugs when possible (as long as they don't depend on actually having a radeon card) but I won't add or change features.

Regarding the memory clock, the script does look for the "current memory clock" line and does nothing if the line isn't there. If you want to display the memory frequency, you can edit the main.js file again, go to line 197 and replace "current m" by "default m".

- Dec 19 2012

I can't reproduce this (but I don't have a Radeon card anymore, so my tests are limited to installing F17 in VirtualBox).

Could you try the following :

- in kwrite, open ~/.kde/share/apps/plasma/plasmoids/radeon-pm/contents/code/main.js

- comment the following lines out (by putting // at the beginning of each of them) : 40, 41, 46, 47

- save, close editor, log out and back in
- Dec 17 2012

Hi,

I'm not sure about cpufreq (isn't it dedicated to cpu power management ?).

Systemd being an init replacement, I don't think it would be of use here (unless you want a daemon that scales the frequencies based on various conditions, but this is way beyond the scope of this simple applet).

About the "pseudo-files" this applet writes to, they are (but my knowledge might not be so up-to-date) the only userspace interface to access radeon power management. Even a power management daemon would need to use this interface (and thus write to the files).

Take care
JM - Nov 09 2012

I just posted a new version. Could you please try this one ?
- Aug 29 2011

You're welcome. I'm glad you found it useful enough to register.

- Aug 21 2011

glad you could solve this. I added a note to the description about this potential issue. - Aug 21 2011

The various paths can vary from a system to another. In order to display the frequencies and voltage, you need to mount the debug file system (as root. Put this in /etc/rc.local if you want it to be persistent) :

mount -t debugfs none /sys/kernel/debug

Then you must find the radeon_pm_info file and paste the resulting path in the corresponding setting :

find /sys/kernel/debug -name radeon_pm_info

About the KDE downloader, I admit I haven't tested this. I'll have a look at it when I'm back from my vacations.
- Aug 03 2011

Le mode dynamique ne semble pas non plus avoir d'effet sur la carte graphique de mon portable (fréquences et voltage restent à la valeur max en permanence). Le mode est donc présent dans l'applet mais je n'ai pas pu le tester sur une carte qui le supporte.

Quand au problème de plantage lors de l'ouverture des réglages, je n'arrive pas à le reproduire (quel que soit le mode sélectionné).

Sinon, le pilote radeonHD est obsolète. Toutes les cartes ATI/AMD utilisent maintenant le pilote radeon, récentes comme anciennes.
- May 25 2011

il n'y a pas de mal, et j'admets que la procédure d'installation pourrait être plus claire sur ce point. Je vais préciser ça. - May 24 2011

that's strange. If the plasmoid had been installed, it should appear in the plasmapkg --list output, and find should, well, find it.

Just in case, did you install the plasmoid as root ? If you did, you shouldn't have, since the default behaviour of plasmapkg is to use the user's profile for installation (meaning that the plasmoid would have been installed in root's profile).

Aside from this, since I can't reproduce it, I have to admit I'm out of ideas. - May 24 2011

just tried 1.3 and 1.4 with the live Mepis 11 dvd. In both cases, the plasmoid actually does show up in the list, so I have no idea why it doesn't for you.
When adding it to the desktop though, only 1.3 seems to work. 1.4 doesn't (I'm going to investigate that).
- May 24 2011

sorry, but I'm definitely fglrx-free, and don't want to go there again.

On the other hand, back when I used it, the one thing that seemed to work right was power management, so I'm not sure that a fglrx-aware plasmoid would be that useful.

If you want to fiddle with frequencies, there's always this utility (although it's not a plasmoid) :

http://amdovdrvctrl.sourceforge.net
- May 24 2011

In my understanding, the plasmoid should show up, even if it doesn't work when added to the desktop/panel.

You can use this command to check if the plasmoid is installed :

plasmapkg --list | grep radeon-pm

You can also check that everything is in place by running this command :

find $HOME/.kde -name radeon-pm -exec ls -lR '{}' \;

I'm now downloading Mepis. I'll keep you posted if I find out why it doesn't show up for you.
- May 24 2011

Your message also reminded me that I had a new version sitting on my computer for ages. You may want to try the updated version. - May 23 2011

what's your KDE version ? It should work with 4.5 and 4.6 (maybe also with older versions but I didn't test with 4.4 and older).

BTW, the plasmoid should appear in the "System Information" category.
- May 23 2011

good. I'll update the description with the kernel version information. - Mar 24 2011

after some googling, the kernel version seems to be the culprit. It looks like the /sys interface was added in 2.6.35. Before that, you add to use the radeon.dynpm and other boot parameters for power management.
- Mar 23 2011

although everything seems to be in order (kms, power management initialized), maybe your kernel misses some bits to make this work (2.6.35+ seems to be required if you look here http://www.x.org/wiki/RadeonFeature, under "KMS Power Management Options").

Also, just in case (but you likely have already checked this), maybe you have a /sys/class/drm/card1 (or 2) directory ? - Mar 23 2011

what's the output of the following commands ?

uname -a

dmesg | grep drm
- Mar 23 2011

I'm glad it worked. I've added the additional option to the installation description.

Regarding the low power mode, on my laptop it seems to have the same effect as the mid profile (which is another reason why I didn't bother with the low profile in the first place). - Mar 14 2011

Try again by adding the package type. This seems necessary with KDE 4.6+ :

plasmapkg -t plasmoid -i radeon-pm.plasmoid

If you confirm it works for you, I will edit the installation procedure.

- Mar 14 2011

That's right. I guess I could add a real low button (and rename the current one to mid), with an option to enable it (defaulting to disabled). - Mar 11 2011

well, actually, the Low button activates the mid profile, precisely because of the warning about potential problems with the actual low profile. I wasn't comfortable with the idea of people yelling at me because I broke their laptop ;-) - Mar 11 2011

I'm glad it finally worked for you. Thanks for reporting the problem, and for your suggestion (it's so much better I can't believe I didn't think of it myself).
- Mar 11 2011

ok, I had to download Opensuse 11.4 and launch it inside VirtualBox to find what this was about. KDE 4.5 and 4.6 do tread URL objects differently, so what worked for me didn't work for you.
I've uploaded a new version. Let's hope there aren't other differences. - Mar 11 2011

I'm on KDE 4.5 myself but I have no idea if it makes a difference. If you're up for a little debugging, could you try the following ?

- copy the radeon-pm.plasmoid file to an empty dir

- unzip radeon-pm.plasmoid

- edit file contents/code/main.js, go to line 31 and add the following instructions :

print(plasmoid.activeConfig); print(deviceUrl);

- save, quit editor and launch the modified plasmoid with this command line :

plasmoidviewer PATH-TO-DIR-WHERE-YOU-UNZIPPED-THE-PLASMOID

- what's the terminal output ? - Mar 11 2011

I added a setting (temperature monitor path) to the configuration dialog. Could you try this new version ?
- Mar 11 2011

Panel maximizer

Plasma 4 Widgets 2 comments

by jemino

Score 50.0%

May 15 2010

actually, I'm not sure (about the broken by design part).
Sadly, I don't have the kind of time that would be required to really delve into the plasma codebase and see if it's possible to solve the problem at its source, whereas this small applet was easy enough to write - May 15 2010