<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://townx.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>townx - Some basic hardware testing on Linux - Comments</title>
 <link>http://townx.org/blog/elliot/some-basic-hardware-testing-linux</link>
 <description>Comments for &quot;Some basic hardware testing on Linux&quot;</description>
 <language>en</language>
<item>
 <title>agree</title>
 <link>http://townx.org/blog/elliot/some-basic-hardware-testing-linux#comment-40164</link>
 <description>&lt;p&gt;i&#039;m playing with all my hardware all the time too! I&#039;m obsessed&lt;/p&gt;</description>
 <pubDate>Wed, 09 Dec 2009 08:20:36 -0600</pubDate>
 <dc:creator>ubieranki</dc:creator>
 <guid isPermaLink="false">comment 40164 at http://townx.org</guid>
</item>
<item>
 <title>I gotta say, linux sounds</title>
 <link>http://townx.org/blog/elliot/some-basic-hardware-testing-linux#comment-39655</link>
 <description>&lt;p&gt;I gotta say, linux sounds great. All the things you can do on it... but then I remember how difficult to use it was when I had to use it in my university. Takes way too much effort to use..&lt;/p&gt;</description>
 <pubDate>Mon, 22 Jun 2009 05:09:56 -0500</pubDate>
 <dc:creator>Kolorowanki</dc:creator>
 <guid isPermaLink="false">comment 39655 at http://townx.org</guid>
</item>
<item>
 <title>Long Way To Go</title>
 <link>http://townx.org/blog/elliot/some-basic-hardware-testing-linux#comment-39626</link>
 <description>&lt;p&gt;Seems like I must start doing things like this right now. Thanks for sharing your own tip.&lt;/p&gt;</description>
 <pubDate>Mon, 15 Jun 2009 03:23:13 -0500</pubDate>
 <dc:creator>Simon Wilby</dc:creator>
 <guid isPermaLink="false">comment 39626 at http://townx.org</guid>
</item>
<item>
 <title>Playing with all my hardware</title>
 <link>http://townx.org/blog/elliot/some-basic-hardware-testing-linux#comment-39580</link>
 <description>&lt;p&gt;Playing with all my hardware is the only thing which I am doing in these days and thanks for sharing your post. I downloaded Backtrack3, Fedora, and &lt;span class=&quot;caps&quot;&gt;SUSE &lt;/span&gt;fir multiple purposes. So I am just testing them via their live cds to determine that which is the best solution for me. Actually I am trying to crack some &lt;span class=&quot;caps&quot;&gt;WPA&lt;/span&gt;-PSK key just for testing in these days and it is the most difficult one for me till now. &lt;/p&gt;</description>
 <pubDate>Sun, 07 Jun 2009 07:00:44 -0500</pubDate>
 <dc:creator>Deniel | cheap web hosting</dc:creator>
 <guid isPermaLink="false">comment 39580 at http://townx.org</guid>
</item>
<item>
 <title>Some basic hardware testing on Linux</title>
 <link>http://townx.org/blog/elliot/some-basic-hardware-testing-linux</link>
 <description>&lt;p&gt;I&#039;ve got a slightly unstable computer at the moment which I&#039;ve been trying to diagnose. Still haven&#039;t worked out exactly what&#039;s wrong (it freezes randomly in both Windows and Linux), but I have found some useful testing tools on the way (for Ubuntu Intrepid Ibex unless otherwise stated).&lt;/p&gt;

&lt;h2&gt;Memory&lt;/h2&gt;

&lt;p&gt;Recent Ubuntu Linux distros include MemTest86+, a memory testing tool. You just select this option from the grub boot menu when your computer starts and it boots into a dedicated memory testing &lt;span class=&quot;caps&quot;&gt;OS.&lt;/span&gt; The tests are fairly simple to get going, but taking hours, literally. You need to run them overnight.&lt;/p&gt;

&lt;h2&gt;Hard disks&lt;/h2&gt;

