tag:blogger.com,1999:blog-60076419066709814672024-03-15T08:54:28.455+01:00LinuxsolverWorkarounds, tricks, solutions, patches and any kind of stuff a linux-user might need. Some true and deep laptop modding too.Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.comBlogger32125tag:blogger.com,1999:blog-6007641906670981467.post-27124020330401584062012-09-05T00:22:00.001+02:002012-11-20T11:49:58.881+01:00How to customize CPU frequency steps<div class="separator" style="clear: both; text-align: center;">
<a href="http://www.tecnologiaericerca.com/wp-content/uploads/2011/01/Intel_Sandy_Bridge.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="248" src="http://www.tecnologiaericerca.com/wp-content/uploads/2011/01/Intel_Sandy_Bridge.jpg" width="320" /></a></div>
Hey everybody,<br />
<br />
here comes a brand new guide on an interesting topic: CPU frequency scaling. Not many of you may know that on newer generation Intel CPUs (Ivy-Sandy Bridge) the kernel governor may decide the most suitable frequency in a plethora of them. In my case, for example (i7 3720QM), I can range from 1200MHz to 3600MHz in steps of 100MHz. This might be exciting, but <b>changing CPU frequency costs a little energy at every transition.</b><br />
Furthermore it happens that in several high-end CPUs, which are the more power consuming too, they cut the lower boundary to 1200MHz, while the <b>real minimum is 800MHz.</b><br />
In this advanced guide I want to introduce you how to modify your BIOS to fully control CPU frequency steps.<br />
<br />
<a name='more'></a>First of all<b> this is not a game</b>. You might seriously introduce instability and crashes and whatever, so please, be sure to know what you are doing. This "how to" is tested for Sandy and Ivy Bridge CPUs, but should apply also to CoreDuo and later.<br />
<br />
One of the requisite of this operation is how to recompile a kernel. <u>If you don't know what that means nor you know how to do that, you'd better go out and find another way to mess up your linux distro :P.</u><br />
<br />
I move my steps on a debian based machine, powered by linux Mint 13 Maya. If you are on Ubuntu or Debian you can follow this guide step by step; if you own another distro take care of translating instruction to your environment.<br />
<br />
Here comes another annoying paragraph of knowledge, so you can fully understand what we are doing. Usually BIOS takes care to understand what your machine has plugged in, and to expose a useful interface to the kernel. This is usually done by the ACPI management structure. Sometimes it happens that either the BIOS or the kernel mess the things up so you have to put the hands under the hood and fix them. <b>This is possible by bypassing the BIOS</b> furnished interface with a custom built one, compiled directly into the kernel. Following this guide you'll: dump stuff from your running BIOS, add or modify sections to implement things (following ACPI standards) and put it in the kernel.<br />
<br />
Ok, time to go to the business.<br />
I suppose you have the tool to compile your own kernel, so I won't introduce them, we'll need msr-tools and iasl, so you can issue:<br />
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo apt-get install msr-tools iasl</span><br />
<span style="font-family: 'Courier New', Courier, monospace;"><br /></span>
<span style="font-family: inherit;">the first is an utility to look in your CPU Model Specific Registers, the second a compiler to decompile and recompile Intel ACPI Source Language Code.</span><br />
<span style="font-family: inherit;"><br /></span>
<span style="font-family: inherit;">Now we need a tool to read accurately frequencies and states; get it <a href="http://code.google.com/p/i7z/" target="_blank">here</a> and install it.</span><br />
<span style="font-family: inherit;"><br /></span>
<span style="font-family: inherit;">The first step is to dump the multiplier limits of your CPU. I found a python script and added support for Sandy Bridge and Ivy Bridge registers, so you can download it <a href="https://www.dropbox.com/s/8fmw4u5r6wf604j/read_msr.py" target="_blank">here</a>. Now run it:</span><br />
<span style="font-family: inherit;"><br /></span>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo modprobe msr</span><span style="font-family: inherit;"><br /></span>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo python read_msr.py --readmsr</span><br />
<span style="font-family: 'Courier New', Courier, monospace;"><br /></span>
<span style="font-family: inherit;">you'll get an extended output: just look for max and min VIDs and FIDs</span><br />
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"></span>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">[cpu7] [CURRENT] FID:31 HID:0 DID:0 VID:0 </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">[cpu7] [TARGET] FID:31 HID:0 DID:0 VID:0 </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">[cpu7] [HIGHEST] FID:26 (HID:0 DID:0) VID:0</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">[cpu7] [LOWEST] FID:8 (HID:0 DID:0) VID:0 </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">[cpu7] [SLFM] FID:0 VID:0 </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">[cpu7] [IDA] FID:0 VID:0 </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">[cpu7] [CURRENTLY ACTIVE FEATURES] IDA:0 EIST:1</span><br />
<br />
<span style="font-family: 'Courier New', Courier, monospace;"><br /></span>
your answer might have little differences. You can see that the current VID and FID are higher than the maximum, this is because of turbo mod, so if possible do the test while running a heavy load process or a stress test (i.e. cpuburnutils). In this case 31 is the highest multiplier.<br />
<br />
<u>At this step you must know that SandyBridge and IvyBridge can't manage VIDs no more. So you won't be able to define voltages, while still you can set the frequencies.</u><br />
<br />
The next step is (obviously) to dump and modify (aka mess up ;D) the BIOS. What we need is the current DSDT file, we can simply dump it by:<br />
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo cat /sys/firmware/acpi/tables/DSDT > dsdt.dat</span><br />
<br />
but before you can read anything you have to decript it:<br />
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">iasl -d dsdt.dat</span><br />
<br />
now open it with your favourite text editor and snoop around. It might still look like a <a href="https://www.google.it/search?q=babylonian+tablet&tbm=isch" target="_blank">babylonian tablet</a> to your eyes. But no fear, make a backup copy and edit the file. We want to find the CPU section, so make a search for "CPU". You'll find something like:<br />
<br />
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">Scope (_PR)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU0, 0x01, 0x00000410, 0x06) {}</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU1, 0x02, 0x00000410, 0x06) {}</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU2, 0x03, 0x00000410, 0x06) {}</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU3, 0x04, 0x00000410, 0x06) {}</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU...</span><br />
<br />
Ok, here is the right point to paste our new code. Be sure to edit it to your needs. We are going to add a general section which carries infos for all the CPUs, then apply them core per core.<br />
The most important part is the <b>control registers definition</b>: in someway there is an ACPI CPU interface to set and monitor CPU frequency. This seems to be called _PCT. We will set register 0x199 as the set register (first line), but also as the monitor register (second line). This is suggested for Sandy and Ivy bridge, because CPU can scale autonomously if the load requires it: if checking the real status you'll get some unexpected transitions resulting in fault. The other CPU family shouldn't be able to do so, but if you experience strange behaviors use for both 0x199.<br />
Then we define the p-states. for each state enter frequency, transition latency, command value, target value:<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> freq lat lat cmd target</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> MHz FFVV FFVV</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">Package (0x06){3100,,0x0A,0x0A,0x1f00,0x1f00}</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"><br /></span>
<span style="font-family: inherit;">Command and target fields must be the same, and they are made by casting to hexadecimal the FID and VID values, in that order. Be sure to add FIDs and VIDs supported by your CPU!</span><br />
Here comes a quoted example, be sure to adapt the steps and the number of the CPUs:<br />
<div style="text-align: center;">
<b><br /></b></div>
<div style="text-align: center;">
<b>DO NOT JUST CUT AND PASTE</b></div>
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Scope (_PR)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"><span class="Apple-tab-span" style="white-space: pre;"> </span>Name (PPC, 0x00)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"><span class="Apple-tab-span" style="white-space: pre;"> </span>Name (PCT, Package (0x02){ // Registers definition</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> ResourceTemplate (){Register (FFixedHW, 0x4, 0x00, 0x199, ,)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }, </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small; white-space: pre;"> // Core Duo and later use here 0x198</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> ResourceTemplate (){Register (FFixedHW, 0x4, 0x00, 0x199, ,)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> })</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"><span class="Apple-tab-span" style="white-space: pre;"> </span>Name (PSS, Package (0x06){ // <-- 06 is the number of P-states defined</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"><br /></span>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">// P-state definition </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Package (0x06){3600,,0x0A,0x0A,0x2400,0x2400},<span class="Apple-tab-span" style="white-space: pre;"> </span>// p-state 0</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Package (0x06){3100,,0x0A,0x0A,0x1f00,0x1f00},<span class="Apple-tab-span" style="white-space: pre;"> </span>// p-state 1</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Package (0x06){2600,,0x0A,0x0A,0x1a00,0x1a00},<span class="Apple-tab-span" style="white-space: pre;"> </span>// p-state 2</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Package (0x06){1600,,0x0A,0x0A,0x1000,0x1000},<span class="Apple-tab-span" style="white-space: pre;"> </span>// p-state 3</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Package (0x06){1200,,0x0A,0x0A,0x0c00,0x0c00},<span class="Apple-tab-span" style="white-space: pre;"> </span>// p-state 4</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Package (0x06){ 800,,0x0A,0x0A,0x0800,0x0800},<span class="Apple-tab-span" style="white-space: pre;"> </span>// p-state 5</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> })</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> </span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU0, 0x01, 0x00000410, 0x06) {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PPC,_PPC)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PCT,_PCT)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PSS,_PSS)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU1, 0x02, 0x00000410, 0x06) {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PPC,_PPC)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PCT,_PCT)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PSS,_PSS)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU2, 0x03, 0x00000410, 0x06) {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PPC,_PPC)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PCT,_PCT)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PSS,_PSS)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU3, 0x04, 0x00000410, 0x06) {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PPC,_PPC)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PCT,_PCT)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PSS,_PSS)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU4, 0x05, 0x00000410, 0x06) {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PPC,_PPC)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PCT,_PCT)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PSS,_PSS)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU5, 0x06, 0x00000410, 0x06) {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PPC,_PPC)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PCT,_PCT)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PSS,_PSS)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU6, 0x07, 0x00000410, 0x06) {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PPC,_PPC)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PCT,_PCT)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PSS,_PSS)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Processor (CPU7, 0x08, 0x00000410, 0x06) {</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PPC,_PPC)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PCT,_PCT)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> Alias(PSS,_PSS)</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> }</span><br />
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"><br /></span>
<br />
Add the code, properly edited, for each logic CPU you find listed in the original DSDT file. Once done we'll want to compile it, and check it has no errors:<br />
<br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">iasl -tc dsdtnew.dsl</span><br />
<br />
I suggest not to try to fix warnings, since the original DSDT might be already bugged (LOL). If you find error out of you code Google is a good friend you can surely ask some help (or leave a comment).<br />
<br />
Once finished you'll find a dsdt.hex file. Move a copy of that to the /include folder of your kernel sources. Now edit the kernel configuration, adding the name of the DSDT to be included in:<br />
<br />
Power management and ACPI options>ACPI Support>"Custom DSDT Table file to include"<br />
<br />
Compile the kernel! Reboot! And check you job with both i7z and cpufreq-info.<br />
<br />
If you messed up things, boot a previous kernel, modify again dsdt and try it again.<br />
<br />
For any help feel free to leave a comment.<br />
<br />
Cheers!<br />
<br />
<br />
<br />
PS: I have tested this on an IvyBridge CPU, any feedback will be appreciated!<br />
<br />Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com7tag:blogger.com,1999:blog-6007641906670981467.post-22765183554033433692012-05-30T09:20:00.001+02:002012-08-19T19:16:24.051+02:00CPU Undervolting with Linux Mint 12<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://1.bp.blogspot.com/-31tKN_U1jfg/TWGWvtZD3dI/AAAAAAAAAEM/cu5jhu_cd2g/s1600/Schermata-7.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="136" src="http://1.bp.blogspot.com/-31tKN_U1jfg/TWGWvtZD3dI/AAAAAAAAAEM/cu5jhu_cd2g/s320/Schermata-7.png" width="320" /></a></div>
Hi guys,<br />
<br />
<a href="http://www.linux-phc.org/">PHC</a> stands for Processor Hardware Control and, as it's easy to understand, it allows users to customize some features of CPU control in a linux environment, as undervolting.<br />
<br />
<a name='more'></a><br />
So what do we need? A Mint (or Debian) box, usually undervolting is useful on laptops: it enhance battery duration and reduces the heat production. You will also need some time and patience, ;]<br />
<ol>
<li>You will need a kernel patch and a particular CPU driver so that the hardware control will be possible. First let's add the repo:<br /><blockquote style="font-family: 'Courier New', Courier, monospace;">
<span style="font-size: x-small;">sudo add-apt-repository ppa:linux-phc/ppa</span><br />
<span style="font-size: x-small;">sudo add-apt-repository ppa:linux-phc/testing</span><br />
<span style="font-size: x-small;">sudo apt-get update</span></blockquote>
</li>
<li style="margin-top: 10px;">Now let's install the kernel and its headers:<br /><blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo apt-get install linux-generic-phc linux-headers-generic-phc</span></blockquote>
First pause... restart your PC and be sure to choose your new *-phc kernel.</li>
<li style="margin-top: 10px;">As we will need to compile some stuff some users might need<br /><blockquote>
<span style="font-size: x-small;"><span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install gtk2-engines-pixbuf python-gtk2-dev build-essential</span></span></blockquote>
And then:<br /><blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo apt-get install dkms debhelper</span></blockquote>
Before doing anything else we have to create an empty file to match dmks autoconfiguration: Intel users go with the first, AMD with the second line!<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo sh -c 'echo >> /etc/modprobe.d/phc-intel.conf'<br />sudo sh -c 'echo >> /etc/modprobe.d/phc-k8.conf'</span></blockquote>
<span style="font-family: 'Courier New', Courier, monospace;"></span><div style="margin-left: 40px;">
</div>
</li>
<li>Now you have to download the driver, choose it looking at your CPU: there are two choices<a href="http://www.linux-phc.org/forum/viewtopic.php?f=13&t=2"> AMD</a> and <a href="http://www.linux-phc.org/forum/viewtopic.php?f=7&t=267">Intel</a>, be sure to take the right one.</li>
<li>Unpack the package to a temporary folder. Open a terminal and move there:<span style="font-family: 'Courier New', Courier, monospace;"><blockquote>
<span style="font-size: x-small;">cd **your_path**</span></blockquote>
</span><u>Intel</u> users can generate a debian package:<blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">make dkms_mkdeb</span></blockquote>
And install the resulting .deb package:<blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo dpkg -i phc-intel-dkms_0.3.2_all.deb</span></blockquote>
While <u>AMD</u> can't generate it, so:<blockquote>
<span style="font-size: x-small;"><span style="font-family: 'Courier New', Courier, monospace;">sudo make dkms_install</span> </span></blockquote>
Now you have your driver ready to go!</li>
<li>So we will unload the old driver:<br /><blockquote style="font-family: 'Courier New', Courier, monospace;">
<span style="font-size: x-small;">sudo modprobe -r acpi-cpufreq</span></blockquote>
Once you're done load the new one, amd users will have the second line, intel the first!<br /><blockquote style="font-family: 'Courier New', Courier, monospace;">
<span style="font-size: x-small;">sudo modprobe phc-intel</span><br />
<span style="font-size: x-small;">sudo modprobe phc-k8</span></blockquote>
If you experience the error: "FATAL: Module acpi_cpufreq is in use." you'll need to:<br /><blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo sh -c ' echo "\n#blackist required to load phc drivers\n </span><span style="background-color: white; font-family: 'Courier New', Courier, monospace; font-size: x-small;">blacklist acpi_cpufreq\n </span><span style="background-color: white; font-family: 'Courier New', Courier, monospace; font-size: x-small;">blacklist cpufreq_stats\n" > /etc/modprobe.d/blacklist.conf'</span><br />
<span style="font-size: x-small;"><span style="font-family: 'Courier New', Courier, monospace;">sudo sh -c ' echo "</span><span style="font-family: 'Courier New', Courier, monospace;">modprobe ##your module##\n" > /etc/modules'</span></span></blockquote>
And REBOOT =_= ...</li>
<li>Now I guess you want a cool GUI to easier setting VIDs: <a href="https://www.dropbox.com/s/krz6wakilt6b5rn/phctool_0.5.2-3.tar.gz" target="_blank">get it here</a>. Unpack it to a <u>non temporary</u> folder and move there.</li>
<li>From the main phctool folder run:<br /><blockquote style="font-family: 'Courier New', Courier, monospace;">
<span style="font-size: x-small;">sudo ./install.sh</span></blockquote>
</li>
<li>Follow the instruction (both yes will be OK)</li>
<li>Create a new program link in the menu with "Main Menu" to the command /**your_path**/pchtool.sh</li>
<li>Be sure to create a startup entry with the command<br /><blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">/**your_path**/</span><span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">phctray.sh</span></blockquote>
So voltages will be restored at each startup! </li>
</ol>
After this installation procedure try to launch phctool from your main menu: there you can set the voltages and see many infos about your CPU. If it happens that you can't refresh the actual values install msr-tools and run it with:<br />
<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo apt-get install msr-tools<br />sudo modprobe msr</span></blockquote>
The correct undervolted values are not universal, so you'll need some testing. If you think you'll need a guide, then take a look here:<br />
<br />
<a href="http://linuxsolver.blogspot.com/2011/10/how-to-set-cpu-voltage.html">http://linuxsolver.blogspot.com/2011/10/how-to-set-cpu-voltage.html</a><br />
<br />
<br />
Cheers!Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com6tag:blogger.com,1999:blog-6007641906670981467.post-72469119724922733662012-05-30T09:07:00.002+02:002012-08-19T19:16:56.492+02:00CPU Undervolting with Ubuntu 12.04<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://1.bp.blogspot.com/-31tKN_U1jfg/TWGWvtZD3dI/AAAAAAAAAEM/cu5jhu_cd2g/s1600/Schermata-7.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="136" src="http://1.bp.blogspot.com/-31tKN_U1jfg/TWGWvtZD3dI/AAAAAAAAAEM/cu5jhu_cd2g/s320/Schermata-7.png" width="320" /></a></div>
Hi guys,<br />
<br />
<a href="http://www.linux-phc.org/">PHC</a> stands for Processor Hardware Control and, as it's easy to understand, it allows users to customize some features of CPU control in a linux environment, as undervolting.<br />
<br />
<a name='more'></a><br />
So what do we need? An Ubuntu (or Debian) box, usually undervolting is useful on laptops: it enhance battery duration and reduces the heat production. You will also need some time and patience, ;]<br />
<ol>
<li>You will need a kernel patch and a particular CPU driver so that the hardware control will be possible. First let's add the repo:<br />
<blockquote style="font-family: 'Courier New', Courier, monospace;">
<span style="font-size: x-small;">sudo add-apt-repository ppa:linux-phc/ppa</span><br />
<span style="font-size: x-small;">sudo add-apt-repository ppa:linux-phc/testing</span><br />
<span style="font-size: x-small;">sudo apt-get update</span></blockquote>
</li>
<li style="margin-top: 10px;">Now let's install the kernel and its headers:<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo apt-get install linux-generic-phc linux-headers-generic-phc</span></blockquote>
First pause... restart your PC and be sure to choose your new *-phc kernel.</li>
<li style="margin-top: 10px;">As we will need to compile some stuff some Ubuntu users might need<br />
<blockquote>
<span style="font-size: x-small;"><span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install </span><span style="font-family: 'Courier New', Courier, monospace;">gtk2-engines-pixbuf python-gtk2-dev build-essential</span></span></blockquote>
And then:<br />
<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo apt-get install dkms debhelper</span></blockquote>
Before doing anything else we have to create an empty file to match dmks autoconfiguration: Intel users go with the first, AMD with the second line!<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo sh -c 'echo >> /etc/modprobe.d/phc-intel.conf'<br />
sudo sh -c 'echo >> /etc/modprobe.d/phc-k8.conf'</span></blockquote>
<span style="font-family: 'Courier New', Courier, monospace;"></span><div style="margin-left: 40px;">
</div>
</li>
<li>Now you have to download the driver, choose it looking at your CPU: there are two choices<a href="http://www.linux-phc.org/forum/viewtopic.php?f=13&t=2"> AMD</a> and <a href="http://www.linux-phc.org/forum/viewtopic.php?f=7&t=267">Intel</a>, be sure to take the right one.</li>
<li>Unpack the package to a temporary folder. Open a terminal and move there:<span style="font-family: 'Courier New', Courier, monospace;"><blockquote>
<span style="font-size: x-small;">cd **your_path**</span></blockquote>
</span><u>Intel</u> users can generate a debian package:<blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">make dkms_mkdeb</span></blockquote>
And install the resulting .deb package:<blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo dpkg -i phc-intel-dkms_0.3.2_all.deb</span></blockquote>
While <u>AMD</u> can't generate it, so:<blockquote>
<span style="font-size: x-small;"><span style="font-family: 'Courier New', Courier, monospace;">sudo make dkms_install</span> </span></blockquote>
Now you have your driver ready to go!</li>
<li>So we will unload the old driver:<br />
<blockquote style="font-family: 'Courier New', Courier, monospace;">
<span style="font-size: x-small;">sudo modprobe -r acpi-cpufreq</span></blockquote>
Once you're done load the new one, amd users will have the second line, intel the first!<br />
<blockquote style="font-family: 'Courier New', Courier, monospace;">
<span style="font-size: x-small;">sudo modprobe phc-intel</span><br />
<span style="font-size: x-small;">sudo modprobe phc-k8</span></blockquote>
If you experience the error: "FATAL: Module acpi_cpufreq is in use." you'll need to:<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo sh -c ' echo "\n#blackist required to load phc drivers</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">blacklist acpi_cpufreq</span><br />
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">blacklist cpufreq_stats" > /etc/modprobe.d/blacklist.conf'</span><br />
<span style="font-size: x-small;"><span style="font-family: 'Courier New', Courier, monospace;">sudo sh -c ' echo "</span><span style="font-family: 'Courier New', Courier, monospace;">modprobe ##your module##" > /etc/modules'</span></span></blockquote>
And REBOOT =_= ...</li>
<li>Now I guess you want a cool GUI to easier setting VIDs: <a href="https://www.dropbox.com/s/krz6wakilt6b5rn/phctool_0.5.2-3.tar.gz" target="_blank">get it here</a>. Unpack it to a <u>non temporary</u> folder and move there.</li>
<li>From the main phctool folder run:<br />
<blockquote style="font-family: 'Courier New', Courier, monospace;">
<span style="font-size: x-small;">sudo ./install.sh</span></blockquote>
</li>
<li>Follow the instruction (both yes will be OK)</li>
<li>Create a new program link in the menu with "Main Menu" to the command /**your_path**/pchtool.sh</li>
<li>Be sure to create a startup entry with the command<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">/**your_path**/</span><span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">phctray.sh</span></blockquote>
So voltages will be restored at each startup! </li>
</ol>
After this installation procedure try to launch phctool from the main menu: there you can set the voltages and see many infos about your CPU. If it happens that you can't refresh the actual values install msr-tools and run it with:<br />
<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">sudo apt-get install msr-tools<br />
sudo modprobe msr</span></blockquote>
The correct undervolted values are not universal, so you'll need some testing. If you think you'll need a guide, then take a look here:<br />
<br />
<a href="http://linuxsolver.blogspot.com/2011/10/how-to-set-cpu-voltage.html">http://linuxsolver.blogspot.com/2011/10/how-to-set-cpu-voltage.html</a><br />
<br />
<br />
Cheers!Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com114tag:blogger.com,1999:blog-6007641906670981467.post-84511320640534758032012-03-12T09:44:00.004+01:002012-07-26T11:22:11.450+02:00CPU Undervolting with Ubuntu 11.10<div class="separator" style="clear: both; text-align: center;">
<a href="http://1.bp.blogspot.com/-31tKN_U1jfg/TWGWvtZD3dI/AAAAAAAAAEM/cu5jhu_cd2g/s1600/Schermata-7.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="136" src="http://1.bp.blogspot.com/-31tKN_U1jfg/TWGWvtZD3dI/AAAAAAAAAEM/cu5jhu_cd2g/s320/Schermata-7.png" width="320" /></a></div>
Hi guys,<br />
<br />
<a href="http://www.linux-phc.org/">PHC</a> stands for Processor Hardware Control and, as it's easy to understand, it allows users to customize some features of CPU control in a linux environment, as undervolting.<br />
<div style="text-align: center;">
<br /></div>
<div style="text-align: center;">
<br /></div>
<div style="text-align: center;">
<a href="http://linuxsolver.blogspot.it/2012/05/undervolting-cpu-in-ubuntu-1204.html">!!UPDATED UBUNTU 12.04 VERSION!!!</a></div>
<br />
<a name='more'></a><br />
So what do we need? An Ubuntu (or Debian) box, usually undervolting is useful on laptops: it enhance battery duration and reduces the heat production. You will also need some time and patience, ;]<br />
<ol>
<li>You will need a kernel patch and a particular CPU driver so that the hardware control will be possible. First let's add the repo:<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
sudo add-apt-repository ppa:linux-phc/ppa<br />
sudo add-apt-repository ppa:linux-phc/testing <br />
sudo apt-get update</blockquote>
</li>
<li style="margin-top: 10px;">Now let's install the kernel and its headers:<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install linux-generic-phc linux-headers-generic-phc</span></blockquote>
First pause... restart your PC and be sure to choose your new *-phc kernel.<br />
</li>
<li style="margin-top: 10px;">As we will need to compile some stuff some Ubuntu users might need <br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install </span><span style="font-family: 'Courier New', Courier, monospace;">gtk2-engines-pixbuf python-gtk2-dev build-essential </span></blockquote>
And then:<br />
<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install dkms debhelper</span></blockquote>
Before doing anything else we have to create an empty file to match dmks autoconfiguration: Intel users go with the first, AMD with the second line!
<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace;">sudo sh -c 'echo >> /etc/modprobe.d/phc-intel.conf'<br />sudo sh -c 'echo >> /etc/modprobe.d/phc-k8.conf'</span></blockquote>
<span style="font-family: 'Courier New', Courier, monospace;"></span><div style="margin-left: 40px;">
</div>
</li>
<li>Now you have to download the driver, choose it looking at your CPU: there are two choices<a href="http://www.linux-phc.org/forum/viewtopic.php?f=13&t=2"> AMD</a> and <a href="http://www.linux-phc.org/forum/viewtopic.php?f=7&t=267">Intel</a>, be sure to take the right one.</li>
<li>Unpack the package to a temporary folder. Open a terminal and move there:<span style="font-family: 'Courier New', Courier, monospace;"><blockquote>
cd **your_path** </blockquote>
</span><u>Intel</u> users can generate a debian package:<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;"> make dkms_mkdeb</span></blockquote>
And install the resulting .deb package:<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo dpkg -i phc-intel-dkms_0.3.2_all.deb</span></blockquote>
While <u>AMD</u> can't generate it, so:<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo make dmks_install</span></blockquote>
Now you have your driver ready to go! </li>
<li>So we will unload the old driver:<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
sudo modprobe -r acpi-cpufreq</blockquote>
Once you're done load the new one, amd users will have the second line, intel the first!<br /><blockquote style="font-family: 'Courier New', Courier, monospace;">
sudo modprobe phc-intel<br />
sudo modprobe phc-k8</blockquote>
If you experience the error: "FATAL: Module acpi_cpufreq is in use." you'll need to:<br /><blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo sh -c ' echo "\n#blackist required to load phc drivers</span><br />
<span style="font-family: 'Courier New', Courier, monospace;">blacklist acpi_cpufreq</span><br />
<span style="font-family: 'Courier New', Courier, monospace;">blacklist cpufreq_stats" >> /etc/modprobe.d/blacklist.conf'</span><br />
<span style="font-family: 'Courier New', Courier, monospace;">sudo sh -c ' echo "</span><span style="font-family: 'Courier New', Courier, monospace;">modprobe ##your module##" >> /etc/modules'</span></blockquote>
And REBOOT =_= ...<br />
</li>
<li>Now I guess you want a cool GUI to easier setting VIDs: <a href="http://www.linux-phc.org/forum/viewtopic.php?f=14&t=17">get it here</a>. Unpack it to a <u>non temporary</u> folder and move there.</li>
<li>You'll need to fix an error, so download<a href="http://www.linux-phc.org/forum/viewtopic.php?f=10&t=270"> this corrected</a> file and save it to:<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">**your path**/phctool/inc/libs/</span></blockquote>
overwriting the existent file. </li>
<li>From the main phctool folder run:<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
sudo ./install.sh </blockquote>
</li>
<li>Follow the instruction (both yes will be OK)</li>
<li>Create a new program link in the menu with "Main Menu" to the command /**your_path**/pchtool.sh</li>
<li>done!</li>
</ol>
After this installation procedure try to launch<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo phctool</span></blockquote>
there you can set the voltages and see many infos about your CPU. If it happens that you can't refresh the actual values install msr-tools and run it with:<br />
<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install msr-tools<br />sudo modprobe msr</span></blockquote>
The correct undervoltedvalues are not universal, so you'll need some testing. If you think you'll need a guide, then take a look here:<br />
<br />
<a href="http://linuxsolver.blogspot.com/2011/10/how-to-set-cpu-voltage.html">http://linuxsolver.blogspot.com/2011/10/how-to-set-cpu-voltage.html</a><br />
<br />
<br />
Cheers!<br />
<ol></ol>Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com14tag:blogger.com,1999:blog-6007641906670981467.post-29954349493183020652012-01-05T08:56:00.001+01:002017-12-03T17:13:18.945+01:00Open .~CR files<div class="separator" style="clear: both; text-align: center;"><img border="0" height="231" src="https://www.cardrecovery.com/images/card_recovery_xp_wide.gif" width="320"></div>Hi guys,<br />
<br />
this time I'm making a small exception and submitting something cool in Windoze system. It happened few weeks ago that my 8GB microsd card got screwed up... with any sort of pic and video in it... my holiday pictures too.<br />
<br />
Since it's always a pain recovering a very damaged memory card (mine was so f*cked that reading the first sectors made it invisible to the OS...) I tried any sort of program, till I came to CardRecovery.<br />
<br />
<a name='more'></a>It looks that the latest version of this sw can jump seriously damaged sectors till it finds a new stable cell. I was able even to disconnect and reconnect the card during the process!<br />
<br />
Sounds great, but once you can see the preview of your files you find that a license is needed to save them. >_<<br />
<br />
Unless you use this program:<br />
<a href="https://ufile.io/upzaw">ufile_download</a><br />
<br />
<br />
Obviously you should do like I did and buy the license!<br />
<br />
Cheers!Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com65tag:blogger.com,1999:blog-6007641906670981467.post-27428481245148789912011-10-12T10:41:00.002+02:002012-07-27T09:16:52.234+02:00How to set the CPU voltage<div style="text-align: justify;">
<div class="separator" style="clear: both; text-align: center;">
<a href="http://3.bp.blogspot.com/-hXWLcnmhqIw/TpVSfAQ464I/AAAAAAAAAEo/_ji1fzkK-tU/s1600/1507.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="http://3.bp.blogspot.com/-hXWLcnmhqIw/TpVSfAQ464I/AAAAAAAAAEo/_ji1fzkK-tU/s1600/1507.jpg" /></a></div>
Hey guys,</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
here I am, I bet that soon or late you were waiting for this piece of knowledge.... I guess a little late, but here it comes. In the following guide you'll learn how to save energy, lower CPU temperature and improve your battery duration (at least on laptops) without (or at least minimizing) bugs and freezing, by setting the voltages of your CPU. If you don't have phctool installed take a look here:</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://linuxsolver.blogspot.com/2011/02/undervolting-cpu-in-ubuntu.html">http://linuxsolver.blogspot.com/2011/02/undervolting-cpu-in-ubuntu.html</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<a name='more'></a><div style="text-align: justify;">
First of all remember that doing those stuff your system might crash without saying "Hey dude, kinda confused here, I'm gonna make a mess soon". So no precious file copying, no disc burning, no thesis writing... I hope you got it, better nothing at all.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<span style="font-size: large;"><b>Tools</b></span></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
We need few stuff:</div>
<ul style="text-align: justify;">
<li><b>Patience</b>: of course this is what does the job.</li>
<li><b>Stress tool</b>: we need something to set the clock to be stressed, and something to put under heavy load the cpu, to see if it fails... so:<br />
<blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
sudo apt-get install cpuburn cpufrequtils lm-sensors</blockquote>
</li>
</ul>
<div style="text-align: justify;">
Ok, what have we installed? <i><b>Cpuburn</b></i> it's a set of commands, each one built for a specific CPU, that make one CPU core the busiest possible. <i><b>Cpufrequtils </b></i>instead gives us the possibility to set the CPU frequency step as we like. At last <b>lm-sensors</b> is a suite to get hardware infos form your box. To install it (from ubuntu HowTo):</div>
<ol style="text-align: justify;" type="1">
<li>Run <br />
<blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
sudo sensors-detect</blockquote>
and answer YES to all YES/no questions. </li>
<li>At the end
of sensors-detect, a list of modules that needs to be loaded will
displayed. Type "yes" to have sensors-detect insert those modules into
/etc/modules. </li>
<li>Next,
run "sudo /etc/init.d/module-init-tools restart". This will read the
changes you made to /etc/modules in step 2, and insert the new modules
into the kernel. </li>
</ol>
<div style="text-align: justify;">
Once you have a working installation of lm-sensors, we have a good way to keep temperatures under control: open a new terminal and launch</div>
<blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
while [ true ]; do sensors; sleep 1; done </blockquote>
<div style="text-align: justify;">
Keep it running in another window and go on with our mission!</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><span style="font-size: large;">How to stress</span></b></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
To stress a CPU you have to run one of the cpuburn commands. They are a big family, but can be split in two: burnP* are for intel CPUs, burnK* for AMD ones. So, if you have already opened sensors to keep temperatures under control (last command), the thing to do is just launch from terminal:<br />
<blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
burnP6 &</blockquote>
the "&" is needed as we have to stress all the cores, so we have to repeat that command for each core. <u>Be sure to write immediately after the last "burn"</u><br />
<blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
killall burnP6</blockquote>
<u>so you can be ready to stop the test if a too high temperature is reached.</u> If the computer does not freeze and the temperature does not blow your box up at least for a couple of minutes, you have 95% of probability to be on an actually stable setting. To be 99% sure you should run the burn test for 10-15 minutes.<br />
<br />
<b><span style="font-size: large;">Tuning Voltages</span></b> </div>
<ol style="text-align: justify;">
<li>The first step is of course to open phctool and take a look at the voltages. In that tab you can see both the frequency steps and the voltages. If you have more than one core you should see on your right several CPUs: you can set and stress all the cores at the same time. </li>
<li>Now open another terminal: we will use this to change the CPU frequencies and stress them. To get some extra info start with:</li>
<blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
sudo cpufreq-info </blockquote>
And take note of your CPU governor. <br />
<li><u>Repeat the following operations for all the cores you have</u>(-c 0; -c 1 ... etc): </li>
<blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
sudo cpufreq-set -c 0 -g userspace </blockquote>
Like this we are able to set our CPU voltage as we like.
<br />
<li style="text-align: justify;">From phctool set the lowest freq @ the lowest voltage for <u>all the cores.</u></li>
<li style="text-align: justify;">
Launch:
<blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
sudo cpufreq-set -c 0 -f **the freq value**</blockquote>
**the freq value** has to be written in the human readable format, just without space (e.g. 800MHz or 1.2GHz ect)</li>
<li> Now we are not sure to be actually using the lowest voltage, to check that go to the analysis tab of phctool and refresh. If you get a wrong [target voltage]/frequency double check what have you done... if it doesn't work for no reason just leave a comment.</li>
<li><b>If the current voltage does not match the target VID</b> then you have some limitation on the motherboard... so don't struggle on how to workaround it, it depends on your mobo/cpu hardware capablities. So take it as the "<b>absolute zero</b>", set it so that current and target VIDs match, and start stress it. </li>
<li>
If the stress test is ok we can move on. The following procedure has to be cycled for all the freq available, <u>for all the cores</u>:<br />
<br />
<ul>
<li><b>Ø_ </b>Set the frequency (<u>of all the cores</u>) with cpufreq-set: <br /><blockquote style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">
sudo cpufreq-set -c 0 -f **the freq value**</blockquote>
Your <i>Voltage Quantum </i><b>Q </b>is now 0.1V <br />
</li>
<li><b>A_ </b>Lower the VID (<u>of all the cores</u>) @ that freq by <b>Q</b></li>
<li><b>B_ </b>Stress test the value @ that freq</li>
<li><b>C_ </b>if the test failed halve <b>Q</b> and set the VID (<u>of all the cores</u>) to the last stable value. If <b>Q</b> is smaller than the VID step then go to the next point, otherwise return to <b>A</b>_</li>
<li><b>D_</b> If you are here you have configured almost at the limit that freq VID. If you want to be safer increase it of a couple of steps (<u>for all the cores</u>). Now move to the next frequency and restart from <b>Ø_</b>.<br /> </li>
</ul>
</li>
<li style="text-align: justify;">If you completed these operations for all the cores and all the frequencies now you have tuned your box! <u>Remember to set "restore VIDs on load"</u> before you can call it a day ^_^</li>
</ol>
I think we are done. If you need any help (but even if you don't need it) feel free to leave a comment!<br />
<br />
<br />
<br />
Cheers!<br />
<ol style="text-align: justify;"><br />
</ol>Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com14tag:blogger.com,1999:blog-6007641906670981467.post-77250393118396744212011-06-16T23:29:00.001+02:002011-06-16T23:35:33.970+02:00Electicsheep screensaver<div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/-RXYmLQO8PE4/TfpvXTtf81I/AAAAAAAAAEk/Lz-YO-csa-I/s1600/electricsheep.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="64" src="http://4.bp.blogspot.com/-RXYmLQO8PE4/TfpvXTtf81I/AAAAAAAAAEk/Lz-YO-csa-I/s320/electricsheep.png" width="320" /></a></div>Hey,<br />
<br />
back again with some stuff. Sorry but in these months I got my brand new job and I'm quite overwhelmed... ^_^"<br />
<br />
Anyway today I'm bringing to light my last solution in Linux environment. This time we are not talking about a useful stuff, but I'm introducing one of the coolest and maybe the most addictive screensaver ever seen: <a href="http://electricsheep.org/">Electricsheep</a>.<br />
<br />
<br />
<a name='more'></a><br />
<br />
Directly from the project page:<br />
"Electric Sheep is a collaborative abstract artwork founded by <a href="http://scottdraves.com/" title="http://scottdraves.com/">Scott Draves</a>. It's run by thousands of people all over the world, and can be <a href="http://community.electricsheep.org/download">installed</a> on any ordinary <a href="http://electricsheep.googlecode.com/files/electricsheep-2.7b29.exe">PC</a> or <a href="http://electricsheep.googlecode.com/files/electricsheep-2.7b29.dmg">Mac</a>. When these computers "sleep", the Electric Sheep comes on and the computers communicate with each other by the internet to share the work of creating morphing abstract animations known as "sheep". The result is a collective "android dream", an homage to Philip K. Dick's novel <i>Do Androids Dream of Electric Sheep</i>."<br />
<br />
Whoa... this sound gorgeous, but... is this screensaver gorgeous too? <a href="http://community.electricsheep.org/samples">Yes, it is</a>! But the installation, at least under linux is kinda cumbersome.<br />
<br />
If you have Ubuntu 10.04 or Debian Sid, then just use the package manager or type "sudo apt-get install electricsheep".<br />
<br />
The other need to follow the following procedure. This is necessary mainly due to a poor programming of Linux configure, and to the use of a not-so-up-to-date graphic library.<br />
<br />
The first smart thing we have to do is downloading the libGlee source from: <br />
<a href="http://elf-stone.com/glee.php" rel="nofollow" title="http://elf-stone.com/glee.php">http://elf-stone.com/glee.php</a>. Unpack it, open a terminal in that folder, compile and install it, simply by entering the line:<br />
<br />
<blockquote><div style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">./configure && make && sudo make install</div></blockquote>Now you can download the sources for electric sheep from here: <a href="http://code.google.com/p/electricsheep/downloads/list">http://code.google.com/p/electricsheep/downloads/list</a><br />
<br />
Unpack it to {your_dir}.Copy the GLee.h and GLee.c (from extacted sources) to {your_dir}<b>\DisplayOutput\OpenGL\</b> and to {your_dir}<b>\Client.</b><br />
<br />
Now go and edit the configure file by simply:<br />
<blockquote style="background-color: #cfe2f3;"><div style="font-family: "Courier New",Courier,monospace;">cp configure configure.bak</div><div style="font-family: "Courier New",Courier,monospace;">nano configure</div></blockquote><br />
ctrl+W and look for <span style="font-family: Arial,Helvetica,sans-serif; font-size: small;">"<b><code>WX_MAJOR=${WX_VERSION%%.*};</code></b>"</span><br />
<br />
This is the right code. Be sure to change the lines as follows<br />
<blockquote><code> <span style="background-color: #cfe2f3; font-size: small;"><span style="font-family: "Courier New",Courier,monospace;">if test x$WX_CONFIG != xno; then</span></span></code><span style="background-color: #cfe2f3; font-size: small;"><br style="font-family: "Courier New",Courier,monospace;" /><code><span style="font-family: "Courier New",Courier,monospace;"> WX_VERSION=`wx-config --version`</span></code><br style="font-family: "Courier New",Courier,monospace;" /><code><span style="font-family: "Courier New",Courier,monospace;"> </span></code><br style="font-family: "Courier New",Courier,monospace;" /><code><span style="font-family: "Courier New",Courier,monospace;"> WX_MAJOR=${WX_VERSION%%.*};</span></code><br style="font-family: "Courier New",Courier,monospace;" /><code><span style="font-family: "Courier New",Courier,monospace;"> WX_MINOR=${WX_VERSION#*.};</span></code><br style="font-family: "Courier New",Courier,monospace;" /><code><span style="font-family: "Courier New",Courier,monospace;"> WX_MICRO=${WX_MINOR##*.};</span></code><br style="font-family: "Courier New",Courier,monospace;" /><code><span style="font-family: "Courier New",Courier,monospace;"> WX_MINOR=${WX_MINOR%%.*};</span></code></span><br />
<code></code></blockquote><code> <br />
</code><br />
Now you should be able to configure by:<br />
<blockquote><div style="font-family: "Courier New",Courier,monospace;"></div><div style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">CXXFLAGS="`wx-config --cxxflags`" LDFLAGS="`wx-config --libs all`" ./configure</div><div style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">make</div><div style="background-color: #cfe2f3; font-family: "Courier New",Courier,monospace;">sudo make install </div></blockquote>You'll find the screensaver in your list from the configuration window.<br />
If the configure process complains about wxWidgets take a look around for a newer version of wxGTK, depending on your linux distro.<br />
<br />
If you have troubles feel free to leave a comment.<br />
<br />
CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com2tag:blogger.com,1999:blog-6007641906670981467.post-54966848146408255992011-04-08T14:52:00.000+02:002011-04-08T19:01:55.182+02:00System Profiler and Benchmark: Hardinfo<div class="separator" style="clear: both; text-align: center;"><a href="http://1.bp.blogspot.com/-3TWIH0PhKZ0/TZ76wqSqFLI/AAAAAAAAAEY/aAjfZieYsUc/s1600/Hardinfo.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="131" src="http://1.bp.blogspot.com/-3TWIH0PhKZ0/TZ76wqSqFLI/AAAAAAAAAEY/aAjfZieYsUc/s320/Hardinfo.png" width="320" /></a></div>Hey folks,<br />
<br />
today I want to suggest you a simple tool for system profiling and benchmark. It is called Hardinfo, hosted at <a href="http://hardinfo.berlios.de/HomePage">http://hardinfo.berlios.de/HomePage</a><br />
<br />
We will take a look at the installation procedure and examine its features, which can be grouped in two set: the system informations and the machine benchmarks.<br />
<br />
As it is quite rare to find a software suite with these features I suggest you to spread the word!<br />
<br />
<br />
<a name='more'></a>Let's take a look at the installation procedure:<br />
Ubuntu Debian and maybe other distros have the precompiled package, just look for the "hardinfo" pack in your package manager and let it do the rest.<br />
<br />
If you have Gentoo or any other distro not having this in its repos I suggest you to get ready to compile the source yourself. It is still quite easy: just download the package from the <a href="http://wiki.hardinfo.org/Downloads">download page</a> and extract the files in it:<br />
<br />
tar -xvf hardinfo-0.5.1.tar.bz2<br />
<br />
move to the right folder, configure and install:<br />
<br />
cd hardinfo-0.5.1<br />
./configure<br />
make<br />
sudo make install<br />
<br />
Now you should find it in your start menu as "System Profiler and Benchmark"<br />
First of all I suggest to run the sync from Information->NetworkUpdater, so you can get updated vendor list and benchmark comparison.<br />
<br />
Now this app is surely useful to have a fast answer to hardware question:<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://3.bp.blogspot.com/-1XXmF8RgK5o/TZ8BcHpVHTI/AAAAAAAAAEc/7Qt70YxvDVw/s1600/Schermata-Summary+-+System+Information.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="235" src="http://3.bp.blogspot.com/-1XXmF8RgK5o/TZ8BcHpVHTI/AAAAAAAAAEc/7Qt70YxvDVw/s400/Schermata-Summary+-+System+Information.png" width="400" /></a></div><br />
But also can give a system rating with several different benchmarks:<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://2.bp.blogspot.com/-gHzBBKWCs-A/TZ8B8iQXj3I/AAAAAAAAAEg/2_t0Rpjx6as/s1600/Schermata-FPU+FFT+-+System+Information.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="235" src="http://2.bp.blogspot.com/-gHzBBKWCs-A/TZ8B8iQXj3I/AAAAAAAAAEg/2_t0Rpjx6as/s400/Schermata-FPU+FFT+-+System+Information.png" width="400" /></a></div><br />
I found particularly useful the network update feature, which is two-way update: your local database is refreshed, but your ratings are transmitted to the online database too and used to generate a knowledge set for benchmark comparing.<br />
Another useful feature is the possibility to build and html report... cool!<br />
<br />
Here comes a piece of mine!<br />
<br />
See ya!<br />
<br />
<style>
body { background: #fff }
.title { font: bold 130% serif; color: #0066FF; padding: 30px 0 10px 0 }
.stitle { font: bold 100% sans-serif; color: #0044DD; padding: 30px 0 10px 0 }
.sstitle{ font: bold 80% serif; color: #000000; background: #efefef }
.field { font: 80% sans-serif; color: #000000; padding: 2px; padding-left: 50px }
.value { font: 80% sans-serif; color: #505050 }
</style><br />
<br />
<h1 class="title">Computer</h1><table><tbody>
<tr><td class="stitle" colspan="2">Summary</td></tr>
<tr><td class="sstitle" colspan="2">Computer</td></tr>
<tr><td class="field">Processor</td><td class="value">2x Intel(R) Core(TM)2 Duo CPU T9800 @ 2.93GHz</td></tr>
<tr><td class="field">Memory</td><td class="value">8063MB (1233MB used)</td></tr>
<tr><td class="field">Operating System</td><td class="value">Gentoo Base System release 2.0.2</td></tr>
<tr><td class="field">User Name</td><td class="value">fabio (Unknown)</td></tr>
<tr><td class="field">Date/Time</td><td class="value">ven 08 apr 2011 14:46:36 CEST</td></tr>
<tr><td class="sstitle" colspan="2">Display</td></tr>
<tr><td class="field">Resolution</td><td class="value">2720x900 pixels</td></tr>
<tr><td class="field">OpenGL Renderer</td><td class="value">Mesa DRI Mobile Intel® GM45 Express Chipset </td></tr>
<tr><td class="field">X11 Vendor</td><td class="value">The X.Org Foundation</td></tr>
<tr><td class="sstitle" colspan="2">Multimedia</td></tr>
<tr><td class="field">Audio Adapter</td><td class="value">HDA-Intel - HDA Intel</td></tr>
<tr><td class="sstitle" colspan="2">Input Devices</td></tr>
<tr><td class="field">Lid Switch</td><td class="value"></td></tr>
<tr><td class="field">Sleep Button</td><td class="value"></td></tr>
<tr><td class="field">Power Button</td><td class="value"></td></tr>
<tr><td class="field">Power Button</td><td class="value"></td></tr>
<tr><td class="field">Video Bus</td><td class="value"></td></tr>
<tr><td class="field">AT Translated Set 2 keyboard</td><td class="value"></td></tr>
<tr><td class="field">HDA Intel Headphone</td><td class="value"></td></tr>
<tr><td class="field">SynPS/2 Synaptics TouchPad</td><td class="value"></td></tr>
<tr><td class="field">Microsoft Microsoft® 2.4GHz Transceiver V1.0</td><td class="value"></td></tr>
<tr><td class="field">Microsoft Microsoft® 2.4GHz Transceiver V1.0</td><td class="value"></td></tr>
<tr><td class="sstitle" colspan="2">Printers (CUPS)</td></tr>
<tr><td class="field">Brother-HL-5250DN-BR-Script3</td><td class="value"></td></tr>
<tr><td class="field">S405</td><td class="value"><i>Default</i></td></tr>
<tr><td class="sstitle" colspan="2">SCSI Disks</td></tr>
<tr><td class="field">ATA OCZ-AGILITY2</td><td class="value"></td></tr>
<tr><td class="field">Optiarc BD ROM BC-5500S</td><td class="value"></td></tr>
</tbody></table><table><tbody>
<tr><td class="stitle" colspan="2">Operating System</td></tr>
<tr><td class="sstitle" colspan="2">Version</td></tr>
<tr><td class="field">Kernel</td><td class="value">Linux 2.6.38-gentoophobos (x86_64)</td></tr>
<tr><td class="field">Compiled</td><td class="value">#2 SMP PREEMPT Fri Mar 25 23:36:39 CET 2011</td></tr>
<tr><td class="field">C Library</td><td class="value">GNU C Library version 2.11.3 (stable)</td></tr>
<tr><td class="field">Default C Compiler</td><td class="value">GNU C Compiler version 4.4.5 (Gentoo 4.4.5 p1.2, pie-0.4.5) </td></tr>
<tr><td class="field">Distribution</td><td class="value">Gentoo Base System release 2.0.2</td></tr>
<tr><td class="sstitle" colspan="2">Current Session</td></tr>
<tr><td class="field">Computer Name</td><td class="value">phobos</td></tr>
<tr><td class="field">User Name</td><td class="value">fabio (Unknown)</td></tr>
<tr><td class="field">Home Directory</td><td class="value">/home/fabio</td></tr>
<tr><td class="field">Desktop Environment</td><td class="value">GNOME </td></tr>
<tr><td class="sstitle" colspan="2">Misc</td></tr>
<tr><td class="field">Uptime</td><td class="value">4 hours, 31 minutes</td></tr>
<tr><td class="field">Load Average</td><td class="value">0,00, 0,00, 0,00</td></tr>
</tbody></table><table><tbody>
<tr><td class="stitle" colspan="2">Display</td></tr>
<tr><td class="sstitle" colspan="2">Display</td></tr>
<tr><td class="field">Resolution</td><td class="value">2720x900 pixels</td></tr>
<tr><td class="field">Vendor</td><td class="value">The X.Org Foundation</td></tr>
<tr><td class="field">Version</td><td class="value">1.10.0.901</td></tr>
<tr><td class="sstitle" colspan="2">Monitors</td></tr>
<tr><td class="field">Monitor 0</td><td class="value">1440x900 pixels</td></tr>
<tr><td class="field">Monitor 1</td><td class="value">1280x800 pixels</td></tr>
<tr><td class="sstitle" colspan="2">Extensions</td></tr>
<tr><td class="field">BIG-REQUESTS</td><td class="value"></td></tr>
<tr><td class="field">Composite</td><td class="value"></td></tr>
<tr><td class="field">DAMAGE</td><td class="value"></td></tr>
<tr><td class="field">DOUBLE-BUFFER</td><td class="value"></td></tr>
<tr><td class="field">DPMS</td><td class="value"></td></tr>
<tr><td class="field">DRI2</td><td class="value"></td></tr>
<tr><td class="field">GLX</td><td class="value"></td></tr>
<tr><td class="field">Generic Event Extension</td><td class="value"></td></tr>
<tr><td class="field">MIT-SCREEN-SAVER</td><td class="value"></td></tr>
<tr><td class="field">MIT-SHM</td><td class="value"></td></tr>
<tr><td class="field">RANDR</td><td class="value"></td></tr>
<tr><td class="field">RECORD</td><td class="value"></td></tr>
<tr><td class="field">RENDER</td><td class="value"></td></tr>
<tr><td class="field">SGI-GLX</td><td class="value"></td></tr>
<tr><td class="field">SHAPE</td><td class="value"></td></tr>
<tr><td class="field">SYNC</td><td class="value"></td></tr>
<tr><td class="field">X-Resource</td><td class="value"></td></tr>
<tr><td class="field">XC-MISC</td><td class="value"></td></tr>
<tr><td class="field">XFIXES</td><td class="value"></td></tr>
<tr><td class="field">XFree86-DGA</td><td class="value"></td></tr>
<tr><td class="field">XFree86-VidModeExtension</td><td class="value"></td></tr>
<tr><td class="field">XINERAMA</td><td class="value"></td></tr>
<tr><td class="field">XInputExtension</td><td class="value"></td></tr>
<tr><td class="field">XKEYBOARD</td><td class="value"></td></tr>
<tr><td class="field">XTEST</td><td class="value"></td></tr>
<tr><td class="field">XVideo</td><td class="value"></td></tr>
<tr><td class="field">XVideo-MotionCompensation</td><td class="value"></td></tr>
<tr><td class="sstitle" colspan="2">OpenGL</td></tr>
<tr><td class="field">Vendor</td><td class="value">Tungsten Graphics, Inc</td></tr>
<tr><td class="field">Renderer</td><td class="value">Mesa DRI Mobile Intel® GM45 Express Chipset </td></tr>
<tr><td class="field">Version</td><td class="value">2.1 Mesa 7.11-devel (git-6638b4a)</td></tr>
<tr><td class="field">Direct Rendering</td><td class="value">Yes</td></tr>
</tbody></table><h1 class="title">Benchmarks</h1><table><tbody>
<tr><td class="stitle" colspan="2">CPU Blowfish</td></tr>
<tr><td class="sstitle" colspan="3">CPU Blowfish</td></tr>
<tr> <td class="field"><big><b>This Machine</b></big></td><td class="value">2931 MHz</td><td class="value">5,920</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 CPU E8400@ 3.00GHz</td><td class="value">3000 MHz</td><td class="value">5.826</td></tr>
<tr> <td class="field">3x AMD Phenom(tm) II X4 B55 Processor</td><td class="value">800 MHz</td><td class="value">3.712</td></tr>
<tr> <td class="field">2x AMD Turion Dual-Core ZM-80</td><td class="value">500 MHz</td><td class="value">10.113</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU E5335@ 2.00GHz</td><td class="value">1994 MHz</td><td class="value">2.147</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 QuadCPU Q9300@ 2.50GHz</td><td class="value">2490 MHz</td><td class="value">15.247</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) 4 CPU 2.40GHz</td><td class="value">2400 MHz</td><td class="value">28.295</td></tr>
<tr> <td class="field">PowerPC 7455, altivec supported (667.00MHz)</td><td class="value">667 MHz</td><td class="value">110.997</td></tr>
<tr> <td class="field">Intel(R) Xeon(R) CPU E5520@ 2.27GHz</td><td class="value">2260 MHz</td><td class="value">13.218</td></tr>
<tr> <td class="field">AMD Athlon(tm) XP</td><td class="value">906 MHz</td><td class="value">27.902</td></tr>
<tr> <td class="field">AMD Phenom(tm) II X4 B50 Processor</td><td class="value">800 MHz</td><td class="value">11.535</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Quad CPU @ 2.93GHz</td><td class="value">1603 MHz</td><td class="value">2.817</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(R) CPU X3210@ 2.13GHz</td><td class="value">2133 MHz</td><td class="value">3.883</td></tr>
<tr> <td class="field">16x Intel(R) Xeon(R) CPU E5530@ 2.40GHz</td><td class="value">1600 MHz</td><td class="value">1.390</td></tr>
<tr> <td class="field">Intel(R) Xeon(TM) CPU 2.80GHz</td><td class="value">2793 MHz</td><td class="value">21.438</td></tr>
<tr> <td class="field">Mobile AMD Sempron(tm) Processor 3400+</td><td class="value">800 MHz</td><td class="value">23.324</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) Dual Core Processor 5050e</td><td class="value">2600 MHz</td><td class="value">7.391</td></tr>
<tr> <td class="field">2x AMD Athlon(TM) MP 2800+</td><td class="value">2152 MHz</td><td class="value">8.469</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPU560@ 2.13GHz</td><td class="value">2128 MHz</td><td class="value">18.709</td></tr>
<tr> <td class="field">3x AMD Athlon(tm) II X3 400e Processor</td><td class="value">800 MHz</td><td class="value">6.473</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) 4 CPU 1.60GHz</td><td class="value">1595 MHz</td><td class="value">37.012</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) i7 CPU 960@ 3.20GHz</td><td class="value">3201 MHz</td><td class="value">2.003</td></tr>
<tr> <td class="field">2x AMD Turion(tm) II Dual-Core Mobile M500</td><td class="value">1500 MHz</td><td class="value">10.689</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM) i7 CPU 930@ 2.80GHz</td><td class="value">2806 MHz</td><td class="value">8.070</td></tr>
<tr> <td class="field">AMD Athlon(tm) 64 Processor 3700+</td><td class="value">1000 MHz</td><td class="value">19.016</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) II N930 Quad-Core Processor</td><td class="value">800 MHz</td><td class="value">4.986</td></tr>
<tr> <td class="field">AMD Sempron(tm) Processor 140 Processor</td><td class="value">2713 MHz</td><td class="value">15.204</td></tr>
<tr> <td class="field">mobile AMD Athlon(tm) XP 2600+</td><td class="value">1662 MHz</td><td class="value">20.237</td></tr>
<tr> <td class="field">4x Intel(R) Atom(TM) CPU D510 @ 1.66GHz</td><td class="value">1667 MHz</td><td class="value">8.336</td></tr>
<tr> <td class="field">2x Quad-Core AMD Opteron(tm) Processor 8346 HE</td><td class="value">1800 MHz</td><td class="value">34.820</td></tr>
<tr> <td class="field">12x Intel(R) Core(TM) i7 CPU X 980@ 3.33GHz</td><td class="value">3334 MHz</td><td class="value">1.238</td></tr>
<tr> <td class="field">AMD Athlon(tm) 64 X2 Dual Core Processor 4400+</td><td class="value">2300 MHz</td><td class="value">17.847</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU E8400@ 3.00GHz</td><td class="value">2997 MHz</td><td class="value">6.276</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 CPU T5600@ 1.83GHz</td><td class="value">1819 MHz</td><td class="value">21.763</td></tr>
<tr> <td class="field">3x AMD Processor model unknown</td><td class="value">2812 MHz</td><td class="value">5.933</td></tr>
<tr> <td class="field">Pentium(R) Dual-CoreCPUE6500@ 2.93GHz</td><td class="value">2933 MHz</td><td class="value">12.963</td></tr>
<tr> <td class="field">AMD Sempron(tm) Processor LE-1100</td><td class="value">1908 MHz</td><td class="value">20.762</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) II X4 B35 Processor</td><td class="value">800 MHz</td><td class="value">3.317</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU L7500@ 1.60GHz</td><td class="value">800 MHz</td><td class="value">10.860</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU T5470@ 1.60GHz</td><td class="value">800 MHz</td><td class="value">11.737</td></tr>
<tr> <td class="field">2x AMD Phenom(tm) 9750 Quad-Core Processor</td><td class="value">2411 MHz</td><td class="value">10.010</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) Neo X2 Dual Core Processor L325</td><td class="value">1500 MHz</td><td class="value">15.456</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 64 X2 Dual Core Processor 4200+</td><td class="value">2200 MHz</td><td class="value">9.421</td></tr>
<tr> <td class="field">4x QEMU Virtual CPU version 0.12.3</td><td class="value">2600 MHz</td><td class="value">4.001</td></tr>
<tr> <td class="field">AMD Athlon(TM) XP1700+</td><td class="value">1477 MHz</td><td class="value">33.429</td></tr>
<tr> <td class="field">2x AMD Turion(tm) 64 X2 TL-60</td><td class="value">800 MHz</td><td class="value">9.704</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(R) CPU5110@ 1.60GHz</td><td class="value">1600 MHz</td><td class="value">5.695</td></tr>
<tr> <td class="field">Intel(R) Celeron(TM) CPU1133MHz</td><td class="value">1133 MHz</td><td class="value">30.195</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) M processor 2.00GHz</td><td class="value">800 MHz</td><td class="value">19.526</td></tr>
<tr> <td class="field">3x AMD Phenom(tm) II X4 B25 Processor</td><td class="value">800 MHz</td><td class="value">5.014</td></tr>
<tr> <td class="field">PowerPC 7447A, altivec supported (1199,00MHz)</td><td class="value">1199 MHz</td><td class="value">55.119</td></tr>
</tbody></table><table><tbody>
<tr><td class="stitle" colspan="3">CPU CryptoHash</td></tr>
<tr><td class="sstitle" colspan="3">CPU CryptoHash</td></tr>
<tr> <td class="field"><big><b>This Machine</b></big></td><td class="value">2931 MHz</td><td class="value">233,770</td></tr>
<tr> <td class="field">AMD Athlon(tm)X2 DualCore QL-66</td><td class="value">2199 MHz</td><td class="value">73.730</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) 4 CPU 2.40GHz</td><td class="value">2400 MHz</td><td class="value">33.048</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(R) CPU5130@ 2.00GHz</td><td class="value">1995 MHz</td><td class="value">163.272</td></tr>
<tr> <td class="field">4x AMD Athlon(tm) II X4 620 Processor</td><td class="value">800 MHz</td><td class="value">343.159</td></tr>
<tr> <td class="field">2x AMD Turion(tm)X2 Ultra DualCore Mobile ZM-86</td><td class="value">600 MHz</td><td class="value">145.530</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU E5405@ 2.00GHz</td><td class="value">2000 MHz</td><td class="value">319.166</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) i7 CPU 880@ 3.07GHz</td><td class="value">1200 MHz</td><td class="value">534.361</td></tr>
<tr> <td class="field">mobile AMD Athlon (tm) 2400+</td><td class="value">1192 MHz</td><td class="value">42.536</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 CPU E7400@ 2.80GHz</td><td class="value">2800 MHz</td><td class="value">154.330</td></tr>
<tr> <td class="field">AMD Athlon(tm) II X4 630 Processor</td><td class="value">2765 MHz</td><td class="value">93.469</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU L9600@ 2.13GHz</td><td class="value">2128 MHz</td><td class="value">146.564</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 CPU T5500@ 1.66GHz</td><td class="value">1663 MHz</td><td class="value">53.691</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) D CPU430@ 1.80GHz</td><td class="value">1795 MHz</td><td class="value">71.959</td></tr>
<tr> <td class="field">AMD Phenom(tm) II X4 20 Processor</td><td class="value">2800 MHz</td><td class="value">93.492</td></tr>
<tr> <td class="field">2x Genuine Intel(R) CPU U7300@ 1.30GHz</td><td class="value">800 MHz</td><td class="value">107.032</td></tr>
<tr> <td class="field">AMD Turion(tm) 64 Mobile Technology ML-37</td><td class="value">2000 MHz</td><td class="value">60.043</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Extreme CPU X9100@ 3.06GHz</td><td class="value">3059 MHz</td><td class="value">130.311</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i5 CPU U 430@ 1.20GHz</td><td class="value">666 MHz</td><td class="value">130.074</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) 4 CPU 1.80GHz</td><td class="value">1793 MHz</td><td class="value">24.153</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i3 CPU M 330@ 2.13GHz</td><td class="value">933 MHz</td><td class="value">185.807</td></tr>
<tr> <td class="field">2x AMD Turion(tm) II Ultra Dual-Core Mobile M600</td><td class="value">2394 MHz</td><td class="value">142.027</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU E5462@ 2.80GHz</td><td class="value">2400 MHz</td><td class="value">438.856</td></tr>
<tr> <td class="field">Mobile AMD Athlon(tm) XP 3000+</td><td class="value">796 MHz</td><td class="value">73.180</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU T5870@ 2.00GHz</td><td class="value">800 MHz</td><td class="value">137.656</td></tr>
<tr> <td class="field">Mobile Intel(R) Pentium(R) III CPU - M1200MHz</td><td class="value">798 MHz</td><td class="value">42.472</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) X2 Dual Core Processor BE-2400</td><td class="value">2305 MHz</td><td class="value">114.074</td></tr>
<tr> <td class="field">3x AMD Athlon(tm) II X3 440 Processor</td><td class="value">800 MHz</td><td class="value">300.933</td></tr>
<tr> <td class="field">2x AMD Turion(tm) II Ultra Dual-Core Mobile M640</td><td class="value">800 MHz</td><td class="value">168.257</td></tr>
<tr> <td class="field">4x Intel(R) Atom(TM) CPU N550 @ 1.50GHz</td><td class="value">1000 MHz</td><td class="value">96.765</td></tr>
<tr> <td class="field">3x AMD Athlon(tm) II X3 445 Processor</td><td class="value">3115 MHz</td><td class="value">313.132</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Extreme CPU X9770@ 3.20GHz</td><td class="value">2403 MHz</td><td class="value">455.964</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) D CPU 3.00GHz</td><td class="value">3000 MHz</td><td class="value">44.463</td></tr>
<tr> <td class="field">Mobile Intel(R) Pentium(R) 4 CPU 2.30GHz</td><td class="value">1600 MHz</td><td class="value">27.748</td></tr>
<tr> <td class="field">AMD Turion(tm) 64 Mobile ML-30</td><td class="value">800 MHz</td><td class="value">25.497</td></tr>
<tr> <td class="field">2x Intel(R) Pentium(R)CPU E6500@ 2.93GHz</td><td class="value">2932 MHz</td><td class="value">121.046</td></tr>
<tr> <td class="field">AMD Phenom(tm) II X4 945 Processor</td><td class="value">2947 MHz</td><td class="value">113.383</td></tr>
<tr> <td class="field">2x Intel(R) Pentium(R) DualCPUT2310@ 1.46GHz</td><td class="value">1463 MHz</td><td class="value">91.247</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU T6400@ 2.00GHz</td><td class="value">1200 MHz</td><td class="value">140.312</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) D CPU 3.06GHz</td><td class="value">3067 MHz</td><td class="value">53.712</td></tr>
<tr> <td class="field">AMD Sempron(tm)</td><td class="value">1663 MHz</td><td class="value">55.622</td></tr>
<tr> <td class="field">AMD Athlon(tm) XP 1600</td><td class="value">1400 MHz</td><td class="value">42.170</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+</td><td class="value">2200 MHz</td><td class="value">116.812</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU E7300@ 2.66GHz</td><td class="value">1600 MHz</td><td class="value">190.853</td></tr>
<tr> <td class="field">4x Intel(R) XEON(TM) CPU 2.20GHz</td><td class="value">2181 MHz</td><td class="value">90.292</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) i7 CPU 940@ 2.93GHz</td><td class="value">1600 MHz</td><td class="value">442.497</td></tr>
<tr> <td class="field">2x Intel(R) Xeon(R) CPU3065@ 2.33GHz</td><td class="value">3500 MHz</td><td class="value">191.399</td></tr>
<tr> <td class="field">AMD Athlon(tm)2200+</td><td class="value">1800 MHz</td><td class="value">54.759</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU P8400@ 2.26GHz</td><td class="value">800 MHz</td><td class="value">151.935</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) M processor 1600MHz</td><td class="value">1600 MHz</td><td class="value">52.018</td></tr>
<tr> <td class="field">AMD Athlon(tm) XP 2100+</td><td class="value">1746 MHz</td><td class="value">50.098</td></tr>
</tbody></table><table><tbody>
<tr><td class="stitle" colspan="3">CPU Fibonacci</td></tr>
<tr><td class="sstitle" colspan="3">CPU Fibonacci</td></tr>
<tr> <td class="field"><big><b>This Machine</b></big></td><td class="value">2931 MHz</td><td class="value">2,791</td></tr>
<tr> <td class="field">3x AMD Phenom(tm) II X4 20 Processor</td><td class="value">800 MHz</td><td class="value">2.351</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(R) CPU X3350@ 2.66GHz</td><td class="value">2666 MHz</td><td class="value">2.843</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU P7700@ 1.80GHz</td><td class="value">1800 MHz</td><td class="value">5.374</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU P8800@ 2.66GHz</td><td class="value">1596 MHz</td><td class="value">3.118</td></tr>
<tr> <td class="field">2x Intel(R) Atom(TM) CPU330 @ 1.60GHz</td><td class="value">1595 MHz</td><td class="value">8.312</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 CPU E7400@ 2.80GHz</td><td class="value">2800 MHz</td><td class="value">3.866</td></tr>
<tr> <td class="field">2x AMD Turion(tm) 64 X2 TL-62</td><td class="value">800 MHz</td><td class="value">4.167</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU U7600@ 1.20GHz</td><td class="value">800 MHz</td><td class="value">7.715</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) i7 CPU 930@ 2.80GHz</td><td class="value">2834 MHz</td><td class="value">2.366</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) M processor 2.10GHz</td><td class="value">2100 MHz</td><td class="value">17.899</td></tr>
<tr> <td class="field">mobile AMD Athlon(tm) XP 2000+</td><td class="value">1666 MHz</td><td class="value">5.185</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 64 X2 Dual-Core Processor TK-57</td><td class="value">1900 MHz</td><td class="value">4.659</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i3 CPU M 380@ 2.53GHz</td><td class="value">2533 MHz</td><td class="value">2.275</td></tr>
<tr> <td class="field">Mobile Intel(R) Pentium(R) 4 - M CPU 1.90GHz</td><td class="value">1900 MHz</td><td class="value">8.739</td></tr>
<tr> <td class="field">AMD Athlon(tm) II X4 630 Processor</td><td class="value">2765 MHz</td><td class="value">2.542</td></tr>
<tr> <td class="field">Pentium(R) Dual-CoreCPUE5300@ 2.60GHz</td><td class="value">2590 MHz</td><td class="value">3.225</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) II X4 910 Processor</td><td class="value">2600 MHz</td><td class="value">2.309</td></tr>
<tr> <td class="field">2x Intel(R) Xeon(R) CPU E5530@ 2.40GHz</td><td class="value">2400 MHz</td><td class="value">2.817</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 QuadCPU Q9300@ 2.50GHz</td><td class="value">2490 MHz</td><td class="value">3.461</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) 4 CPU 2.53GHz</td><td class="value">2525 MHz</td><td class="value">6.155</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) III CPU - S 1400MHz</td><td class="value">1392 MHz</td><td class="value">7.740</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPU723@ 1.20GHz</td><td class="value">1196 MHz</td><td class="value">6.910</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(R) CPU E5405@ 2.00GHz</td><td class="value">1995 MHz</td><td class="value">3.925</td></tr>
<tr> <td class="field">AMD Sempron(tm) 2200+</td><td class="value">1494 MHz</td><td class="value">5.974</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) II N930 Quad-Core Processor</td><td class="value">800 MHz</td><td class="value">3.461</td></tr>
<tr> <td class="field">AMD Athlon(tm) XP 1600</td><td class="value">1400 MHz</td><td class="value">5.815</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i5 CPU M 450@ 2.40GHz</td><td class="value">2400 MHz</td><td class="value">2.871</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM) i7 CPU 920@ 2.67GHz</td><td class="value">2659 MHz</td><td class="value">2.334</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPU 2.50GHz</td><td class="value">2492 MHz</td><td class="value">6.037</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU T7500@ 2.20GHz</td><td class="value">800 MHz</td><td class="value">4.399</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) X2 Dual Core Processor BE-2400</td><td class="value">2305 MHz</td><td class="value">3.916</td></tr>
<tr> <td class="field">2x Intel(R) Xeon(R) CPU5148@ 2.33GHz</td><td class="value">2327 MHz</td><td class="value">4.215</td></tr>
<tr> <td class="field">Mobile AMD Athlon(tm) 64 Processor 3700+</td><td class="value">1600 MHz</td><td class="value">3.298</td></tr>
<tr> <td class="field">3x AMD Phenom(tm) II X3 710 Processor</td><td class="value">800 MHz</td><td class="value">2.528</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Extreme CPU X9650@ 3.00GHz</td><td class="value">1998 MHz</td><td class="value">2.656</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Extreme CPU X9770@ 3.20GHz</td><td class="value">2403 MHz</td><td class="value">2.439</td></tr>
<tr> <td class="field">2x Intel(R) Atom(TM) CPU Z530 @ 1.60GHz</td><td class="value">1067 MHz</td><td class="value">8.438</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU T5750@ 2.00GHz</td><td class="value">1994 MHz</td><td class="value">4.962</td></tr>
<tr> <td class="field">Mobile AMD Sempron(tm) Processor 2100+</td><td class="value">1000 MHz</td><td class="value">7.000</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) processor600MHz</td><td class="value">598 MHz</td><td class="value">17.849</td></tr>
<tr> <td class="field">mobile AMD Athlon(tm) XP 1500+</td><td class="value">500 MHz</td><td class="value">7.971</td></tr>
<tr> <td class="field">PowerPC 740/750 (350.00MHz)</td><td class="value">350 MHz</td><td class="value">44.427</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) III CPU family1400MHz</td><td class="value">1048 MHz</td><td class="value">12.665</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Extreme CPU X7900@ 2.80GHz</td><td class="value">2800 MHz</td><td class="value">3.652</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU X3460@ 2.80GHz</td><td class="value">1197 MHz</td><td class="value">2.026</td></tr>
<tr> <td class="field">2x Intel(R) Pentium(R) 4 CPU 3.40GHz</td><td class="value">2400 MHz</td><td class="value">4.132</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(TM) MP CPU 2.50GHz</td><td class="value">2500 MHz</td><td class="value">4.623</td></tr>
<tr> <td class="field">AMD Athlon(tm) XP 2200+</td><td class="value">1782 MHz</td><td class="value">5.313</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i3 CPU 560@ 3.33GHz</td><td class="value">1197 MHz</td><td class="value">2.016</td></tr>
<tr> <td class="field">2x AMD Turion(tm)X2 Ultra DualCore Mobile ZM-86</td><td class="value">600 MHz</td><td class="value">3.755</td></tr>
</tbody></table><table><tbody>
<tr><td class="stitle" colspan="3">CPU N-Queens</td></tr>
<tr><td class="sstitle" colspan="3">CPU N-Queens</td></tr>
<tr> <td class="field"><big><b>This Machine</b></big></td><td class="value">2931 MHz</td><td class="value">6,671</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) X2 Dual Core Processor BE-2400</td><td class="value">2305 MHz</td><td class="value">14.981</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) i7 CPU 930@ 2.80GHz</td><td class="value">2834 MHz</td><td class="value">0.780</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU E5430@ 2.66GHz</td><td class="value">2000 MHz</td><td class="value">0.805</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) Dual Core Processor 5000B</td><td class="value">1000 MHz</td><td class="value">14.474</td></tr>
<tr> <td class="field">2x Intel(R) Atom(TM) CPU N475 @ 1.83GHz</td><td class="value">1000 MHz</td><td class="value">16.703</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU E5345@ 2.33GHz</td><td class="value">1998 MHz</td><td class="value">0.964</td></tr>
<tr> <td class="field">Intel(R) Xeon(TM) CPU 2.80GHz</td><td class="value">2793 MHz</td><td class="value">9.811</td></tr>
<tr> <td class="field">8x Quad-Core AMD Opteron(tm) Processor 2378</td><td class="value">800 MHz</td><td class="value">0.828</td></tr>
<tr> <td class="field">16x AMD Opteron(tm) Processor 6136</td><td class="value">2400 MHz</td><td class="value">0.861</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 64 X2 Dual Core Processor 5000+</td><td class="value">1000 MHz</td><td class="value">15.152</td></tr>
<tr> <td class="field">AMD Athlon(tm) Processor LE-1640</td><td class="value">1000 MHz</td><td class="value">10.766</td></tr>
<tr> <td class="field">Mobile Intel(R) Celeron(TM) CPU 1200MHz</td><td class="value">1200 MHz</td><td class="value">19.105</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(TM) CPU 2.80GHz</td><td class="value">2800 MHz</td><td class="value">19.470</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 Quad CPUQ8300@ 2.50GHz</td><td class="value">2500 MHz</td><td class="value">9.144</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU W5580@ 3.20GHz</td><td class="value">3193 MHz</td><td class="value">0.831</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Quad CPUQ9550@ 2.83GHz</td><td class="value">2830 MHz</td><td class="value">15.537</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) M processor 1400MHz</td><td class="value">1396 MHz</td><td class="value">17.709</td></tr>
<tr> <td class="field">AMD Sempron(tm) 2200+</td><td class="value">1494 MHz</td><td class="value">18.257</td></tr>
<tr> <td class="field">2x Dual-Core AMD Opteron(tm) Processor 1210</td><td class="value">1800 MHz</td><td class="value">19.977</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPU 2.20GHz</td><td class="value">2194 MHz</td><td class="value">14.588</td></tr>
<tr> <td class="field">2x Pentium(R) Dual-CoreCPUE2210@ 2.20GHz</td><td class="value">2199 MHz</td><td class="value">10.997</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU E6850@ 3.00GHz</td><td class="value">1998 MHz</td><td class="value">7.157</td></tr>
<tr> <td class="field">2x Intel(R) Pentium(R) DualCPUT2410@ 2.00GHz</td><td class="value">800 MHz</td><td class="value">11.984</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 Duo CPU E6750@ 2.66GHz</td><td class="value">2656 MHz</td><td class="value">9.363</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 CPU T5500@ 1.66GHz</td><td class="value">1000 MHz</td><td class="value">25.132</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) MP 2400+</td><td class="value">1800 MHz</td><td class="value">31.882</td></tr>
<tr> <td class="field">AMD Phenom(tm) II X4 840T Processor</td><td class="value">2893 MHz</td><td class="value">6.978</td></tr>
<tr> <td class="field">Pentium(R) Dual-CoreCPUE5200@ 2.50GHz</td><td class="value">2500 MHz</td><td class="value">9.247</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) D CPU 3.33GHz</td><td class="value">3341 MHz</td><td class="value">9.402</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPUE3300@ 2.50GHz</td><td class="value">3003 MHz</td><td class="value">8.339</td></tr>
<tr> <td class="field">Genuine Intel(R) CPU 2.30GHz</td><td class="value">2300 MHz</td><td class="value">11.033</td></tr>
<tr> <td class="field">mobile AMD Athlon(tm) XP 1500+</td><td class="value">500 MHz</td><td class="value">22.843</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 Quad CPUQ6600@ 2.40GHz</td><td class="value">2400 MHz</td><td class="value">11.222</td></tr>
<tr> <td class="field">3x AMD Phenom(tm) II P820 Triple-Core Processor</td><td class="value">1800 MHz</td><td class="value">13.754</td></tr>
<tr> <td class="field">2x AMD Turion(tm) X2 Dual Core Processor L510</td><td class="value">1600 MHz</td><td class="value">19.342</td></tr>
<tr> <td class="field">Mobile AMD Athlon(tm) 64 Processor 2700+</td><td class="value">800 MHz</td><td class="value">22.194</td></tr>
<tr> <td class="field">Intel(R) Celeron(TM) CPU1066MHz</td><td class="value">733 MHz</td><td class="value">25.309</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 Duo CPU E7200@ 2.53GHz</td><td class="value">2534 MHz</td><td class="value">13.035</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) II X4 840T Processor</td><td class="value">800 MHz</td><td class="value">9.612</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 Duo CPU E7300@ 2.66GHz</td><td class="value">2644 MHz</td><td class="value">9.051</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) 9500 Quad-Core Processor</td><td class="value">1100 MHz</td><td class="value">10.745</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) M processor600MHz</td><td class="value">599 MHz</td><td class="value">37.586</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 64 X2 Dual Core Processor 5800+</td><td class="value">1000 MHz</td><td class="value">16.877</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPU 2.00GHz</td><td class="value">2000 MHz</td><td class="value">14.716</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) 4 CPU 1.50GHz</td><td class="value">1496 MHz</td><td class="value">22.283</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Quad CPUQ8200@ 2.33GHz</td><td class="value">2333 MHz</td><td class="value">19.451</td></tr>
<tr> <td class="field">Genuine Intel(R) CPU U1300@ 1.06GHz</td><td class="value">1067 MHz</td><td class="value">22.400</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) CPUQ 820@ 1.73GHz</td><td class="value">1199 MHz</td><td class="value">0.824</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) III Mobile CPU1133MHz</td><td class="value">1132 MHz</td><td class="value">25.935</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) i7 CPU 920@ 2.67GHz</td><td class="value">3799 MHz</td><td class="value">0.901</td></tr>
</tbody></table><table><tbody>
<tr><td class="stitle" colspan="3">FPU FFT</td></tr>
<tr><td class="sstitle" colspan="3">FPU FFT</td></tr>
<tr> <td class="field"><big><b>This Machine</b></big></td><td class="value">2931 MHz</td><td class="value">2,815</td></tr>
<tr> <td class="field">AMD Phenom(tm) 9650 Quad-Core Processor</td><td class="value">2311 MHz</td><td class="value">9.766</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU E5620@ 2.40GHz</td><td class="value">2394 MHz</td><td class="value">1.614</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) DualCPUE2160@ 1.80GHz</td><td class="value">1781 MHz</td><td class="value">19.621</td></tr>
<tr> <td class="field">06/17</td><td class="value">2333 MHz</td><td class="value">7.746</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) Neo X2 Dual Core Processor L335</td><td class="value">1600 MHz</td><td class="value">11.173</td></tr>
<tr> <td class="field">AMD Athlon(tm) Processor TF-20</td><td class="value">1600 MHz</td><td class="value">25.298</td></tr>
<tr> <td class="field">2x Genuine Intel(R) CPU T2250@ 1.73GHz</td><td class="value">1729 MHz</td><td class="value">5.568</td></tr>
<tr> <td class="field">Mobile Intel(R) Celeron(R) CPU 1.50GHz</td><td class="value">1495 MHz</td><td class="value">15.404</td></tr>
<tr> <td class="field">2x AMD Phenom(tm) II X4 B50 Processor</td><td class="value">3084 MHz</td><td class="value">3.131</td></tr>
<tr> <td class="field">AMD Athlon(tm) XP 2900+</td><td class="value">1992 MHz</td><td class="value">16.063</td></tr>
<tr> <td class="field">Mobile AMD Athlon(tm) 64 Processor 3400+</td><td class="value">2194 MHz</td><td class="value">15.352</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 Duo CPU L9400@ 1.86GHz</td><td class="value">1862 MHz</td><td class="value">8.677</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) III CPU 1200MHz</td><td class="value">1202 MHz</td><td class="value">38.002</td></tr>
<tr> <td class="field">PowerPC 7447A, altivec supported (1420,00MHz)</td><td class="value">1420 MHz</td><td class="value">45.506</td></tr>
<tr> <td class="field">AMD Sempron(tm) Processor 3100+</td><td class="value">1980 MHz</td><td class="value">19.988</td></tr>
<tr> <td class="field">Mobile AMD Sempron(tm) Processor 4000+</td><td class="value">2200 MHz</td><td class="value">14.398</td></tr>
<tr> <td class="field">AMD Duron(tm) procwss{</td><td class="value">1792 MHz</td><td class="value">19.122</td></tr>
<tr> <td class="field">AMD V120 Processor</td><td class="value">2200 MHz</td><td class="value">9.320</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Quad CPU @ 2.93GHz</td><td class="value">1603 MHz</td><td class="value">1.372</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) DualCPUT2370@ 1.73GHz</td><td class="value">1729 MHz</td><td class="value">10.083</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i3 CPU 560@ 3.33GHz</td><td class="value">1197 MHz</td><td class="value">1.325</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i3 CPU 550@ 3.20GHz</td><td class="value">1200 MHz</td><td class="value">1.354</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) i7 CPU 975@ 3.33GHz</td><td class="value">1596 MHz</td><td class="value">1.046</td></tr>
<tr> <td class="field">AMD Sempron(tm) 2200+</td><td class="value">1512 MHz</td><td class="value">40.664</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) D CPU 3.00GHz</td><td class="value">3000 MHz</td><td class="value">9.258</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Quad CPUQ6700@ 2.66GHz</td><td class="value">2669 MHz</td><td class="value">1.511</td></tr>
<tr> <td class="field">2x Dual-Core AMD Opteron(tm) Processor 1210</td><td class="value">1800 MHz</td><td class="value">9.780</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU E7400@ 2.80GHz</td><td class="value">2793 MHz</td><td class="value">3.267</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU@ 2.40GHz</td><td class="value">2400 MHz</td><td class="value">3.953</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPU420@ 1.60GHz</td><td class="value">1600 MHz</td><td class="value">12.370</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 64 X2 Dual Core Processor 4400+</td><td class="value">1000 MHz</td><td class="value">7.325</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i5 CPU M 560@ 2.67GHz</td><td class="value">1199 MHz</td><td class="value">1.381</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) Dual Core Processor 4850e</td><td class="value">2500 MHz</td><td class="value">7.387</td></tr>
<tr> <td class="field">VIA Nano processor U2250@1300+MHz</td><td class="value">1600 MHz</td><td class="value">37.459</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) II X4 B60 Processor</td><td class="value">3700 MHz</td><td class="value">1.187</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(R) CPU X3360@ 2.83GHz</td><td class="value">2003 MHz</td><td class="value">1.177</td></tr>
<tr> <td class="field">AMD Athlon(tm) XP 1700+</td><td class="value">1605 MHz</td><td class="value">26.810</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPU 2.50GHz</td><td class="value">2492 MHz</td><td class="value">12.003</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) 9850 Quad-Core Processor</td><td class="value">1300 MHz</td><td class="value">1.998</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Quad CPU @ 2.40GHz</td><td class="value">2400 MHz</td><td class="value">1.689</td></tr>
<tr> <td class="field">4x AMD Phenom(tm) 9650 Quad-Core Processor</td><td class="value">1200 MHz</td><td class="value">2.189</td></tr>
<tr> <td class="field">4x Quad-Core AMD Opteron(tm) Processor 1352</td><td class="value">2100 MHz</td><td class="value">2.198</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) D CPU220@ 1.20GHz</td><td class="value">1197 MHz</td><td class="value">18.565</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU U9300@ 1.20GHz</td><td class="value">800 MHz</td><td class="value">7.168</td></tr>
<tr> <td class="field">AMD Sempron(TM) 3000+</td><td class="value">2000 MHz</td><td class="value">18.028</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 7850 Dual-Core Processor</td><td class="value">1400 MHz</td><td class="value">3.796</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) CPUQ 720@ 1.60GHz</td><td class="value">933 MHz</td><td class="value">1.509</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(R) CPU5130@ 2.00GHz</td><td class="value">1995 MHz</td><td class="value">2.028</td></tr>
<tr> <td class="field">16x Intel(R) Xeon(R) CPU E5530@ 2.40GHz</td><td class="value">1600 MHz</td><td class="value">1.497</td></tr>
<tr> <td class="field">VIA Nehemiah</td><td class="value">532 MHz</td><td class="value">101.106</td></tr>
</tbody></table><table><tbody>
<tr><td class="stitle" colspan="3">FPU Raytracing</td></tr>
<tr><td class="sstitle" colspan="3">FPU Raytracing</td></tr>
<tr> <td class="field"><big><b>This Machine</b></big></td><td class="value">2931 MHz</td><td class="value">4,770</td></tr>
<tr> <td class="field">8x Quad-Core AMD Opteron(tm) Processor 2354</td><td class="value">2200 MHz</td><td class="value">21.655</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM)2 Quad CPUQ6700@ 2.66GHz</td><td class="value">2669 MHz</td><td class="value">22.647</td></tr>
<tr> <td class="field">8x Intel(R) Xeon(R) CPU E5345@ 2.33GHz</td><td class="value">1998 MHz</td><td class="value">38.008</td></tr>
<tr> <td class="field">AMD Phenom(tm) 9550 Quad-Core Processor</td><td class="value">2210 MHz</td><td class="value">22.880</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i3 CPU M 370@ 2.40GHz</td><td class="value">933 MHz</td><td class="value">16.552</td></tr>
<tr> <td class="field">Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz</td><td class="value">1200 MHz</td><td class="value">40.325</td></tr>
<tr> <td class="field">mobile AMD Athlon(tm) 4 1600+</td><td class="value">1395 MHz</td><td class="value">36.589</td></tr>
<tr> <td class="field">4x Intel(R) Xeon(TM) MP CPU 3.66GHz</td><td class="value">3670 MHz</td><td class="value">56.827</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) III CPU family1400MHz</td><td class="value">1048 MHz</td><td class="value">66.053</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) 4 CPU 1600MHz</td><td class="value">1593 MHz</td><td class="value">62.636</td></tr>
<tr> <td class="field">2x Intel(R) Pentium(R) 4 CPU 3.60GHz</td><td class="value">3600 MHz</td><td class="value">35.879</td></tr>
<tr> <td class="field">3x AMD Processor model unknown</td><td class="value">2812 MHz</td><td class="value">12.511</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) III Mobile CPU 700MHz</td><td class="value">700 MHz</td><td class="value">67.776</td></tr>
<tr> <td class="field">2x AMD Athlon(tm)X2 DualCore QL-60</td><td class="value">1900 MHz</td><td class="value">14.138</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 64 X2 Dual Core Processor 5600+</td><td class="value">2800 MHz</td><td class="value">11.763</td></tr>
<tr> <td class="field">AMD Turion(tm) 64 X2 Mobile Technology TL-56</td><td class="value">1795 MHz</td><td class="value">30.323</td></tr>
<tr> <td class="field">8x Quad-Core AMD Opteron(tm) Processor 2376</td><td class="value">1100 MHz</td><td class="value">28.869</td></tr>
<tr> <td class="field">Mobile AMD Sempron(tm) Processor 2800+</td><td class="value">1600 MHz</td><td class="value">32.144</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) DualCPUT2370@ 1.73GHz</td><td class="value">1729 MHz</td><td class="value">26.954</td></tr>
<tr> <td class="field">2x AMD Turion(tm) Neo X2 Dual Core Processor L625</td><td class="value">800 MHz</td><td class="value">20.530</td></tr>
<tr> <td class="field">4x Intel(R) Core(TM) i5 CPU M 450@ 2.40GHz</td><td class="value">2400 MHz</td><td class="value">11.516</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU U9300@ 1.20GHz</td><td class="value">800 MHz</td><td class="value">32.565</td></tr>
<tr> <td class="field">3x AMD Phenom(tm) II X4 B25 Processor</td><td class="value">800 MHz</td><td class="value">12.524</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) III Mobile CPU 866MHz</td><td class="value">665 MHz</td><td class="value">54.409</td></tr>
<tr> <td class="field">2x AMD Turion(tm) X2 Ultra Dual-Core Mobile ZM-82</td><td class="value">600 MHz</td><td class="value">15.310</td></tr>
<tr> <td class="field">2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+</td><td class="value">2200 MHz</td><td class="value">15.629</td></tr>
<tr> <td class="field">AMD Athlon(tm) Processor 2650e</td><td class="value">1596 MHz</td><td class="value">29.661</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) CPU 2.20GHz</td><td class="value">2194 MHz</td><td class="value">36.590</td></tr>
<tr> <td class="field">2x AMD Turion(tm) X2 Dual-Core Mobile RM-74</td><td class="value">600 MHz</td><td class="value">15.463</td></tr>
<tr> <td class="field">2x Intel(R) Xeon(TM) CPU 3.06GHz</td><td class="value">3057 MHz</td><td class="value">40.207</td></tr>
<tr> <td class="field">8x Intel(R) Core(TM) i7 CPU X 920@ 2.00GHz</td><td class="value">1199 MHz</td><td class="value">4.564</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU P8400@ 2.26GHz</td><td class="value">800 MHz</td><td class="value">14.968</td></tr>
<tr> <td class="field">Mobile Intel(R) Pentium(R) III CPU - M1066MHz</td><td class="value">731 MHz</td><td class="value">44.109</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU T5250@ 1.50GHz</td><td class="value">1000 MHz</td><td class="value">27.422</td></tr>
<tr> <td class="field">2x AMD Turion(tm) II Dual-Core Mobile M500</td><td class="value">1500 MHz</td><td class="value">15.168</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM) Duo CPUL2400@ 1.66GHz</td><td class="value">1000 MHz</td><td class="value">32.322</td></tr>
<tr> <td class="field">2x Pentium(R) Dual-CoreCPUE6700@ 3.20GHz</td><td class="value">2936 MHz</td><td class="value">8.206</td></tr>
<tr> <td class="field">2x Genuine Intel(R) CPU T2050@ 1.60GHz</td><td class="value">800 MHz</td><td class="value">34.504</td></tr>
<tr> <td class="field">AMD Athlon(tm) XP processor 1800+</td><td class="value">1533 MHz</td><td class="value">31.855</td></tr>
<tr> <td class="field">Mobile AMD Athlon(tm) XP 2800+</td><td class="value">1459 MHz</td><td class="value">36.889</td></tr>
<tr> <td class="field">Intel(R) Pentium(R) III Mobile CPU1200MHz</td><td class="value">798 MHz</td><td class="value">45.741</td></tr>
<tr> <td class="field">2x Intel(R) Core(TM)2 Duo CPU T7300@ 2.00GHz</td><td class="value">2001 MHz</td><td class="value">16.273</td></tr>
<tr> <td class="field">2x AMD Athlon(TM) MP 2800+</td><td class="value">2152 MHz</td><td class="value">26.849</td></tr>
<tr> <td class="field">2x AMD Phenom(tm) II X6 1035T Processor</td><td class="value">2604 MHz</td><td class="value">9.521</td></tr>
<tr> <td class="field">AMD Athlon(tm) 64 Processor 3700+</td><td class="value">1000 MHz</td><td class="value">21.169</td></tr>
<tr> <td class="field">Intel(R) Core(TM)2 Duo CPU E7500@ 2.93GHz</td><td class="value">1596 MHz</td><td class="value">13.547</td></tr>
<tr> <td class="field">AMD Turion(tm) 64 Mobile Technology MK-38</td><td class="value">2200 MHz</td><td class="value">20.935</td></tr>
<tr> <td class="field">Mobile Pentium II</td><td class="value">299 MHz</td><td class="value">151.837</td></tr>
<tr> <td class="field">AMD Athlon(tm) II X2 240 Processor</td><td class="value">4290 MHz</td><td class="value">14.928</td></tr>
<tr> <td class="field">Intel(R) Celeron(R) M processor800MHz</td><td class="value">569 MHz</td><td class="value">109.434</td></tr>
</tbody></table>Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-32738297304848106552011-03-23T13:19:00.000+01:002011-03-24T22:44:19.274+01:00Phctool bug with kernels 2.6.38<a href="https://lh5.googleusercontent.com/-H3uPYfwLFhY/TYnlGyaMz3I/AAAAAAAAAEU/sf97Vq373ng/s1600/Schermata-12.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="136" src="https://lh5.googleusercontent.com/-H3uPYfwLFhY/TYnlGyaMz3I/AAAAAAAAAEU/sf97Vq373ng/s320/Schermata-12.png" width="320" /></a>Hey guys,<br />
<br />
unfortunately another bug in phc and phctool.... with 2.6.38 kernel throttling interface has moved, so you get:<br />
<br />
<a name='more'></a><br />
<br />
<blockquote style="background-color: #9fc5e8;"><pre class="bz_comment_text"><span style="font-size: small;">Traceback (most recent call last):
File "./phctool.py", line 468, in <module>
app=appgui()
File "./phctool.py", line 83, in __init__
self.throttling=throttling.throttlecontrol(self.cpuinfo.data)
File "inc/libs/throttling.py", line 16, in __init__
self._cpus_have_interface() ##check which CPU has a trottling
interface
File "inc/libs/throttling.py", line 23, in _cpus_have_interface
if
os.path.exists('/proc/acpi/processor/'+self.cpus[cpu]['acpi']['acpiname']+'/throttling')
&
os.path.exists('/proc/acpi/processor/'+self.cpus[cpu]['acpi']['acpiname']+'/limit'):
KeyError: 'acpiname'</span></pre></blockquote><br />
this has already been reported to bugzilla, I wrote a patch but it's just a temporary solution, you can get it from here:<a href="https://bugs.gentoo.org/show_bug.cgi?id=360009"> https://bugs.gentoo.org/show_bug.cgi?id=360009 </a><br />
<br />
The file needs to be placed in<br />
<br />
<blockquote><span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">/usr/share/phctool/inc/libs/cpuinfo.py</span></blockquote> If anyone has some python skills and/or a CPU with throttling interface available (I don't), feel free to post a comment so we can solve this!<br />
<br />
<br />
CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com4tag:blogger.com,1999:blog-6007641906670981467.post-25450798428993255092011-02-20T23:34:00.005+01:002012-05-30T09:25:23.755+02:00Undervolting CPU in Ubuntu<div class="separator" style="clear: both; text-align: center;">
<a href="http://1.bp.blogspot.com/-31tKN_U1jfg/TWGWvtZD3dI/AAAAAAAAAEM/cu5jhu_cd2g/s1600/Schermata-7.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="136" src="http://1.bp.blogspot.com/-31tKN_U1jfg/TWGWvtZD3dI/AAAAAAAAAEM/cu5jhu_cd2g/s320/Schermata-7.png" width="320" /></a></div>
<div style="text-align: center;">
<br /></div>
Hi guys,<br />
<br />
as for MakeMKV I want to open another tool to Ubuntu users too: <a href="http://www.linux-phc.org/">PHC</a>. It stands for Processor Hardware Control and, as it's easy to understand, it allows users to customize some features of CPU control in a linux environment, as undervolting.<br />
<br />
<div style="text-align: center;">
Gentoo users should look at <a href="http://linuxsolver.blogspot.com/2010/10/cpu-downvoltage-downclock-and.html">this specific guide</a>! <br />
<br />
<br />
<span style="color: #0000ee; text-decoration: underline;"><a href="http://linuxsolver.blogspot.it/2012/03/cpu-undervolting-with-ubuntu-1110.html">!!UPDATED UBUNTU 11.10 VERSION!!!</a></span><br />
<span style="color: #0000ee; text-decoration: underline;"><a href="http://linuxsolver.blogspot.it/2012/05/undervolting-cpu-in-ubuntu-1204.html">!!UPDATED UBUNTU 12.04 VERSION!!!</a></span></div>
<br />
<a name='more'></a><br />
So what do we need? An Ubuntu (or Debian) box, usually undervolting is useful on laptops: it enhance battery duration and reduces the heat production. You will also need some time and patience, ;]<br />
<ol>
<li>You will need a kernel patch and a particular CPU driver so that the hardware control will be possible. First let's add the repo:<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
sudo add-apt-repository ppa:linux-phc/ppa<br />
sudo add-apt-repository ppa:linux-phc/testing <br />
sudo apt-get update</blockquote>
</li>
<li style="margin-top: 10px;">Now let's install the kernel and its headers:<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install linux-generic-phc linux-headers-generic-phc</span></blockquote>
First pause... restart your PC and be sure to choose your new *-phc kernel.<br />
</li>
<li style="margin-top: 10px;">As we will need to compile some stuff some Ubuntu users might need <br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install </span><span style="font-family: 'Courier New', Courier, monospace;">gtk2-engines-pixbuf python-gtk2-dev build-essential </span></blockquote>
And then:<br />
<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace;">sudo apt-get install dkms debhelper</span></blockquote>
Before doing anything else we have to create an empty file to match dmks autoconfiguration: Intel users go with the first, AMD with the second line!
<blockquote class="tr_bq">
<span style="font-family: 'Courier New', Courier, monospace;">sudo sh -c 'echo >> /etc/modprobe.d/phc-intel.conf'<br />sudo sh -c 'echo >> /etc/modprobe.d/phc-k8.conf'</span></blockquote>
<span style="font-family: 'Courier New', Courier, monospace;"></span><div style="margin-left: 40px;">
</div>
<br />
</li>
<li>Now you have to download the driver, choose it looking at your CPU: there are two choices<a href="http://www.linux-phc.org/forum/viewtopic.php?f=13&t=2"> AMD</a> and <a href="http://www.linux-phc.org/forum/viewtopic.php?f=7&t=267">Intel</a>, be sure to take the right one.</li>
<li>Unpack the package to a temporary folder. Open a terminal and move there:<span style="font-family: 'Courier New', Courier, monospace;"><blockquote>
cd **your_path** </blockquote>
</span><span style="font-family: 'Courier New', Courier, monospace;"><br />
</span>Now we have to generate a debian package (AMD users with newer kernels might find troubles, in case leave a comment):<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;"> make dkms_mkdeb</span></blockquote>
And install the resulting .deb package. Now you have your driver ready to go! </li>
<li>So we will unload the old driver:<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
sudo modprobe -r acpi-cpufreq</blockquote>
Once you're done load the new one, amd users will have the second line, intel the first!<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
sudo modprobe phc-intel<br />
sudo modprobe phc-k8</blockquote>
</li>
<li>Now I guess you want a cool GUI to easier setting VIDs: <a href="http://www.linux-phc.org/forum/viewtopic.php?f=14&t=17">get it here</a>. Unpack it to a <u>non temporary</u> folder and move there.</li>
<li>You'll need to fix an error, so download<a href="http://www.linux-phc.org/forum/viewtopic.php?f=10&t=270"> this corrected</a> file and save it to:<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">**your path**/phctool/inc/libs/</span></blockquote>
overwriting the existent file. </li>
<li>From the main phctool folder run:<br />
<blockquote style="font-family: "Courier New",Courier,monospace;">
sudo ./install.sh </blockquote>
</li>
<li>Follow the instruction (both yes will be OK)</li>
<li>relogin and make two links to let you launch these programs directly from terminal:<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo ln **your path**/phctool.sh /usr/bin/phctool</span><br />
<span style="font-family: 'Courier New', Courier, monospace;">sudo ln **your path**/phctray.sh /usr/bin/phctray</span></blockquote>
</li>
<li>done!</li>
</ol>
After this installation procedure try to launch<br />
<blockquote>
<span style="font-family: 'Courier New', Courier, monospace;">sudo phctool</span></blockquote>
there you can set the voltages and see many infos about your CPU. The correct values are not universal, so you'll need some testing.<br />
<br />
UPDATE<br />
<br />
I wrote a new guide to tune voltages, take a look here:<br />
<br />
<a href="http://linuxsolver.blogspot.com/2011/10/how-to-set-cpu-voltage.html">http://linuxsolver.blogspot.com/2011/10/how-to-set-cpu-voltage.html</a><br />
<br />
<br />
Cheers!<br />
<ol></ol>Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com127tag:blogger.com,1999:blog-6007641906670981467.post-86360191459430062282011-02-10T23:11:00.001+01:002011-03-16T12:17:52.272+01:00Bluray on Ubuntu without rip!<div class="separator" style="clear: both; text-align: center;"></div><div class="separator" style="clear: both; text-align: center;"><a href="http://3.bp.blogspot.com/-egWvc_ggnNk/TJiR5HWnX4I/AAAAAAAAAB4/i2l6X6zWVdQ/s1600/screenshot-20100921%2540130535.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="173" src="http://3.bp.blogspot.com/-egWvc_ggnNk/TJiR5HWnX4I/AAAAAAAAAB4/i2l6X6zWVdQ/s320/screenshot-20100921%2540130535.png" width="320" /></a></div>Hey guys,<br />
<br />
few months ago I wrote down a guide for Gentoo to play Bluray Discs without ripping. As it seems that the topic is hot I want to help Ubuntu and Debian friends too :]. The solution is the same, just the package handling is different, so the how-to will have some changes!<br />
<br />
<a name='more'></a>First of all Ubuntu (and Debian) does not come with gompiling tools, so you'll need to get them. Further let's include some dependencies too, so voilà:<br />
<br />
<blockquote><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo apt-get install build-essential libc6-dev libssl-dev libgl1-mesa-dev libqt4-dev</div></blockquote><br />
Here comes the same procedure as Gentoo linux:<br />
<br />
Once you're done visit <a href="http://www.makemkv.com/forum2/viewforum.php?f=3">MakeMKV forum</a> and get both makemkv_v[...]_bin.tar.gz and makemkv_v[...]_oss.tar.gz, saving them on your drive.<br />
<br />
Let's unpack them:<br />
<br />
<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">tar -xf makemkv_v[...]_bin.tar.gz<br />
tar -xf makemkv_v[...]_oss.tar.gz</blockquote>Now move in each folder. You should have all needed deps already so go straight to compile and install<br />
<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">cd makemkv_v[...]_bin<br />
make -f makefile.linux<br />
sudo make -f makefile.linux install<br />
cd ..<br />
cd makemkv_v[...]_oss<br />
make -f makefile.linux<br />
sudo make -f makefile.linux install</blockquote>Nearly done. If you want to start makeMKV just type in your term<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo makemkv &</blockquote>Getting into the business insert a BD in your drive and check if it is recognized by the application. Sometimes the title of the disk does not match the film title but don't worry ^_^<br />
Now:<br />
<ol><li>From File > Open disc > chose your disc or push the button below in the main window</li>
<div class="separator" style="clear: both; text-align: center;"><a href="http://1.bp.blogspot.com/_lqr72cLxjWU/TJh_oD7-o4I/AAAAAAAAABo/RWJnSzgQ3GA/s1600/screenshot-20100921%40114928.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://1.bp.blogspot.com/_lqr72cLxjWU/TJh_oD7-o4I/AAAAAAAAABo/RWJnSzgQ3GA/s1600/screenshot-20100921%40114928.png" /></a></div><li>MakeMKV will analyze your drive to find AACS and decript the Bluray. Once it's done you'll see more infos about your disc.</li>
<li>Go File > Stream or the button below:</li>
<div class="separator" style="clear: both; text-align: center;"><a href="http://2.bp.blogspot.com/_lqr72cLxjWU/TJiA9Np__qI/AAAAAAAAABw/iV41cky7fc8/s1600/screenshot-20100921%40115453.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://2.bp.blogspot.com/_lqr72cLxjWU/TJiA9Np__qI/AAAAAAAAABw/iV41cky7fc8/s320/screenshot-20100921%40115453.png" /></a></div><li>Once you read "Operation sucessfully completed. Streaming server started, web server address is..." you're ready to share your stream.</li>
<li>Let's open VLC Media > Open Network Stream</li>
<li>We just have to write "<span style="background-color: #9fc5e8;">http://localhost:51000/stream/title0.ts</span>" in the text box. If title0 doesn't work try with following ones (title1, title2, etc.).</li>
<li>Click Play</li>
</ol><br />
Enjoy Ubuntu guys! <br />
<ol></ol>Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com1tag:blogger.com,1999:blog-6007641906670981467.post-48687522902656465822011-02-09T23:42:00.004+01:002011-03-25T15:35:03.754+01:00Phctool patch for 2.6.36 kernels<div class="separator" style="clear: both; text-align: center;"><a href="http://www.clker.com/cliparts/8/7/d/c/1237916492482224985pitr_Patch_icon.svg.med.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="198" src="http://www.clker.com/cliparts/8/7/d/c/1237916492482224985pitr_Patch_icon.svg.med.png" width="200" /></a></div>Here comes a bug solution for Phctool, committed in gentoo package 0.5.2-2-r1 and developed by me :]<br />
<br />
Phctool python-based graphic interface seems to not work due to the way CPUs id is defined. Looks like it's based still on /proc/acpi/processor/CPU./info which is no more present in my system. It looks like that kernel 2.6.36 and later doesn't support those deprecated /proc/acpi directories even with CONFIG_ACPI_PROCFS enabled. <br />
<a name='more'></a><br />
No window opens, if run in terminal you get:<br />
<br />
<br />
<div style="font-family: "Courier New",Courier,monospace;">Traceback (most recent call last):</div><div style="font-family: "Courier New",Courier,monospace;">File "./phctool.py", line 468, in <module></div><div style="font-family: "Courier New",Courier,monospace;">app=appgui()</div><div style="font-family: "Courier New",Courier,monospace;">File "./phctool.py", line 81, in __init__</div><div style="font-family: "Courier New",Courier,monospace;">self.cpuinfo=cpuinfo.cpuinfo() ##functions to gather CPU informations</div><div style="font-family: "Courier New",Courier,monospace;">File "inc/libs/cpuinfo.py", line 12, in __init__</div><div style="font-family: "Courier New",Courier,monospace;">self._get_acpi_cpus() ##get ACPI-supported CPUs</div><div style="font-family: "Courier New",Courier,monospace;">File "inc/libs/cpuinfo.py", line 43, in _get_acpi_cpus</div><div style="font-family: "Courier New",Courier,monospace;">self.data[cpunr]['acpi']['exist']=False</div><div style="font-family: "Courier New",Courier,monospace;">UnboundLocalError: local variable 'cpunr' referenced before assignment</div><br />
<br />
Expected Results: <br />
Open UI GUI. Looks like that functionality is still available, just the GUI is<br />
missing.<br />
<br />
<br />
<br />
The solution stands just in replacing a lib with a newer one, which I committed to gentoo bugzilla.<br />
<br />
So download the file from <a href="http://bugs.gentoo.org/attachment.cgi?id=260511&action=view">here</a> (right click, save as)<br />
<br />
backup the old file:<br />
<br />
<div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo mv /usr/share/phctool/inc/libs/cpuinfo.py /usr/share/phctool/inc/libs/cpuinfo.py.bak</div><br />
copy the new <br />
<br />
<br />
<div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo cp #*path to download*#/cpuinfo.py /usr/share/phctool/inc/libs/cpuinfo.py</div><br />
if experience wrong behaviour write a comment!<br />
<br />
CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com1tag:blogger.com,1999:blog-6007641906670981467.post-34578336308555926072011-02-08T23:03:00.000+01:002011-02-09T23:44:58.952+01:00Laptop modding: install usb on mini PCI-e<div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/_lqr72cLxjWU/TVG6yrYDylI/AAAAAAAAAEE/7eRBgmHV3xg/s1600/DSC00909.JPG" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="150" src="http://4.bp.blogspot.com/_lqr72cLxjWU/TVG6yrYDylI/AAAAAAAAAEE/7eRBgmHV3xg/s200/DSC00909.JPG" width="200" /></a></div>Hey guys,<br />
<br />
some time passed, but still some hot stuff for you. If you have a laptop, you've experience the "damn, no free USB... it s*cks". I'm sure that of course all the small sticks that hang out from your laptop case are in terrible danger or feel uncomfortable... I have the solution... obviously not for everybody... be sure you have an idea of what you're doing...<br />
<br />
<a name='more'></a>We are talking about installing a usb device inside your laptop, without loosing free usb outside. Things you must know:<br />
<ul><li><b>If you do the wrong thing you may f*ck your box</b></li>
<li><u>You need some space enough to make the device fit in the case</u></li>
<li>you need to solder... really tiny stuff...</li>
</ul>But let's reveal the most interesting news: <b>you have a free usb under your wifi card</b>. Yeah, that's it... pcie ports contain one usb port each.<br />
Let's introduce the usb standard:<br />
<br />
<table align="center" border="1" cellpadding="3" cellspacing="0"><tbody>
<tr><th>Pin</th> <th>Name</th> <th>Cable color</th> <th>Description</th> </tr>
<tr> <td>1</td> <td>VCC</td> <td>Red</td> <td>+5 VDC</td> </tr>
<tr> <td>2</td> <td>D-</td> <td>White</td> <td>Data -</td> </tr>
<tr> <td>3</td> <td>D+</td> <td>Green</td> <td>Data +</td> </tr>
<tr> <td>4</td> <td>GND</td> <td>Black</td> <td>Ground</td></tr>
</tbody></table><br />
If you want to know more (look at pin disposition) <a href="http://pinouts.ru/Slots/USB_pinout.shtml">here</a>. While VCC is the alim line and GND is the ground, there are two channels for data, used to communicate serially. Looking at the mini PCIe:<br />
<br />
<table align="center" border="1" cellpadding="3" cellspacing="0"><colgroup><col width="86"></col><col width="86"></col><col width="86"></col><col width="86"></col></colgroup> <tbody>
<tr> <td colspan="2" height="16" style="text-align: center;" width="86"><b>Top side</b></td> <td colspan="2" style="text-align: center;" width="86"><b>Bottom side</b></td> </tr>
<tr> <td align="RIGHT" height="16" width="86">1</td> <td align="LEFT" width="86"></td> <td align="RIGHT" width="86">2</td> <td align="LEFT" width="86">3.3V</td> </tr>
<tr> <td align="RIGHT" height="16">3</td> <td align="LEFT">Reserved****</td> <td align="RIGHT">4</td> <td align="LEFT">GND</td> </tr>
<tr> <td align="RIGHT" height="16">5</td> <td align="LEFT">Reserved****</td> <td align="RIGHT">6</td> <td align="RIGHT"><div style="text-align: left;">1.5V</div></td> </tr>
<tr> <td align="RIGHT" height="16">7</td> <td align="LEFT">CLKREQ#</td> <td align="RIGHT">8</td> <td align="LEFT">Reserved**</td> </tr>
<tr> <td align="RIGHT" height="16">9</td> <td align="LEFT">GND</td> <td align="RIGHT">10</td> <td align="LEFT">Reserved**</td> </tr>
<tr> <td align="RIGHT" height="16">11</td> <td align="LEFT">REFCLK-</td> <td align="RIGHT">12</td> <td align="LEFT">Reserved**</td> </tr>
<tr> <td align="RIGHT" height="16">13</td> <td align="LEFT">REFCLK+</td> <td align="RIGHT">14</td> <td align="LEFT">Reserved**</td> </tr>
<tr> <td align="RIGHT" height="16">15</td> <td align="LEFT"></td> <td align="RIGHT">16</td> <td align="LEFT">Reserved**</td> </tr>
<tr> <td colspan="4" height="16" style="text-align: center;"><b>Mechanical key</b></td> </tr>
<tr> <td align="RIGHT" height="16">17</td> <td align="LEFT">Reserved</td> <td align="RIGHT">18</td> <td align="LEFT">GND</td> </tr>
<tr> <td align="RIGHT" height="16">19</td> <td align="LEFT">Reserved</td> <td align="RIGHT">20</td> <td align="LEFT">Reserved***</td> </tr>
<tr> <td align="RIGHT" height="16">21</td> <td align="LEFT">GND</td> <td align="RIGHT">22</td> <td align="LEFT">PERST#</td> </tr>
<tr> <td align="RIGHT" height="16">23</td> <td align="LEFT">PERn0</td> <td align="RIGHT">24</td> <td align="LEFT">+3.3Vaux</td> </tr>
<tr> <td align="RIGHT" height="16">25</td> <td align="LEFT">PERp0</td> <td align="RIGHT">26</td> <td align="LEFT">GND</td> </tr>
<tr> <td align="RIGHT" height="16">27</td> <td align="LEFT">GND</td> <td align="RIGHT">28</td> <td align="LEFT">+1.5V</td> </tr>
<tr> <td align="RIGHT" height="16">29</td> <td align="LEFT">GND</td> <td align="RIGHT">30</td> <td align="LEFT">SMB_CLK</td> </tr>
<tr> <td align="RIGHT" height="16">31</td> <td align="LEFT">PETn0</td> <td align="RIGHT">32</td> <td align="LEFT">SMB_DATA</td> </tr>
<tr> <td align="RIGHT" height="16">33</td> <td align="LEFT">PETp0</td> <td align="RIGHT">34</td> <td align="LEFT">GND</td> </tr>
<tr> <td align="RIGHT" height="16">35</td> <td align="LEFT">GND</td> <td align="RIGHT">36</td> <td align="LEFT">USB_D-</td> </tr>
<tr> <td align="RIGHT" height="16">37</td> <td align="LEFT">Reserved*</td> <td align="RIGHT">38</td> <td align="LEFT">USB_D+</td> </tr>
<tr> <td align="RIGHT" height="16">39</td> <td align="LEFT">Reserved*</td> <td align="RIGHT">40</td> <td align="LEFT">GND</td> </tr>
<tr> <td align="RIGHT" height="16">41</td> <td align="LEFT">Reserved*</td> <td align="RIGHT">42</td> <td align="LEFT">LED_WWAN#</td> </tr>
<tr> <td align="RIGHT" height="16">43</td> <td align="LEFT">Reserved*</td> <td align="RIGHT">44</td> <td align="LEFT">LED_WLAN#</td> </tr>
<tr> <td align="RIGHT" height="16">45</td> <td align="LEFT">Reserved*</td> <td align="RIGHT">46</td> <td align="LEFT">LED_WPAN#</td> </tr>
<tr> <td align="RIGHT" height="16">47</td> <td align="LEFT">Reserved*</td> <td align="RIGHT">48</td> <td align="LEFT">+1.5V</td> </tr>
<tr> <td align="RIGHT" height="16">49</td> <td align="LEFT">Reserved*</td> <td align="RIGHT">50</td> <td align="LEFT">GND</td> </tr>
<tr> <td align="RIGHT" height="16">51</td> <td align="LEFT">Reserved*</td> <td align="RIGHT">52</td> <td align="LEFT">+3.3V</td></tr>
</tbody></table><br />
Looking at the 36 and 38 pins... whoa! here it is. The most interesting thing is that <b>usually </b>no wifi card uses this port, thus it stands here unused. The missing stuff is just the alim: I suggest to connect two USB port 5V contact together (of course from the inside) and solder there the source of your VCC: this will share the load on the ports preventing the overcurrent drain.<br />
<br />
You can connect there whatever you want, but follow these few advices:<br />
<ul><li>work on power off, and double check everything before giving power</li>
<li>use always a multimeter </li>
<li>open the device box and unsolder the USB tip pad by pad: if you break it you'll feel damned stupid</li>
<li>double check if the device fits before apply any mod to the case</li>
<li>use a VERY SMALL TIP SOLDER and do not solder miniPCIe on the pads: they will shortcut immediately, use the climbing wires of the connector, as in the bottom picture</li>
<li>use the shortest wire you can and the smallest amount of tin you can, if needed use a smaller couple of wires to take out the connection</li>
<li>twist the data wires if they run for more than 3-4 cm</li>
</ul>your result should look like this:<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/_lqr72cLxjWU/TVG6yrYDylI/AAAAAAAAAEE/7eRBgmHV3xg/s1600/DSC00909.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="http://4.bp.blogspot.com/_lqr72cLxjWU/TVG6yrYDylI/AAAAAAAAAEE/7eRBgmHV3xg/s320/DSC00909.JPG" width="320" /></a></div><br />
<br />
<br />
<br />
<b>WARNING</b>: some USB drives needs fast connection! long cables with poor shielding will cause unstable link!<br />
<br />
In my case the installed stuff is not only the USB receiver of my wireless desktop set, but <u>also a switch to activate and deactivate it when needed</u>. I'll post about it in the feature.<br />
<br />
If you have a question leave a comment please, I'll answer surely!<br />
<br />
CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com2tag:blogger.com,1999:blog-6007641906670981467.post-62650228718448482662010-12-20T18:28:00.000+01:002010-12-20T18:28:52.294+01:00Sorry for the long absenceHey guys,<br />
<br />
sorry for my long absence, I've been really busy in these months and unrfotunately I'm going to be so till the end of March... If I'll have some spare time I'll write again, continuing the new modding section.<br />
<br />
CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-55487595707993546312010-10-14T21:24:00.001+02:002010-10-14T21:25:15.916+02:00How to dismount MSI PR201<div class="separator" style="clear: both; text-align: center;"><a href="http://1.bp.blogspot.com/_lqr72cLxjWU/TLcCp1fn9lI/AAAAAAAAAC4/am3tPTlMeqc/s1600/DSC00488%281%29.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="http://1.bp.blogspot.com/_lqr72cLxjWU/TLcCp1fn9lI/AAAAAAAAAC4/am3tPTlMeqc/s320/DSC00488%281%29.JPG" width="320" /></a></div>Today I'm starting a new serie of posts regarding laptop modding. The first step of every laptop modding is of course the notebook dismount. The tools required are very common: a small screw driver, better if magnetic, a pair of tweezers, a plastic blade (maybe a plastic knife or plettrum) and the most important of course patience and care.<br />
<a name='more'></a>Be sure you know what you want to do. If you need just to plug in or out some component you don't need to fully dismount the laptop. Just turn it upside down, and remove the <b>main shell</b> by removing the four screws (two near the hinges and other two on it) and you'll gain access to the main components. If you want to change the optical drive things are even easier: just remove the screw in the middle of the chassis to let it slide out. Of course you'll need to move the connection plate from the old drive to the new.<br />
<br />
Talking about the real PR201 dismount procedure, as all the laptops, has some critical steps so be very careful. The most important thing in our case is to keep the laptop open. Move the screen as far as it can go and leave it like that for all the steps.<br />
<br />
Starting from the beginning the first thing is to remove the <b>keyboard</b>. To do that you need to remove four small metal covers near speakers and multifunctional keys, they are just near to Esc, Del and between F5 and F6, F10 and F11. Under them you'll find four plastic locks, just push them delicately to release the keyboard. To completely remove it you'll need to free the flat cable, sliding the lock bar.<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://1.bp.blogspot.com/_lqr72cLxjWU/TLcDU_9caYI/AAAAAAAAAC8/FFYK6zIkwi0/s1600/DSC00915.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="http://1.bp.blogspot.com/_lqr72cLxjWU/TLcDU_9caYI/AAAAAAAAAC8/FFYK6zIkwi0/s320/DSC00915.JPG" width="320" /></a></div>Under the keyboard you'll find a screw (wow) and two other flat cables. Be very delicate and release both, then remove the screw too. On this side we're done, so turn it around, letting the screen lean out from the board, maybe let it lay on your lap.<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://3.bp.blogspot.com/_lqr72cLxjWU/TLdVfrHMkCI/AAAAAAAAADA/cVuurnVBdHc/s1600/DSC00910.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="320" src="http://3.bp.blogspot.com/_lqr72cLxjWU/TLdVfrHMkCI/AAAAAAAAADA/cVuurnVBdHc/s320/DSC00910.JPG" width="240" /></a></div>On the back there are several screws, we first need to remove the main shell as already described. Take out the hard drive unscrewing its carry and making it slide to the border till it releases. The next step is to remove the <b>screen</b>: keep it on your lap and remove the remaining two screws. Now the screen is released, but not free as there are several cables, follow them carefully and remove their connectors: they should be<br />
<ul><li>an antenna cable</li>
<li>a couple near the hard drive for camera and backlight</li>
<li>the LCD cable near the fan</li>
<li>the microphone cable that runs through the mainboard to its connector placed near the ram slots.</li>
</ul><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><img border="0" height="240" src="http://4.bp.blogspot.com/_lqr72cLxjWU/TLdWT_STPFI/AAAAAAAAADE/vanX23cvEIc/s320/DSC00911.JPG" style="margin-left: auto; margin-right: auto;" width="320" /></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Wifi card, cmos battery and LCD cable connector.</td></tr>
</tbody></table><div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/_lqr72cLxjWU/TLdWT_STPFI/AAAAAAAAADE/vanX23cvEIc/s1600/DSC00911.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"></a></div><br />
To full dismount the lid too you must remove the rubber bolts at the corner of the screen to reveal the hidden screws. Once you take them apart gently slide the plastic blade along the border, releasing the locks and letting the <b>LCD panel out</b>. Be careful not to damage the cables and the panel itself as they are crucial.<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><img border="0" height="240" src="http://4.bp.blogspot.com/_lqr72cLxjWU/TLdX0JNY45I/AAAAAAAAADM/N0J5qBabW38/s320/DSC00908.JPG" style="margin-left: auto; margin-right: auto;" width="320" /></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Start from here, releasing the block visible on the right.</td></tr>
</tbody></table><div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/_lqr72cLxjWU/TLdX0JNY45I/AAAAAAAAADM/N0J5qBabW38/s1600/DSC00908.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"></a></div><div class="separator" style="clear: both; text-align: center;"></div><br />
Now let's go back to the <b>main chassis</b>. Take care of all those screws you can see in the chassis, remove optical drive, pcie cards, the fan and the three screws surrounding the cpu. Remove express card and card reader covers. Now comes the hard part: starting from the battery slot insert the plastic blade between the top and the bottom part and open the main chassis. Be very careful as it is quite complicated, don't force it as you might have forgotten a hidden screw. The mainboard is not going to remain connected to the palmrest shell but to the bottom part. Pay attention to the audio out and mic in, they must remain with the mainboard as they're soldered. Once it's released unplug the other connector left and pull it out.<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><img border="0" height="240" src="http://2.bp.blogspot.com/_lqr72cLxjWU/TLdXW8zCRtI/AAAAAAAAADI/GFK1rKqjeXg/s320/DSC00907.JPG" style="margin-left: auto; margin-right: auto;" width="320" /></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Pay attention to these, they must remain with the bottom (matte) not with the top (glossy)</td></tr>
</tbody></table><div class="separator" style="clear: both; text-align: center;"><a href="http://2.bp.blogspot.com/_lqr72cLxjWU/TLdXW8zCRtI/AAAAAAAAADI/GFK1rKqjeXg/s1600/DSC00907.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"></a></div>Now we are really close to the full dismount. If you need to free the <b>mainboard</b> too there is just a couple of screws left, one on the top face, under the multifunctional keys, the other holds the heatpipe: release them, but be sure not to mess up with the thermal pad and the thermal compound if you don't have the right stuff to replace them. Now focus on the VGA connector: you have to pull it up while forcing the chassis a bit so it comes out of its hole with the whole board.<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://1.bp.blogspot.com/_lqr72cLxjWU/TLcCp1fn9lI/AAAAAAAAAC4/am3tPTlMeqc/s1600/DSC00488%281%29.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="http://1.bp.blogspot.com/_lqr72cLxjWU/TLcCp1fn9lI/AAAAAAAAAC4/am3tPTlMeqc/s320/DSC00488%281%29.JPG" width="320" /></a></div>Yeah, we are finally done. To <b>reassemble</b> everything it's quite easy, no strange steps:<br />
<br />
<ul><li>Insert the mainboard in the bottom chassis, screw it in the second hole, the one between the vent hole of the main board and the big Intel IC.</li>
<li>Mount the main chassis and re-plug the connector.</li>
<li>Screw everything except the hinges, and the two holes that are going to be filled by the main shell screws.</li>
<li>Make the hinges fit in their spaces, then carefully screw the hinges in the holes closer to the edge. Now make the cables run in their places, making sure that they are relaxed enough so they won't stretch when you close the lid: you should find a white sign on them, just let it stand at the chassis border, just before cable guides. These two cable guides are made by very fragile plastic tips, so be delicate and don't break them.</li>
<li>Plug everything in and be sure you're not forgetting anything. Take care of the heatpipe position and the thermal compound must to be replaced. Be sure to connect the fan alim unless you'll burn your cpu!</li>
<li>Place the main shell and let it slide till it's locked, then screw it.</li>
<li>Turn the laptop to put the keyboard back in. Remember to screw the last left hole and be gentle with flat cables and keyboard locks.</li>
</ul><br />
Before giving power back double check there is nothing left!<br />
<br />
Power on!<br />
<br />
Coming soon: mainboard map and my modding works,<br />
<br />
Stay tunedAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-77664389753482204522010-10-10T13:18:00.000+02:002010-10-10T13:18:52.015+02:00Remove Openoffice start delay<div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/_lqr72cLxjWU/TLGgxurGN-I/AAAAAAAAAC0/Ru4F_EzVEJ4/s1600/screenshot-20101010@131745.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://4.bp.blogspot.com/_lqr72cLxjWU/TLGgxurGN-I/AAAAAAAAAC0/Ru4F_EzVEJ4/s1600/screenshot-20101010@131745.png" /></a></div>Hey,<br />
<br />
even if in many setups this trouble it's silent in fast environment it's really a pain. I'm talking about the slow startup of Openoffice when you want to open a file. It takes ages to do nothing, as it doesn't write or read from drive, no CPU use or whatever. It took a lot to figure out where the trouble was. From time to time it happened to do some text edit without internet connection... and surprise... no problem!<br />
<br />
<a name='more'></a>So it was quite obvious that the trouble concerned net configurations, but it was still way too far from identifying it.<br />
<br />
I was quite lucky when I found the solution somewhere. I don't remember where exactly, so please forgive me if I don't link back to the source.<br />
<br />
Openoffice somehow wants to retrieve a local address, so we are going to give it! Just edit the right file:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /etc/hosts</blockquote>and look for the local address line. it should look something like:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">127.0.0.1 *yourhostname* localhost<br />
::1 localhost</blockquote>you should add just "*yourhostname*.(none)" to the first line, so it looks like this:<br />
<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">127.0.0.1 *yourhostname* localhost *yourhostname*.(none)<br />
::1 localhost</blockquote>Save and close, your next Openoffice start will be faster than ever! Fast and painless!<br />
<br />
Cheers!Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-4114126166470802312010-10-09T10:30:00.002+02:002010-10-09T10:30:00.250+02:00Speedup Desktop Environment<div class="separator" style="clear: both; text-align: center;"><a href="http://3.bp.blogspot.com/_lqr72cLxjWU/TK-K_53SCXI/AAAAAAAAACw/96hNrL5Qpzc/s1600/screenshot-20101008@231912.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="http://3.bp.blogspot.com/_lqr72cLxjWU/TK-K_53SCXI/AAAAAAAAACw/96hNrL5Qpzc/s1600/screenshot-20101008@231912.png" /></a></div>Hey,<br />
<br />
one of the last post I was wondering what made my system idle for 3 sec before finishing boot. I think I've found. I asked <u>Sherlock Holmes</u> and he revealed me the truth. So let's take the chance and find the best way to get a <a href="http://www.xfce.org/?layout=normal">responsive and fast environment</a>.<br />
<br />
First of all unless you have a good dedicated graphic card I suggest to forget about <b>compiz</b> and other beautiful but useless beautifiers. I even suggest <b>Xfce</b> which is very light fast and reliable. This means that <b>Gnome</b> and <b>KDE</b> are good if you want a cool look, but not always the best choice.<br />
<br />
In my case I have an Integrated Intel Graphics, so I <u>have to</u> do without compiz, I love very minimalist desktops, so <u>decided</u> to do without compiz, without KDE and without Gnome, just <b>Xfce</b>, and an even lighter panel manager, <b>tint2</b>.<br />
<a name='more'></a>In my experience moving a working system from a desktop environment to another can mess up lots of things. So the better choice is to make a fresh install in another partition where you can try the new environment.<br />
<br />
In our case we are going to pull in <b>Xfce</b>, so you'd better follow the official handbook: <br />
<a class="l noline" href="http://www.gentoo.org/doc/en/xfce-config.xml">Gentoo> Linux Documentation -- The Xfce Configuration Guide</a><br />
<br />
You'll see Xfce is more lightweight, can support almost any gnome application (using gnome libs) and has a quite good appeal. Panels are very customizable both in their settings and their components. The most interesting option is to not show any icon on the desktop, and application menu with right click on it. So when you want to open an application just right click anywhere on the desktop and here you go. All these settings are easily reachable from xfce4 settings manager, just take a look in its sections.<br />
<br />
If you want an even more lightweight panel manager, with a cool flavour, then what you look for is <b>tint2</b>. You can see some configs and some screenshots <a href="http://code.google.com/p/tint2/">here</a>. The strong point is the extreme customization: it can be a wonderful thing for patient users... if you're not... hem... better keep xfce panel ;].<br />
<br />
If you want to give it a try it can be installed without troubles even over existing xfce installation, without issues. You can find it in the Gentoo repository, just emerge it with<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -pv tint2</blockquote>if you want to keep it and not to use xfce panel you can remove xfce4-panel in the session settings.<br />
<br />
<b>Now the Sherlock Holmes' answer: delete xfce stuff in ~/.cache folder and... whoa! load in no time!</b><br />
<br />
Cheers<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://tnrdlibrary.files.wordpress.com/2009/12/sherlock-holmes.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="225" src="http://tnrdlibrary.files.wordpress.com/2009/12/sherlock-holmes.jpg" width="320" /></a></div>Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-9341523585539286372010-10-08T00:59:00.002+02:002010-10-14T21:43:28.292+02:00CPU downvoltage, downclock and monitoring on gentoo linux<div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/_lqr72cLxjWU/TK5QIjrszoI/AAAAAAAAACs/5sWrTI_1OUU/s1600/coreduo.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="200" src="http://4.bp.blogspot.com/_lqr72cLxjWU/TK5QIjrszoI/AAAAAAAAACs/5sWrTI_1OUU/s200/coreduo.jpg" width="200" /></a></div>Hey everybody,<br />
<br />
since I assembled my laptop starting from spare parts I had a serious problem: heat. I don't mean my laptop went on fire in idle, but when doing some serious computing form my MRI jobs, it happens to work for several minutes with both CPU at 100%. That should not scare anybody, but I did force my barebone specs plugging a T9800 CPU, 35W, when the suggested CPU was of downvolted family (25W). Hehe :]. Obviously you can solve many overheating troubles, but the first solution should always be heatsink cleaning and fan check.<br />
<br />
Keeping in mind that I always run my pc with the best airflow possible (no pc-bag under it or cover while sitting on the bed etc.), this is how I solved my problem, handling the CPU management in the same time, and how I tested the final configuration.<br />
<br />
<a name='more'></a>The first step is to get prepare the kernel. You should check for <b>ACPI Processor P-state</b> or <b>AMD Opteron/Athlon64 PowerNow</b> or the required driver for your architecture. Let's take Intel Core 2 Duo as example: build ACPI P-state as a <u>module </u>that will be called <b>acpi-cpufreq</b>. If you'll follow to the end this guide we are going to replace this module, so be sure not to build it in kernel. Also take a look at the active governors (few lines upper).<br />
Obviously you should make the module load at startup, by adding the name in /etc/conf.d/modules or in the proper file if you don't have OpenRC.<br />
<br />
Then we need to install a reliable hardware monitor. I suggest GKrell or conky. As I enjoy minimalist environments, I prefer <b>conky</b> ;].<br />
Conky is a very handy system monitor and can do any sort of thing (yeah, almost any), even run scripts and plot their output. In our case what we need is to see CPUs clocks and temperatures (if you care usage too).<br />
So:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -av conky</blockquote>Even if default configs are available I'll paste here a short line for monitoring those values we need. You can customize your configuration by editing <span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">~/.conkyrc</span> and following <span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">man conky</span> instruction.<br />
<blockquote><span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">${color0}CPU$color ${freq_g 1}G ${cpubar cpu1 4,45} ${hwmon 0 temp 1}C </span></blockquote><br />
We are quite ready to begin. In the first part of my cpu experiments (;]) I used <b>cpufrequtils</b> to be able to set governor and clock myself. I suggest to begin here, to see what your CPU can really do:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -av cpufrequtils</blockquote>It is divided in a couple of function: <b>cpufreq-info</b> gets info from the CPU, <b>cpufreq-set</b> can set clock or governor etc... Their helps can explain how they work better than me. What you need is just to play a little, aiming to see the highest and the lowest clock etc. I used this tool to write some scripts to manually set clock or to change governor by keyboard shortcuts.<br />
<br />
This is all the way deprecated as you'll put your eyes on <b>cpufreqd</b>. It relies on a set of profiles and rules, based on acpi information (AC plug, battery level, open apps, CPU request), to decide what is the best governor and what is the right clock in that moment. Let's emerge it<br />
emerge -av cpufreqd<br />
and let's add it to default runlevel<br />
sudo rc-update add cpufreqd default<br />
Now you should customize your config. Look at default:<br />
sudo nano /etc/cpufreqd.conf<br />
and decide what is the best for you. In my case I created several profiles and rules, one of them was handling overheating, here it comes the profile and the rule:<br />
<br />
<blockquote><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">[Profile]<br />
name=limited<br />
minfreq=80%<br />
maxfreq=80%<br />
policy=performance<br />
[/Profile]<br />
#cpu too hot <br />
[Rule]<br />
name=CPU hot<br />
acpi_temperature=80-100<br />
cpu_interval=50-100<br />
profile=limited<br />
[/Rule]</div></blockquote>This can do the job quite good. The reduction of clock can lower very fast the temperature of the CPU, bringing it back to full speed as soon as it can.<br />
<br />
This is good, but not best. Googling around I found <b><a href="http://www.linux-phc.org/">phc project</a></b>, which works on cpu management. In their stuff that there is a cpu driver and coupled application that can handle CPU more in detail: you can change the core voltage of every frequency step. This can lead to two main consequences: you'll use less energy to run the core (less battery consumption) but you'll generate less heat too. ;]<br />
This time we have to set a USE flag to let user run the main application and change values of cpu voltage.<br />
<blockquote style="font-family: "Courier New",Courier,monospace;"><div style="background-color: #9fc5e8;">sudo nano /etc/portage/package.use</div></blockquote>add the following line<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sys-power/phctool sudo</blockquote>then let's emerge it with its driver:<br />
<blockquote><span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -av phctool phc-intel </span><span style="font-family: "Courier New",Courier,monospace;">(or phc-k8)</span></blockquote>Once you've set correctly permissions (see portage output), let's move to the new driver:<br />
<blockquote><div style="font-family: "Courier New",Courier,monospace;"><span style="background-color: #9fc5e8;">sudo modprobe -r acpi-cpufreq</span> (or your arch old driver)</div><span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo modprobe phc-intel</span><span style="font-family: "Courier New",Courier,monospace;"> (or phc-k8)</span></blockquote>to launch the application start it from command line:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">phctools</blockquote>and customize your voltages. Be careful not to exaggerate, make small steps and small modifies sequentially, testing results each time. Remember to set the option "restore VIDs on load" so it will get your last config and load it automatically.<br />
<br />
Last tool is very dangerous, so if you don't know what you're doing just stop here. Following these steps you might broke your system, I don't feel liable for any trouble. Testing thermal behavior is simple-stupid with cpuburn.<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -av cpuburn</blockquote>It will install some "burn**" binaries. They are created each for a specific kind of cpu. Intel users should chose burnP* family while AMD burnK*. The command generates a single-core stress, so let's workaround it (run <span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">burn** &</span> one time for each core). Remember to be ready with <span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">killall burn**</span> if the temperature rises too fast or too high.<br />
<br />
The final result of downvolting by 0,15V my CPU is that it never goes over 80°C even on full load; this keeping my pcufreqd rules and advantages. It's a pity that on idle I already have the lowest voltage available (at least it seems so as I can't get it lower), so my batteries won't improve lasting ;P...<br />
<br />
CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com3tag:blogger.com,1999:blog-6007641906670981467.post-67608858588847890382010-10-07T00:17:00.000+02:002010-10-07T00:17:49.594+02:00MSI PR201 and linux: bluetooth, fingerprint, Intel video, Intel audio and card reader<div class="separator" style="clear: both; text-align: center;"><a href="http://eu.msi.com/uploads/prod_b__20091027112647.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="288" src="http://eu.msi.com/uploads/prod_b__20091027112647.jpg" width="320" /></a></div>Hi everybody,<br />
<br />
today I'm going to write about some tricks to fully handle MSI PR201 features. As comes out of the title we are going to treat 5 main areas: bluetooth dongle, fingerprint sensor, Intel Graphics, Intel audio and MSI PR201 is a small but complete notebook, it comes in a small and lightweight chassis, with a 12" screen. It has a Montevina chipset, so it won't support latest Intel processors (i5, i7 etc), but can run up to the T9900 or X9100 with 3,1GHz clock. The ram supported is DDR2 up to 8GB. Our hardware is going to be:<br />
<blockquote>Device 002: ID 0db0:a97a Micro Star International <b>Bluetooth</b> EDR Device<br />
Device 002: ID 147e:1000 Upek (<b>fingerprint</b> sensor)<br />
<b>VGA compatible controller</b>: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller<br />
Audio device: Intel Corporation 82801I (ICH9 Family) HD <b>Audio Controller</b><br />
<b>?? Card Reader ?? </b></blockquote><br />
<a name='more'></a>So let's begin from the <b>bluetooth</b> device. It's fully supported out of the box, so you won't need strange patches or custom drivers if you have a quite new kernel. The software infrastructure is carried by the bluez package, so first of all let's emerge it: (as alway double check you use flags so you install it in the way you want)<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -av bluez</blockquote>Once it's done we have to add the rc script to init sequence:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo rc-update add bluetooth default</blockquote>Till this point it seems right-forward, but you'll find a great surprise as it won't work :P. The trouble stands in the system policy to manage rights on bt device. So nothing new, we just need to edit the right file and get it work:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /etc/dbus-1/system.d/bluetooth.conf</blockquote>This is an xml-like file which carries the information we need to modify. As you can read rights are granted just to root user. Your user should already be in "plugdev" group, so let's punch another hole adding the followin lines before or after the "root" section:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;"> <policy group="plugdev"><br />
<allow own="org.bluez"/><br />
<allow send_destination="org.bluez"/><br />
<allow send_interface="org.bluez.Agent"/><br />
<allow send_interface="org.bluez.HandsfreeAgent"/><br />
<allow send_interface="org.bluez.MediaEndpoint"/><br />
</policy></blockquote>If you don't want to use plugdev group or don't want to give full rights just modify that in the way you prefer.<br />
<br />
Moving on to <b>fingerprint</b> sensor I have to admit that the only feature available (user password replacement) is quite useless: you can always tell someone your pw in case of emergency and let someone use your pc, unless you can make a copy of your fingerprint and leave it in a safe place. ;]<br />
Anyway if you are interested I set it last year following <a href="http://rvshiro.wordpress.com/2009/01/14/fingerprinting-under-ubuntu-810-on-asus-n10jc/">this guide</a>, but I'm not going to set it up again, unless a new bunch of features for fingerprint sensors comes out.<br />
<br />
Intel Graphics GMA 4500HD comes with GM45 chipset, and still can render stuff decently. I decided to renounce having a dedicated graphics, preferring a smaller and lighter laptop (less than 2kg and sized as a paper sheet). To spit some juice out of our box is a good advice to move to newest video environment, so let's "x11" overlay using layman (emerge -pv layman):<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo layman -a x11</blockquote>if you don't care about bleeding edge keep it this way, if you want to risk some more unmask the 9999 serie. So let's get ready to upgrade our system. First of all we need to add a new videocard:<br />
sudo nano /etc/make.conf<br />
the line should look: <br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">VIDEO_CARDS="intel i965"</blockquote>as our chipset core is supported by "<b>i965</b>". Now looking at the future I suggest adding "<b>gallium</b>" USE too. It enables the new sw rendering. Later we'll see some stuff about it. Now we can update those packages:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -avuD mesa mesa-progs xorg-server xorg-drivers xf86-video-intel xf86-input-synaptics libdrm</blockquote>and be sure to add all the drivers installed as we are going to update (hopefully) the xorg server so <u>they will not work anymore</u>. Almost done. Now reboot in your system and test if all drivers are working. If they are broken rebuild them against the newer xorg version.<br />
If everything it's ok, it worths a try enabling gallium mesa rendering. So check you have glxgears. Read carefully, <u>you might get a stuck environment</u>: try enabling it with<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">eselect mesa set i965 gallium</blockquote>actually <u>now the rendering does not work</u>, but in the past it did work, maybe is a temporary bug. Before running the following command the right procedure to go back is:<br />
<ul><li>logging in another console with (Ctrl+Alt+F2),</li>
<li><span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">eselect mesa set i965 classic</span></li>
<li>sudo reboot</li>
</ul>now you know how to go back you can try:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">glxgears</blockquote>;]<br />
If you want to set up a custom xorg.conf you can find loads of infos here: <a href="http://intellinuxgraphics.org/documentation.html">Intel Linux Graphics: Documentation</a><br />
<br />
Great. <b>Intel HD Audio</b> device relies on the modules:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">snd_hda_intel,<br />
snd_hda_codec_realtek,<br />
snd_hda_codec_si3054,<br />
snd_hda_codec_intelhdmi</blockquote>you can enable them in your kernel under the path:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">-> Device Drivers<br />
-> Sound card support<br />
-> Advanced Linux Sound Architecture<br />
-> PCI sound devices <br />
-> Intel HD Audio</blockquote>be sure to build them as <u>modules</u>. When you are done be sure to have working audio. A tragic issue of this hardware is the management of headphone output and system speakers. Jack sensing (auto swap from speakers to headphone and vice-versa) seems to be implemented via software in windoze driver, so here we have a great possibility (to use both speakers and headphone together). This may let someone think he can't turn off speakers using headphone, but it's not true. All you need is to load the driver with a particular option, so we can have a single slide for volume out and a couple of switches to toggle those lines:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /etc/modprobe.d/alsa.conf</blockquote>and append this line, with which you ask a 2 channel switch (speaker vs headphones)<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">options snd-hda-intel model=targa-2ch-dig</blockquote>now at boot you'll have your hardware configured correctly.<br />
<br />
Last, but not least important is <b>card reader</b>. Whoa.... it drives me mad. I still can't even find it in pci, usb or whatever. I'm still trying to get it work, but I don't know even the name. In future I'm going to install windoze on a temporary HD drive and see the info from the proprietary driver. It happened that last firmware update blew up my usb-boot with windoze, so I have to phisically change the drive to make this test. I remember that it looked something like a simulated serial drive but nothing more.<br />
<br />
I'll come back with more info, as always.<br />
<br />
CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-12163489279159963832010-10-04T13:46:00.003+02:002010-10-04T15:28:59.069+02:00Boot time tuning chapter 5th: Timing<div class="separator" style="clear: both; text-align: center;"><a href="http://www.dicts.info/img/ud/stopwatch2.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="192" src="http://www.dicts.info/img/ud/stopwatch2.jpg" width="200" /></a></div>Hi everybody,<br />
<br />
as promised I'm here again with another chapter about boot tuning. Last time I made a little step back to improve my system reliability, today I'm moving forth again, with no renounce of course!<br />
<br />
The solution I was trying it is very customizable, but I'm going to explain as well as I can how can you achieve the same degree of optimization on your box. Our requisites are a <b>text editor</b>, <b>bootchart</b> and if you are running gentoo we will use <b>eselect</b> tool. If you don't have bootchart you can find a guide how to install it <a href="http://linuxsolver.blogspot.com/2010/09/boot-time-tuning-chapter-first.html">here</a> or googling around.<br />
<br />
As always I suggest you to give up if you don't know what you're doing, unless you try it on a "testbox". I don't take liability of any consequence.<br />
<br />
<a name='more'></a>First of all we need to put your inittab to native form. So<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /etc/inittab</blockquote>and throw away any previous changes, it should have no "&" and no "once" either: "once" has to be replaced with "wait", so we will have a default system init. To prove it is alright we will use an <b>eselect</b> tool, you should have it installed by default. If you have a very fast boot already (I mean under 20s) you might want to improve sampling frequency to better see processes. Just edit the conf file:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /etc/bootchartd.conf</blockquote>and edit the proper line:<br />
<blockquote style="background-color: #9fc5e8;"><span style="font-family: "Courier New",Courier,monospace;">SAMPLE_PERIOD=0.1</span> or even <span style="font-family: "Courier New",Courier,monospace;">0.05</span></blockquote><div class="separator" style="clear: both; text-align: center;"><a href="http://1.bp.blogspot.com/_lqr72cLxjWU/TKm2pMAnlfI/AAAAAAAAACk/eqpdjeQQNi0/s1600/bootchart_def_col.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="200" src="http://1.bp.blogspot.com/_lqr72cLxjWU/TKm2pMAnlfI/AAAAAAAAACk/eqpdjeQQNi0/s200/bootchart_def_col.png" width="49" /></a></div><br />
Now we are ready to trace all processes and services, so reboot your system in bootchart mode, and once finished, open the graph. Default inittab launches 3 blocks in sequence, waiting for the previous to finish before starting the following. You should be able to identify those blocks, they are the famous "<b>sysinit</b>", "<b>boot</b>" and "<b>default</b>" runlevels, each with its own rc and processes. I took a picture of my default bootchart and made three boxes over it (black, red and blue) for sysinit, boot and default.<br />
<br />
Now what you want to do is to squeeze those blocks and make them run overlapped as far as it does not create troubles to your boot. So we are going to introduce a script, whose aim is to control the boot timing.<br />
<br />
Sound so silly but it makes the job flawlessly:<br />
<br />
<blockquote><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">#!/bin/sh </div><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sleep $1</div><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">/sbin/rc boot &</div><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sleep $2</div></blockquote><br />
let's save it as <b>/sbin/trigger</b> and give it the rights to be executed.<br />
Consider your boot graph and take note of the time duration of sysinit block and boot block. They will be our starting values of $1 and $2 (in this order). Now move to your inittab and let's tweak it: we need to put again the & in the sysinit line <br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">si::sysinit:/sbin/rc sysinit &</blockquote>and we should edit the boot line, changing it to<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">rc::wait:/sbin/trigger [sysinittime] [boottime]</blockquote>Done.<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://2.bp.blogspot.com/_lqr72cLxjWU/TKm7Eb8i9HI/AAAAAAAAACo/nlZID8eltI0/s1600/bootchart_col.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="200" src="http://2.bp.blogspot.com/_lqr72cLxjWU/TKm7Eb8i9HI/AAAAAAAAACo/nlZID8eltI0/s200/bootchart_col.png" width="47" /></a></div><br />
The procedure now sounds repetitive but can lead to great results. First of all reboot and check if boot time is approx the same as before, but more important, run<br />
sudo eselect rc show all<br />
to see if all rc are started and running as they should.<br />
Now try to reduce both times by a 15% and reboot. Check graph, check time, check services with eselect. If alright move on, and reduce 20% etc. Here is my new boot chart, with blocks highlighted. As you can see time has passed to 13s to 10s with no reliability problem.<br />
<br />
Looking at future, you can notice that after default runlevel block there is a "low-grass plain". Actually my desktop comes out after 6-7 seconds, then system waits for his messiah, takes a coffee cup, makes some stretching... I dunno... I'm trying to find out why it takes so much to do anything and then suddenly launch the session-startup scripts and whatever.<br />
<br />
<u>Gonna ask Sherlock Holmes and tell you.</u><br />
<br />
Stay tuned!Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-90371973035019631332010-10-03T12:01:00.000+02:002010-10-03T12:01:41.447+02:00Boot time tuning chapter 4th: Reliability<div class="separator" style="clear: both; text-align: center;"><a href="http://smidgenpc.com/wp-content/uploads/2010/05/broken_laptop.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="http://smidgenpc.com/wp-content/uploads/2010/05/broken_laptop.jpg" width="320" /></a></div>Hey,<br />
<br />
<div class="separator" style="clear: both; text-align: center;"></div>today I'm making a little step back but another forward. I mean that in the last tuning chapter I was enthusiastic of my 9 sec boot time, even knowing I was on the edge of the blade. Actually nothing bad has happened, I was even able to cut away another second.<br />
<br />
I did optimize booting levels and made some order in my xorg.conf. Maybe some little extra is given by the latest xorg version, which I installed in these days. At the very end of my optimization I was able to boot in <b>8s</b>... <u>but sometimes I was not able to boot</u>. So here is the detailed story.<i></i><br />
<br />
<a name='more'></a>First let's talk about optimizations.<br />
<br />
As you were able to see in last chapter images, the X system startup takes a lot of time, so I tried to get more info about it. We are talking about 6-7 seconds: during this time, the new generation Xorg infrastructure (which has become more flexible and dynamical, cooperating with hal daemon) monitors you hardware and try to guess what you want your desktop look like. This stuff includes hardware polling, modules and drivers loading but even monitor and outputs sizes and resolutions, positions etc. So the simplest thing to do is to fill the xorg.conf file with your default settings. I'm not getting into the business this time, it's a huge argument, maybe we'll talk about it another day, but I'm not leaving you alone! (Of course not!) The most of information needed to generate a good xorg.conf file are in <b><span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">man xorg.conf</span></b> (surprise surprise!!!;) ). Intel Graphics users can find vital extra infos and tips here: <a href="http://intellinuxgraphics.org/documentation.html">Intel Linux Graphics: Documentation</a><br />
<br />
Moving on, the rest of the news is a simple-stupid idea:<u> "If something is not needed in boot, remove it"</u>. So I got rid of those useless rc services. Then it came another great (rofl) idea: <u>"If something is not needed in early booting, then move it in default runlevel"</u>. This is simple and someway effective.<br />
<br />
Anyway here comes the "bad" news.<br />
<br />
The only trouble I step into was a read-write issue. Getting in the detail what happened was an early try to write on the disk, most of times by bootchart (lol), which caused whole the boot process to stop in a bunch of errors... Hehe... that happened with read-only filesystem so no effects on my box, but better make a step backward and get a more reliable system.<br />
<br />
The sysinit level contains few tasks that are made usually in read only mode. This is done for some security reasons I suppose, anyway what we should care about is to let this few things run in the traditional way and not let other runlevels to start in the meanwhile. So get your inittab and edit:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /etc/inittab</blockquote>the sysinit line should not have the "&" we added few days ago:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">si::sysinit:/sbin/rc sysinit</blockquote><br />
Done.<br />
<br />
I'm not giving up. I'm already thinking about a temporized solution, to let higher runlevel start some seconds after sysinit start, without waiting for it to end. I'll let you know about it. <br />
<br />
CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-71807217373488613212010-10-02T11:49:00.003+02:002010-10-02T11:49:00.649+02:00Multidimensional matrices operations: Matlab mtimesx<div class="separator" style="clear: both; text-align: center;"><a href="http://www.mathworks.com/matlabcentral/fx_files/25977/9/mtimesx.JPG" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="90" src="http://www.mathworks.com/matlabcentral/fx_files/25977/9/mtimesx.JPG" width="320" /></a></div>Hi guys,<br />
<br />
today it's the first time I'm writing about something concerning the world of engineering. In particular we are talking about matlab: an awsome platform for computing. Imagine a swiss-knife with easy high-level programming language, GUIs, rapid and optimized libraries, data importing, terminal board connection, graphig drawing, 3d animation, system terminal interface and lots of toolbox developed by users from all over the world: this is Matlab.<br />
<br />
When I heard the first time that name at university I was not happy to learn another programming language more than C++, but time made me change my mind. Now that program is the base to do any sort of thing in my working environment. A brief look at my work is some 3-d processing on a set of slices coming from MRI (Magnetic Resonance Imaging), and believe the results are amazing.<br />
<br />
<a name='more'></a><br />
Sometimes when programming it is obvious to introduce a for loop. In matlab this is nothing but slow. It might be useful for a first stub of the algorithm, but loops are really too slow, due to the literal translation and execution of the code each time the loop cycles. To avoid that loss of time and to use the power of both (or all) the cores there are some smart solutions: one of them is certainly mtimesx.<br />
<br />
Mtimes is the default function to execute matrix product and division. This is a good solution to replace a loop as the operation is readed once, the libraries are compiled in C, and the procedure is optimized.<br />
<br />
This is true, but not the best one can do. For example you might need to use 3D matrices: mtimes supports just 2D operations, so you should employ a loop. What I mentioned above now comes to light: there is a multi-dimensional martices support developed from James Tursa, <b><a href="http://www.mathworks.com/matlabcentral/fileexchange/25977-mtimesx-fast-matrix-multiply-with-multi-dimensional-support">mtimesx</a></b>. It requires some compilation in Matlab (nothing for a gentoo user), all documented in its guide. That function, not only enables ND matrices product, but is faster than mtimes in many cases (look at image).<br />
<br />
The result is amazing, I experienced a serious reduction of time (maybe an order). Just a little note. If you work with 3D matrices, ok, but going over 3D is risky: in our world we can experience a 3+D environment (time is not really the 4th dimension), so even if employing a 4D or 5D algorithm can be faster than ever, remember that programming it and debugging it might be seriously complicated.<br />
<br />
Good luck.Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com3tag:blogger.com,1999:blog-6007641906670981467.post-10276311119547714342010-10-01T15:42:00.000+02:002010-10-01T15:42:32.369+02:00New Adobe Flash support for 64 bit systemHi guys,<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://1.bp.blogspot.com/_lqr72cLxjWU/TKXkEBkbEBI/AAAAAAAAACc/0A4rYEdgEM4/s1600/screenshot-20101001@153403.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="189" src="http://1.bp.blogspot.com/_lqr72cLxjWU/TKXkEBkbEBI/AAAAAAAAACc/0A4rYEdgEM4/s320/screenshot-20101001@153403.png" width="320" /></a></div><br />
Seems finally the day has come. One of the most desidered ad still not available features of 64bit os was the Flash-reader plugin. Still on Gentoo-x86_64 it was the default choice to install the 32bit plugin with 32bit precompiled libraries and nspluginwrapper. This sounds not easy and indeed it is, at least conceptually. The major cause of the choice was of course the lack of a 64bit plugin. Maybe some opensource were available, but you know those work correctly on 1 content over 10.<br />
<br />
Adobe released the <a href="http://labs.adobe.com/technologies/flashplayer10/">Adobe Flash Player "Square" on sept 27th</a>, but gentoo portage have already included beta version few months ago. It comes with beta version 10.2, here comes the steps to install it.<br />
<br />
<a name='more'></a>The easiest thing you might do, this time is wrong.<br />
<br />
We need to set first of all the right keywords for the plugin. Let's issue:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -pv adobe-flash</blockquote>You should activate 64bit and deactivate nspluginwrapper and 32bit.<br />
So let's go and edit make.conf<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /etc/make.conf</blockquote>and check not to have 32bit and nspluginwrapper flags<br />
now let's go to package.use and check there too:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /etc/portage/package.use</blockquote>be sure to remove unwanted words and add the 64bit, the line should look:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">www-plugins/adobe-flash 64bit -32bit</blockquote>Now we are ready:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -av adobe-flash</blockquote>Portage should remove the emul-linux libraries and add just the plugin.<br />
To see results you might need a system reboot.<br />
<br />
Cheers!Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-34552668711483468522010-09-28T00:19:00.002+02:002010-09-28T00:24:48.709+02:00Wicd: customizing networks configuration<div class="separator" style="clear: both; text-align: center;"><a href="http://3.bp.blogspot.com/_lqr72cLxjWU/TKEXqNjH-3I/AAAAAAAAACM/WKa5EWZ75V0/s1600/screenshot-20100928@001439.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="257" src="http://3.bp.blogspot.com/_lqr72cLxjWU/TKEXqNjH-3I/AAAAAAAAACM/WKa5EWZ75V0/s320/screenshot-20100928@001439.png" width="320" /></a></div><span style="background-color: #9fc5e8;"></span>Hey,<br />
<br />
As a good Xfce user I know some gnome-kde alternative applications. One of the best of this crew is certainly <a href="http://wicd.sourceforge.net/">Wicd</a>, a Network manager. First of all it handles wired and wireless networks in a cute graphical environment, but most important it works flawlessly with many wireless cards and chipset, has a ndiswrapper support and it is relatevely easy to open a backdoor and create your profile as you need.<br />
<div class="separator" style="clear: both; text-align: center;"></div><br />
I mean if you have a strange wifi setup due to your system admin at work or internet provider at home, or a reserved wifi connection in your university campus, you can create a simple text file to send required parameters to wifi-supplicant wich still does its job.<br />
<a name='more'></a>The starting point of today's tip is the folder where you can find all the encryption protocols files:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">ls /etc/wicd/encryption/templates</blockquote>As you can see there are many files, each named as the protocol that it contains, and a summary file, called <b>active</b>, in which are listed all the active protocols.<br />
<br />
So the next step is to understand what a protocol file contain. Thank God they are plain text, so open it easily as, (for example)<br />
<blockquote><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">geany wep-shared</div></blockquote>let's look at that file: the first part is what we can call a header<br />
<br />
<div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">name = WEP Shared/Restricted</div><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">author = Dan O'Reilly</div><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">version = 1</div><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">require key *Key<br />
----- </div><br />
then it comes the configuration for wpa_supplicant:<br />
<br />
<div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">ctrl_interface=/var/run/wpa_supplicant </div><div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">network={<br />
ssid="$_ESSID"<br />
scan_ssid=$_SCAN<br />
key_mgmt=NONE<br />
auth_alg=SHARED<br />
wep_key0=$_KEY<br />
wep_tx_keyidx=0<br />
priority=5<br />
}</div><br />
It is quite easy to understand how we have to mix our ingredients in this recipe.<br />
<br />
We have <b>keywords</b>, <b>constants</b> and <b>variables</b>.<br />
<br />
<b>Keywords</b> are coming from the wpa_supplicant.conf sintax, you can get lots of examples just with <span style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">man wpa_supplicant.conf</span>: there you should find the keywords that fit your needs, just take care to look the conf for your same network kind.<br />
<br />
<br />
Talking about <b>constants</b> they are very readable here, or the may vary from network to network, that's why we have <b>variables</b>: they are given by the user, or auto-filled with info coming from the network scanning. In the example you can recognize them as they begin with "$_". In your configuration you can require a variable to be filled by the user writing its name in the "required" line of the header.<br />
<br />
So get your network configuration parameters and take a look at them. There should be some sensible data (pw, username): those are the one you want to type into the application GUI, the other can be constants or internal variables.<br />
<br />
In conclusion you can translate the config file structure as follows:<br />
<br />
<div style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">name = <b><i>My custom config name</i></b><br />
author = <b><i>ME!</i></b><br />
version = <b><i>Version#</i></b><br />
require key *Key <i><b>variable *Variable_Name_Displayed_in_GUI</b></i><br />
-----<br />
ctrl_interface=/var/run/wpa_supplicant<br />
network={<br />
ssid=<b>"$_ESSID" <---------- auto filled</b><br />
scan_ssid=$_SCAN <---------- auto filled<br />
key_mgmt=NONE<br />
auth_alg=SHARED<br />
wep_key0=<b>$_KEY <----------filled by the user</b><br />
wep_tx_keyidx=0<br />
priority=5<br />
}</div><br />
Last advices:<br />
<ul><li>In variables displayed names underscore are translated into spaces. Spaces are used just to separate a var from the next ones</li>
<li>Remember to update the "active" summary adding the name of your <u>config file </u>unless it was just some practice and you don't need that configuration :P</li>
<li>Without the required variables set by th user the network config won't be accepted. </li>
<li>Keep your wifi safe ^_^</li>
</ul><br />
<ul></ul>CheersAnonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com0tag:blogger.com,1999:blog-6007641906670981467.post-902880426637378512010-09-25T12:21:00.003+02:002010-09-29T14:24:48.461+02:00MakeMKV UpdatesHere we are,<br />
<br />
as I promised I found some news about MakeMKV. First of all in the "multimedia" gentoo overlay you can find MakeMKV. It sounds to be very easier to install, just few steps, anyway it seems to have not the latest version.<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="http://2.bp.blogspot.com/_lqr72cLxjWU/TJ3MfSBd74I/AAAAAAAAACI/NCGEdBqsFpE/s1600/screenshot-20100925@122314.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://2.bp.blogspot.com/_lqr72cLxjWU/TJ3MfSBd74I/AAAAAAAAACI/NCGEdBqsFpE/s1600/screenshot-20100925@122314.png" /></a></div><br />
Second, if you have troubles trying to view Avatar it seems to have a kind of encryption still not supported. As always those stuff have useless copyrights guards etc... I'll never understand that.<br />
<br />
Third I have a good workaround for testing the program some time more, but please, support those guys and their work!<br />
<br />
<a name='more'></a>Starting from the beginning let's explain how to get the overlay makemkv version.<br />
What you need is the overlay manager, called layman:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -av layman</blockquote>If you want to see the available overlays type<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">layman -L</blockquote>then let's add to the portage tree the multimedia overlay<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">layman -a multimedia</blockquote>Great. The next step is the easiest:<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">emerge -av makemkv</blockquote>Done.<br />
<br />
They claim to have a license purchased for gentoo users. Actually in my box the evaluation timer remains. Please be sure you know what you are doing. <u><b>I'm not responsible for applying that in your system.</b></u> <br />
In Windoze it was the paleolithic age, but here works like a charm. You need the right to set date, this script should not work.<br />
<br />
First of all change your settings and <b><u>do not check for updates on the net</u></b>. Then create a script in your /usr/bin/ called mkvext<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo nano /usr/bin/mkvext</blockquote>then put in it the following code<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">#!/bin/bash<br />
date --set='-1 years'<br />
makemkv &<br />
sleep 3<br />
date --set='+1 years'</blockquote>you can obviously replace "years" with "months" or even "days"<br />
now let's make it executable<br />
<blockquote style="background-color: #9fc5e8; font-family: "Courier New",Courier,monospace;">sudo chmod 777 /usr/bin/mkvext</blockquote>the last step is to change the launcher to make it work, so for <b>Xfce</b> users:<br />
<blockquote style="background-color: #9fc5e8;">sudo nano /usr/share/applications/makemkv-makemkv.desktop </blockquote>and change the following lines:<br />
<blockquote style="background-color: #9fc5e8;"><div style="font-family: "Courier New",Courier,monospace;">Exec=makemkv > Exec=mkvext</div><div style="font-family: "Courier New",Courier,monospace;">TryExec=makemkv > TryExec=mkvext</div></blockquote>save, close, env-update and test<br />
<br />
^_^Anonymoushttp://www.blogger.com/profile/18444487786108961840noreply@blogger.com1