Hi, the new package also includes my nvclock plugin. I attached an ebuild which builds it if the use flag is specified. You might want to add a few warning that the plugin will oc an NVidia card w/o further checks and possible damage it, if the wrong values are put into the config file. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 69295 [details] ebuild with nvclock use flag
- Please attach always in plain text. - The ebuild header is invalid. The plugin should probably better be an ebuild, instead adding a yet another superfluous use flag.
I ticked auto when I attached the patch. I just modified the preivious ebuild, thus the header. Of course I left it to the maintainer to clean it up, but just wanted to show hot to compile the nvclock plugin. If the maintainer thinks it should be a seperate ebuild, he may have fun doing so. I wonder how to compile the plugin itself w/o major patching of the cpufreqd's build system. This ebuild works for me and I'll keep it in my local overly.
Please always submit proposed ebuild changes as a unified diff (diff -u) against the latest version available in portage.
Created attachment 70413 [details, diff] cpufreqd nvclock fix In case you want to enable nvclock support, you might want to use these two patches, as well, which prevent cpufreqd/nvclock from flooding open fd's.
Created attachment 70414 [details, diff] nvclock fd fix
cpufreqd-2.0.0-pre1 added to portage including the above patches. malverian, perhaps attachment #70414 [details, diff] should be added to the stand-alone nvclock ebuilds as well?
Created attachment 70834 [details, diff] cpufreqd nvcock fix (updated/conservative) After talking with author of nvclock, he suggest using this way to set mem/core clock. This one disallows overclocking laptop and integrated graphics, but according to author that isn't very safe anyway.
Thanks, applied. In the future, please provide patches that apply with -p1, not -p0 as this makes it much easier to use them from within ebuild. It also makes it easier to see which package, the patch is intended for.
Your useflag is named wrongly. It should be "nvidia" not "nvidea"...
*nvclock-0.8_beta2 (14 Oct 2006) 14 Oct 2006; <malverian@gentoo.org> +files/nvclock_acinclude_qtlibs.patch, nvclock-0.7-r1.ebuild, +nvclock-0.8_beta2.ebuild, -nvclock-0.8b.ebuild: Fix compile problem with USE=qt3 when Qt4 is installed (#114872). Compilation fix with USE=qt3 on AMD64. Version bump (#143023, #107334).
