<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title type="html">Bitwise.org</title>
<link rel="alternate" type="text/html" href="http://www.bitwise.org"/>
<link rel="self" type="application/atom+xml" href="http://www.bitwise.org/atom.xml"/>
<updated>2007-11-15T14:36:12+11:00</updated>
<author>
<name>Mark Chandler</name>
<uri>http://www.bitwise.org</uri>
</author>
<id>http://www.bitwise.org/</id>
<generator uri="http://nanoblogger.sourceforge.net" version="3.3 RC5">
NanoBlogger
</generator>

<entry>
<title type="html">Fedora 8</title>
<author>
<name>mcl</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2007/09/#e2007-09-08T15_22_47.txt"/>
<id>http://www.bitwise.org/archives/2007/09/#e2007-09-08T15_22_47.txt</id>
<published>2007-09-08T15:22:47+11:00</published>
<updated>2007-09-08T15:22:47+11:00</updated>

<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">

<p>Fedora "Werewolf" 8 is a good release. I've been running it on my Pioneer laptop since Test 1 and I think it's enough of an advance to be worthy of a new version number. I much prefer the new theme to the F7 theme - it has the cool clean but still attractive look that I like in Gnome. </p>

I still need to have another play with it, but the Online Desktop feature looks interesting.<br>
<br>
Rhythmbox *finally* hit version 0.11 and includes the cross-fading feature that allows tracks to play without a gap between them. Essential stuff for mixed albums.<br>
<br>
Gnash 0.8.1 is available from the standard repository and provides damn good support for most Flash-based content.<br>

<p>The X1600 graphics card in the laptop isn't supported for its native resolution of 1280x800, but I can get the Free RadeonHD driver which compiles and works very nicely. Last I heard from <a href="http://www.phoronix.com/scan.php?page=article&item=887">Phoronix</a>, there was a problem with the ATI driver and 2.6.23 kernels, so no Desktop Effects for me anytime soon it seems. Hopefully the RadeonHD crew will build in 3D and AIGLX support before the 8.43 ATI driver is released, so I'm not tempted to add any closed source junk to my build. I think that's asking a lot, though. ;-) </p>

<p>Another hardware feature that I'm looking to have supported soon is the Atheros Wireless card. Currently, the ath5k drivers, in the 2.6.23 kernel, recognise the card and its capabilites. Unfortunately, trying to scan for APs or trying any other configuration typically results in a lock-up. I've blacklisted the driver for now and am using the Madwifi drivers from ATrpms until the fully Free drivers work properly. <br>

I'll probably migrate my desktop to F8 this weekend using the two old SATA disks that were my F6 install. Once I'm happy that it's solid, I'll push it onto the 250GB disks that I'm using now for F7. </p>
</div>
</content>

</entry>
<entry>
<title type="html">Migration to Fedora 7</title>
<author>
<name>mcl</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2007/06/#e2007-06-25T00_24_14.txt"/>
<id>http://www.bitwise.org/archives/2007/06/#e2007-06-25T00_24_14.txt</id>
<published>2007-06-25T00:24:14+11:00</published>
<updated>2007-06-25T00:24:14+11:00</updated>

<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
I've moved on again to the latest edition of Fedora on my home workstation. I took the cowards' way out and bought new hardware to do it. Actually, that was kind of cool too: the disks are two 250GB Seagate SATA (ST3250310AS) drives that only seem to have one platter, so they're unusually light. I'm guessing that this is the new vertical stacking of magnetic signals that I'd read about in Slashdot a while ago.</p>
<p>
I installed the drives and booted up from the install disk for x86_64. There was a problem with video, so I swapped to the text only mode. This is where I found that you can't create RAID arrays (or was it logical volumes?) in the textual installer. Frustrated, I switched back to the graphical install but unplugged the 2nd of my two monitors in the hope that that was where the problem lay .Fortuately, it was.</p>
<p>
The rest of the install was fine, and I'm very happy to happy to have Firefox & Thunderbird 2.0 now. I overlaid a backup of my home directory on top of the new one, and have pretty much everything back the way I want.</p>
<p>
One weird thing was that the sound configuration went out of whack. Having a webcam with audio capabilities seemed to confuse the configuration. I ended up with two entries in my modules.conf for different sound devices, but having the same index. I went looking in there after I'd read some <a href="http://www.fedoraforum.org">Fedora Forum</a> articles about similar problems. Changing them to different indexes fixed the problem.</p>
</div>
</content>

</entry>
<entry>
<title type="html">YouTube working with Gnash</title>
<author>
<name>mcl</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2007/06/#e2007-06-09T14_33_09.txt"/>
<id>http://www.bitwise.org/archives/2007/06/#e2007-06-09T14_33_09.txt</id>
<published>2007-06-09T14:33:09+11:00</published>
<updated>2007-06-09T14:33:09+11:00</updated>

<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
I grabbed the latest copy of <a href="http://www.gnu.org/software/gnash/">Gnash</a> from CVS today, compiled it on my workstation, and installed it. To my surprise, it allowed me to use <a href="http://www.youtube.com">YouTube</a> almost perfectly. Also, Flash content from the <a href="http://www.illwillpress.com">Dread Squirrel Foamy</a> now seems to work much better. I was having sound sync issues with it before.
</p>
<p>
My workstation spec is still Fedora Core 6 x86_64 and I'm running Gnash as a plugin for Firefox 1.5.0.12.
</p>
</div>
</content>

