So you could couple fsb and vcore, but in userspace. Maybe adding two module options would help for the rights problem: I’m using it now along with emerge gnome-cpufreq-applet Mon Jan 03, The trouble maker is: Of course the coupling should only be modifyable by root, so this would be pretty safe then.
|Date Added:||9 November 2014|
|File Size:||28.3 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Couldn’t atxo1 make some sort of “slave mode” to atxp1, that it only accepts changes in vcore from kernel space and a “master mode” for the the cpufrequ driver, that it controlls a slave which connects to it?
But of course we could set up the tables ourselves using programs like prime95, can’t we.
Linux Kernel Driver DataBase: CONFIG_SENSORS_ATXP1: Attansic ATXP1 VID controller
I already tried cpufreq-nforce2 without voltage changing some time ago. I tried using make on itbut, it ended up returning an error, I’d c opy paste it if I had a middle mouse button but it seems to complain about a cpufreq not being declared.
Not sure yet why this occurs, there are no FP operations in the module. You have already running a 2.
CONFIG_SENSORS_ATXP1: Attansic ATXP1 VID controller
Ok, thanks for the calculation fix. Is it even worth it? Maybe these don’t even on the cpu but on the mainboard only?
On my NF7-S 2. Nevertheless trying to compile atxp1 I get: Can you measure the amound of electricity you save with additional cpufreq-nforce2?
So you could couple fsb and vcore, but in userspace. Yes, a daemon would attansci great to have. Than that is maybe for you if you want to dynamically change you CPU speed and voltage power saving when idle. Because not all VCore controllers support 1.
But what really would be ubercool is a daemon that not only can handle the FSB frequenzy changes but also the changes to cpu core voltage.
Linux Kernel: drivers/hwmon/atxp1.c File Reference
Sun Jan 02, 3: Display atransic from previous: Is it necessary to build this i2c stuff as modules? Does anyone have a nice ruleset for it? Sonic Lux Guru Joined: The trouble maker is: Sun Jan 02, 4: The devices kernel environment is completely different.
Mon Jan 03, Mostly the RAM is the limiting factor. Unfortunately I’ve not heard yet that this works with the nForce2 chipset.
VCore pairs are different between various CPUs. The kernel patch is now available at: Of course the coupling should only be modifyable by root, so this would be pretty safe then.
Wed Jan 05, Perhaps the best would be to let udev handle the permissions? Mon Jan 03, 6: Also the kernel environments are different, writing a third module that controls both is possible, but not very nice.