Package Details: paramano 0.72-1

Git Clone URL: https://aur.archlinux.org/paramano.git (read-only, click to copy)
Package Base: paramano
Description: Docking battery monitor and CPU governer controller (fork of trayfreq)
Upstream URL: https://gitlab.com/dphillips/paramano
Licenses: GPL
Submitter: phillid
Maintainer: phillid
Last Packager: phillid
Votes: 74
Popularity: 0.000000
First Submitted: 2014-09-27 04:47 (UTC)
Last Updated: 2022-11-19 08:18 (UTC)

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 Next › Last »

RedoX commented on 2012-07-25 12:34 (UTC)

Made some changes, compatibility should be ok with current kernels (mine is 3.4.6-1). You can find the updated files at: http://www.redox.ws/Repository/trayfreq-179.tar.gz The patch is not perfect (there's a lot of unwanted stuff in it since I had to do an "autoreconf -f -i" ) but I'm not an expert with these kind of stuff. It would be cool if the maintener could update the AUR package since my webhosting is not well adapted for this use.

foobarrior commented on 2012-04-13 14:22 (UTC)

i made a patch http://pastie.org/3780721

robvelor commented on 2012-02-20 06:31 (UTC)

I got this to work using z0id's workaround.

<deleted-account> commented on 2011-12-09 14:33 (UTC)

After adding those lines to the build function it still gives me a "buffer overflow" error. It would be great if this worked

z0id commented on 2011-10-25 21:07 (UTC)

Ok, so you can get it to run by disabling the default cflags. Place unset CXXFLAGS unset CFLAGS in the build() function. However, it will no longer display the battery icon with post 3.0.4 kernels since /proc/acpi is deprecated and moved to /sys. Trayfreq uses the libacpi, which uses /proc/acpi. I think libacpi is deprecated too, in favor of libudev. This was the greatest piece of software in the world :)

<deleted-account> commented on 2011-10-14 18:17 (UTC)

Any fix for the "buffer overflow" error? I mean except downgrading the kernel.

z0id commented on 2011-10-07 09:13 (UTC)

Update: It runs into the buffer overflow issue with kernel 3.0.6-1. After downgrading to 3.0.4-1 it works again.