</entry>
<entry>
<title type="html">OpenMoko First Steps</title>
<author>
<name>mcl</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2007/03/#e2007-03-24T15_19_47.txt"/>
<id>http://www.bitwise.org/archives/2007/03/#e2007-03-24T15_19_47.txt</id>
<published>2007-03-24T15:19:47+11:00</published>
<updated>2007-03-24T15:19:47+11:00</updated>
<category term="OpenMoko" />
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
I've followed the instructions from <a href="http://www.openmoko.org">OpenMoko</a> and <a href="http://www.openembedded.org">OpenEmbedded</a> for setting up the environment on FC6.
</p>
<p>
I've had to get "quilt" and "texi2html", but I still can't see a native FC6 version of Psycho, so I guess my makes will take a while until I get that sorted out. Hopefully the first cut is the deepest, and susequent makes will be paper-cuts.</p><p>
Running the OpenMokoMake takes a loooong time. In that time, I looked at what's involved with creating a new package. It seems as though creating a new BitBake recipe is what's required.</p>
<p> Well the make died, but fortunately a quick Google revealed that the problem has a bug report already. As I'm using an x86_64 system, I suffered <a href="http://bugs.openembedded.org/show_bug.cgi?id=1765">Bug 1765</a>. So I did what I was told from the <a href="http://lists.openmoko.org/pipermail/openmoko-devel/2007-February/000506.html">list archive</a> and went on my merry way</p>
</div>
</content>

</entry>
<entry>
<title type="html">Rhythmbox 0.9.7 for FC6</title>
<author>
<name>mcl</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2006/12/#e2006-12-28T18_27_15.txt"/>
<id>http://www.bitwise.org/archives/2006/12/#e2006-12-28T18_27_15.txt</id>
<published>2006-12-28T18:27:15+11:00</published>
<updated>2006-12-28T18:27:15+11:00</updated>
<category term="Fedora" />
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>After waiting around for the URL redirect bug in Rhythmbox to get fixed in FC6, I decided to see what the problem was. After some investigation, I found that it had been fixed in 0.9.6 (FC6 uses 0.9.5 at time of writing). I had a look to see if an update was in testing, but I couldn't see anything. I saw that there was a 0.9.7 for FC7, but didn't want to go playing in that area. So, I decided to create my own package.</p>
<p>I took the src.rpm from FC6, updated the source with the vanilla tarball from Gnome and had a go. I had some issues with libgpod being < 0.4 and old Gnome dekstop integration stuff being dropped in 0.9.6 & 0.9.7.</p>
<p>Eventually, I made these: <br>
<a href="http://www.bitwise.org/rpms/rhythmbox-0.9.7-1.fc6.bw.x86_64.rpm">Rhythmbox-0.9.7</a><br>
<a href="http://www.bitwise.org/rpms/rhythmbox-bw.spec">Rhythmbox spec file (Bitwise)</a>
</p>
<p>
WARNING: I've disabled iPod support because of dependency problems.<br>
WARNING: I'm not an expert at this; use at your own risk.<br>
</p>
<p>Contact me at mcl if you have any comment.</p>
</div>
</content>

</entry>
<entry>
<title type="html">Blogging Tool</title>
<author>
<name>mef</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2006/12/#e2006-12-26T17_07_01.txt"/>
<id>http://www.bitwise.org/archives/2006/12/#e2006-12-26T17_07_01.txt</id>
<published>2006-12-26T17:07:01+11:00</published>
<updated>2006-12-26T17:07:01+11:00</updated>

<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
I have a LiveJournal account for personal blogging. I've let it go stale as I was finding it tedious to update through the web-client and I didn't like the idea of downloading software onto my machine to update it. Browsing through the Fedora packages list, I found a few tools for updating blogs from the desktop. First I found BloGTK, then Gnome-Blogger, and finally Drivel. I've settled on Drivel as it provides good keyboard controlled access to the LiveJournal features.
</div>
</content>

</entry>
<entry>
<title type="html">Same module, different options</title>
<author>
<name>mef</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2006/12/#e2006-12-24T16_13_19.txt"/>
<id>http://www.bitwise.org/archives/2006/12/#e2006-12-24T16_13_19.txt</id>
<published>2006-12-24T16:13:19+11:00</published>
<updated>2006-12-24T16:13:19+11:00</updated>

<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>I finally figured out how to get two TV tuner cards working in my Myth box. This might seem really obvious at first, but when one card isn't working properly, it becomes a litle more complicated.</p>
<p>
Basically the fix is this: add the option parameter to the modules.conf, or in this case the cx88xx file in the modules.d directory. It looks like the following</p>
# DV1000T, then Fusion <br>
options cx88xx card=35,15 <br>
<p>I have to do it this way, because the Fusion card isn't recognised. It doesn't seem to have a sub-PCI-id burned onto the card.</p>
<p>The fix is simple and kinda obvious when you look at how network cards deal with different options (speed, duplex, etc.) for the same module. But there really was nothing I found that just said it could be done for any module. I'm still not really sure that it can, but it would make sense if modules followed a template that allowed this behaviour.</p>
<p>Anyway, I hope this helps somebody out there with a similar problem.</p>
</div>
</content>

