Date: Tue, 04 Nov 2003 16:17:01 -0400 From: "Jud" <judmarc@fastmail.fm> To: "nw1" <network101@covad.net> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable-- Message-ID: <20031104201701.6D9CB79830@server2.messagingengine.com> In-Reply-To: <00a101c3a306$8cde0e40$0300a8c0@install> References: <20031104003834.45540.qmail@web14609.mail.yahoo.com><000e01c3a26e$a5024ec0$0300a8c0@install> <oprx3ebfhn0cf2rk@mail.messagingengine.com> <003e01c3a281$1fdb6a20$0300a8c0@install> <oprx305vyl0cf2rk@mail.messagingengine.com> <00a101c3a306$8cde0e40$0300a8c0@install>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 4 Nov 2003 14:05:02 -0500, "nw1" <network101@covad.net> said: [snip] > > > I'm interested in those missing sysctl variables I posted @ > > > http://69.3.136.141/freebsd/installation/sysctl_variables_missing. > > > Using a Third party > > > application/script to fix something that was natively working or under > > > control, I don't > > > think, is the way to go and causes another level of complexity. [snip] > No problem, I am interested in any and all *sane/reasonable feedback. I > haven't been to > much a fan of using third party applications to fix something the > original code or > hardware should be able to handle. FVCool isn't a "third party application" as I understand the term. Perhaps a portion of the README file will make things clearer: "As is well known AMD's Athlon/Duron is a 'hot' CPU. It really produces a lot of heat. This is mainly because it consumes a lot of electric power. However, there is an another reason: Generally CPU goes into power-save mode when it is in the idle state, but in almost all the mother boards this is prohibited in the case of Athlon/Duron mother boards in their original BIOS settings. This software changes the PCI configuration data of the chipset (north bridge), and allow Athlon/Duron to go into power-save mode. The principle is very simple if you have information. Actually, you can do exactly the same thing as this software manually by using the 'pciconf' command in FreeBSD. "Why mother board vendors release their products with such BIOS settings? Well, there is a reason: There is a possibility to get the system unstable and/or even to hang or crash the system. Therefore, this software is somewhat dangerous in this respect, and I will not take any responsibilities for problems caused by using this software. Please check the original Martin Peters's VCool web site for learning more of technical details: http://vcool.occludo.net/" So what FVCool does is utilize the 'pciconf' command to encourage AMD CPUs to go into power-save mode when idle, a function most motherboard manufacturers turn off for the stability reasons mentioned by FVCool's author. As the documentation says, you can manually make these changes with the 'pciconf' command, but why not save typing by installing the port and running the 'fvcool' command, or run it automatically with a script? Based on the names of the sysctls you're after, I'd speculate they may operate in much (or even exactly) the same way. That is why I wondered, in response to your advice to Paul Mather, whether those sysctl settings would work with Intel CPUs. Jud
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031104201701.6D9CB79830>