<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>Thomas Lynema&#039;s Weblog &#187; hardware</title> <atom:link href="http://lynema.org/tag/hardware/feed" rel="self" type="application/rss+xml" /><link>http://lynema.org</link> <description>Discover Goal, Work/Play, Achieve Goal, Repeat</description> <lastBuildDate>Sat, 17 Dec 2011 18:10:23 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3</generator> <item><title>Adventures in Motherboard Failure</title><link>http://lynema.org/2009/05/28/adventures-in-motherboard-failure</link> <comments>http://lynema.org/2009/05/28/adventures-in-motherboard-failure#comments</comments> <pubDate>Thu, 28 May 2009 22:47:06 +0000</pubDate> <dc:creator>lyz</dc:creator> <category><![CDATA[Tech]]></category> <category><![CDATA[hardware]]></category><guid
isPermaLink="false">http://lynema.org/?p=163</guid> <description><![CDATA[The last piece of hardware that I expect a failure from is the motherboard.  There are no moving pieces, not much wear and tear.  Plus, I spent $250 on the last board.  It was an AW9D-MAX; top of the line when it was purchased.  I would expect it to last more than 2 1/2 years [...]]]></description> <content:encoded><![CDATA[<p>The last piece of hardware that I expect a failure from is the motherboard.  There are no moving pieces, not much wear and tear.  Plus, I spent $250 on the last board.  It was an AW9D-MAX; top of the line when it was purchased.  I would expect it to last more than 2 1/2 years of off and on use.   Now that you already know what went wrong, I&#8217;ll lay out the troubleshooting that finally lead me to this conclusion.  Motherboard issues are extremely hard to diagnose.</p><p>My computer began power cycling itself for seemingly no reason about a month ago.   The times it would occur were inconsistent.  I could narrow it down to times when the system was under a lot of stress.   Kernel compilation combined with watching a flash video would take the system down within 2 minutes.  I also noticed that the crashes weren&#8217;t always the same; sometimes I would catch a glimpse of a kernel panic when on the console.</p><p>Instability is an awful thing.  It prompted me into action quickly.  The first things that were changed out were the processor and the video card.  They were recent purchases, changes I was going to do anyway.  The issue still persisted.</p><p>At this point, I went off the path.  Every kernel or BIOS feature that could cause instability was checked.  I went though 10 different kernel setups, flashing the BIOS, and resetting the BIOS to factory defaults.  In a final attempt to convice myself that this was not an OS issue, I reproduced the problem on a live CD.</p><p>Memory can go bad at times.  I proved this was not the case by two methods, switching out DIMMs and running memtest86+.  The problem wasn&#8217;t the memory modules.</p><p>There were only two options left.  The power supply and the motherboard.  At this point, all hope of a painless fix were lost.  It was time to spend some hard earned money.</p><p>I started by replacing the power supply.  I have had power supply issues before that had caused flakiness.  When a system is under load, a poor power supply (or one with insufficient wattage) will no longer be able to power the components of the system.  I decided that getting a modular, 80+ efficiency power supply would be worth it even if it wasn&#8217;t the issue.   I am now the proud owner of an Enermax EMD625AWT power supply.</p><p>The Enermax power supply is great.  The fan doesn&#8217;t spin up unless the power usage is high, so it stays nice and quiet.  After reading a bunch of reviews on it, I am totally convinced that I made the right call on purchasing it.  However, it was not the problem.</p><p>The problem was the motherboard.  It had to be, there was nothing else.  That story is for another blog post.</p> ]]></content:encoded> <wfw:commentRss>http://lynema.org/2009/05/28/adventures-in-motherboard-failure/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to Turn on Your Arcade Remotely</title><link>http://lynema.org/2008/06/09/how-to-turn-on-your-arcade-remotely</link> <comments>http://lynema.org/2008/06/09/how-to-turn-on-your-arcade-remotely#comments</comments> <pubDate>Mon, 09 Jun 2008 21:27:23 +0000</pubDate> <dc:creator>lyz</dc:creator> <category><![CDATA[Tech]]></category> <category><![CDATA[arcade]]></category> <category><![CDATA[hardware]]></category><guid
isPermaLink="false">http://lynema.com/?p=123</guid> <description><![CDATA[As you probably do not know, I am the proud owner of a Tech Romancer cabinet.  The cabinet&#8217;s life as a one trick pony ended shortly after the purchase, and it is now a very capable mame box. There is one large issue with having a computer inside of a large, wooden box.  Where&#8217;s the [...]]]></description> <content:encoded><![CDATA[<p>As you probably do not know, I am the proud owner of a Tech Romancer cabinet.  The cabinet&#8217;s life as a one trick pony ended shortly after the purchase, and it is now a very capable mame box.</p><p>There is one large issue with having a computer inside of a large, wooden box.  Where&#8217;s the power button supposed to go?  The easy solution is to run cables off of the current power switch to some other button that is placed in a more convenient location.  This approach was considered, but I didn&#8217;t like it.  I thought that remote control was the way to go with this.</p><p>Looking back, this may have been a just for fun decision.  Although, running wires and modding the computer would have been more work.  The main driver was that the computer could not easily be removed once the button was in place.  Also, the location to put button wasn&#8217;t obvious.</p><p>It is a little known fact that there are some always on power coming from the computer&#8217;s power supply.  IMon takes advantage of this and created products such as the Imon Inside.  This gives the ability to receive remote signals even when the computer is in a powered down state.  Once the motherboard&#8217;s power button is rerouted to the Imon Inside, the computer can power itself on remotely.  How cool is that?</p><p>Unfortunately, this is not the end of the story.  The Imon device operates via infra red signals.  These don&#8217;t travel through 1/2&#8243; of wood well.  My initial tests worked great when the computer was out in the open, but not when placed inside of the cabinet.</p><p>There is a solution to this problem too.  I honestly didn&#8217;t think I&#8217;d find a cooler product than the Imon, but I was happily mistaken thanks to the Next Generation Remote Control Extender. It turns out that they make an RF transmitter that poses as a AAA battery.  By replacing one of the batteries with an RF transmitter and putting the RF receiver in the cabinet by the infrared receiver, the signal was remote was now able to push commands through the cabinet.</p><p>Success was finally mine.</p><p>Materials</p><p>Imon Inside ~ $60  Purchased at Newegg<br
/> Next Generation Remote Control Extender ~ $33 Purchased at Amazon</p> ]]></content:encoded> <wfw:commentRss>http://lynema.org/2008/06/09/how-to-turn-on-your-arcade-remotely/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: basic (User agent is rejected)
Database Caching 8/17 queries in 0.005 seconds using disk: basic

Served from: lynema.org @ 2012-02-04 10:52:08 -->