</entry>
<entry>
<title type="html">Fedora Core 6</title>
<author>
<name>mef</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2006/12/#e2006-12-11T18_50_53.txt"/>
<id>http://www.bitwise.org/archives/2006/12/#e2006-12-11T18_50_53.txt</id>
<published>2006-12-11T18:50:53+11:00</published>
<updated>2006-12-11T18:50:53+11:00</updated>
<category term="Linux" />
<category term="Fedora" />
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>It's that time of year again - another Fedora release means that I have to look at upgrading and/or re-installing my systems to the new release. My impression is that as soon as a new release is done, support tends to move onto it straight-away. So, there's not much point in hanging around on the old and busted version.</p>

<p>This time around, I really didn't feel like re-installing my main workstationfrom scratch. I'd had good success upgrading my work laptop from FC5 to FC6 using an update install, but it didn't translate to the workstation. I downloaded the DVD iso from the iiNet mirror and created an install DVD, but the update part of the install failed to recognise the existing installation. As I'd ignored the built-in fake-RAID controller and used software RAID instead, the installer became confused when it saw the disks. It didn't see the sRAID and LVM disks.</p>

<p>Still not wanting to do a scratch install, I opted for the YUM update method.This is pretty much problem-free, but leaves the system a little rough around the edges. I had to remove some packages that had 64 and 32-bit versions as it was causing problems with dependecy resolution. Post-upgrade, I've still had do things like remove OpenOffice.org and reinstall it. Pupplet doesn't seem to work properly and sound had to be played with so that ALSA knew the difference between the mic on my USB webcam, and the C8KS sound device.</p>

<p>I'm pretty happy with the result, but I may get the urge to buy two new disks and recreate the install from scratch. I'm pretty cautious about messing with my personal data, so I like to leave the data on the disks completely alone if possible. I might just wait until FC7 comes out :) </p>
</div>
</content>

</entry>
<entry>
<title type="html">Disk failure</title>
<author>
<name>mef</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2006/12/#e2006-12-11T00_44_39.txt"/>
<id>http://www.bitwise.org/archives/2006/12/#e2006-12-11T00_44_39.txt</id>
<published>2006-12-11T00:44:39+11:00</published>
<updated>2006-12-11T00:44:39+11:00</updated>

<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">

<p>
It happens to the best of us... The 40GB disk I have in the Ultra 10 decided to have a bad day, and took the server with it. I was fortunate in that the data were recoverable. I was able to re-install OpenBSD 3.6 on one of the original 4GB disks, and migrate the data over. I started with the mail server, as I needed it for some important emails coming to the bitwise.org accounts. I've only now gotten around to migrating the web-server files.</p>
<p>
</div>
</content>

</entry>
<entry>
<title type="html">iPod surgery</title>
<author>
<name>mef</name>
</author>
<link rel="alternate" type="text/html" href="http://www.bitwise.org/archives/2006/10/#e2006-10-29T19_22_00.txt"/>
<id>http://www.bitwise.org/archives/2006/10/#e2006-10-29T19_22_00.txt</id>
<published>2006-10-29T19:22:00+11:00</published>
<updated>2006-10-29T19:22:00+11:00</updated>

<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
So, my last entry talked about the gorgeous new Acer AL2216W that my girl got me for my birthday. That was some serious brownie points racked up with that gift. I had get the balance back... but how?!<br>
<br>
Fortune smiled on me, and made a Sad Mac face at her when her iPod died. She turned it on last week and it did the Sad Mac face, which is what happens when something serious has gone wrong. She tried the basic reset procedures and got nada. Following the Apple website instructions, her next step was to lodge a support request with Apple. Apple's next step was to quote a knob-tastic AU$388 to fix he iPod. This is made even more outrageous by the fact that a new 30GB iPod (her's is a 20GB) is cheaper than that (about AU$380). <br>
<br>
Being rather pissed at Apple, she started looking at <em>other</em> DAPs to get as a replacement for the (now) iPuc. I figured that as long as she wasn't going to get it fixed that there wasn't much to lose in having a go at fixing it.<br>
<br>
Some Googling found me instructions on how to open up the iPod case. There's very little in the way of a seam, but a thin bladed dinner knife got me in. There are spots that you can prise into, and spots that you can't. Probe around if you're doing this yourself.<br>
<br>
Inside, the iPod is basically three parts: the front panel, the control circuitry on the back panel, and the hard disk. It was almost immediately obvious that the flat cable that connects the control circuitry to the hard disk was slightly pulled out from hard disk. I pushed this home and started the iPod. After a few seconds the iPod started normally.<br>
<br>
I concluded two things from this exercise: I was back on even standing in the brownie points arena; and, considering how easy some fixes must be for iPods, Apple have a shocking policy on repairs.
</div>
</content>

</entry>

</feed>
