<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>More of a programming nerd than is strictly healthy. See also {nevyn.nu, thirdcog.eu, twitter}</description><title>Overooped</title><generator>Tumblr (3.0; @nevyn)</generator><link>http://overooped.com/</link><item><title>National Consumer Agency of Denmark: iBook Lab Report</title><description>&lt;a href="http://www.forbrug.dk/fileadmin/Filer/PDF/ENGF959-orig.pdf"&gt;National Consumer Agency of Denmark: iBook Lab Report&lt;/a&gt;: &lt;p&gt;Okay, so back in 2006, the consumer agency of Denmark did some research on why the iBook G4’s logic board seems to break after 12-18 months. Turns out it’s almost always the same fault: a ISL 6225CA chip where the pins 1 and 28 are badly solded to the board, which makes the solder crack. This is why clamping or shimming the iBook makes it work, it rejoins the solder temporarily. &lt;a href="http://coreyarnold.org/ibook/"&gt;Several users&lt;/a&gt; &lt;a href="http://coreyarnold.org/ibook/?p=20#comments"&gt;have tried&lt;/a&gt; &lt;a href="http://www.edugames.dse.nl/logicboardrepair/"&gt;to solder&lt;/a&gt; the break or shim the motherboard. Shimming only seems to work for a while, while soldering seems to work great.&lt;/p&gt;

&lt;p&gt;It’s odd that I had such a hard time to find this report, given that it’s by far the most common reason why an iBook G4 breaks.&lt;/p&gt;</description><link>http://overooped.com/post/67847886</link><guid>http://overooped.com/post/67847886</guid><pubDate>Thu, 01 Jan 2009 21:42:00 +0100</pubDate><category>hackbook</category><category>iBook</category></item><item><title>It’s about an hour til’ the next year comes round,...</title><description>&lt;img src="http://25.media.tumblr.com/MLhBbCcsbi62esv6aMgUEeeEo1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;It’s about an hour til’ the next year comes round, so I put the project in a box to work on it later. BUT HEY, why not &lt;a href="http://flickr.com/photos/nevyn/3153890991/in/set-72157611917994727/"&gt;boot it while it’s in the box&lt;/a&gt;? OHYEAH.&lt;/p&gt;</description><link>http://overooped.com/post/67720822</link><guid>http://overooped.com/post/67720822</guid><pubDate>Wed, 31 Dec 2008 22:48:00 +0100</pubDate><category>ibook</category><category>hackbook</category></item><item><title>Okay, still broken, but at least FREE OF ITS PLASTIC PRISON!</title><description>&lt;img src="http://25.media.tumblr.com/MLhBbCcsbi62cnoau9ZazC9Po1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Okay, still broken, but at least &lt;a href="http://flickr.com/photos/nevyn/3154729178/in/set-72157611917994727/"&gt;FREE OF ITS PLASTIC PRISON&lt;/a&gt;!&lt;/p&gt;</description><link>http://overooped.com/post/67720653</link><guid>http://overooped.com/post/67720653</guid><pubDate>Wed, 31 Dec 2008 22:47:00 +0100</pubDate><category>ibook</category><category>hackbook</category></item><item><title>I’m building a wearable computer. Starting with getting...</title><description>&lt;img src="http://26.media.tumblr.com/MLhBbCcsbi62b5dxCiSvbUr9o1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;a href="http://flickr.com/photos/nevyn/sets/72157611917994727/"&gt;I’m building&lt;/a&gt; a &lt;a href="http://faculty.arch.usyd.edu.au/kcdc/journal/vol2/dcnet/sub8/front_wearable.jpg"&gt;wearable computer&lt;/a&gt;. Starting with &lt;a href="http://flickr.com/photos/nevyn/3153890563/in/set-72157611917994727/"&gt;getting this old iBook working&lt;/a&gt;. Ohyeah.&lt;/p&gt;</description><link>http://overooped.com/post/67720563</link><guid>http://overooped.com/post/67720563</guid><pubDate>Wed, 31 Dec 2008 22:45:00 +0100</pubDate><category>ibook</category><category>hackbook</category></item><item><title>Broken iBook. Anyone know what this could be?

Update: I’m...</title><description>&lt;img src="http://30.media.tumblr.com/MLhBbCcsb693gua6mM8BQNxk_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Broken iBook. Anyone know what this could be?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Update:&lt;/em&gt; I’m pretty sure it’s a broken graphics card. In the kernel panic crash report, the graphics driver is always in the call stack.&lt;/p&gt;</description><link>http://overooped.com/post/28128765</link><guid>http://overooped.com/post/28128765</guid><pubDate>Thu, 06 Mar 2008 17:45:00 +0100</pubDate><category>ibook</category><category>hackbook</category></item></channel></rss>