&lt;p&gt;The smartmontools package includes some testing tools for hard disks which have &lt;span class=&quot;caps&quot;&gt;S.M.A.R.T. &lt;/span&gt;capability (most modern motherboards and hard disks support this). Once you&#039;ve installed the package, you can use the &lt;strong&gt;smartctl&lt;/strong&gt; command line tool to run diagnostics on your hard disks.&lt;/p&gt;

&lt;p&gt;I used this tool like this:&lt;/p&gt;



&lt;pre&gt;
$ sudo smartctl -t long /dev/sda
&lt;/pre&gt;



&lt;p&gt;This starts the test, which will take a fair amount of time (mine took around 30 minutes for a 40Gb disk). Once it&#039;s finished, you can do:&lt;/p&gt;



&lt;pre&gt;
$ sudo smartctl -H /dev/sda
&lt;/pre&gt;



&lt;p&gt;to see the results. Mine looked like this:&lt;/p&gt;



&lt;pre&gt;
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is &lt;a href=&quot;http://smartmontools.sourceforge.net/&quot; title=&quot;http://smartmontools.sourceforge.net/&quot;&gt;http://smartmontools.sourceforge.net/&lt;/a&gt;

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
&lt;/pre&gt;



&lt;h2&gt;&lt;span class=&quot;caps&quot;&gt;CPU&lt;/span&gt;&lt;/h2&gt;

&lt;p&gt;A simple test to max out your &lt;span class=&quot;caps&quot;&gt;CPU &lt;/span&gt;(and exercise your graphics card) is to run &lt;span class=&quot;caps&quot;&gt;GLX &lt;/span&gt;gears:&lt;/p&gt;



&lt;pre&gt;
$ glxgears -info
&lt;/pre&gt;



&lt;p&gt;However, that doesn&#039;t really stress your system. For that, I used a tool called &lt;a href=&quot;http://users.bigpond.net.au/CPUburn/&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CPU&lt;/span&gt; Burn-in&lt;/a&gt;. This is ostensibly an overclockers tool, but what it does is attempt to push your &lt;span class=&quot;caps&quot;&gt;CPU &lt;/span&gt;to maximum operating temperature so you can see whether it&#039;s stable. It&#039;s a binary download, so it&#039;s very easy to use, and has a &lt;a href=&quot;http://users.bigpond.net.au/CPUburn/downloads/cpuburn-in.tar.gz&quot;&gt;Linux version&lt;/a&gt;. Unzip it, cd to the directory, and run:&lt;/p&gt;



&lt;pre&gt;
./cpuburn-in 10
&lt;/pre&gt;



&lt;p&gt;where 10 is the number of minutes you want to run the tests for. This one scared me a bit, as I watched the temperature of my &lt;span class=&quot;caps&quot;&gt;CPU &lt;/span&gt;and system slowly climb. Read the caveats and warnings on the web site before running this tool.&lt;/p&gt;

&lt;h2&gt;Monitoring&lt;/h2&gt;

&lt;p&gt;While you&#039;re doing all this, you want to watch the system temperature etc. For this, you can use the xsensors tool. This is a simple apt-get on Ubuntu, but for some reason the default config. file is in the wrong place (it&#039;s called /etc/sensors3.conf but the app. is expecting /etc/sensors.conf). You can tell it where the config. file is using the -c switch, e.g.&lt;/p&gt;



&lt;pre&gt;
./xsensors -c /etc/sensors3.conf
&lt;/pre&gt;



&lt;p&gt;This displays a graphical readout of various system temperatures, fan speeds etc..&lt;/p&gt;

&lt;p&gt;You can also watch various aspects of system usage by adding the hardware monitor applet to your panel (right-click on the panel and select Hardware Monitor). This lets you watch how much your &lt;span class=&quot;caps&quot;&gt;CPU, &lt;/span&gt;memory, disks etc. are being utilised.&lt;/p&gt;</description>
 <comments>http://townx.org/blog/elliot/some-basic-hardware-testing-linux#comments</comments>
 <category domain="http://townx.org/tech">tech</category>
 <pubDate>Thu, 04 Jun 2009 14:22:46 -0500</pubDate>
 <dc:creator>elliot</dc:creator>
 <guid isPermaLink="false">775 at http://townx.org</guid>
</item>
</channel>
</rss>
